> I had  the folder qooxdoo-2.0.1-sdk (as extracted from
> qooxdoo-2.0.1-sdk.zip) in a folder called qooxdoo in the localhost folder
> (C:\Users\cuningham\Documents\localhost which is the root of the
> webserver) on my desktop. I ran into a problem with an application so I
> tried to start from scratch by renaming the application folder (which was

Which problem was that? Was it path-related?

> also in the qooxdoo folder) and running
> "qooxdoo-2.0.1-sdk\tool\bin\create-application.py -name=HelloWorld" with
> the current directory being the qooxdoo folder. I ran "generate.py
> source-all" which completed successfully, but the new application would
> not load properly in the browser.

What was the issue? Which exact error would you get in the browser
console? Did you check that all source file were loaded?

>I found this line in the config.json
> file:
>
>                     "QOOXDOO_PATH" :
> "../../../../../../users/cuningham/documents/localhost/qooxdoo/qooxdoo-2.0.1-sdk",
>
> I could not figure out why the path was set like this so I deleted the
> entire qooxdoo-2.0.1-sdk folder and the application folder, extracted
> qooxdoo-2.0.1-sdk.zip and placed the contents in my qooxdoo folder just as
> before. I ran another create-application and found the same QOOXDOO_PATH
> in the config.json file.
>
> Where is this coming from?

I'd like to know myself. But the main point to take away here is that this
path *is correct* (although it could be simplified). We had reports about
that before, but I was never able to reproduce it with our Windows boxes.
There must be something triggering this behavior which I haven't been able
to reproduce. That being said, I'd say the loading issue is the important
problem. Whether these two are related I cannot say.

> Why did it not go back to normal after I
> deleted everything?

Why should it?! I see no reason to assume that this was a singular
accident that can be overcome by deleting everything and repeating what
you did before. Repeating doesn't usually fix things.

> Editing this path and running generate.py works, but I
> really would like to know why it is doing this.

Editing the path would only be interesting if this fixes your loading
problem. But I suspect it doesn't. I would be more interested to learn why
your app doesn't load properly after a successful build.

T.



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to