Closed (won't fix)
Project:
Less CSS Preprocessor
Version:
6.x-2.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
17 May 2011 at 14:02 UTC
Updated:
11 Jul 2011 at 22:11 UTC
Jump to comment: Most recent file
Comments
Comment #1
bocaj commentedAlso, I would be willing to work on a patch for this if others are interested in this...and corey.aufang is willing to make the change.
Comment #2
patrickharris commentedYes - this makes a lot of sense to me.
Comment #3
davidfells81@gmail.com commentedGreat idea!
Comment #4
Headache commentedYes, would be nice.
Comment #5
timoti commentedmakes sense to me.
Comment #6
bocaj commentedSince there were a number of people interested in this I decided to create a patch. This is rolled against 2.x-dev.
Also, the less.admin.inc file can be removed as it is no longer used.
You will find the settings at the bottom of admin/settings/performance.
Comment #7
corey.aufang commentedWhile the functionality on the settings page is similar to what is available @ admin/settings/performance, I find it is more helpful that the LESS settings are clearly available.
I have more often been extremely frustrated trying to find where a module's configuration options are than being annoyed by another admin/settings/* page.
Comment #8
jox commentedI agree somewhat with #7.
I think minimalness must not necessarily be a reason to eliminate something. Usability should come first.
Maybe thematically it does not fit 100% as well. While the Less settings have impact on performance, it is not the primary subject. It is a penalty.
On the other hand it would be helpful to have an overview of all the performance affecting options.
But then it could/should also include the "Rebuild theme registry on every page." setting, "hidden" in the Apprearance configuration (admin/appearance/settings/theme). EDIT: This is even more misplaced, since it is a development setting that can not be found in the development section.
Comment #9
bocaj commentedI do agree with #7 and #8. I personally just hate a configuration page that has a couple of configurations. Then, depending on the modules you enable, the Site Configuration menu easily becomes a mile long.
I agree that the performance page might not be the best place for this, since it really isn't a performance tool, I just don't think that it needs to have it's own page.
Thankfully Drupal 7 has the configuration section segmented a little more.
I think that the LESS settings could be better placed somewhere else, I'm just not sure exactly where :)
Comment #10
bocaj commentedNow that I've thought about this some more, I don't know that there's a better place for the settings than on it's own page. Since Drupal 7 does a lot better job of breaking out the Configuration menu this probably isn't much of an issue anymore.
Thanks for all your input!