What juggling? I simply do a build, place the resulting two js files in my
main folder on the server and make sure that the resource folder (and
possibly the icon folder, I don't remember) is also in that directory and
you should be ready to go. I have never had an issue with paths.
Jim
On Wed, Dec 10, 2008 at 10:08 AM, Kenny Tilton <[EMAIL PROTECTED]>wrote:
> Kenny Tilton wrote:
> > Sorry for a weird report but we have a vital demo in 24hrs and my
> > qooxdoo setup has stopped working. No idea what I did moving things
> > around. It is probably not a qooxdoo issue, but I am desperate so I am
> > sending up a flare. here goes:
> >
> > 1. I am using qooxdoo downloaded just now from qooxdoo trunk, but I see
> > this as well with the SDK and older downloads.
> >
> > 2. The issue manifests itself with the tutorial "custom" hello world
> > example.
> >
> > 3. If I follow the tutorial and double-click the index.html it works
> fine.
> >
> > 4. Now I start up my Lisp HTTP server and aim the browser at
> localhost:9000
> >
> > 5. This fails because the Lisp server does not find the qooxdoo tree.
> > What has worked in the past is copying that into the source directory.
> > That then lets the server find everything until a bunch of requests like
> > this come along, as echoed by the server:
> >
> > 127.0.0.1 - - [Wed, 10 Dec 2008 16:09:14 GMT]
> > "GET /source/class/custom/Application.js HTTP/1.1" 404 233
> >
> > If it was asking for /class/custom/Application.js it would work.
> >
> > I have tried giving the server the location of qooxdoo instead of
> > copying the whole thing into source. That works but then fails on the
> > same thing: not finding all the app specific stuff because of the
> > "source" prefix (at least as far as I can understand).
> >
> > Mysteries:
> >
> > 1. I do not get the "source" prefix, since later this will be running
> > under "build". but...
> >
> > 2. browsers have no trouble with the source prefix... do they just try
> > searching upwards?! :)
> >
> > 3. The same set-up used to work, no idea how I screwed things up.
>
>
> 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.
>
> Meanwhile, my various experiments indicate qooxdoo is creatively
> assembling paths on the fly, so as I try to make the server happy by
> moving things or publishing directories for it to search qooxdoo ends up
> still asking for something the server cannot find.
>
> 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. I did
> not realize that at the time so I started poking and prodding and
> restoring to backup copies of the app itself until I was /really/
> screwed. :)
>
> qooxdoo roolz, but this dynamic/hardocde directory juggling seems a bit
> brittle.
>
> cheers, ken
>
>
> ------------------------------------------------------------------------------
> 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
>
------------------------------------------------------------------------------
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
