Feature suggestion: Contribute languages to an extension point, and move bundled languages to a separate plug-in

[jensli]

1. Contribute a language directory through an extension point

It would sometimes be useful to be able to contribute a language directory through an extension point, instead of placing the language file in a tracked language directory. This is the case for language designers who wish to use LiClipseText as a component for a plug-in for their specific language.

The contributed directory could be tracked just as other languages directories.

2. Move the bundled languages to a separate plug-in

The other part of this suggestion is useful in the same situation. When used for syntax colors (and other functionality) for one specific language I think it is to disruptive for the user to also get syntax colors for a bunch of other languages.

This language-bundle plug-in could make the languages available by contributing them to the extension point.

There could then be three different Eclipse features for LiClipseText.

1. One standard which include bundled languages.
2. One called LiClipseText Core (or something like that) which don't come bundled with languages.
3. One called LiClipseText Language Bundle (or something like that).

Background and motivation

I have for some time had a low intensity project that aims to create a minimal effort way to use Eclipse with new languages, which don't have advanced plug-ins available. The suggestions above aims to help with that project.

I have so far created a plug-in which lets user get problem markers from compiler output for compilers that are run as external program builders. It is available on Bit Bucket. (I have also created some smaller plug-ins, but most of the functionality they provide seem to be available in LiClipseText.)

Right now my plug-ins, together with a colorer plug-in and standard Eclipse features, enables a user to get much useful functionality for a new language. But it requires some effort to set up this, several separate plug-ins need to be installed and configured, and builders and launcher need to be added.)

I would like to create a framework that language designers can use to, with minimal effort, create custom plug-ins for their languages. LiClipseText could be the most important part of such a framework, and the features suggested here aims to enable that.

[fabioz]

Sorry for not seeing this issue sooner (somehow github was not notifying me -- ideally, report bugs in https://www.brainwy.com/tracker/LiClipseText/).

Regarding your suggestions, I think that the suggestion to contribute directories through extension points a no-brainer (it was already on my mind, just hadn't time to do it).

Would you be interested in providing a pull request for that?

As for part 2, I don't know... I think I'd separate the languages to a different plugin after 1) is done, but I don't think separate features should be needed (i.e.: if clients want, they can rely only on the needed plugins without actually referencing the full feature with everything).