Anjuta Roadmap

2.30

Editor (depends on GtkSourceView)

• code-folding
• inspection of text type

Searching

• Merge async search patch

Language support

• Write language support plugins for more languages
• Add member completion based on symbol-db plugin
• Integrate devhelp into calltips

Version Control

• Add/Remove/Rename of files in file-manager and/or project-manager should update the status of VCS

Build

• Add ability to build single files (without Makefile)

• Adapt build system to various environment Anjuta/Roadmap/BuildSystemCleanUp

Symbol-DB

• Provide "Locals" support for files not conained in the project on-the-fly (maybe in-memory database).

PackageKit integration

• Bug 558856 - Use PackageKit to detect and install missing packages

General aspects

Extensibility

To provide means to extent Anjuta in varying ways.

• Encouraging bindings for other languages. This is essentially a gateway to many interesting plugin developments involving language specific plugins. I believe our framework is at very good position to support language bindings, thanks to Sebastien. But we need more efforts to promote this and give guidance (documentation, website, demonstration, examples) to prospective 3rd party developments.
• Provide remote templates download for user to just browse and find his right template. Also to allow uploading new templates. This will need some kind of web service, but I think it can be worked out somewhere in anjuta.org. However, the biggest issue is maintaining it in user's installation. Maybe it's just better to depend on host packaging system to avoid reinventing the wheel?

Automated regression and module testing

• Since we are now part of GNOME suit, reliability is becoming more important. We need to focus on automated testing also. While clearly we don't have the resource to go full blown test suit, we can hopefully have some regression testing for complicated features that have way too many test cases typically not easily covered in normal usage.
• Module testing is also interesting. We could come up with some generic module testing setup that would allow independent plugin testing without involving other plugins too much. We have some basic setup using anjuta-shell, but something better can be thought out.