> Ok. �ow do I set prefix for qooxdoo paths that qx.$$libraries
was like
> this
> {"__out__":{"sourceUri":"/qxapp/script"},"myapp":{"resourceUri":"/qxapp/resource","sourceUri":"/qxapp/class"},"qx":{"resourceUri":"../framework/source/resource","sourceUri":"../framework/source/class"}};
Which version should that be? - I suppose "source".
Well, this is something completely different to what you asked in your
other mail. Why do you want to enforce an absolute URI path for your
"myapp" library (which I wouldn't recommend)? Are you trying to run your
source version from a web server?
You cannot control the "__out__" library, as it is generated. What you can
do is adding a "uri" parameter to your myapp's "library" config entry,
e.g. like this. In the "jobs" section add
"libraries: {
"library" : [
{ "manifest" : "./Manifest.json",
"uri" : "/qxapp"
}
]
}
But even this will not achieve what you want, as the library's Manifest
settings are always taken into account, so the above "library" key would
e.g. lead to
{"myapp":{"resourceUri":"/qxapp/js/resource","sourceUri":"/qxapp/js/class"}...
It will all become much easier if you allow URIs relative to your
index.html, like
{"__out__":{
"sourceUri":"./js/script"},
"myapp":{
"resourceUri":"./js/resource",
"sourceUri":"./js/class"},
...
}
as this would be auto-generated from your config with just
compile-options/paths/app-root being adapted.
T.
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
