[Gambas-devel] for future gambas development

José L. Redrejo Rodríguez jredrejo at ...101...
Sun Aug 20 13:10:23 CEST 2006


El dom, 20-08-2006 a las 12:49 +0200, Benoit Minisini escribió:
> On Sunday 20 August 2006 11:47, José L. Redrejo Rodríguez wrote:
> > Hi Benoît. In previous emails we have talked about a future use of
> > gambas for web development, doing it as easy as it is now to switch from
> > qt to gtk.
> > I've found this toolkit that could do it possible. It's  lgpl licensed
> > and looks really promising:
> >
> > http://qooxdoo.org/about
> >
> > Regards.
> 
> Thanks for the link.
> 
> Then the big problem is how to define the interface *and* the code in Gambas, 
> and see it in the browser with this toolkit. I see no solution at the moment.
> 
> If the code is in Gambas, then all events generated by the interface on the 
> browser should be sent to the server. 
> 
> In other words, an XmlHttpRequest must be put between each GUI Gambas method 
> and the browser, and between each browser event and GUI Gambas event handler. 
> The browser can send an XmlHttpRequest to the server as needed, but I think 
> the contrary is impossible.


mmm, it's possible, take a loot at comet
(http://en.wikipedia.org/wiki/Comet_%28programming%29)
There is already a python implementation, so why not a gambas one?


> 
> In other words, the event loop must be completely managed by the browser.
> 
> Maybe by taking their code, and modifying it deeply? It is an huge job...

Using comet it shouldn't be so deeply. Anyway, we would need a
javascript/ajax/gambas expert to do such thing


> 
> Another point: their toolkit is rather slow on my Firefox, but I think we 
> cannot do anything about that. Thanks to AJAX, now we will need an AthlonX2 
> to browse the web :-)
> 

mmm, I haven't noticed it slowly, running in a 2.0 GHz pentium mobile
laptop. It's slow the first thing you access to the web page to load all
the javascript stuff, but in next accesses it goes fine thanks to the
cache. Anyway, not everybody has a 2.0 GHz microprocessor, so it should
be tested in slower machines.






More information about the Devel mailing list