Creating a dark theme

baltasarq <[email protected]> Mon, 22 May 2023 01:08:12 -0700 (PDT)
Newsgroups gmane.editors.scite.general
Message-ID <[email protected]>
Is the SciTE configuration files system a mess?

I'm creating my own dark theme (public at 
https://github.com/Baltasarq/My-Scite-Conf ).

I thought the configuration files scheme was:

general properties: global.properties
my modifications: user.properties
a given programming language "pr": pr.properties

So far so good. Until I found that some colors were not changing. Then I 
found that there are basic colors in global properties to change too 
(embedded languages). Okay.

But then I wanted to change the colors for XML. Okay, there is not 
XML.properties, or similar. There is an HTML properties file. Mmmm... let's 
do a grep. And the results were appalling, you have XML configuration set 
in Embedded.properties and html properties. Maybe html.properties makes 
sense, but... what is Embedded.properties?

The answer is... I don't really know. Embedded properties not only defines 
colors for embedded languages, but also for the position of the window, 
compile commands...

For me, either Embedded.properties is superfluous if global and user 
properties exist, or global.properties does not make sense.

It seems to me that somehow this reflects the evolution of the 
configuration system for SciTE. Probably firstly only Embedded.properties 
existed, and then global/users properties files appeared (or the other way 
round). Then a single file for each programming language (or group).

This creates confusion. Which properties file should I modify?
I think this properties file system should be reviewed  and cleaned.
 
-- Baltasar

-- 
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/78b44b33-2414-4e1c-9547-69b3704041a2n%40googlegroups.com.