Imachecache presets naming conventions need to be more specfic

7 replies [Last post]

Sun, 01/24/2010 - 14:14

domineaux

Offline

Joined: 05/27/2009

Juice: 193

I use imagecache with almost all sites. The imagecache presets are a nightmare as so many module builders create their own settings presets for Imagecache.

The same with UC, which is a further annoyance. The admin has to remember or become familiar with what size equates to what narrative description of the respective imagecache presets.

Simple solution:

All presets for image caches should be as follows: 85x85scaled= 85 x 85 pixels scaled, 100x100cropscaled = 100 x 100 pixels cropped and scaled

How hard can that be, and how much easier it would be to manage all the other images on sites, and become familiar with image sizes quickly in UC as well.

Thumbnails can mean all different sizes to users from 32x32 pixels to 120x120 pixels. I just don't see the point of not-specific narrative imagecache descriptions. I guess it wouldn't make much difference to someone with one site. Currently, I am maintaining several sites. Naming conventions with imagecache are a nightmare. I have a cheat sheet with name descriptions and sizes listed. Just a pain in the old wazoo.

It would be nice if others who agree would simply make a quick posting on this thread as encouragement for UC devs to look into this.

Thanks.

Sun, 01/24/2010 - 22:44

#1 View page

torgosPizza

Offline

Joined: 08/14/2007

Juice: 4110

Re: Imachecache presets naming conventions need to be more specf

Unless I'm missing something, the only imagecache presets that Ubercart creates as (and correct me if I'm wrong) are something like product, uc_catalog, and uc_thumbnail. It's been a while since I've looked at UC's default presets, but I know it's not very many.

Those presets you mention sound like they are custom. The nice thing about Imagecache is you can create whatever presets you like, and name them however you please.

I feel like maybe I don't understand your issue very well. Are you sure this is an Ubercart issue and not Imagecache?

--
Help directly fund development: Donate via PayPal!

Mon, 01/25/2010 - 01:35

#2 View page

domineaux

Offline

Joined: 05/27/2009

Juice: 193

Re: Re: Imachecache presets naming conventions need to be more s

I am using more than UC on several sites, along with imagecache. On one site I have 8 definitions for Imagecache present items.

Product, uc_catalog, uc_thumbnail, in the listing along with other presets that have names that don't clearly identify size and management of the cached items are difficult to track.

If the uc_catalog name was = "90x90SC" , then it would indicate 90x90 pixels Scaled & cropped, that would immediately indicate size and how image is managed, just by looking at the name.

The image size and how it is managed would be clearly identified. This way, in many instances if the imagecached items were close enough ore equal you could choose quickly by the way the preset is named.

This is probably more of an Imagecache issue. Regardless, if UC identified each of the 3 values more specifically to size and how the image is managed with a naming convention as described it would sure make things easier.

Some of what I said may sound repetitive, but I think I got it "splained" this time.

Mon, 01/25/2010 - 02:13

#3 View page

torgosPizza

Offline

Joined: 08/14/2007

Juice: 4110

domineaux wrote: Product,

domineaux wrote:

Product, uc_catalog, uc_thumbnail, in the listing along with other presets that have names that don't clearly identify size and management of the cached items are difficult to track.

I understand what you are saying. But those few that are created by Ubercart can always be renamed, especially if you intend to have many different presets that cover a wide range of dimensions. Your reasoning is solid (I definitely can't argue with it) but I am having difficulty seeing how this is really an issue.

For our site, the name "uc_thumbnail" is more than enough, but that isn't always true for everyone. We created other namespaces that tell where they are located, like "home-featured" and that sort of thing - which isn't a ton of information but helps me at least know where they are located within the site itself.

Quote:

Regardless, if UC identified each of the 3 values more specifically to size and how the image is managed with a naming convention as described it would sure make things easier.

To be honest, I think if UC created an Imagecache preset called "350x200cropped" that would make less sense to me. I would ask "what module created this?" and "where is it used on the site?" Whereas something like uc_thumbnail and cart have clear meanings, much moreso than the alternative. You could, of course, edit these by clicking the "Edit" link in admin/build/imagecache and make them more specific, i.e., "uc_cart_300x250" and "uc_thumbnail_200x200" etc. etc.

But I think as the default, the way it is now is fine. YMMV of course.

--
Help directly fund development: Donate via PayPal!

Tue, 01/26/2010 - 14:23

#4 View page

domineaux

Offline

Joined: 05/27/2009

Juice: 193

Re: domineaux wrote: Product,

Quote:

On my sites I care less what modules or where used, it's the size and image settings that interst me. This way as I or users work the site, the formatting takes on the uniformity desired.

When I'm working with Views and other tools I know by looking at the name of the image cache item what size it is.

I didn't realize you could rename imagecache items in UC. I thought they were called from so many places and modules it would create alot of issues if changed.

Thanks for the chat.

Tue, 01/26/2010 - 14:27

#5 View page

torgosPizza

Offline

Joined: 08/14/2007

Juice: 4110

Re: Re: domineaux wrote: Product,

No worries, glad to help

And just for anyone else coming upon this thread, Imagecache and Ubercart are completely separate modules; Imagecache can be "plugged into" by something like Ubercart to create a "default" preset. In most cases, if you can't configure Ubercart or another contributed module to use your own, specific presets, you also have the ability to a) override the preset with your own options, or b) rename the default preset, as domineaux was asking. You don't need to stick with any of the defaults if they don't work for your setup - they can be modified, and overridden to suit your own special site requirements.

--
Help directly fund development: Donate via PayPal!

Sat, 07/17/2010 - 16:31

#6 View page

ergophobe

Offline

Joined: 06/21/2010

Juice: 115

Thanks for this discussion. I

Thanks for this discussion.

I came here trying to find out of I could rename presents without breaking my cart. The answer appears to be yes.

I have to say that names like "85x85_scaled_cropped" would drive me nuts. I can always adjust the actions on a display. I want to know "what is the context for this preset?" or put another way "Which images does this preset control?"

My issue is simply want a bit more "verbose" descriptions for clients using a crop tool which uses preset names to make a menu. So Product_Page and Product_Listing and Cart might work better for them (or not).

Anyway, to me this is like the difference between semantic markup and presentational markup. The current UC naming conventions are semantic, and the OP's suggestions are presentational. For me, I much prefer a semantic nomenclature for my presets, even if in the end, maybe some of them have the same set of actions.

Consider this.

1. I build a site that uses 85x85_scaled in my shopping cart and for my gallery thumbnails.
2. Now I decide those are kind of small for my gallery, so I bump them to 150x150.
3. Oops, I forgot that presentational setting is used for the cart too, so that's broken. Now I have to redo my theme to use a different preset.

So a vote for keeping it the way it is.

In terms of the namespace issue, I think the best thing would be to do like for module functios and just append uc_ to every preset.

Sat, 07/17/2010 - 17:07

#7 View page

ergophobe

Offline

Joined: 06/21/2010

Juice: 115

Re: Imachecache presets naming conventions need to be more specf

A little experimentation and research tells me that you can't simply rename imagecache presets that are storage type "default". Rather, it will create different presets.

So now I'm asking the same question that kicked this off (more or less).

Is using different presets a simle matter of the theming layer, so I can grep for imagecache presets in the theme and handle it there, or will some things get messed up in modules?

Ubercart

Navigation

User login