The general answer to this is to use the 'source-httpd-config' Generator
job, but this is not yet available in the 2.1.x line of qooxdoo. So I'm
afraid you need to do it by hand. See this manual entry
http://manual.qooxdoo.org/devel/pages/desktop/develop_how_to.html#running-the-source-version-through-a-web-server
(specifically the section "Rolling your own"). The basic idea is to
configure your web server with an alias path that is "high enough" on
your file system to include all qooxdoo libraries that go into your
source application.
If you have the chance make a second qooxdoo install by checking out the
Git repo, create a desktop skeleton with it and run 'generate.py
source-httpd-confg' in the skeleton. It will create a web server
configuration file (type of web server is configurable) that you can
include in your main web server configuration. It will define an alias
to a suitable file system path on your machine from where all relative
URLs within the qooxdoo application will work. You should be able to
adapt this config file to your normal qooxdoo 2.1.1 installation so you
can continue to work with your normal environment. (If you place the git
repo alongside your 2.1.1 installation and the desktop skeleton
alongside your normal app in the file system, this will be allmost trivial).
T.
On 05/13/2013 01:48 AM, rips...@hushmail.com wrote:
Hi,
I am developing a qooxdoo desktop GUI that is an integral part of
bigger enterprise application. That's why all the contents is served
by an application server, and testing it as file:/// is not possible.
Generally, the application runs OK, with the exception that it can't
load minimize/maximize/close icons for a qx.ui.window.Window. Server
log shows me that the application tries to access
http://localhost:8080/qooxdoo-2.1.1-sdk/framework/source/resource/qx/decoration/Simple/window/*.gif.
Obviously, qooxdoo framework sources are not served by an appserver,
and shouldn't be. I can workaround this by copying missing resources
into <myapp>/source/resource/qx/* and patching
libinfo.__out__.qx.resourceUri in the generated
source/script/myapp.js, but of course this is a hack that will only
work until next generate action is called (that means, until I
add/remove a class or make similar modification). Is there any
standard way of how to deal with this issue? The build version is not
affected, but obviously it can't use it for development. For the
source version, I'm using ./generate.py without arguments, that means,
I'm building source-hybrid; in other cases (source and source-all), it
will try to pull _all_ the qooxdoo classes from the server, not only
the resources.
Thanks in advance!
Ripston
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their applications. This 200-page book is written by three acclaimed
leaders in the field. The early access version is available now.
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their applications. This 200-page book is written by three acclaimed
leaders in the field. The early access version is available now.
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
