Introducing my hrc files in eclipse colorer plugin

Hi! First of all big thanks for Colorer and FAR Plugin.

My task is implementing syntax coloring for C-like language (all C syntax + additional keywords).  HRC file was written for this purpose and perfectly works with FAR. But there are some notes about Eclipse Plug-in. As I understand I need to place *.hrc into net.sf.colorer_x.x.x\colorer\hrc\auto folder. It’s not Eclipse-like style of extending. Would be better if I can write my own plugin and introduce my HRC file in plugin.xml by using some extension point. Is it possible to implement such feature?

Going further, I’d like have coloring only for chosen existing languages and/or new languages, so to my mind be better if colorer pluging would be divided into two parts – pluging that implements engine and defines extension point for introducing hrc files and plugin with hrc files. So if someone wants to define its own set of colored languages he just reuses core plugin and implements its own plugin with subset of hrcs.

Best Regards,

Sergey Gomanyuk,

ISP RAS (www.ispras.ru),

junior research assistant,

e-mail: sergg@...

phone: +7 (095) 912-5317 (4428 additional)

cell: +7 (926) 4547743 

> Personally I'm agree with Dmitry - see no reason why we should split plugin at this level of abstraction.

Assume that I’d like to provide in my product coloring only for my language. As I understand under given license agreement I can modify colorer plugin by removing editor definitions from plugin.xml, add my hrc file and define my own editor. Well it’s the way but for me very non-elegant way.

By the way, if someone who uses my product, also by some reasons wants to use colorer plugin with all supported languages then there is real conflict possibility.

In offered case I just define extension with my hrc file and reuse colorer core plugin. So your plugin is still encapsulated, nonmodified, can be updated via update site and so on. And moreover it is standard way of extending plugin functionality  in eclipse community (not modifying source of given plugin but using its extension points).