PDA

View Full Version : [OPEN] [CMD 4.0.0.126] x-split-css generating files, but not being used



ZachG
3 Sep 2013, 7:34 AM
I posted in the general Sencha Cmd forum (http://www.sencha.com/forum/showthread.php?271250-3.1.2.342-x-split-css-generating-files-but-not-being-used), but didn't get a response.


Our index.html file includes ${app.bootstrap.css}, which does an import of ${app.out.css.path}
We're having issues in IE due to the selector limit.
It looks like x-split-css works because I have two files.

Is there a property that needs to be set so ${app.boostrap.css} will import the split files?
Or is there a file other than that we need to be using?

slemmon
3 Sep 2013, 3:49 PM
You shouldn't need to do anything on top of running the build. The index file should link to an AppName-all.css file in the resources folder that should import all of the split css files. Should look something like:



@import 'BigCss-all_01.css';@import 'BigCss-all_02.css';@import 'BigCss-all_03.css';@import 'BigCss-all_04.css';


*This was an example I did where I set the limit to 1000 and required Ext.* to ensure I had some splitting going on.

ZachG
3 Sep 2013, 6:53 PM
My THEME-all.css is all of the styles concatenated together.
We found a workaround by hooking to -after-sass and writing an ant script to find all the subfiles.

What does your build-impl.xml look like?
I'm not at work or else I'd post line

ZachG
4 Sep 2013, 4:54 AM
I updated the title with the version of cmd we're actually using.
My bad on any confusion.

ZachG
4 Sep 2013, 7:51 AM
We saw this behavior when doing a


sencha app build

When we did a


sencha package build

The -all.css was generated correctly.

Is the inconsistency between the two intentional?

slemmon
4 Sep 2013, 8:31 AM
Thanks for the report! I have opened a bug in our bug tracker.