Ability to make mass changes to "Output Folder" #9

Closed
joshuairl opened this Issue Apr 5, 2012 · 6 comments

Projects

None yet

4 participants

@joshuairl

First things first, this is simply the BEST windows LESS compiler there is...
SimpLESS is dumb... :p

That being said...
When I add my folder, it assumes I want to put all my "css" output in the same folder as my "less" files.
This doesn't align with my workflow really.

I have tons of less files, and each time I load a new site...
I have to right click and change each one individually to "Select Output"

Can this be fixed easily or is it a big fix?

@marklagendijk
Owner

First things first, this is simply the BEST windows LESS compiler there is...
SimpLESS is dumb... :p

Glad you like it. Don't hate on SimpLESS though,

I have tons of less files, and each time I load a new site...
I have to right click and change each one individually to "Select Output"

Having 'tons' of LESS files is quite common. It isn't that common, however, to have 'tons' of CSS files. Are you sure you need all the different CSS files, and couldn't have 1 LESS file which combines them by using '@import's?

Can this be fixed easily or is it a big fix?

This could be implemented quite easily. I would add an 'context menu' on the directory list with an menu-item 'Select output folder for all files'.

@joshuairl

Thanks for getting back to me on this.
Sorry, I wasn't really "hating"... I guess I just didn't see the charm in it... :-\

I guess you're right on the CSS files, wasn't really thinking about it like that...
I guess if you're just making separate CSS files for all of your objects in a web application there could still be quite a few separate ones but sounds like you have a plan.

Whatever makes the most sense to you, I'll roll with it.

Also, I found the ProgramData folder and edited my XML and it definitely helped me get my situation in order for now.

Thank you again!

Sincerely,
Joshua F. Rountree

@basher
basher commented May 18, 2012

Sorry for opening a duplicate issue... I hadn't spotted this one (and I did look).

Where I work, we need to have separate CSS files (and lots of them in different module-specific folders) for our CMS.
Each file may or may not have dependencies, which are then "imported" using a custom packager script.
Also, individual pages / user controls can link to individual CSS files as required.

We than concatenate/minify all CSS and JS on the page when it renders.

So, for us, it would be really useful to be able to select multiple LESS files and output to a folder in 1 go.

@jonschlinkert

I know this is marked as closed, but I actually think adding a context menu with the option to output all to a specific folder would be really helpful. If a use case would help, the reason I'd find it valuable is that during development I like to keep "wip" less files separate from the production less/css. In other words, this is how I sandbox the less files for new components I'm working on. I have each wip less file import the variables and mixins directly so it can compile to css independently - making it easier to tweak and isolate problems. Once something meets my standards it gets imported into the main .less file.

@jmclocklin jmclocklin pushed a commit to jmclocklin/WinLess that referenced this issue Dec 18, 2012
Jacob McLocklin #27 Add setting to allow custom output file name
This changeset solves two problems by adding a new setting that allows
users to opt-in to use the "advanced" output file selector.  This new
selector is simply an OpenFileDialog instead of a terrible
FolderBrowserDialog.   The two problems that this new dialog solves are:
(1) A custom file name can be added as requested by issue #27, and (2)
It is much easier to edit the output folder with the OpenFileDialog
because you can type/paste a file path (which helps a bit with issue
#9).
e54504d
@marklagendijk
Owner

The right solution for this issue would be:

  1. Add an extra menu-item 'Select output folder for all files' should be added.
  2. This menu-item should pop-up an VistaFolderBrowser dialog.
  3. After selecting a new folder the folder-part of all files should be changed to the new folder.
@marklagendijk
Owner

Closing all issues.
WinLess 1.x is now in maintenance mode. This means that at this time no feature requests will be accepted. Bug reports are still welcome, but all current issues are closed to make sure that the open issues are only about current bugs.

WinLess 2.x is a rewrite of WinLess using node-webkit. The development of WinLess 2.0 can be followed here. Most of the work is done, however, since my priorities have shifted it is now not clear whether it will ever be finished. Feature requests will only be accepted after the 2.0 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment