Lullabot recently did a podcast on deprecated (or soon to be deprecated) modules. One of the modules mentioned was that the Image module could soon be deprecated, in light of the advancements in CCK, most notably ImageField and ImageCache. Since I am now at the point where I need to create an image gallery for my website, I began wondering if I should try to make it work work using CCK, ImageField, ImageCache, and Views (if needed).
My question is, is there a module that allows you to arrange nodes in groupings and sub-groupings (I hesitate to use the word "galleries"). I know about Acidfree, but I don't think that it makes use of custom node types. I know about Gallery and Coppermine, but they, too, fall under the same difficulty. What I'm looking for is, I suppose, a general module that will allow custom inclusion of node types. Is there anything like that available?
I tried using views, but I could not get it to list sub-groupings alongside the regular node listings (using taxonomy as the hierarchy).
Do I need to hold off until Drupal 6 with it's new (from the book module) hierarchy module?
I really want to get away from the Image module, if possible. I don't like the alternate sizes ("thumbnail", "original", etc.) showing up in the links below the node. Plus, I think that the ImageCache filters could be expanded to include watermarking.
Any suggestions/ideas?
-Corey
Comments
Image module looks certainly
Image module looks certainly looks to be destined for 'deprecation'. This will be a slow death though because there are still some things like watermarking, bulk imports, galleries and 'ease of use' are missing from the CCK, Views, imagefield and imagcache combo.
I'm having the same problem deciding which avenue to go on a particular project, image.module or imagefield but looks like the image.module route is going to be the choice in this case as eventhough the imagefield route is far more flexible there are those features which are missing that is my decider.
Should you go with Image.module i'm sure there will be a module written for converting to imagefield if it does not already exit. If it can't wait go image.module if it can wait, the features we require will appear soon as the imagefield and related modules are really actively being developed.