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
|
Is it possible to package the WebWorkbench compiler into a standalone executable (and without installing Ruby)? It already exist for the .Less files (with the dotLess project) and CoffeeScript, but not for Sass, which is I think a big lack for this metalanguage. I am a front-end developer and I use WebWorkbench every day. But I think that the possibilities to also compile Sass files without installing nothing more (like Ruby or WebWorkbench) would be a big plus. Especially for other persons who are working on the web project, but only occasionally on the front-end part. Or in the case where we deliver the source codes to the customer. So for example we could kick off the executable compiler as a build task, or with a PowerShell script (would be very useful in the case of a SharePoint project). Additionally, a person who making a fresh installation of the solution could both compile the project and the SASS files, without having to install third applications. For example: Thanks a lot (and sorry for my English). |
|
|
We have begun some internal work towards breaking out the compilers and it's possible this will lead in future to standalone compilers, but we are more focused on tooling. So we can't make any promises about whether we would do this. That's a good point about making solutions self-contained though -- we like to work that way too! |
|
|
Thanks for your reply, I understand and appreciate a lot the improvements on the latests WW 2 and 3. So I cross my fingers hoping that the standalone compiler will become a reality. |
|
|
Standalone compiler can be a product on its own. I would love to use it with ASP.NET Bundling. |
|
|
I'm also agree. Ideally, I think the compiler on the build server and the one we use in Web Workbench should be the same. |
|
|
I see guys that you are trying to sell tooling and I'm more than happy to pay for it but the current solution of having both SCSS and CSS files in the repo might cause a lot trouble. Let me explain what I mean by that.
That's why compiling all scripts is required either as part of the app startup or the build process. I hope this gives you a few more arguments when you talk to your Product Manager :). This feature is a must have unless you can solve the above problem in a different way. Thanks Pawel |
|