change allowing division by type and therefore multiple presets per setting
| Project: | ImageCache |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Let me preface this request by saying I think imagecache is really cool and since I'm really a designer more than a developer I don't know what's involved in this sort of undertaking - although I imagine this would be a huge and fundamental change to the way imagecache currently works and therefore a lot of work. That being said, here's my dream for how imagecache could eventually work:
Imagecache Admin would be divided into something like the following:
- Types (ex. size/scale/shape, color, overlays, etc.)
- Presets
Then of course:
- An admin would have the ability to either create types (maybe - unless predefined types eliminates conflicts)
- An admin would have the ability to create presets that belong to a given type
On a given site I might create the following types and presets for example (these are arbitrary examples just to explain the idea):
- Type: Size/Scale/Shape
- Preset: Thumbnail (60x60 pixels)
- Preset: Landscape Small (120x240 pixels)
- Preset: Landscape Large (240x480 pixels)
- Preset: Portrait Small (240x120 pixels)
- Preset: Portrait Large (480x240 pixels)
- Type: Color
- Preset: Desaturated
- Preset: Red
- Preset: Blue
- Type: Overlays
- Preset: Watermarked
- Preset: Gradient Glow
Then, on cck field display settings or on view field display settings, instead of a list of the various imagecache presets to choose from a user would be able to select one preset of each type to use, and perhaps separately select the outcome (ex. link to node, etc.). So if I was building a view of user profiles I might want an avatar type image field shown in my listing with each user, and I might add the field to my view and then check both the Thumbnail and Desaturated presets for the display and also check the option to output as link to node.
I realize that the types may need to be predefined types that can't conflict (rather than letting users create types), I'm open to that.

#1
subscribe