Install plugin via custom installer
For first time install, we suggest you download whole update site include XULRunner plugins:
- Windows 32 bit
- Linux 32 bit
- Linux 64 bit
- Mac OS X 32 bit
- Windows 64 bit
- (These files are stored in different web site)
- Read this notice if you get error message, especially for Windows x64 with Eclipse 4.3.x
After Mozilla plugin installed, you can download the latest plugin file and copy it to $ECLIPSE_HOME\dropins folder once new version released.
If you want to uninstall the plugin, just remove the copied file/folders.
Install plugin via update site
The typical procedures are:
- Update site: http://bravo30.heliohost.org/update or http://bravo2.000webhostapp.com/update
- Step by step procedures
Procedures for install this plugin manually
- Download Mozilla XULRunner with Java XPCOM enable
(The installation steps can be found in release note
(If you only want to use it in Eclipse, please do these steps and no need to install it)
- Download plugins file "com.beck.ep.wtool_2.6.2.jar"
- Copy the file to $ECLIPSE_HOME/dropins
- Ensure you already install required plugins, include webtools/GEF/EMF, Java XPCOM library and Mozilla Rhino library
- The plugin will detect/modify this setting and ask you whether to restart Eclipse when plugin active.
If you prefer to do it manually, modify $ECLIPSE_HOME\configuration\config.ini, add one line
Once the installation complete, you can open the HTML Visual view via "Windows"-> "Show view"-> "Other...". Then open jsp/htm file with your prefer editor, this view could detect active editor automatic.
Another choose is open jsp/htm. To edit .jsp file using this plugin, right click on the file and select "Open With" -> "Bravo JSP Editor"
You can also change the default editor setting, so you don't have to do this when open a file.
If you get an error after upgrade to new version, follow these step may fix the error
- Open command line windows
- Go to eclipse home folder
- Execute "eclipse -clean"
Some settings are config by project, click here for more info, following settings are shared in workspace.
- Editor preference
- CSS style of rendered element
- JSP Taglib render: The JSP Taglib will be rendered to HTML element and display in visual part of this editor. Basic config and tag handler config could define how custom taglib be rendered.