On 01/12/2011 06:03 PM, Stefan Andersson wrote:
> Thanks Thomas for your answer!
>
>> This is generally not the case. All resources, from whatever
>> library, are referenced by their so called "resource id", which is
>> a globally unique identifier. Resource id's always start with the
>> library's name space, so you have to make sure that app 1's
>> resources are stored under "source/resource/app1/..." (or some
>> other name space identifier). Then you can refer to them from any
>> library with e.g. "app1/icons/smile.png".
>
> we do this and it works if the resources is only in "app"
What does 'only in "app"' mean? Is the resource file physically in the
app library? Which name space does its path reflect, is it
app/source/resource/app/...
or
app/source/resource/app1/...
? If you add resources to a library (like app), with a *different* name
space than the library has itself, you are shadowing the respective
resources from the original library, so you should only do this if you
want to achieve exactly this shadowing.
Otherwise, a resource "app1/foo/bar.png" should be located in
app1/source/resource/app1/foo/bar.png
and if you include app1's manifest in a another application, you should
be able to reference app1/foo/bar.png in this application alright.
If this is not the case, in the browser look into Firebug or similar to
find out which uri the client is trying to load when the resource is
being used. We can work from this onward.
>
>> The other thing you might be stumbling over is qooxdoo's
>> AliasManager, which allows you to use aliases for resource id's,
>> which allows to shorten them and abstract away e.g. the theme in
>> effect. So you will see code like this:
>
>> new qx.ui.form.Button("My button",
>> "icon/22/actions/edit-clear.png")
>
> We use the AliasManager and we have posted a code addition to comply
> with it and url generation qx.data.store.Json too.
So I presume this answer means you are not using any resource aliases
that are not resolved.
> If I understood you correctly the "run" directive of the generator
You mean the "run" config key?!
> use the local ("app 1" and "app 2") resource code?
I'm not getting this. The "run" config key just invokes other jobs.
Resources are found through their id's. "app 1" and "app 2" would not be
legal in resource id's, as they contain blanks where the segments of
resource id's have to be valid JS identifiers (for compatibility's sake).
> Where is the local data, like paths et, saved? in respective package
> or in the boot package?
Again, I'm not getting this. Uri's, or their components, are saved in
the loader package of an app. In the source version, they basically
reflect the relative paths to the libraries on disk. In the build
version, all resources are copied to the build directory, so there is
essentially only one root path to them.
T.
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
