Thank you for the answers. Sounds reasonable to do it like this but
thinking of a scenario, where I have a central server for the complete
development team where the rpc part for example is maintained by other
people than me, I'd like to update all my stuff into the docroot for
testing the application. I don't have the chance to run any python on
this server too.
I'm wondering if it would make sense to have a debug build like the
source build, but with anything needed to run like in the release build.
This would make it possible to compile on my development machine and
copy the application to the host server and test it in my browser. This
could be another option for the generate script e.g. "debug" or something.
Nevertheless this works for me now.
Connor.
Am 22.05.2012 12:14, schrieb John Spackman:
> Hi Connor
>
> When you created you app with create-application.py, it detects where
> the Qooxdoo installation directory is and generates a relative path to
> it; you need to make sure that your application folder, and qooxdoo,
> and every path in between is available via the web server's root. If
> your app is at http://localhost:8080/myapp, try moving qooxdoo folder
> to http://localhost:8080/qooxdoo and edit myapp/config.json to change
> the "QOOXDOO_PATH" macro to "../qooxdoo" and re-run generate.py.
>
> John
>
> From: Connor <[email protected] <mailto:[email protected]>>
> Reply-To: qooxdoo Development <[email protected]
> <mailto:[email protected]>>
> Date: Tuesday, 22 May 2012 08:23
> To: qooxdoo Development <[email protected]
> <mailto:[email protected]>>
> Subject: [qooxdoo-devel] Debug source and rpc-server cross-domain trap
>
> Hi,
> Usually I test my qooxdoo application with a source build (source-all)
> by loading it from a file. This is great because I have uncompressed
> JS classes.
> Now I've learned that I need to open my application in the same
> location (apache) for testing my rpc-calls to avoid cross domain
> requests. This seems to cause problem with the source build because
> classes are not found by the server:
>
>
> "NetworkError: 404 Not Found -
> http://localhost:8080/source/class/sdxtest/theme/Color.js?nocache=0.6859094274812332";
> Color....4812332
>
> Is there a "best practice" for this case ?
>
> Thanks,
> Connor
>
> ------------------------------------------------------------------------------
> 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]
> <mailto:[email protected]>
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
> ------------------------------------------------------------------------------
> 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
------------------------------------------------------------------------------
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
