To Whom May Be Listening,
For far too long I’ve been touting a “Version 2” of Minimee, only to see time pass by and the feature list grow. Which is not to say I haven’t been toiling away. Rather I’ve been working on things, off and on, for ages. And it seems that quite often I’m taking two steps forward and one step back.
As it turns out, there are two “tiny” features that are causing me grief, stunting progress towards implementing other features. so I’m considering dropping them. What would be great to hear from you, Dear Community, is if anyone would even notice…
combine=“no” and minify=“no”
There has always been the ability to turn on and off Minimee’s “minifying” and “combining” of files. Supporting these requires a crazy circus act of if/else/then/buts/foreach cruft, and for every “thing” I want to do to a file, it has to be done at every turn. It’s annoying, and I’ve long been wondering if it’s even necessary.
I’ve pretty much convinced myself already that minify=“no” is pointless; that if you want to disable minification, you might as well be disabling Minimee altogether, which has always been possible.
And I’m also thinking that there’s no real advantage to combine=“no” - that again it defeats the purpose of what Minimee is supposed to be doing. Besides, if you ever really need a paricular CSS or JS file to be Minimee’d on it’s own, simply wrap it in it’s own tag pair.
But I’d really appreciate anyone’s input. It’s impossible for me to predict all the ways Minimee is being used (and expected to behave). Aside from when you’re building/debugging a site, has anyone ever found real-world usefulness with either of these features?
Many, MANY thanks for your time, and your ideas.
Keep calm and carry on, EErs.