I am trying to work with nodejs, the browser-based Cloud9 IDE and qooxdoo,
which seems to be a good fit in general. However, qooxdoo toolchain's
dependency on python scripts doesn't fit this approach. 

Currently, I can edit files and run the app from Cloud9 as long as the class
tree doesn't change. But when it does, I need to sync my project to GitHub,
update a clone on my Desktop, run the generator there, update GitHub, and
finally the clone in Cloud9. 

Did you ever consider porting the generator to javascript, to run on top of
an abstraction layer that would allow it to be used with nodejs, Rhino, and
file-access enabled HTML5? Of course, this would by itself solve my
particular problem, as it still would have to be integrated into Cloud9 as a
plugin. 

Regardless of my particular use case, though, wouldn't it make sense,
eventually, to shift to a javascript-only paradigm, which would probably
help adoption. The ability to run the generator in the browser, if only for
demonstration purposes (on-the-fly generation of optimized code that could
be stored in a browser storage). And I wonder about speed improvements, too. 

Nothing I would open a enhancement bug about, but interesting to consider in
the long term, don't you think?

Cheers,
Christian 

--
View this message in context: 
http://qooxdoo.678.n2.nabble.com/qx-toolchain-in-the-browser-tp7391511p7391511.html
Sent from the qooxdoo mailing list archive at Nabble.com.

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to