Syntax Tools

[alex]

New Syntax Tools Plugin has been published.
The plugin contains functions for importing of syntax files from other editors (as UltraEdit, TextPad or PSPad) into HippoEDIT format.

More information can be found on wiki.
Suggestions and comments - here.

[Anonymous]

Idea, dirty: take Delphi component econtrol.ru; make a dll from it; make dll parse file to token list (econtrol can it); use dll to get tokens ; get token colors too; and color all after it.

only dirty idea

[alex]

Generally I have not understood for what purpose for...
And seems much more complex as just parse configuration files in javascript as it already done for UE, TextPad and PSPad...

[Anonymous]

Didn't understand? bad. i try to write it again. u can take Scintilla library and parse source code to Scintilla structures. then HE calls this Scintilla based code part and takes parsed results from it. then HE colorizes file, based on this Scintilla results.

what for? for coloring like in Scintilla.

why not use Scintilla as is? HE can't do it.

[alex]

But why not to just define syntax schema for HippoEDIT? It will be much less effort then writing new parser based on Scintilla.
I understand the idea, and it is possible to write a plug-in for HE that extends built in syntax highlighting, but I do not see benefits, for rather big effort.
It will make sense if HE can not do syntax highlighting by itself, or syntax highlighting of Scintilla will be much more powerful. 

[Anonymous]

i assumed Sci Hilite IS MORE powerfull. e.g., take Oberon lexer. does HE hilite all Oberon constructs so correct as Sci lexer does? no. and Oberon lexeer written in Oberon as external DLL (maybe it bad example - u can't use it).

or C++ lexer in Sci -isn't it more powerfull. not sure.
if Sci hilite isn't more powefull, forget it.

[alex]

HE currently do not have schema for Oberon (maybe need to migrate one from UE or TextPad if somebody need). So, I can not compare. Probably, if language has very complicated syntax, that can not be covered by regexp definitions, and has dedicated, hardcoded lexer for scintilla, scintilla will be better (actually not scintilla as you mentioned, but lexer). But is it cost effort.. ?

C++ in Scintilla is not more powerful (maybe they can parse #ifdef _DEBUG, HE cant ). But HE can highlight special characters in strings (like \n \r \t etc), highlight functions and classes, todos etc.

So, it it rather time consuming to create for HE Scintilla based lexer + Scintilla lexer will not provide all information HE needs.
If somebody else would like to help with such plugin, I will provide all needed help

BR, Alex.