Using Sencha Cmd 184.108.40.206, and ExtJS 4.1.1a
This is very confusing.
The docs say:
sencha theme build default
This will place the sliced images in the "./resources/css/default" folder alongside the CSS file generated by SASS. This approach reduces the size of the CSS file since all image paths are relative to the CSS file location.
That would be:
[public]/resources/css/mytheme/images go here
But it seems that it has to be:
and even more confusing,
When I run:
sencha theme build mytheme
The images are created as:
(this is not what the Docs says).
As you can see, the resources directory is inside "MyApp" directory. Not only that, based on the docs, I would expect the images here:
Please clarify. Why all this discrepancy ?
Also, when I build the css with compass compile, can you explain me howExtJS decides when to use the slices ? I guess it detects if it is IE, but then, in which path it looks for the images ?
The generated "mytheme" CSS, which is located at:
and is looking for images at:
But I would expect the CSS to point to:
Currently there's no guide that can clarify all these issues.
I apologize for the delay in replying to this thread. We are in the middle of some major work to support multiple themes in the framework for Ext JS 4.2 and have decided that we need to back-port some of that from Cmd 3.1 to Cmd 3.0.1 to resolve these issues.
In the next release we will be consolidating themes into bundles (that is, all of the pieces of a theme will be kept in a single folder) for easy sharing and path resolution...
We will be releasing 3.0.1 very soon and have taken that basic approach to solve all of these path issues. This should set things up better for Ext JS 4.2 / Cmd 3.1 as well.
And the theme guide has been updated to reflect those changes.
Please watch for the Cmd 3.0.1 notice and then check for guide updates at that time.
With Cmd 3.0.1 out, I am noticing that the new guides are not yet updated. I will try to get them pushed ASAP.
This version contains a number of important changes to theme organization that are moving towards a themes as free-standing packages model. More to come on that but the new guides should help clarify this for 3.0.1.