Re: [Beaver-devel] Patch: warning removal && TODO's

[Higor Eurípedes]

> I also looked at some libraries. Scintilla was the first (a
> collegue of mine suggested it). The problem is: it's for
> c++ so this is probably a no-go. vim uses in my knowledge
> ctags or some other crazy code ^^ i don't know how this is
> applicable on gtkTextView (since vim and joe work on the
> console level, probably with ncurses).

Both joe and vim use regex. The difference is that they use *curses
to print the colors on the screen. We can use the regex to find where
are the symbols/words that we want to highlight and create GtkTextMark
that point to do highlighting.

GtkSourceView uses regex too and its fast, but i dont like GtkSourceView
highlighting.

> the other thing is that every new library adds a dependency
> to beaver, which we want to avoid. so i came up with an
> idea some time ago, to create simple xml files (glib
> includes a small xml parsing algorithm) and to optimize the
> marking/tagging in the gtkTextView (at the moment, i think,
> this is done by looking up every possible keyword in the
> text, leading to passing through the text multiple times,
> instead of going through all the words in the text once and
> looking up if this is a keyword or not).
>
> the main feature of beaver is and should ever be, that it
> is very small (that's why damn small linux uses beaver as
> text editor).

Well, im suggesting to implement the code, not just use a library.
Maybe create a embbed libBeaver? hahaha
I know it takes time but, maybe it could be implemented in a 0.4.5 or
0.5.0 release or in the next GSOC?

Just placing highlighting code in another file is enought for now :]


-- 
Higor Euripedes (enygmata)