On 07/14/2016 12:55 PM, Fabio Zadrozny
wrote:
The idea with this editor isn't to provide the Liclipse feature, but
to provide a new framework for implementing a textual editor and a
generic editor that could work on most languages (using composition
via extension points rather than inheritance).
TextMate support would only be a possible way to contribute features
to that editor, many others would be possible (simply highlighting
keywords for example can be enough in many cases). We do not want
the generic editor to depend on TextMate nor Liclipse, but we would
like it to be kindly able to integrate external features such as the
ones provided by Liclipse.
That's exactly the goal. Eclipse IDE has some millions of users.
Very few of them will install Liclipse or whatever else extension
(this is true for any extension, they hit a very few proportion of
the target users using raw Eclipse IDEs). So about the TextMate
thing, or other grammars for more languages, the goal is exactly to
have it in Eclipse itself, to make sure many users can take
advantage of it.
If this is to become a critical part of the IDE, I'd find dangerous
to just include Liclipse as it: it's going to need some maintenance,
and you seem to be lacking time for that. So, from Platform POV, it
seems safer to reimplement parts of it that or to find alternatives
that seem more "sustainable", than to depend on legacy code that
author cannot commit on maintaining.
--
|