| commit | 0ce3a7fa982f06826858d3ae399a493cfa4a5f66 | [log] [tgz] |
|---|---|---|
| author | Todd Wang <toddw@google.com> | Mon Nov 30 12:30:51 2015 -0800 |
| committer | Todd Wang <toddw@google.com> | Mon Nov 30 12:30:51 2015 -0800 |
| tree | 78187839d4aa5b6085ccbc14cb360a6ff995d92d | |
| parent | 7a75eaad93df6eeafbb699e8fcd99433ae827581 [diff] |
browser: Remove the -builtin_vdlroot flag. The vdl tool needs access to its standard packages when compiling and generating code. It can either find the packages under VDLROOT/JIRI_ROOT, or it can use the packages built-in to the tool itself. The previous behavior was that if -builtin_vdlroot=false (the default), we'd always look under VDLROOT or JIRI_ROOT. The new behavior gets rid of the flag, and changes the behavior as if it were set to true. If VDLROOT or JIRI_ROOT are set, we always use that value, otherwise we extract the built-in vdlroot to a temporary directory. The previous behavior was to write out the data as a base64/gzipped/tarball with line breaks. The new behavior writes out a gzipped/tarball as raw binary data, without line breaks. This is simpler; there's no need for the base64 encoding. The previous behavior only included *.vdl files in the tarball; we also need to include vdl.config files, since they affect code generation for dependant packages. Added an explicit test to make sure the builtin vdlroot data contains exactly what we expect; the net result is similar to the go-generate test (which reminds us when we've forgotten to run go-generate), but is a bit more localized. MultiPart: 6/6 Change-Id: I2c8c5e4b80aa5f81c7803d73ced548ff76fdb07e
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.