> After writing, I found this section of the manual:
>
> http://qooxdoo.org/documentation/1.0/ui_resources
>
> which helped answer my questions. I ended up copying the files I wanted
> inside my own resource section, but the "libraries" job of the
> config.json is not explicitly mentioned there and sounds like it would
> be simpler. Would you (or anyone else who knows what thron7 is speaking
> of) be willing to add a short example of this to that page? this might
> work as a fourth option under the "Using qooxdoo icons with widgets"
> section.
First off, let me re-state the "everything-is-a-library" mantra. Your
application has a library structure, the qooxdoo framework classes are
(obviously) provided as a library, and any other qooxdoo contribution or
application created with 'create-application.py' can act as a library.
To create a runnable script classes and resources are drawn from the
involved libraries. All the standard jobs like 'source', 'build' etc.
use two libraries to work with by default, namely your application and
the qooxdoo framework. This is the reason why you don't have to do
anything special when using images from the qooxdoo framework - this
library is automatically considered, and this is the reason why there's
no fourth option in the "Using qooxdoo icons with widgets" section. The
second and third option both rely on the fact that the qooxdoo library
is known! And if you just want to use some icons from there, this is the
way to go.
But if you want to use resources (or classes, for that matter) from a
third library (be it something you wrote yourself, a contribution from
contrib.qooxdoo.org, or other third-party qooxdoo lib), you have to make
these libraries known to the build process, additionally to the two
default libs. The easiest way to do this is to override the "libraries"
job, as hinted at in the config.json of every gui skeleton
(create-application.py -t gui). The "jobs" section there starts like this:
"jobs" :
{
// Uncomment the following entry to add a contrib or library to your
// project; make sure to adapt the path to the Manifest.json; if you are
// using a contrib: library, it will be downloaded into the path
specified
// by the 'cache/downloads' config key
"libraries" :
{
"library" :
[
{
"manifest" : "contrib://SkeletonApplication/trunk/Manifest.json"
}
]
},
The example given here refers to the case that you want to use a contrib
lib directly from the qooxdoo contrib repository, but the principle is
the same when using local libs, just replace the "contrib://..." string
with a proper path to its Manifest.
HTH,
T.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
