[MGNLDAM-282] Crop image proportionally and by entering dimensions Created: 13/Jul/13  Updated: 23/Aug/22

Status: Open
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: 1.0.1
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Marvin Kerkhoff Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File 2.5 crop proportional.png     PNG File screenshot-1.png    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Story Points: 3
Team: AuthorX

 Description   

 

User story

As an Editor I want to crop my image proportional or by numbers.

 

Acceptance criteria

  • Image editor provides checkbox for proportional resizing
  • Proportion remains when changing width or height

 



 Comments   
Comment by Antti Hietala [ 19/Apr/18 ]

marvink2, can you explain the business use case for resizing the originals in the DAM app? damfn provides functions to resize (also proportionally) https://documentation.magnolia-cms.com/display/DOCS56/How+to+work+with+images+using+damfn#Howtoworkwithimagesusingdamfn-Displayingresizedimages. The purpose of DAM is typically to store high-resolution originals.

Comment by Marvin Kerkhoff [ 19/Apr/18 ]

The Main idea was in 2013 to make more use of the cropping functions of the DAM. So to change the sizes of an image or propotions based on real values in the dam. It's obvious that damfn is the way to go for the Frontend. But in the DAM App the cropping feauture has one big disadvantage. You have no good control for the size of the image and you cannot crop in specified propotions. I also think this will fix a lot of this issues. https://github.com/sevensource/magnolia-responsive-dam

Generated at Mon Feb 12 04:58:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.