You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the SciTE sources there are ton of language definitions as scite\src\***.properties files just waiting to be used.
For most users those defaults would be fine. So an API could look like:
having a LexStyleProperties class
which can read the scite\src\***.properties
create the lexer from that
and the style definitions, with an option to give another Styling class instance which defines the colors to be used and can be shared between different lexers
have some calls to use the "other" stuff definid in the properties files, like the file endings etc.
Don't know how much effort this is, didn't dive into the SciTE sources yet. Maybe there is something like that already there.
The text was updated successfully, but these errors were encountered:
In the SciTE sources there are ton of language definitions as
scite\src\***.properties
files just waiting to be used.For most users those defaults would be fine. So an API could look like:
LexStyleProperties
classscite\src\***.properties
Styling
class instance which defines the colors to be used and can be shared between different lexersDon't know how much effort this is, didn't dive into the SciTE sources yet. Maybe there is something like that already there.
The text was updated successfully, but these errors were encountered: