Re: coding text editor

I'm the author of a (closed source) IDE and one of the few who is not
using
the scintilla widget. I can only tell you that the stuff recommended
from steve
is old and makes a lot of features impossible or had to implement.
Texts are
not span's of characters. They are structured in lines and we should
preserve
this. Today it is not a problem to have 200.000 different strings in
memory.

Remember that text editors are really complex beasts these days if you
want
to implement different features like good folding and syntax
colorization. Text
storage management is not really important anymore because of the
GBytes of
RAM.

Even better use multiple text engines and map to them based on the
file. If i
ever have the time i will for example add a special "Brief" like
structure that
does allow to view/edit gigabyte size log files without holding more
then a few
Kilobytes in text.

But you have to ask yourself what you want to learn by doing this. If
you are
a C programmer who want to learn more about C++ i don't think this is
a good
excercise. You will run into too many real world text editing problems
that do
not help you with your intended goal.



.

Relevant Pages

  • Re: Debugger not working in Vs.net 2003
    ... I got the following log info, When I start the VS IDE with my web project, ... > The log I mentioned are under the IIS's log files, ...
    (microsoft.public.vsnet.debugging)
  • ata5.01 error messages
    ... I am getting the following error message in my log files over and over ... With all the drives I have, how can I see which one os ata5? ... ide and ide on pci. ...
    (alt.os.linux.suse)