Anjuta is a very powerful development environment because of its tight
integration with other tools (like GDB, Valgrind, autotools). Vim is just as
powerful of an editor, however for the most part it remains isolated from the
rest of the development cycle, solely satisfying the role of an editor. I
propose to embed a gvim editor into Anjuta to get the best of both worlds.

Essentially, this means the implementation of the IAnjutaEditor interface,
however, because of the nature of gVim several other aspects have to be
considered:

1. The gVim editor has to grab all the keyboard events because of it's modal
   interface. Support for switching in and out of the editor must be
   implemented.
2. Vim has a lot of complex commands for selection, movements, deletion etc.
   This makes the implementation of the interface slightly more complicated.
3. Unlike other editors, where commands to navigate between open files,
 creating/opening files, etc. are separable, in vim they are a part of the
 editor. This means that there has to be a way for vim to tell Anjuta that
 it's changing files, etc. This will be the most complex part of the project.

Also in the scope of the project is to create functions in vim so that it can
control some of Anjuta's features (build, start debugging, create to-do notes).