Code::Blocks Forums
Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: rickg22 on March 22, 2008, 09:31:34 pm
-
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... :(
-
thats really bad news :(
-
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.
-
Well, Code::Blocks uses its own version of wxScintilla already anyway, so I don't see how this is a too big problem.
-
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?
-
gtksourceview for one.
-
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
-
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 ;-) )
-
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).
-
what would be very cool is to implement a native wxwidgets text editor using the drawing functions :lol:
-
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 (http://article.gmane.org/gmane.comp.lib.wxwidgets.devel/84542/match=rudely+forked)
-
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.
-
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?
-
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?!
-
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.
-
Morten, I'm happy to help test it if you want to throw me a patch against the latest svn.
Ok... unfortunately I wasn't able to do it. SVN diff does not consider files that have been added and the diff tool just makes non-workable patches. :?
So... I have added a ZIP file that contains the wxscintilla sources of the SDK folder (the include folder is not affected). So remove the original sdk/wxscintilla folder and copy the one from the ZIP archive into it. BTW: The makefile build system is not yet updated.
-
Edit: Ps.: I cannot attach a "patch" (ZIP archive) of such big size, so look here: http://www.martin-halle.de/archive/wxscintilla.zip
Awesome. I'll have time to look at it in a few hours.
Am I looking for anything in particular? Broken old features? Potential new features? Just hit it with a hammer and see if it still ticks?
-
Am I looking for anything in particular? Broken old features? Potential new features? Just hit it with a hammer and see if it still ticks?
Well... especially trying under Linux and (most important) fixing the build system for linux so that it works at all would be of much help. I don't like Linux anymore. It has tricked me too often recently. So I am Windows only atm.
BTW: I have forgotten to add the CodeBlocks project file that needs an update, too. So you have to do it manually... just add all sources of sdk\wxscintilla\src\scintilla\include and sdk\wxscintilla\src\scintilla\src. Don't add anything else... we don't need these parts.
-
Ok... unfortunately I wasn't able to do it. SVN diff does not consider files that have been added and the diff tool just makes non-workable patches. :?
svn diff should work if you svn add the new files first.
-
Well... especially trying under Linux and (most important) fixing the build system for linux so that it works at all would be of much help. I don't like Linux anymore. It has tricked me too often recently. So I am Windows only atm.
Hey, Morten. I haven't forgotten about this. It's building fine, but I want to kick the tires some more when I have a free hour or two.
-
Hi CB team.
I need to program an editor into my wx application. wxScintilla seems the best option, but I have some problems with it. Reading this thread one understands the sad estate of that project.
Now I find two choices. [1] Use Scintilla library directly, or [2] Make some fixes to the wxScintilla v1.72 (SVN). But I have noticed you have kept an updated version for your own needs (Wonderful!).
I would like to ask a humble question. Could I use your updated version of wxScintilla? Is it under wxWindows license?
Thanks so much in advance.
Best regards
-Jeisson
-
I would like to ask a humble question. Could I use your updated version of wxScintilla? Is it under wxWindows license?
It's under GPL3, just as the rest of C::B, too. If that license suits your needs, go ahead. :P
Alternatively there is another IDE that uses an own further improved version of wxScintilla called CodeLite. To be honest I am not sure under what license this goes, but it's surely OpenSource at least. You can ask the author of that IDE (Eran Ifrah) via a PM. He is member of our forum under the nick name "eranif".
As another alternative: Are you aware, that a kind of "wxScintilla" called STC is part of the wxWidgets sources? It's here:
[wxWidgets_sources]\contrib\src\stc
...for wxWidgets 2.8.10; or here:
[wxWidgets_sources]\src\stc
...for wxWidgets 2.9.x.
-
As another alternative: Are you aware, that a kind of "wxScintilla" called STC is part of the wxWidgets sources? It's here:
[wxWidgets_sources]\contrib\src\stc
...for wxWidgets 2.8.10; or here:
[wxWidgets_sources]\src\stc
...for wxWidgets 2.9.x.
Morten. Your words are light.
I did not know wxStyledTextCtrl is actually a Scintilla control, it is not in the wx-2.8.10 docs (docs-2.9 (http://docs.wxwidgets.org/trunk/classwx_styled_text_ctrl.html) includes it). This is fantastic. I am going to try STC.
BTW.: wx-2.9-svn (http://groups.google.co.cr/group/wx-dev/browse_thread/thread/9eed0a12c0a93ae8/7d162c220a5a3685) seems to be updated to Scintilla 2.01.
Thanks so much, again
Best regards
-Jeisson
-
By the way, are you plan to merge your own Scintilla binding with wxWidgets3`s stc control after migrating to new wxWidgets version? I think this would useful for both - wxWidgets core and CodeBlocks project.
-
By the way, are you plan to merge your own Scintilla binding with wxWidgets3`s stc control
I doubt this will happen any time soon. The STC component is still based on scintilla 1.7.x to my knowledge and lacks a lot of features we've added already. As we depend partially on these new features we would either need to adopt STC or stay with (our) wxScintilla. the latter makes more sense to me.
-
CodeBlocks should be wxScintilla mantainers(sp?) they actually do it
See something if you search wxscintilla in google the third result is codeblocks forums.
Who could be interested in getting wxscintilla?
- developers (mostly cpp developers)
- developers using wxWidgets
- developers interested on creating some editor prolly with code highlighting capabilities
If you show them codeblocks and how to build an ide simply extending codeblocks, some of them would be happy dont you think.
You set a web page with a download link and a documentation page and you place some banners. That would be fine :)