Bug 42046 - [syntax highlighting] Decouple syntax highlighting from editors
Summary: [syntax highlighting] Decouple syntax highlighting from editors
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 2.1.1   Edit
Hardware: All All
: P3 enhancement with 5 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-26 18:26 EDT by Nathan Niesen CLA
Modified: 2014-09-28 14:54 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nathan Niesen CLA 2003-08-26 18:26:00 EDT
Syntax highlighting appears to be a function of each editor instead of 
something that applies to all editors (i.e. each editor appears to have its own 
syntax highlighting implementation). There should be one syntax hightlighting 
implementation for all editors and the implementation should provide a flexible 
way to add highlighting for new file types. There are plugins like 
EclipseColorer that perform syntax highlighting on over 100 file types but 
using this editor means I lose all the smarts built into the JDT editor, XML 
editors, etc.... The jEdit (www.jedit.org) open source editor has syntax 
hightlighting that uses configuration files to add highlight for new file types 
and tweak highlight for existing file types.
Comment 1 Nathan Niesen CLA 2003-08-26 18:36:15 EDT
This could be taken a step further to also include "content assistance" the is 
plugable and extensible. I think the number of plugin editors available is and 
indication that core editor should be more extensible. jEdit and IntelliJ both 
have content assistence and syntax hightlighting for multiple file types 
without requiring the duplication of basic editing.
Comment 2 Rafael Chaves CLA 2003-08-26 18:59:41 EDT
Routing to Platform/Text...
Comment 3 Dani Megert CLA 2003-08-27 05:42:48 EDT
You are correct in the sense that the current approach is to
- provide API so that clients can write their own editors
- provide concrete editors (e.g. Java)

We did not (yet?) intend to provide a generic editor.
Comment 4 Andre John Mas CLA 2008-01-11 18:06:22 EST
For me this is a must, if it can be achieved. Currently Eclipse does not seem to include a text-based XML editor, with support for syntax highlighting. By being able to take a generic text-based editor that supports pluggable highlighting rules, this would certainly help address this to a certain extent and allow support for other languages, such as php, perl, etc.

The windows editor 'TextPad' support syntax highlighting via pluggable syntaxes, as can be found here:

  http://www.textpad.com/add-ons/syna2g.html


Comment 5 Jeffrey Ridout CLA 2009-06-26 04:03:46 EDT
Excellent suggestion, voted!
Comment 6 Jeffrey Ridout CLA 2009-06-26 04:05:33 EDT
I forgot to mention...

This would also be a great step into accomplishing themes for syntax highlighting.
Comment 7 Nitin Dahyabhai CLA 2010-02-26 11:39:34 EST
(In reply to comment #4)
> For me this is a must, if it can be achieved. Currently Eclipse does not seem
> to include a text-based XML editor, with support for syntax highlighting.
> ...

The WTP project includes an XML Editor (http://eclipse.org/webtools), its first Release in 2005.
Comment 8 Dawid Pakula CLA 2014-09-28 14:54:29 EDT
Is this possible to refresh this issue?

As far as I know, orion project have a pluggable syntax highlighting. Maybe will be possible to port it's model to e4?

Same for content assist.