Re: [rgui-dev] RE: Backend Debouch

[Kero van Gelder]

> NOTICE TO ALL GUTOPIANS: THIS IS AN IMPORTANT THREAD, SOME ADDITIONAL
> INPUT WOULD BE VERY USEFUL. PLEASE EXPRESS YOUR OPINION AS THIS COULD
> FUNDEMENTALLY CHANGE HOW WE PROCEED.

> okay that makes more sense. so what we're getting at here is simply a
> matter of using SWT C source versus using Ruby-Gnome, SWin/VRuby, and
> RubyCocoa/RubyAEOSA. SWT gives us a couple of others too: Motif and
> Photon, but we'd have to figure out how to address ParaGUI and possibly
> Wise if Kero gets it multi-platform capable.

Ruby-Wise could build on graphics engines (i.e. framebuffer + some
event mechanism should work, too). Though Ruby-Wise could build on
toolkits like gtk, too, it's current architecture does not readily
support that.

Now if I understand everything correctly, SWT is built on
toolkits. That's distinctly different and would give Ruby-Wise its own
place, aimed for smaller systems (less libraries).

> * who will do the "JNI" C translation for Ruby. i fear it is out of my
> league, as i haven't used C for over 10 years.
> 
> * if we use SWT who will build the respective GUtopIa backend
> interfaces? I can hadle one of them (GTK's) while i hammer out the the
> primary meta-api, like i'm doing presently, but not all.
> 
> * how do we integrate ParaGUI, Wise, or other backends if we use SWT?

Answered above, w.r.t. Wise.
If ParaGUI covers 3D stuff, that has its own place, too.

> * finally, is licensing an issue?

+--- Kero ------------------------------ address@hidden ---+
|  Don't split your mentality without thinking twice       |
|                          Proud like a God -- Guano Apes  |
+--- M38c ---------- http://httpd.chello.nl/k.vangelder ---+