Hi,
Although I cannot commit to any result or schedule, I have in my
plans to contribute to have the text editor supporting coloration
and content-assist without the need to create a new editor, for
example relying on textmate grammars, but probably allowing to hook
up any coloration/content-assist strategy to the text editor.
The idea would be that the Text Editor could provide some basic
features for most file types without the need to specialize it and
to create a specific editor, but only relying on external services
or an internal registry of grammars to add that behaviour.
Tom Schindl and Angelo Zerr have already made some work on this
topic, and here is the current entry point or this story
https://bugs.eclipse.org/bugs/show_bug.cgi?id=486961 .
I believe this is a big topic that could be titled "Reducing cost of
basic support for new languages"
Some other bugs/topics I'm interested in that will probably affect
Platform/UI
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=489540 and
https://bugs.eclipse.org/bugs/show_bug.cgi?id=102527 , is a
sub-topic of the user experience topic that I would call "Make the
IDE forgiving mistakes and helpful for poor users". In general, I'll
try to be careful about which error report and quickfixes can help
the users directly in the IDE rather than forcing them to go read
bad answers and StackOverflow.
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=489719 and maybe
even considering a "Welcome Questionnaire" like Oomph initiated, but
maybe more at the Platform UI/IDE level. This would be also a
sub-topic of UX, that could be title "You're more and more welcome!"
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=489799 and
https://bugs.eclipse.org/bugs/show_bug.cgi?id=489719 (again), also
in the UX I guess, about making it comfortable and productive to
have Eclipse as default editor in the OS.
|