Sam Saffron wrote:
If been writing a little logviewer gui for rails, originally I really
wanted to use shoes, but there are a few critical controls missing
(since shoes does not really target these sort of apps), namely no list
view / virtual list view, no scrollbar, no splitter. Anyway I ended
setteling for wxruby and got stuff working, to a degree.
But then I realised there is a huge issue with most mri based guis
frameworks for ruby, threading.
You mean like Java?
I have never seen a thread improve an application. If a work loop takes too
long, you should use a window timer, then split your loop up into time slices.
If a GUI must respond to asynchronous events, you should find a way to multiplex
these events together with the GUI's own event thread.
I have no idea what these systems are for Gtk+ and SQLite - and my ignorance is
itself a root problem. Threading tutorials invariably show trivial examples that
should not be threaded.
As it stands Im giving up on MRI for this and trying out jruby since it
has native threads.
How did I guess you had Java experience? (-;
