Different output path

Hi,

I would like to see a setting for a different output path, or ideally automagical output to an accompanying directory - just like the Less.app (Mac) and the similar WinLess provide: place the .css in the sibling folder:

myproject\LESS\mystyles.less

becomes

myproject\CSS\mystyles.css

Will this be possible someday?

Thanks!

Thanks for the suggestion! Ill add this to the backlog for future enhancements. If anyone else is keen on this please let us know :)

Jeremy

Yes, please add the ability to output to any arbitrary CSS directory.

Like in our config.rb for Compass:

httppath = "/" sassdir = "." cssdir = "../css" imagesdir = "../images" javascripts_dir = "../js"

Please make this a part of the free version.

Please add this feature. It is indispensable for a clean project structure.

Thanks.

I would very much like this feature also.

I would use this feature if it were available. I agree that it is indispensable to clean project structure.

I totally agree. When using command-line, I've always customized my output-path. I actually thought this already was a common feature in the web-workbench. I'd be very grateful to see this feature enabled.

Good news - this is actually already available in WW. There is now an column available as part of the settings to customize the output path for the generated assets so you can set this there.

Jeremy

Sounds great! Is this feature available in the free edition or only in pro edition? Currently I'm using the free edition available via VS Extension Gallery. I can't see any columns for this under Mindscape -> Web Workbench Settings. I only see columns for:

• Compile
• Minify (Go Pro)
• File
• Options (enable/ disable debug info)

I can't see any options for this under Tools -> Options -> Web Workbench.

It is in both versions but it was included after the last gallery update - we are pushing out an update later today to the gallery so check again after updating :)

Jeremy

Thank you, it is there.

However, it would be nice to have a global setting for the project instead of clicking on each file to set the output directory. It is tedious (from a UX perspective) to click on each and every file, find a folder, and set it when they may all be the same. We should be able to set a base directory for the entire project and then individually override if we wish. If the base directory is set and a .scss file exists in a subfolder, then the subfolder should be created in the output directory.

We have many scss files, and it is very tedious to go through them all.

Where is the path stored? Is it in a file I can easily edit?? If so, then in the meantime I would be happier if I could c&p the output folder in a text file for each file.

Will this setting follow the project so that other devs will pick up the output path(s)?

Thanks for the feedback - we are planning to do a bit of an overhaul on the settings dialog to help with bulk operations so I will keep that in mind for those updates. For now you will need to make those changes manually. The changes themselves are persisted into the project file (if you are working with a project type that has a project file) or if you are using a Website project you will see a .mswwsettings file and the settings are stored in there. Both are just XML so you can edit them by with your text editor of choice :)

Both of those files should be in source control so yes you would be sharing them with other developers - bear that in mind if you end up using absolute paths!

Jeremy

That last comment about relative paths would be a great one if your tool supported it.

By default, your tool shows me (in the GUI) a path of ..\css BUT in the .proj file it writes:

<Content Include="scss\about.scss">
  <Compile>True</Compile>
  <Minify>True</Minify>
  **<OutputFolder>C:\projects\development\psp\MemberWeb\css</OutputFolder>**
  <CompileStyle>Nested</CompileStyle>
  <DebugInfo>False</DebugInfo>
</Content>

So, I go about fixing/editing it to:

<Content Include="scss\about.scss">
  <Compile>True</Compile>
  <Minify>True</Minify>
  <OutputFolder>..\css</OutputFolder>
  <CompileStyle>Nested</CompileStyle>
  <DebugInfo>False</DebugInfo>
</Content>

and then things don't work so well.... GUI gets confused, files don't get created. (They eventually do if I open a file and edit it back to the absolute path)

However, to make things worse, if I include a subdir like:

<Content Include="scss\manage\global.scss">
  <Compile>True</Compile>
  <Minify>True</Minify>
  <OutputFolder>..\css\manage</OutputFolder>
  <CompileStyle>Nested</CompileStyle>
  <DebugInfo>False</DebugInfo>
</Content>

it creates the css under the original folder as: scss\css\manage\global.css !! WTF

Please go back to the drawing board on this one so we don't have to hack the .proj file anymore. Let's stick with a global, base dir for all output css. That is much easier than this.

I appreciate the effort, but try to test for usability.

Thanks.

Oh, and also, don't auto-include the .css files in the project (or make it an option if you really want to). Not having the .css in the project is the reason I have .scss files to begin with!

Output paths are not working for me. It's still writing to the generated stylesheets folder. It's also not minifying and is outputting debug info, even though I've set all these things differently. I looked at the ruby config and it's not getting updated. I set it by hand for now but would like to see this fixed.

Also, could you please have the output path change dialog open to the current project's folder? It's really frustrating having to drill down to a folder from the desktop dialog.

win8/vs2012

Thanks.

It sounds like you are using Compass?

If you are then the output folder has no impact here - the folder is controlled by Compass configuration. Ill look at excluding offering an output folder option for files which will be picked up by Compass to avoid future confusion here.

Jeremy

Correct. I am using Compass.

That would be much less confusing in the meantime but it would be nice to see gui configurations for Compass at some point.