Jean-Baptiste BRIAUD -- Novlog wrote: > Congratulation ! I like LISP :-)
:) > > Just curious : > On software architecture point of view, you may not use all the power of > client-side CPU. > Why did you use server-side CPU to produce GUI ? > GUI doesn't need to be served by server, only data has to ... Right now I am just exploring. If performance is good we have the advantage of a seamless application model vs one with the client over here and the data over there and forever linking the two with HTTP requests. So far performance looks good. btw, the client CPU /is/ serving the GUI: the server just sends over some strings (JS code) that direct the building of the GUI. If the GUI is static, no strings need get sent after start up. Startup already sends over quite a bit of code so I do not think this will stand out. Yes, once up more events get flown back to the server, but then most event handling will need data so a request (or three) happens anyway. Meanwhile, if something in particular turns out to be slow, nothing stops us from writing some JS the usual way. Kinda like the days of hand-coding assembler if the 3GL compiler could not generate tight enough code. Possibly something like tracking mouseover or individual keypresses might require this. We'll see, but even if so it will be a local optimization leaving the big win of seamless development intact. The interfaces I create tend to be dynamic and change shape as the user works and the underlying data model changes. This means the bifurcation of data and GUI is not really there: the GUI /is/ data decided by the server code in contemplation of the model data. ie, Yes, I have real problems with the classic idea of model-view in which the view is so detached from the model. It's a good dichotomy, but should not be reflected in a division of the code base into client code and server code, as I see it. But that is just rationalization: the really big win is being able to forget the client-server interface, almost forget qooxdoo/javascript, and have the whole application in one place, both for coding ease and for communication of view with model -- it's easy, they are in the same program! A Lisp program. :) cheers, ken > > On 24 mai 2010, at 21:53, Kenneth Tilton wrote: > >> Screenshots: http://github.com/kennytilton/qooxlisp/downloads >> >> Intro: http://wiki.github.com/kennytilton/qooxlisp/ >> >> Congrats to the qooxdoo team for a great product. >> >> kt >> >> -- >> http://www.stuckonalgebra.com >> "The best Algebra tutorial program I have seen... in a class by itself." >> Macworld >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> qooxdoo-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > ------------------------------------------------------------------------------ > > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.437 / Virus Database: 271.1.1/2895 - Release Date: 05/25/10 > 06:26:00 > -- http://www.stuckonalgebra.com "The best Algebra tutorial program I have seen... in a class by itself." Macworld ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
