Background
I am the developer of the Vrapper project .
Vrapper contains two main parts
- Vim emulation library (vrapper.core)
- The part of Eclipse that makes good use of it
We want vrapper.core to be Eclipse-unaware, so it is reused outside of Eclipse. Currently, we can "decorate" all kinds of Eclipse text editors and our small text editor, which we use for unit testing.
vrapper.core implements all kinds of commands, modes, etc. They all communicate with Platform - an interface that abstracts the basic material (text editor, clipboard, settings system, etc.).
When a mode is created for the editor, it asks the platform if there are additional commands that correspond to the base editor, the current edited file type, etc.
EclipsePlatform provides these commands using the Eclipse extension point mechanism.
So, consider the following projects (there are more):
- vrapper.core - Eclipse-independent code for Vrapper
- vrapper.eclipse is an Eclipse plugin that depends on vrapper.core
- surround.core - Eclipse-independent code that emulates surround.vim (Vim plug-in)
- surround.eclipse is an Eclipse fragment for vrapper.eclipse
which makes it the surround.core command .
There are two ways to deal with them:
Eclipse.
, vrapper.eclipse vrapper.core,
, surround.core surround.eclipse.
- 3
- OSGified vrapper.core, surround.core
- < > vrapper.eclipse
- surround.eclipse vrapper.core
, .
, vrapper.core,
surround.core, ( vrapper.eclipse โ surround.eclipse).
, Eclipse ,
eclipse,
surround.core .
- surround.core,
.
, , , eclipse, .
(, vim) - . . , Eclipse (, , JDT). , () , eclipse. , - eclipse. eclipse - , . , .
, " ".
, , , .
, , .
- .core Ant, .jar
*. eclipse
- *. eclipse MANIFEST.
( , )
. Eclipse,
Eclipse .
eclipse library + eclipse specific,
( ).
/?