QSciScintilla with lexilla support?

[Roland Hughes]

Hello,

It was unclear from your query _exactly_ what you are looking for. 
Scintilla itself has Qt support built in. I don't use it, so I don't 
know. If you don't want to deal with the mountain of bugs in Qt or the 
licensing issues you could use that.

https://scintilla.org/

If you want something better than Qt with a much tinier bug database and 
zero QML bugs because all things QML have been removed you can look into 
CopperSpice.

https://www.copperspice.com/

There is no commercial version of CopperSpice so no "Everybody must buy 
a license" definition of "OpenSource." I have a non-commercial fork of 
Scintilla for CopperSpice. It has a few differences, but is kept 
reasonably close to Scintilla. Usually within a year.

https://sourceforge.net/projects/csscintilla/

The copperspice_examples directory of the code has multiple editors 
starting from the most basic of "just throw the widget in a window" to 
several with EDT keypad navigation. One of the biggest pitfalls of 
Scintilla is there is no tutorial. The SCiTE text editor started out 
being that, then became where every feature was tested so there is no 
longer any "print hello to the printer" example. CsScintilla has that.

RedDiamond

https://sourceforge.net/projects/reddiamond/

Is a full on editor with EDT keypad navigation, themes, configurable 
backups using lexers, theme import/export and many more features. 
Another new version should be out in a few months.

Note: Do not use the CsScintillaDocument class or its ScintillaDocument 
counterpart no matter which way you go. Those classes are going away 
very soon. For CsScintilla they will go away in the very next release. 
Neil wants them gone out of Scintilla as well.

Note 2: Many/most of the Lexers that are part of Lexilla library are 
legacy lexers. They don't support all of the new lexer features in the 
documentation.

Note 3: Coordinating colors across lexers to have a common theme is a 
real PITA. Everybody re-used the same numbers for different things. If 
you are going to create a production quality theme supporting editor 
which works for more than 2-3 similar languages, you have some work to 
do. You may have noticed that most of the "new" editors being released 
OpenSource support only C/C++, Java, and Python; not because those are 
the most popular, but because they are syntax similar and the default 
lexers are pretty close in how they use the paint-by-numbers system.

Roland

-- 
Roland Hughes, President
Logikal Solutions
(630)-205-1593

http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.johnsmith-book.com
http://www.logikalblog.com
http://www.interestingauthors.com/blog


-- 
This email has been checked for viruses by Avast antivirus software.
www.avast.com