The implementation as a whole is based on outdated technologies and does not work with current versions of Eclipse (Kepler) and Xtext (2.x) among other components.

Update the core functionality by migrating to current version of Eclipse and Xtext. Core functionality encompasses parsing and editing support, i.e. the most basic building blocks provided by Xtext. This can be achieved "in-place" - by working with the existing resources directly, or "in parallel" - by starting from a clean state in a new parallel location and migrating relevant resources as necessary, while the original resources are kept for reference. I would recommend the latter, but this is not to say that the former would not be possible.

The easiest approach is to export the tooling as a plugin. Investigate how this can be best achieved and possibly automated (e.g. for nightly builds).

Alternatively, a lightweight and environment independent solution would be to deploy the tooling as an RCP application. Investigate how this can be best achieved and what possible drawback it may entail. If the effort is too high, this option could be postponed or discarded.

Use proper formatting on the Wiki pages, especially the development documentation.

   This is code..
      Properly indented 
   and formatted

This is a Level 0 heading

This is a Level 0 heading

• this is a bullet list
  • with nested elements

1. this is a numbered list
   1. with nested elements
   2. in sequence
2. ...

etc.

This allows for using other facilities of Trac that rely on such formatting, such as Table of Contents, PDF export, etc.

Attach and include screenshots where applicable (attachment permissions have been fixed). Attach other documents where applicable as well (although they should preferably be added to SVN and then linked accordingly which makes management bearable).