Just wondering how the featureset compares with imagefield.module. Are there any specific extra features that this module has, or difference in approach?

Comments

ndeschildre’s picture

ndeschildre commented
Status: Active » Closed (fixed)

Yes, a lot!
It does what imagefield does, plus support of presets edition, preset selection in the node edit page. Plus supporting the nodereference mode.
I have updated README.txt with much more infos.

alan d.’s picture

alan d. commented

There is a lot of work involved with creating the module, is there any reason why you choose to go down this path? Especially now that ImageField is now Image in Drupal 7 core, so just interested in reasons.

There is a contributed module that allows cropping per upload for imagefield, and others that allow you to associate additional information with the widget, so is this just a marriage of the three modules with a couple of additional addons?

EmilOberg’s picture

EmilOberg commented

I think you're missing the functionality.

Uberimage is built for editorial use (but could just aswell be used for other purposes) where you're using the same image on multiple places but with different size/cropping. For a newspaper, you might want to have an image in the main news flow, the same image but a bit bigger and wider as a heading for the article itself and a smaller rectangular image as a blurb/push/teaser/splash. Uberimage lets you, in this example, set 3 image presets with different sizes/ratios through imagecache and when the user is uploading an image it automagically gets scaled and cropped according to these three presets but the user can override that and adjust to her liking, or even override with a whole new image for one of the presets.

How do you achieve that with ImageField/ImageField Crop?

naheemsays’s picture

naheemsays commented

Except for the overriding, the different presets is standard in imagefield. (administer >> content types >> manage fields >> display settings)

Then either using filefield_sources or node_reference (in the case that you want each image to have its own node), you can reuse existing images in multiple nodes.

However this is all standard and does in include overriding the default settings, which is probably one of the new features of this module. I have not investigated this module further to see exactly what other extras/differnces there are, so I cannot comment much.

alan d.’s picture

alan d. commented

We are about to start a project that requires a distributed image store. Thus the interest in any image projects out there. Not trying to be negative, but I know how much work is involved. I'm the maintainer of upload element, that module still has a few issues, the last couple would take an entire rewrite to resolve and reintroduce missing functionality that caused the issues in the first place. This was taken over in D7 by image, thankfully saving myself a bit of work maintaining it into the future!

We are considering a custom filter format to:

a) hook into the image on the remote host. This may or may not be a Drupal install, but for distributed access control the money is on Drupal at this stage.
b) filter format to copy down and render the image according to the required presets. It was here where we would have looked at the custom crop functionality and stored the data in the filter tag.

Anyway, the point was that at this presentation stage (image selection / placement) where we will be looking at this functionality. To duplicate the entire CCK field / widget seems like a lot of work! I just wondered if you had tried this, and for some reason, dropped this approach. In the early planning stages, this was considered to be minimal in relation to doing the actual wysiwyg plugin + distributed work / access controls programming. Any experiences at this, good or bad, would be greatly appreciated.

Alan

PS: Nice site and big thumbs up for contributing your work back into the community.