Re: dark theme

Baltasar:

> I think that these concepts should be moved to the top level, so ScITE would know about keywords, identifiers and so on, and then the lexers would not have anything to do with colors, only maybe with specific symbols that are not dealt with by the top level.
> This way, it would be possible to create different "style" files, light, dark, QBasic editor...

   Lexers know nothing about colours: they assign a style number to each lexical class they understand. More recent lexers associate tags with each lexical class including "keyword", "operator", "comment", etc. These tags are not currently used in styling as they are not implemented on all lexers.

   Multiple lexical classes may be representing similar types: Python has 8 literal string classes. Some people may like all these styled the same but others will prefer distinct styles. Many people want multiple sets of keywords (or known identifiers) with distinct styles. A theme system should not squash classes together for ease of implementation but should allow for gradual specialization both at theme definition and user customization levels.

   Theme systems are often too-fragile, breaking when new classes are introduced as they would need to accommodate the new class in harmony with current styles. Theme authors are often only interested in a subset of languages they use and are unaware of nuances in other languages.

   Neil

-- 
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/scite-interest/6FF1A3D1-948C-4A78-9180-388558580A34%40me.com.