Bug 204828 - User selects the way text is higlighted.
Summary: User selects the way text is higlighted.
Status: RESOLVED DUPLICATE of bug 42550
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.3   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL: http://www.lunar-ocean.com/blog/scala...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-27 12:20 EDT by Antoine Toulmé CLA
Modified: 2007-10-04 02:51 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Antoine Toulmé CLA 2007-09-27 12:20:04 EDT 
From the comments of http://www.lunar-ocean.com/blog/scala-syntax-extension/

Alex proposes to have the user select the way tokens are highlighted in Eclipse, instead of having the plugin developer choose for him.

The user should then be able to highlight elements and give it a particular color and/or style a la CSS.
Comment 1 Antoine Toulmé CLA 2007-09-28 03:10:09 EDT 
Added Alex in CC.
Comment 2 Alex Blewitt CLA 2007-09-28 04:59:58 EDT 
One of the reasons why this suggestion is nice is that there could be a platform-provided (well, IDE) list of common token names and colours. For example, 'keywords', 'identifiers', 'method/function' etc.

This could allow other language projects (JDT, DLTK etc.) to use the same common set of colour formatting for all languages, instead of having to define them in several places for each different language.

As a side-note, the ability to configure these as css colours would be useful since one could use the classes to configure other properties of the keyword's presentation, though of course only a small subset would be interpreted. But it might be useful in HTML exports of the file that could use the same .css (and perhaps add additional properties for viewing that might not be available for HTML export)
Comment 3 Dani Megert CLA 2007-10-04 02:51:48 EDT 

*** This bug has been marked as a duplicate of bug 42550 ***