> I seem to have found a work-around: always build. The Lisp server finds
> stuff then, I guess because qooxdoo is resolving everything during the
> generate and putting it one place.
>
That's right. But you can use the source version under a web server if
you follow my rule of thumb from the other reply.
> I also noticed that the generate.py created for an application hardcodes
> a path back to the real generate.py, which is how I got into this mess
> -- I cleaned up what I thought was a stray copy of qooxdoo and it turns
> out that was the copy from which I had generated my application.
My recommendation would be to not use generate.py at all. Add
{qx}/tool/bin to your PATH, or define a straight shell alias to
{qx}/tool/bin/generator.py.
> qooxdoo roolz, but this dynamic/hardocde directory juggling seems a bit
> brittle.
>
The basics are easy:
- "source" version: all files are referenced through URIs using relative
paths.
- "build" version: all files are copied/merged under a common root (the
"build" directory), so no references escape this tree.
That means among other things: You can copy/move around the build
version. You can only deal with the "convex hull" of all involved paths
in the source version.
Thomas
>
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
