JavaVi - vi/vim editor clone nbvi
Brought to you by:
err
Menu
▾
▴
Tree [473f58] default Rel_1_0_0_beta3 / History
| File | Date | Author | Commit |
|---|---|---|---|
| javahelp | 2007-06-12 |
|
[b4a468] - No Deque on jdk1.5, so beta3 |
| nbproject | 2007-06-12 |
|
[473f58] - No Deque on jdk1.5, so beta3 |
| nbvi-suite | 2007-06-12 |
|
[473f58] - No Deque on jdk1.5, so beta3 |
| src | 2007-06-09 |
|
[fecaaa] - Add java help |
| .cvsignore | 2007-01-21 |
|
[a6fa1b] - Add property sheet for specifying control cha... |
| README | 2007-04-19 |
|
[ed8946] - Allow jVi activation for a TopComponenet to b... |
| build.xml | 2007-01-17 |
|
[a637f0] - Add :ts |
| manifest.mf | 2007-06-09 |
|
[fcb771] - Add java help |
Read Me
Both jvi and nbvi should be checked out of the CVS repository, and they should reside in the same directory. To build everything, with NetBeans open nbvi/nbvi-suite (yep, its backwards) and build it. jvi-project can be built and run as a standalone app for debugging jVi internals. jvi is the platform independent code. It is referenced from the free form project nbvi/nbvi-suite/jvi-project. jvi-project is wrapped by the module jvi-wrapper. nbvi is the module that interface jVi to NetBeans. The nbvi module's display name is "jVi KeyBindings" and jvi-wrapper's display name is "jVi Core". jvi-wrapper and nbvi are contained in nbvi-suite. The clean and build targets on jvi-wrapper are modified to clean/build jvi-project.