Announcement: wxScintilla is officially abandoned :(

[rickg22]

I've just received a mail from wyo - the wxScintilla developer, and he told me that he doesn't support the project anymore. If someone wants to take on the project he's welcome to contact wyo and ask for the rights.

Here's the mail:

Hi Ricardo,

I've given up on OpenSource and don't support wxScintilla anymore. IF
you still plan to use it, you can have it. Contact Francesco Montorsi,
he can give you the rights.

Otti

So, if we want to adapt Scintilla to our project, then we're on our own...   

[JGM]

thats really bad news

[dmoore]

well, I think this should be used as an opportunity to free the codeblocks core of an explicit dependency on any editor. ideally new editors could be swapped in using the plugin framework. perhaps, realistically this is a medium term goal, but at least worth some thought.

[thomas]

Well, Code::Blocks uses its own version of wxScintilla already anyway, so I don't see how this is a too big problem.

[JGM]

ideally new editors could be swapped in using the plugin framework.

And what editors are better than scintilla out there, that are open source and c++ compatible?

[dmoore]

gtksourceview for one.

[JGM]

gtksourceview for one.

But that will add more dependencies to codeblocks (gtk dependencies) Maybe that's a problem, also merging that to work with wxwidgets could be troublesome

[rickg22]

Whoa whoa wait...
i said wxScintilla is not supported. But we can still use Scintilla!

wxScintilla and Scintilla are *TWO ENTIRE DIFFERENT PROJECTS*. wxScintilla is a wrapper around Scintilla. In fact I managed to compile cb with the latest version of scintilla (1.76).

(Perhaps this would be a good opportunity to update, too ;-) )

[dmoore]

I wasn't trying to imply cb should abandon (wx)scintilla, rather that the cb base should be flexible enough to accomodate more than one source editor control. the news about wxscintilla just highlights the risk of being unnecessarily tethered to upstream projects.

wrt gtksourceview, it would be a natural fit on linux. wxwidgets on linux is wxgtk after all. if it was a plugin, would it matter if it wasn't multi-platform? (still have scintilla). gtksourceview might not be better than scintilla, just an alternative (and who knows what the future may bring).

[JGM]

what would be very cool is to implement a native wxwidgets text editor using the drawing functions  :lol:

[troels]

So, if we want to adapt Scintilla to our project, then we're on our own...   

As of wx2.9, the original Scintilla wrapper wxStyledTextCtrl (wx/contrib/../stc) has become an 'official' wx class (wx/src/stc).
Is it really necessary to fork?
Regards

PS: wxScintilla fork

[rickg22]

I recall that in the wx2.4 times, the STC editor wasn't well maintained, and wxScintilla was seen (at least by me) as some kind of blessing. But knowing we can patch it whenever we can without having to depend on a specific wx version, I feel better. It's much more convenient when you can modify the code however you like.

[DrewBoo]

wxScintilla is a wrapper around Scintilla. In fact I managed to compile cb with the latest version of scintilla (1.76).

Interesting.

Did you have to massage a lot of code/files?

What would the end user see on your build that is different?  Performance differences?  Features?

[MortenMacFly]

Ok... I embedded scintilla 1.7.6 into the latest wxScintilla (the one of C::B 08.02) within C::B. On Windows it works, but I had to modify wxScintilla for this (as expected). Now what should I try to see if bugs got fixed / remain?!

[DrewBoo]

Ok... I embedded scintilla 1.7.6 into the latest wxScintilla (the one of C::B 08.02) within C::B. On Windows it works, but I had to modify wxScintilla for this (as expected). Now what should I try to see if bugs got fixed / remain?!

Morten, I'm happy to help test it if you want to throw me a patch against the latest svn.