On 10/20/2010 05:55 PM, Andy Fuchs wrote:
> BTW: Could you explain what all these 'prefixes' mean? It now works through
> try and error, but I don't really understand what I'm doing :-/
If you look into the generated .meta file, it might dawn on you :). The
strings that identify images in there, so called "resource ID's", can
only be inferred from the file path if the generator knows where to
"chop off" a prefix path that doesn't belong to the ID. That's the whole
issue about the prefixes. (You can even have the generator cut off a
prefix from the path, and replace it with some substitute, to arrive at
a proper resource id).
Resource id's are used throughout qooxdo code to refer to images, css
files and such. They have to be "globally unique" in the scope of the
application (i.e. all code including application code, framework
classes, and all used qooxdoo libraries and contribs). Therefore, all
resource id's start with the name space of the library they belong to,
like "qx/*" for resource id's from the framework, or "myapp/*" for a
custom application called "myapp". Then the remaining path up to the
file name ensues, like they are usually stored under the
"source/resource" folder of a qooxdoo app.
To keep things "simple" and allow you to combine images in arbitrary
paths on your file system, you have to specify the prefixes for the
cut-off. The alternative would be to force all involved images to be
under some qooxdoo library's source/resource path when combining them,
which seemed to be too much restriction at the time the feature was
implemented.
>
> The info in the manual is not very enlightening here...
>
> "images" :
> {
> //OK - this is where the combined file is saved
> "${THEME_PATH}/button-combined-tb.png":
> {
> //??
> "prefix": [ "${THEME_PATH2}" ],
Chop-off prefix for the result (combined) image.
> "input" :
> [
> {
> //??
> "prefix": [ "${THEME_PATH2}" ],
Chop-off prefix for this group of input images.
> "files" :
> [
> // this is were the source files are located...
> "${THEME_PATH2}/button-[tb]*.png",
> "${THEME_PATH2}/button-pressed-[tb]*.png",
> "${THEME_PATH2}/button-disabled-[tb]*.png",
> "${THEME_PATH2}/button-focused-[tb]*.png"
> ]
> }
> ],
>
So, in this (I hope made-up) example, ${THEME_PATH2} would be stripped
from the result image path to derive its id, assuming that THEME_PATH2
is a proper substring of THEME_PATH, as otherwise
"button-combined-tb.png" IS NOT a legal resource id.
In the same vein, for the input images THEME_PATH2 CANNOT be a valid
prefix, as when stripped from the input file path, the remaining path
like "button-t.png" cannot be a valid resource id. Therefore, the above
config would run, but would not create a usable .meta file for the
combined image.
HTH,
T.
------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
