Jump to:
| Project: | Data URI Sprites Generator |
| Component: | User interface |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Hi Dimitry
I'm continuing to test the module.
I have some thoughts on the interface.
If you agree with any of them, let me know, and I'll try to make some patches.
The overall principle I'm looking at is "Less is more".
Ideally a module should 'Just work'.
For example the jQuery Update modules simply needs to be enables in order to provide a new version of the jQuery Library.
No need for any configuration.
The pathauto module starts working straight away, but lets the user change the default settings.
So, with that in mind.
1. Settings page.
I don't know if there is a need for a separate settings page.
Ideally any configuration would be done directly on
admin/settings/performance
within the 'Bandwidth optimizations' section.
2. 32Kb per image limit
Is this setting really needed?
The reality is that IE7 and IE8 support is mandatory [from a practical point of view], so why would anyone uncheck that box?
The code could be written so as to make that available as an option if a future release [when usage of those browsers is lower], but not expose that setting to the user right now.
Is there was some extra work needed for IE6 only?
If so, then that could be an option, as many people [though not me just yet], choose not to support IE 6.
Regards
Alan
Comments
#1
Module will just work for most common use-cases (IE 6+ and other browsers) with default settings, so you'll only need to enable it.
IE 6 & 7 support provided by MHTML generation, so IE 6 doesn't needs extra work. I think we can completely remove all settings from UI, and some of them from code ("Enabled" option, for example).
#2
UI was completely removed. Module will start working after enabling it (if CSS aggregation is enabled too).
http://drupal.org/cvs?commit=394188
#3
Automatically closed -- issue fixed for 2 weeks with no activity.