Building Themes with Sencha Cmd 3.0.0.250

[mysticav]

Using Sencha Cmd 3.0.0.250, and ExtJS 4.1.1a
This is very confusing.

The docs say:

cd /path/to/MyApp
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:

[public]/build/resources/images/mytheme

and even more confusing,
When I run:

sencha theme build mytheme

The images are created as:

[public]/build/MyApp/resources/images/mytheme

(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:

[public]/resources/css/mytheme/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:

[public]/resources/css/mytheme/app.css

and is looking for images at:

[public]/ext/resources/themes/images/default

But I would expect the CSS to point to:

[public]/resources/css/mytheme/

or

[public]/build/resources/images/mytheme/

Currently there's no guide that can clarify all these issues.

Seems that te most updated guide is this:
http://docs.sencha.com/ext-js/4-1/#!.../command_theme

But again, not clear and inconsistent.

[amoathou]

I agree. It would be nice if the documentation was updated so it wasn't so confusing and was accurate.

[mysticav]

Or at least, if someone can post a tutorial about the whole compiling process with Cmd .250

[ldonofrio]

This in a pain. I ended up editing utils.rb to put the images where i want

[stewardsencha]

Mind sharing your edits?
I failed at ruby.

[dongryphon]

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.