1. #21
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,339
    Vote Rating
    132
    dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all

      0  

    Default


    Have you tried @import-ing them from ./sass/etc/all.scss? That file is included automatically and can pull in arbitrary things
    Don Griffin
    Ext JS Development Team Lead

    Check the docs. Learn how to (properly) report a framework issue and a Sencha Cmd issue

    "Use the source, Luke!"

  2. #22
    Sencha User mono blaine's Avatar
    Join Date
    Jul 2008
    Location
    Turkey
    Posts
    123
    Vote Rating
    8
    mono blaine will become famous soon enough

      0  

    Default


    Quote Originally Posted by dongryphon View Post
    Have you tried @import-ing them from ./sass/etc/all.scss? That file is included automatically and can pull in arbitrary things
    Thanks! You've pointed me in the right direction.

    Apparently, we cannot use the following syntax:

    Code:
    @import "../../resources/css/foo.css";
    Because @import "foo.css" is evaluated as a css import and is converted into the following form by sass:

    Code:
    @import url("../../resources/css/foo.css");
    In order to include the contents of the specified file, its extension must be "scss".

    A suggestion to handle this issue was proposed:

    https://github.com/nex3/sass/pull/442

    but it was rejected due to the fact that "sass is an extension to css and must be compatible to css and blabla" (so why have you used the @import syntax in the first place?)

    Anyway, I have come up with an ugly solution:

    As @dongryphon suggested, include your css files as @import directives in ./sass/etc/all.scss
    (File extensions must be scss)

    Code:
    @import "../../../__tmp/resources/css/foo.scss";
    @import "../../../__tmp/resources/css/bar.scss";
    Notice the relative paths: I think during the build process the current path here is "YourApp\build\AppName\production"

    Edit your build.xml file and add the following lines:

    Code:
    <target name="-before-sass">
        <mkdir dir="${app.dir}/__tmp/resources/css"></mkdir>
        
        <copy todir="${app.dir}/__tmp/resources/css">
            <fileset 
                dir="${app.dir}/resources/css" 
                includes="*.css"
                excludes="@{base}-all*.css"/>
        </copy>
        
        <exec executable="cmd" dir="${app.dir}/__tmp/resources/css">
            <arg line="/c ren *.css *.scss" />
        </exec>
    </target>
    
    <target name="-after-sass">
        <delete dir="${app.dir}/__tmp" />
    </target>
    which is,

    1. Create a temporary directory structure "__tmp/resources/css" under the root folder of your app,

    2. copy -almost- all css files into that folder.

    3. Rename *.css as *.scss

    Initially I wanted to use the css files copied by Sencha Cmd under build/xxx/production/resources/css folder, but it appears they're not copied yet during stage "-before-sass". So I manually copied them into another folder (__tmp) that I manually create during the build process.

    4. Delete __tmp during -after-sass

    That's all.

  3. #23
    Sencha User
    Join Date
    Apr 2010
    Posts
    75
    Vote Rating
    4
    HriBB is on a distinguished road

      0  

    Default


    Quote Originally Posted by existdissolve View Post
    Hi Don--

    Thanks for the reply. I guess what I'm getting at is trying to understand the best and fastest way to rapidly develop a theme, specifically the recompilation of the .scss into CSS. I've been testing sencha package build and sencha ant sass, and each process takes approximately 40 seconds for the former, and at least 15 seconds for the latter. In previous versions, I could simply add a compass watch, and compilation would be immediate, and would not require an extra action.
    Yeah, same problem here. Takes waaaay to long to build.

    +1 for a "sencha package watch"

    One way ... you could just edit "build/APP/production/resources/APP-all.css", add styles, and when you're happy, put them in "./sass/etc/all.scss" and rebuild. Of course for the stuff in "./sass/etc/var/" and "./sass/etc/src/" to work, you need to rebuild theme package.

  4. #24
    Sencha Premium Member
    Join Date
    Jul 2012
    Posts
    3
    Vote Rating
    0
    icheasty is on a distinguished road

      0  

    Default


    Same issue here, it is taking 50 seconds to run the "sencha package build" command.
    The ideal workflow is to modify the SASS files with compass watch running in the background and then to run a full build for the images once the changes are validated in a modern browser.

  5. #25
    Sencha User existdissolve's Avatar
    Join Date
    Jan 2010
    Location
    Kansas
    Posts
    522
    Vote Rating
    85
    existdissolve is just really nice existdissolve is just really nice existdissolve is just really nice existdissolve is just really nice existdissolve is just really nice

      0  

    Default


    Quote Originally Posted by icheasty View Post
    Same issue here, it is taking 50 seconds to run the "sencha package build" command.
    The ideal workflow is to modify the SASS files with compass watch running in the background and then to run a full build for the images once the changes are validated in a modern browser.
    While it still takes a bit of time, running sencha ant sass should recompile all the SASS, but only take about half the time (in my experience).

  6. #26
    Sencha User
    Join Date
    Oct 2012
    Posts
    1
    Vote Rating
    1
    AwesomeBobX64 is on a distinguished road

      1  

    Default I can't even build the themes that are included.

    I can't even build the themes that are included.


    I was trying to re-skin the Neptune theme switching from it's base color to a shade of red.
    My theme/package is called KUS. I tried building my theme/package with "sencha package build" from the packages/KUS directory and I got this error:
    Code:
    ...
    [INF] -before-js:
    [INF] executing compass using system installed ruby runtime
       remove resources/KUS-all-debug.css 
       remove resources/KUS-all-rtl-debug.css 
        error KUS-all-debug.scss (Line 539: Invalid CSS after "@import '": expected selector or at-rule, was "../../ext-theme...")
       create resources/KUS-all-debug.css 
        error KUS-all-rtl-debug.scss (Line 539: Invalid CSS after "@import '": expected selector or at-rule, was "../../ext-theme...")
       create resources/KUS-all-rtl-debug.css 
    [ERR] 
    [ERR] BUILD FAILED
    [ERR] com.sencha.exceptions.ExProcess: compass process exited with non-zero code : 1
    [ERR] 
    [ERR] Total time: 10 seconds
    [ERR] 
    [ERR] BUILD FAILED
    [ERR] com.sencha.exceptions.BasicException: com.sencha.exceptions.ExProcess: compass process exited with non-zero code : 1
    [ERR] 
    [ERR] Total time: 11 seconds
    [ERR] com.sencha.exceptions.BasicException: com.sencha.exceptions.ExProcess: compass process exited with non-zero code : 1
    I thought I couldn't have done anything wrong since all I did was create a Component.scss file in my theme/package's sass/var directory with only a $base-color setting so I decided to see if I could perform the same build operation in the ext-theme-neptune package and got nearly the same error:

    Code:
    ...
    [INF] -before-js:
    [INF] executing compass using system installed ruby runtime
       remove resources/ext-theme-neptune-all-debug.css 
       remove resources/ext-theme-neptune-all-rtl-debug.css 
        error ext-theme-neptune-all-debug.scss (Line 539: Invalid CSS after "@import '": expected selector or at-rule, was "../../ext-theme...")
       create resources/ext-theme-neptune-all-debug.css 
        error ext-theme-neptune-all-rtl-debug.scss (Line 539: Invalid CSS after "@import '": expected selector or at-rule, was "../../ext-theme...")
       create resources/ext-theme-neptune-all-rtl-debug.css 
    [ERR] 
    [ERR] BUILD FAILED
    [ERR] com.sencha.exceptions.ExProcess: compass process exited with non-zero code : 1
    [ERR] 
    [ERR] Total time: 9 seconds
    [ERR] 
    [ERR] BUILD FAILED
    [ERR] com.sencha.exceptions.BasicException: com.sencha.exceptions.ExProcess: compass process exited with non-zero code : 1
    [ERR] 
    [ERR] Total time: 9 seconds
    [ERR] com.sencha.exceptions.BasicException: com.sencha.exceptions.ExProcess: compass process exited with non-zero code : 1
    As you can see, the errors are nearly identical save for the working directories.
    My intuition tells me there's something wrong with the files that Sencha Cmd is generating for theming.

    I'm using ExtJS 4.2.0.663 and Sencha Cmd 3.1.0.256.

    I'm about to try updating the Sencha Cmd to the latest beta in the hopes that this has been fixed already but I'd like to use that as a last resort.

  7. #27
    Sencha User
    Join Date
    Aug 2012
    Posts
    15
    Vote Rating
    0
    svper is on a distinguished road

      0  

    Default


    I've been trying to get this new themes thing to work for a while now.
    I've had some success but:

    scss problem.png

    everything in the var/view folder get's included in the css file. Everything outside that var/button/Button.scss etc does not get included when i build. Why is this ?

  8. #28
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,339
    Vote Rating
    132
    dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all

      0  

    Default


    Quote Originally Posted by AwesomeBobX64 View Post
    I was trying to re-skin the Neptune theme switching from it's base color to a shade of red.
    My theme/package is called KUS. I tried building my theme/package with "sencha package build" from the packages/KUS directory and I got this error:
    How is your package stored in relation to the SDK? The message implies that the package and the SDK are not in the expected relative path.

    Have you followed the steps in the theme guide - http://docs.sencha.com/extjs/4.2.0/#!/guide/theming to get your workspace and theme package started?

    Quote Originally Posted by AwesomeBobX64 View Post
    I decided to see if I could perform the same build operation in the ext-theme-neptune package and got nearly the same error:
    Yes, there is an issue with re-building the themes in the SDK because of how they are built before being placed in the ZIP we deploy so the error sounds the same but not something in Cmd rather in the themes themselves.
    Don Griffin
    Ext JS Development Team Lead

    Check the docs. Learn how to (properly) report a framework issue and a Sencha Cmd issue

    "Use the source, Luke!"

  9. #29
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,339
    Vote Rating
    132
    dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all

      0  

    Default


    Quote Originally Posted by svper View Post
    I've been trying to get this new themes thing to work for a while now.
    I've had some success but:

    Attachment 43166

    everything in the var/view folder get's included in the css file. Everything outside that var/button/Button.scss etc does not get included when i build. Why is this ?
    The issue is with the namespace associated with the Sass in your app. By default, the app.sass.namespace variable (defined in .sencha/app/sencha.cfg) specifies your application's namespace. This means that only classes in that namespace will be considered.

    To style the Ext namespace *and* your application namespace, you could go one of two ways:

    1. Set app.sass.namespace to blank to allow your Sass to target the global namespace. This will require that you create an "Ext" folder in your ./sass/var and ./sass/src folders as well as a folder with the name of your application's namespace.

    Code:
        sass/
            var/
                Ext/
                    button/
                        Button.scss
                App/
                    view/
                        Viewport.scss
    2. Make a theme package for the Ext namespace and keep that separate from your app. For packages, their equivalent package.sass.namespace defaults to Ext and the folder structures you have would remain like you have them just some files would migrate to the theme package.
    Don Griffin
    Ext JS Development Team Lead

    Check the docs. Learn how to (properly) report a framework issue and a Sencha Cmd issue

    "Use the source, Luke!"

  10. #30
    Sencha User
    Join Date
    May 2012
    Posts
    2
    Vote Rating
    0
    chrisjunkie is on a distinguished road

      0  

    Default


    Following on from what mono blaine

    has said, I got this to work on OSX by putting the following in my build.xml:

    Code:
        <target name="-before-sass">
    	    <mkdir dir="${basedir}/__tmp/resources/css"></mkdir>
    	    
    	    <copy todir="${basedir}/__tmp/resources/css">
    	        <fileset 
    	            dir="${basedir}/resources/css" 
    	            includes="*.css"
    	            excludes="@{base}-all*.css"/>
    	            <mapper type="glob" 
              from="*.css" to="*.scss"/>
              
    	    </copy>
    	    
    	</target>
    
    
    	<target name="-after-sass">
    	    <delete dir="${basedir}/__tmp" />
    	</target>
    Hope this can help someone

Turkiyenin en sevilen filmlerinin yer aldigi xnxx internet sitemiz olan ve porn sex tarzi bir site olan mobil porno izle sitemiz gercekten dillere destan bir durumda herkesin sevdigi bir site olarak tarihe gececege benziyor. Sitenin en belirgin ozelliklerinden birisi de Turkiyede gercekten kaliteli ve muntazam, duzenli porno izle siteleri olmamasidir. Bu yuzden iste. Ayrica en net goruntu kalitesine sahip adresinde yayinlanmaktadir. Mesela diğer sitelerimizden bahsedecek olursak, en iyi hd porno video arşivine sahip bir siteyiz. "The Best anal porn videos and slut anus, big asses movies set..." hd porno faketaxi