OK, I started to look at this a little more. I think it may be possible to have a demobrowser that would append the demo code into the demo tab for rendering, and then also make available the ability to edit the code and re-render the edited code. This is going to be a decent-sized undertaking, but I think it might work.
It would probably be simplest to do a kitchen-sink build when building the demo-app, so that extra javascript files don't need to be loaded for each individual demo. Also, I think it would be quite fun and interesting to have a demo editor environment complete with a server-side component. We did some Proof-of-Concept tinkering with this, and I think I can put a beta up in a few days. The goal here would enable editing of demos & saving/publishing new demos...very loosely, like a wiki-type approach. More to come... Hugh Gibson wrote: > > As you have looked into this, can you list what steps are necessary to do > this? Please give server and client details. If there is enough interest > we might end up with a user-programmed version. > > I'm particularly interested to know if the server can be bypassed in any > way. That would greatly increase the chances of this being accepted by > Fabian etc. > > This would dramatically reduce the barrier to getting started with > qooxdoo. More users implies more momentum. > > Hugh > -- View this message in context: http://www.nabble.com/Source-code-Javascript-in-online-demos---allow-edit--tp16780558p16825416.html Sent from the qooxdoo-devel mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
