| commit | e2f39dc254ee61280602986b3abc0d06fc314477 | [log] [tgz] |
|---|---|---|
| author | Adam Sadovsky <asadovsky@gmail.com> | Thu Jan 14 14:37:18 2016 -0800 |
| committer | Adam Sadovsky <asadovsky@gmail.com> | Thu Jan 14 14:37:19 2016 -0800 |
| tree | 912a0d0ebaf0d81b9e0dfa3417c0b8840685d530 | |
| parent | 65b83cb68a4639f49e5ba5fbe1f7b9c1d68c789b [diff] |
browser: gosh: address TODOs
More specifically:
- Eliminates Shell.Main, since it's easy enough to use
Shell.Fn and set the returned Cmd's Args
- Renames Shell.Fn to Shell.FuncCmd
- Extends Shell.{Cmd,FuncCmd} comments to explain what's
done with the given arguments
- Makes it so NewShell takes a snapshot of os.Environ() and
uses that henceforth
- Makes it so NewShell filters out any gosh env vars coming
from outside
- Renames registry.go's Fn to Func, Register to
RegisterFunc, and Call to CallFunc
- Adjusts the behavior of RegisterFunc so that names are
augmented to produce collision-resistant handles of the
form "file:line:name"
- Makes callFunc and Func.call private for now, until
there's a clear need for them to be exported
- Eliminates gosh.Run
- Renames Cmd.Shutdown (which we decided to keep) to
Cmd.Terminate
- Changes Cmd.Signal and Cmd.Terminate to fail if Wait
has been called
- Drops Cmd.Kill; if it proves necessary, we'll add a
gosh.Kill implementation of os.Signal that tells
Cmd.Signal and Cmd.Terminate to issue Process.Kill
Also, updates v23test:
- Same changes as in gosh (Fn->FuncCmd, no more Main)
- Replaces v23test.Run with TestMain (simple case) and
InitTestMain (advanced case)
- Eliminates the hack with credentials env vars
MultiPart: 5/8
Change-Id: Iea100c6bf34cc7de1a367423cbdc09c25051df0f
The namespace browser is a web application that lets developers and other users view and interact with the Vanadium world. Starting from their namespace root or other mount table, users can browse through the mount table hierarchy and see where services are mounted. The user can select a service to see more detailed information about it, and can also interact with the service, invoking methods to examine or modify the state of the service.
As a Vanadium web application, the Namespace Browser requires that users install the Vanadium Extension from the Chrome Web Store. If you try to run the web app without the extension, it will prompt you to install it.
Here is the link to the Vanadium Extension: https://chrome.google.com/webstore/detail/vanadium-extension/jcaelnibllfoobpedofhlaobfcoknpap
The Vanadium Namespace Browser lives online at https://browser.v.io/
You do not need to build your own copy of the namespace browser in order to use it, unless you want to modify it or see how it works.
To build a local copy, install the Vanadium environment and be sure to include the web profile.
Next, to build your own copy of the namespace browser, run:
cd $JIRI_ROOT/release/projects/browser make build
This compiles the relevant bundle files in the ‘public’ folder. The assets inside must be served as your own instance of the web app.
You can serve a local instance of the Namespace Browser by executing the following command:
make start
Navigate to http://localhost:9001 to launch the namespace browser. You can quit by using CTRL-C on the console running make start.
If you have any problems after updating the code, try cleaning the build.
make clean
make start
The namespace browser has some unit and integration tests that verify basic functionality. Run these tests with the following command:
make test
The code repository for the Namespace Browser is on GitHub.
Bugs and other issues can be submitted to the Namespace Browser Issue Tracker.