[Aeditor-talk] transition from 2003 into 2004

[Simon Strandgaard]

On Sun, 2004-01-04 at 13:34, Mark wrote:
> On Monday 29 Dec 2003 3:01 pm, Simon Strandgaard wrote:
> <snip lot's of interesting stuff about the state of Aeditor>
> 
> >
> > Hopefully a nice GUI frontend will be added. Opinions needed to which
> > GUI-toolkit I should choose?
> >
> 
> I would recommend using a toolkit which available along with Ruby. Which means 
> either TK, which is part of the standard library, or Fox, which at least is 
> part of the windows installer.

Did not know that fxruby are shipped with the windows installer?   Thats
cool, that will affect the outcome of this question. 


> I don't do much GUI programming but having experimented with both of them I 
> think that Fox has a cleaner API.
> 
> Also AFAIK FreeRide uses Fox, so that would make your next point easier.
> 
> > Maybe embed the Aeditor widget into FreeRIDE ?
> >

Yes Fox has a much cleaner api than TK. Actually its cleaner than many
other gui toolkits. Making custom widgets are less complex than
elsewhere.

Yes FreeRIDE uses fxruby.

Though I see a few problems with fox:
* no unicode, no i18n. Will have to wait until version2.
* fox doesn't use font rendering done by the X11-server, so no anti
aliasing. 

A solution could be to render the widget myself, by using freetype and
operate with unicode inside the widget. This is a thought which keeps
coming back.. I guess this will become the future.


OTOH Gnome/Qt has unicode and antialiasing. But gnome api are nasty and
qt license sux.



BTW: The new regexp-scanner routine are almost done. The only problem
remaining are nested repeats /x((.)*)*x/, which I hope to solve soon.
Its deals much more efficient with repeats than the previous routine.
The previous routine had a conceptualy broken backtracking routine,
in the new routine it of cause works. 
I will let you know about its progress.

--
Simon Strandgaard