PSPad future - new editor engine

This engine base comes from Synedit. I hope I will be able use it without margin changes to PSPad behavior. This is the reason, why I test it.
For now I see only advantages.

Quote:

All highlighters are in external JSON files - another plus

Do you want to prepare the JSON files by your self? If no, we can help you!

Ilya:

Quote:

All highlighters are in external JSON files - another plus

Do you want to prepare the JSON files by your self? If no, we can help you!

I count with help, cause I don't know all syntaxes.
Some highlighters already exists as part of component.
I plan to write some tool what will help with new highlighter creation - something like User highlighter in existing PSPad.

If you need some help count on me.
I don't know Delphi but for translation to Italian or perl syntax or other things I can help.

What do you think about common highligting styles? All syntaxes split to keyword-based (C, Delphi, Java, etc.) and tag-based (HTML, XML, etc.) and have common settings, how to highlight keywords, string, comments, tags, attributes and other elements. Every language inherites common settings, can override or extend them. Users can set their preferences for common settings and overrides for every language they want.

For example, I prefer old Borland style for all programming languages like Delphi, PHP or SQL, and default coloring for HTML and XML. In current version of PSPad I have to redefine my preferences for every language I want to use, because of there isn't common way.

Such principle is already included. There are named groups of keywords.
Important is create list of group names and keep it in highlighters. It will allow you to set color for all groups in all highlighters at once = you can create themes.

Hello Jan,

Is there any progress on this? Need any help from users of PSPAD in development or documentation?

--
Thanks

Just now I am stocked with my job work.

I just checked out the demo, and it looks very nice. I like the Wood theme!!
Can't test much detailed issues, since not much functionality implemented, but it looks very nice. Don't see any problems with it.

This seems like a great future for PSPad (if you'll keep the name).

I saw a few issues in HTML with scripts like:
- If php end is after comment character, it isn't interpreted as php end

<?php $var = 'value'; // This is comment ?>

- seems to have difficulty interpreting PHP $var["{$var2}"] (although I'm not sure I still need it but it's still part of some legacy code); $var["$var2"] is OK.
- also some code nesting issues which I'm sure isn't easy

var fld = new Ext.form.ComboBox({
<?php if (isset($GLOBALS['extjsv']) && $GLOBALS['extjsv'] < 3) { ?>
store: new Ext.data.SimpleStore({
<?php } else { ?>
store: new Ext.data.ArrayStore({
<?php } ?>
fields: ['nummer', 'naam'],
...
}),
...
});

Which results in everything being folded until the EOF.

Folding seems sensitive by the way: just cicking in column 1 (trying to select some code) already folded it.

Not trying to be negative at all but you asked for initial feedback, right?!

As I said: looks very promising indeed and this will really put PSPad back next to others like NP++ where it belongs!

Thanks for all the effort, Jan!!!

Patrick