Magnolia Imaging Module

Implement a SaveHandler that does the actual image resizing

Details

  • Type: Task Task
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: None
  • Fix Version/s: 1.0
  • Component/s: controls, dialogs
  • Labels:
  • Description:
    Hide

    "target" size should be configurable: for example, if we want to create thumbnails, we might want the users to be able to select ANY square area in the image, but the selected zone should be resized to 100x100px.

    Output format/quality should also be configurable.

    One of the goals to keep in mind is that one single original image could be resized in multiple different sizes (thumbnail, small, medium, original, ... see flickr or zenphoto for instance)

    Show
    "target" size should be configurable: for example, if we want to create thumbnails, we might want the users to be able to select ANY square area in the image, but the selected zone should be resized to 100x100px. Output format/quality should also be configurable. One of the goals to keep in mind is that one single original image could be resized in multiple different sizes (thumbnail, small, medium, original, ... see flickr or zenphoto for instance)

Issue Links

Activity

Hide
Grégory Joseph added a comment - 30/May/07 9:18 PM

for 3.0 compatibility, we're providing a DialogHandler (extends ParagraphEditDialog)
for 3.1, we will potentially introduce a postSave() mechanism on the SaveHandler

Show
Grégory Joseph added a comment - 30/May/07 9:18 PM for 3.0 compatibility, we're providing a DialogHandler (extends ParagraphEditDialog) for 3.1, we will potentially introduce a postSave() mechanism on the SaveHandler
Hide
Grégory Joseph added a comment - 01/Jun/07 7:21 PM

Using the DialogHandler, the targetWidth/targetHeight parameters have to be defined at dialog, because I don't see a clean way of getting back to the control holding the rest of the configuration. If we introduce a postSave mechanism in 3.1, it should somehow get a map of control config nodes / saveInfo to be able to set the target size at control level.

Show
Grégory Joseph added a comment - 01/Jun/07 7:21 PM Using the DialogHandler, the targetWidth/targetHeight parameters have to be defined at dialog, because I don't see a clean way of getting back to the control holding the rest of the configuration. If we introduce a postSave mechanism in 3.1, it should somehow get a map of control config nodes / saveInfo to be able to set the target size at control level.
Hide
Grégory Joseph added a comment - 04/Jun/07 7:41 PM

MGNLIMG-12 was fixed: ImageCropperControl now exposes its config node. We get hold of the dialog and loop on all its subs - we get the config node of each instance of ImageCropperControl that's encountered and loop over them to process images. (ie multiple croppers in one dialog should be supported)

Show
Grégory Joseph added a comment - 04/Jun/07 7:41 PM MGNLIMG-12 was fixed: ImageCropperControl now exposes its config node. We get hold of the dialog and loop on all its subs - we get the config node of each instance of ImageCropperControl that's encountered and loop over them to process images. (ie multiple croppers in one dialog should be supported)
Hide
Grégory Joseph added a comment - 26/Aug/08 2:12 PM

Using MAGNOLIA-2272 is probably the best way for now

Show
Grégory Joseph added a comment - 26/Aug/08 2:12 PM Using MAGNOLIA-2272 is probably the best way for now
Hide
Grégory Joseph added a comment - 30/Apr/09 7:47 PM

Closing this issue for now. We're doing major refactoring of the module. Followup MGNLIMG-33 if you're interested.

Show
Grégory Joseph added a comment - 30/Apr/09 7:47 PM Closing this issue for now. We're doing major refactoring of the module. Followup MGNLIMG-33 if you're interested.

People

Dates

  • Created:
    25/May/07 2:39 PM
    Updated:
    30/Apr/09 7:47 PM
    Resolved:
    30/Apr/09 7:47 PM