All / _why 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. My architecture for my logviewer is: pump all of the log messages over drb to the logviewer, on the logviewer app chuck the data into a sqlite db and then pull in the info required from the db to display screens of data. So, I need a background thread to load the data into my sqlite db, and I dont want it to interfere/clash with the ui thread. So, I was thinking, is there any way of loading 2 instances of MRI in a single process. If there was I could just spawn another MRI instance for my BG stuff and communicate to it via an actor pattern or something. As it stands Im giving up on MRI for this and trying out jruby since it has native threads. Help/advice much appreciated Sam
