Hi Kenny,
see my comments below.
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.
>
> Does this ring a bell for anyone?
Yes it does :)
The issue you describe is a bug which will be fixed with the upcoming
0.8.1 release. The problem is that currently (with 0.8) you do not have
an easy approach to change the URI's of your source version.
You'll run into trouble because the paths at the file system are not
identical with the setup of the paths of your HTTP server.
qooxdoo computes the paths (=URI's on the web server) automatically, so
the path "/source/class/custom/Application.js" is correct when running
your application with the "file:///" protocol, but it fails at your
web-server just because the setup is different. There is no path like
"/source/class/custom/Application.js".
The "URI handling" is nicely described by Thomas at
http://qooxdoo.org/documentation/0.8/generator_config_articles#uri_handling
so just take a look at it and tell us if it's the documentation you
searched for.
I'll come up with more documentation soon describing different setups as
examples to clear up things even more.
cheers,
Alex
------------------------------------------------------------------------------
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
