Re: Colour scheme unification

On 06/02/2010 08:27, Keith wrote:
> Would it be possible to update the lexers to allow a user to change, for
> example, function colour in one place and have it change in all
> languages? At present it seems that each lexer pretty much redefines all
> of it's colours, making customizing colours for multiple languages a
> real pain.

There is already something like that in SciTEGlobal.properties: see

# Give symbolic names to the set of colours used in the standard styles.
colour.code.comment.box=fore:#007F00
colour.code.comment.line=fore:#007F00
colour.code.comment.doc=fore:#3F703F
colour.code.comment.nested=fore:#A0C0A0
colour.text.comment=fore:#0000FF,back:#D0F0D0
colour.other.comment=fore:#007F00
colour.embedded.comment=back:#E0EEFF
colour.embedded.js=back:#F0F0FF
colour.notused=back:#FF0000

colour.number=fore:#007F7F
colour.keyword=fore:#00007F
colour.string=fore:#7F007F
colour.char=fore:#7F007F
colour.operator=fore:#000000
colour.preproc=fore:#7F7F00
colour.error=fore:#FFFF00,back:#FF0000

section, just below the general font definitions which contribute too to 
unification.

It is already used in some common lexers, for example the cpp.properties:

# Comment: /* */.
style.cpp.1=$(colour.code.comment.box),$(font.code.comment.box)
# Line Comment: //.
style.cpp.2=$(colour.code.comment.line),$(font.code.comment.line)
# Doc comment: block comments beginning with /** or /*!
style.cpp.3=$(colour.code.comment.doc),$(font.code.comment.doc)
# Number
style.cpp.4=$(colour.number)
# Keyword
style.cpp.5=$(colour.keyword),bold
# Double quoted string
style.cpp.6=$(colour.string)
# Single quoted string
style.cpp.7=$(colour.char)
# UUIDs (only in IDL)
style.cpp.8=fore:#804080
# Preprocessor
style.cpp.9=$(colour.preproc)
# Operators
style.cpp.10=$(colour.operator),bold

Now, some lexers have more states than standard colours (Perl for 
example), some people might prefer to have distinct colour schemes (to 
distinguish JavaScript work from C++ work for example), and so on.
Moreover, each lexer's properties is made by contributors, reflecting 
their preferences.
These colour schemes are provided as "reasonable base", made to be 
customized by everybody.

Now, I can't talk for Neil, but I think that you can do your unification 
on your preferred languages for yourself, preferably based on these 
standard colours, then propose the changes. They might be approved... or 
not, or with changes.
IIRC, that's how I proposed these standard colours (or extended them, I 
don't recall exactly).

-- 
Philippe Lhoste
--  (near) Paris -- France
--  http://Phi.Lho.free.fr
--  --  --  --  --  --  --  --  --  --  --  --  --  --

--

-- 
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com.
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en.