Hi, folks.
I've been out of the loop for a while, but have just caught up with this thread and the one about Vala. Just wanted to add $0.02:
- I'm not really a C programmer (Java background), so would welcome non-C opportunities for plugin writing. Although I actually do like Lua scripting. - Vala looks promising because it generates C code. This sounds a bit like eg CoffeeScript compiling to JavaScript. If it generates similar (or better?) machine code, and is easier for humans, sounds good. Given my background, I would certainly find it easier to contribute to Vala code than to C code. But I'm not expert in the dependency issues. - Scintilla may be ugly compared to GtkSourceView, but my experience of their respective editors (eg Notepad++) is that it provides more features - and worthwhile ones. Even code folding is a plugin in Gedit. And I love rectangular selection. So I don't like the idea of swapping to GtkSourceView.
Thrawn
------------------------------ On Mon, Dec 2, 2013 12:54 PM AEDT Lex Trotman wrote:
Hi All,
Just a note I am still summarising the thread, but "real life" is getting in the way. Real soon now (hopefully).
Cheers Lex
I agree on scintilla being better.
I don't know if this is because of gtksourceview or not, but loading large files or files with long lines freezes up gedit2/pluma, which uses gtksourceview. I used to prefer gtksourceview, but I think I prefer scintilla more now.
I could have just lacked experience, but navigating the code to add background color or select regions didn't seem as easy with gtksourceview. Their iterators, marks, and other anchor/location-types seemed to be unintuitively mixed and would become stale data quickly without even the text changing.
Thanks,
Steve
On 13-12-15 11:01 PM, Steven Blatnick wrote:
I agree on scintilla being better.
I don't know if this is because of gtksourceview or not, but loading large files or files with long lines freezes up gedit2/pluma, which uses gtksourceview. I used to prefer gtksourceview, but I think I prefer scintilla more now.
My experience is exactly the opposite (not with Gedit though). GSV works incrementally while pumping the GUI loop, Scintilla completely blocks it.
I could have just lacked experience, but navigating the code to add background color or select regions didn't seem as easy with gtksourceview. Their iterators, marks, and other anchor/location-types seemed to be unintuitively mixed and would become stale data quickly without even the text changing.
My experience is exactly opposite. GSV feels natural in GTK+ since most of its API is directly inherited from the existing GtkTextView widget and the rest of its API is very idiomatic. Scintilla's GTK+ backend, without going into a huge rant, has quite possibly the worst, most foreign API to ever be unleashed on the world.
Cheers, Matthew Brush
LOL. I will say that my initial reason for preferring gtksourceview when I was looking for another editor was the native feel, which is a major reason I was only looking at gtk-based editors. Maybe my experiences are just because Geany has done such a darn good job of using scintilla while gedit hasn't done such a good job of using gtksourceview :-)
On 12/16/2013 10:46 AM, Matthew Brush wrote:
My experience is exactly opposite. GSV feels natural in GTK+ since most of its API is directly inherited from the existing GtkTextView widget and the rest of its API is very idiomatic. Scintilla's GTK+ backend, without going into a huge rant, has quite possibly the worst, most foreign API to ever be unleashed on the world.