This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I have been using the plugin with great sucess and I really appreciate the quick turn arounds on updates. I just had a question and was wondering if you had any suggestions for me. When I have small scss files then when I click save it takes a very small time, however my file is now about 2500 lines and so every time I click save it is now taking 20 seconds to generate -- I doubt this can be avoided, but do you have any suggestions in helping speed the process? I'm a saver so having to wait 20 seconds every time adds up pretty quickly. Also, when I make a change now and then go back to another window in visual studio then it freezes like it is saving even though I didn't save. I'm running Resharper also, if that might matter. Any tips or thoughts would be appreciated. Thanks |
|
|
Hmm, that does sound frustrating -- I know what you mean about saving all the time! Unfortunately the CSS compilation is out of our hands -- we just run the Sass compiler, which is written in Ruby and isn't blindingly fast. Even so, 20 seconds sounds very slow. We'll see if there is anything we can do at our end to improve matters but this may turn out to be a limit of the Sass compiler on the IronRuby runtime (in which case we'll try to prioritise improvements to @import handling so you can more easily split your big file into several small files). I'm not sure what would cause the 'freezing when you didn't save' effect. We run most of the highlighter on a background thread (the main exception being calculating the squigglies: this should be reasonably fast but could slow down if you are importing another file). Do you see a similar effect as you type, or only when you switch away from the Sass window? |
|
|
I figured that it probably wasn't in your hands for the compiling. The freezing effect only happens when I switch away from Sass within Visual Studio (doesn't happen, usually, if I switch to a browser and then back to visual studio). Typing doesn't seem to produce the freezing. I will probably just try to change my workflow a little and split the files up more so as not to have such large ones to have to compile. Thanks for the reply |
|
|
also I was going to mention that it only happens when the document is unsaved. If it is saved, then I can move between windows fine. |
|
|
I do have the same problem; switchin windows from an unsaved .scss file will free Visual Studio for about 14 - 20 seconds, soooo killing for efficiency and coding performance :( Step to reproduce
Sounds really weird. Although it takes a long time, I don't mind waiting 15 seconds when saving the file, but when it freezes everytime you change window ..... very annoying. Somebody knows the cause, a workaround or the solution? Maybe there is a feature to regenerate the .css onsave only? I am using Visual Studio 2010 Ultimate with SharePoint templates and AnkhSVN (subversion) plugin. Thanks in advance, |
|
|
Hi Markuz, Thanks for the information. We'll keep trying to reproduce this. Regarding regenerating the CSS on save only, that is what it should be doing -- it should definitely NOT be regenerating whenever you switch file. Is this what you're seeing? E.g. if you create a trivial SCSS file, save it (to generate the CSS), then make a change in a value (e.g. 10px -> 20px), switch away WITHOUT saving, and examine the generated CSS, do you see the change? If so, please let us know! |
|
|
Hi Ivan, I can confirm that the .css is regenerated when I swith window with an unsaved edited .scss file as origin. When I open and change the .scss (without saving), my sourcecontrol tells me (after the freeze) that the .css is 'checked out / edited'. Also I do see my additional statement in a class in the .css that I added to the .scss (without saving). Thanks, |
|
|
Hello. I think the compiling time is slow on the IronRuby implementation. This makes me sad, since the other plugin required the hassle of starting the sass background daemon. :( |
|
|
Yeah, I can confirm what Frexuz is saying. Currently running a 2500+ line Scss file which takes over 10 seconds to compile. Just as a test I installed & configured Ruby + Compass in my project directory which compiles the same files in about half a second or less. Looks like IronRuby has some serious issues compiling large stuff. Hope someone can find a solution to this, otherwise I'll have to look into integrating Compass, because currently it's getting more frustrating every day. |
|
|
Hi Pleunv, Could you email us your Scss file? Would just be great to have such a large file as part of our test suite. Just email it to jd@mindscape.co.nz or attach it to this post. Also, awesome avatar picture :-) We're looking at all areas of the Web Workbench for improvements. Cheers! |
|
|
Hi John, Did you find a solution yet? Do someone did sent you an example .css already to test with? Mark |
|
|
No, nothing yet. Nobody has sent me anything. |
|
|
I think he might have meant me frexuz :-) No I didn't receive any files. If you guys are having issues with particular files please do send them through to me with details: jd@mindscape.co.nz or support@mindscape.co.nz and we'll investigate. We have switched over how compilation occurs in recent versions (new JS engine in V2 onwards) so the speeds should be faster, but if you're getting crashing issues we're happy to help dig further. Start by firing us your source files to test locally. Cheers, John-Daniel Trask |
|
|
Hi John, I have the Web Workbench Pro 2.0.371.18852 and saving a Sass file is too slow. I'm using VS2010 ultimate, Win7 Ultimate 64 on a 12 GB Core i7 920, and it takes 20s or more and 40% CPU. It's very unusual any process taking so much CPU here :) Thanks, Wagner |
|