Is there a specific reason why the module provides the "ifa_crop_100_75", "ifa_200", and "ifa_thumbnail" ImageCache presets?

Most sites, including ours, will have their own sizes and presets and shouldn't need these presets. Unfortunately, the way that they're currently bundled, they cannot be deleted. I do like the fact that they can be hidden from the drop down in the Image Assist window, but really I don't think these presets are necessary.

If the concern is that there will not be any presets to show by default if the user hasn't defined any, I think that's acceptable. The user will just end up seeing the option for using the original image size, which is expected behavior if you haven't defined any presets.

Comments

franz’s picture

franz
any
Location Montréal
commented

Too much user-friendly at cost of non-developer-friendly...

Something to think about.

lourenzo’s picture

lourenzo commented

Hello.

The preset ifa_thumbnail is required when listing images.

The other two are bundled to provide some samples if the user is not familiar with imagecache.
Thinking of it, those two bundled presets could be removed if it's annoying, but we need to know if someone out there is already counting on them.

guypaddock’s picture

guypaddock commented

Ah, okay; that makes sense.

For the optional ones, what if they were rolled into an optional additional module?

franz’s picture

franz
any
Location Montréal
commented

#3: Yeah, it would be like a IFA Starter Pack =P

karljohann’s picture

karljohann commented

I strongly agree with (at least) not adding the other two presets. They're not really in the way but they kind of muddy the waters if you know what I mean. Plus, getting rid of them is a hassle!

mrfelton’s picture

mrfelton commented

I agree too... developers and site builders generally don't want to have extra cruft forced onto them when they probably have no need for it as they will be customising and using their own imagecache presets. I understand that it makes it easy for end users who just want something to install and be ready to use with minimal configuration, but in most cases, setting up a module like this is the job of a site builder, who will most likely know how to set up an imagecache preset. I say, keep the thumbnail one, since that is clearly required for the browser, but just add documentation that explains that you can create your own presets and integrate them. And, if you really like, create a 'starter pack' module to hold the additional stuff, as mentioned above.

karens’s picture

karens commented

In the meantime developers can use hook_imagecache_default_presets_alter(&$default_presets) to remove or alter presets added by other modules.