Hi Ripston,
The actual path from your source to the SDK is probably something like
../../../../../qooxdoo-2.1.1-sdk, which is why the server looks at
/qooxdoo-2.1.1-sdk.
The source version just references the needed SDK files with relative
paths, so those files *will* need to be served by the web server on the
same relative paths.
An easy way to do that is to map the DocumentsRoot or an Alias to a
common parent directory of your application and the qooxdoo-sdk.
For example:
your app: /aa/bb/cc/app
qx sdk: /aa/bb/libs/qooxdoo-2.1.1-sdk
Then make sure that /aa/bb/ is accessible through your web server.
---
That being said: In our projects, we are using a slightly different
approach:
1) The qx framework is stored in /usr/lib/qooxdoo-2.1-sdk.
2) Our document root looks like this:
/var/www
+ usr (empty dir)
| + lib (empty dir)
| | + qooxdoo-2.1-sdk -> /usr/lib/qooxdoo-2.1-sdk (symlink)
+ a
| + b
| | + c
| | | + theapp
3) In config.json, the qooxdoo_path macro contains an /absolute/path:
/usr/lib/qooxdoo-2.1-sdk
This way we can access any version (inclusing source) through
http://localhost/a/b/c/theapp. It does not matter how deep the path to
the app is, because the qooxdoo sdk is always available at an absolute
path (/usr/lib/qooxdoo-2.1-sdk).
I hope this helps.
Regards,
Marc
On 13-05-13 01:48, 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
