On 09/23/2011 04:46 PM, Seldaiendil D. Flourite wrote:
2011/9/22 thron7 <[email protected]
<mailto:[email protected]>>
To use a library, you always have to do two things:
1. Make the library known to the build system.
This is achieved by providing a corresponding "library" key in
config.json, e.g.
"libraries" :
{
"library" :
[
{
"manifest" : "path/to/library/Manifest.json"
}
]
}
In your case, the "manifest" entry would probably be something
like "../eyeos-qx/Manifest.json".
Yes, I did it, but it was ignored because this namespace was already
existing in another library (qooxdoo library), with ./generate.py -w
build it said:
- Skipping duplicate library "qx"
Ah, ok. See, each library has to have its own name space, so they must
be distinct. But they can have common root elements.
So when you create the library for you eyeos-qx library, you could do
this with
create-application.py -n eyeos-qx -s qx.ui.decoration
which will create a top-level directory "eyeos-qx" and a library in it
with name space "qx.ui.decoration". This is a name space distinct from
"qx", although they share the same root "qx". In another project, you
could have e.g. a library with name space "foo.bar" and another with
"foo.baz" and a third with "foo.baz.boing" etc. Of course it is a bit
confusing in you special case to have a library name space that is also
a "sub-name space" of the qx library; I would have probably used
something more distinct, like "qx.eyeos.ui.decoration" or similar, if I
wanted a shared root with the framework.
Having said all this, it means it should work. But I would never
*recommend* to duplicate qooxdoo framework name spaces as a name space
for a library! Why not stick with something much more distinct (and
unambigous) like "eyeos.ui.decoration"?!
2. Refer to resources from the library, e.g. by using its classes
in the code:
var a = new qx.ui.decoration.RoundBorder();
or referencing them in the "include" config key.
I did it, thats what it says I was referencing a unknown global symbol:
Yeah, that was certainly a follow-up issue.
I will answer more in a separate mail, so you can work on this in the
meantime.
T.
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
