Changes to the image cropper plugin

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Changes to the image cropper plugin

marnixkok
Hello everyone,

Currently, a small initiative is underway to customize the image cropper plugin, making it easier to use for content editors. At the moment we have a number of improvements in mind, but we would also like to hear from you, to discover other ways of improving the plugin.

There is a JIRA issue related to this question, it contains a preliminary fix: https://issues.onehippo.com/browse/CMS7-5407

Below I've listed a number of things we would like to improve:

1. have the "to-be cropped image" fit inside the cropper viewport.

Currently, the image is shown fullsize inside the tiny little viewport. If the image is 1000 pixels wide (which is not uncommon), the content editor will have to scroll a lot to get a nicely cropped image; this is not what you'd want. The YUI plugin does not support this out of the box but I've changed some of its code and provided a fix as an attachment to the JIRA issue.

2. add an option to allow the cropper result to have one dimension fixed (either width or height).

A good usecase for this would be: cropping sidebar images. Sidebars usually have a fixed width, but not a fixed height. This option would allow the content editor to easily slice images that will always fit the intended location in the site.

3. add a "maximize" button to the image cropper dialog

Eventhough, in point one, we have addressed the issue of difficult to select cropper regions, bigger is still better. That's why we suggest adding a maximize button to the image cropper dialog.

4. adding a flag that toggles the automatic image generation for imageset elements.

The current behavior of adding an image to the CMS is such that the CMS generates an imageset with scaled variations for every imageset element. In a situation where the imageset elements are used for cropping purposes this is not ideal.  Allowing the developer to toggle the auto-scale behavior per imageset element would be a nice addition.

These four points are the changes we would like to make to the image cropper plugin. However, as previously stated, we very much welcome your input. This way we will be able to make changes that useful for as many people as possible.

Awaiting your response!

With kind regards,

Marnix Kok
Reply | Threaded
Open this post in threaded view
|

Re: Changes to the image cropper plugin

Minos Chatzidakis-2
Hello Marnix,

Thanks for following our suggestion and making the cropper improvements official by filing a jira issue.
I've shared my thoughts in long previous messages with you, I will update jira with comments at some point of time.

I just want to request all involved hippos to share their thoughts on the cropper improvements and provide any feedback they consider valuable.
Also I'd like to let you know that this Hippo Friday I implemented a poc for point 1 (scalable images - no scrollbars), which I integrated to our cms trunk and it worked perfectly. Does not yet support all functionality but it is promising.

Thank you,

Minos



On Tue, Aug 2, 2011 at 10:43 AM, marnixkok <[hidden email]> wrote:
Hello everyone,

Currently, a small initiative is underway to customize the image cropper
plugin, making it easier to use for content editors. At the moment we have a
number of improvements in mind, but we would also like to hear from you, to
discover other ways of improving the plugin.

There is a JIRA issue related to this question, it contains a preliminary
fix: https://issues.onehippo.com/browse/CMS7-5407

Below I've listed a number of things we would like to improve:

1. have the "to-be cropped image" fit inside the cropper viewport.

Currently, the image is shown fullsize inside the tiny little viewport. If
the image is 1000 pixels wide (which is not uncommon), the content editor
will have to scroll a lot to get a nicely cropped image; this is not what
you'd want. The YUI plugin does not support this out of the box but I've
changed some of its code and provided a fix as an attachment to the JIRA
issue.

2. add an option to allow the cropper result to have one dimension fixed
(either width or height).

A good usecase for this would be: cropping sidebar images. Sidebars usually
have a fixed width, but not a fixed height. This option would allow the
content editor to easily slice images that will always fit the intended
location in the site.

3. add a "maximize" button to the image cropper dialog

Eventhough, in point one, we have addressed the issue of difficult to select
cropper regions, bigger is still better. That's why we suggest adding a
maximize button to the image cropper dialog.

4. adding a flag that toggles the automatic image generation for imageset
elements.

The current behavior of adding an image to the CMS is such that the CMS
generates an imageset with scaled variations for every imageset element. In
a situation where the imageset elements are used for cropping purposes this
is not ideal.  Allowing the developer to toggle the auto-scale behavior per
imageset element would be a nice addition.

These four points are the changes we would like to make to the image cropper
plugin. However, as previously stated, we very much welcome your input. This
way we will be able to make changes that useful for as many people as
possible.

Awaiting your response!

With kind regards,

Marnix Kok

--
View this message in context: http://hippo.2275632.n2.nabble.com/Changes-to-the-image-cropper-plugin-tp6644044p6644044.html
Sent from the Hippo CMS 7 mailing list archive at Nabble.com.
_______________________________________________
Hippo-cms7-user mailing list and forums
http://www.onehippo.org/cms7/support/forums.html



--
With kind regards/Met vriendelijke groet,
Minos Chatzidakis

Amsterdam - Oosteinde 11, 1017 WT Amsterdam
Boston - 1 Broadway, Cambridge, MA 02142

US +1 877 414 4776 (toll free)
Europe +31(0)20 522 4466
www.onehippo.com

______________________________
__________________________________
This e-mail may be privileged and/or confidential, and the sender does
not waive any related rights and obligations. Any distribution, use or
copying of this e-mail or the information it contains by other than an
intended recipient is unauthorized. If you received this e-mail in
error, please advise me (by return e-mail or otherwise) immediately.


_______________________________________________
Hippo-cms7-user mailing list and forums
http://www.onehippo.org/cms7/support/forums.html
Reply | Threaded
Open this post in threaded view
|

Re: Changes to the image cropper plugin

Ate Douma-3
In reply to this post by marnixkok
Hi Marnix,

Thank you a lot for your contribution which is very much appreciated and
definitely something we are interested in to work on (together with you) to
integrate.
BTW: as Minos already mentioned, he already picked up a small part of it :)

 From a formal and legal POV, it is important for us, and the product, to make
sure external contributions are granted to Hippo under appropriate licensing terms.

For Hippo this means your contribution, and all external contributions in
general only can be incorporated when they are provided to us using the Apache
Software License (ASL 2.0) or otherwise compatible license [1].

For relatively small contributions and patches like your image cropper
enhancements, it will be sufficient if you can explicitly say so as a comment in
the corresponding JIRA issue itself. For larger scale and/or further follow-up
contributions we might need a signed Contributor agreement (based upon the
Apache Software Foundation Contributor agreement), but this won't be needed in
this case.

So I have to ask you to please add a (separate) comment to the CMS7-5407 issue
stating your contribution is provided to Hippo under the ASL 2.0 license.

Thanks again for your effort so far and we're looking to further proceed and
work together with you.

Kind regards,

Ate Douma
Hippo Chief Architect

[1] http://www.apache.org/licenses/LICENSE-2.0.html

On 08/02/2011 10:43 AM, marnixkok wrote:

> Hello everyone,
>
> Currently, a small initiative is underway to customize the image cropper
> plugin, making it easier to use for content editors. At the moment we have a
> number of improvements in mind, but we would also like to hear from you, to
> discover other ways of improving the plugin.
>
> There is a JIRA issue related to this question, it contains a preliminary
> fix: https://issues.onehippo.com/browse/CMS7-5407
>
> Below I've listed a number of things we would like to improve:
>
> 1. have the "to-be cropped image" fit inside the cropper viewport.
>
> Currently, the image is shown fullsize inside the tiny little viewport. If
> the image is 1000 pixels wide (which is not uncommon), the content editor
> will have to scroll a lot to get a nicely cropped image; this is not what
> you'd want. The YUI plugin does not support this out of the box but I've
> changed some of its code and provided a fix as an attachment to the JIRA
> issue.
>
> 2. add an option to allow the cropper result to have one dimension fixed
> (either width or height).
>
> A good usecase for this would be: cropping sidebar images. Sidebars usually
> have a fixed width, but not a fixed height. This option would allow the
> content editor to easily slice images that will always fit the intended
> location in the site.
>
> 3. add a "maximize" button to the image cropper dialog
>
> Eventhough, in point one, we have addressed the issue of difficult to select
> cropper regions, bigger is still better. That's why we suggest adding a
> maximize button to the image cropper dialog.
>
> 4. adding a flag that toggles the automatic image generation for imageset
> elements.
>
> The current behavior of adding an image to the CMS is such that the CMS
> generates an imageset with scaled variations for every imageset element. In
> a situation where the imageset elements are used for cropping purposes this
> is not ideal.  Allowing the developer to toggle the auto-scale behavior per
> imageset element would be a nice addition.
>
> These four points are the changes we would like to make to the image cropper
> plugin. However, as previously stated, we very much welcome your input. This
> way we will be able to make changes that useful for as many people as
> possible.
>
> Awaiting your response!
>
> With kind regards,
>
> Marnix Kok
>
> --
> View this message in context: http://hippo.2275632.n2.nabble.com/Changes-to-the-image-cropper-plugin-tp6644044p6644044.html
> Sent from the Hippo CMS 7 mailing list archive at Nabble.com.
> _______________________________________________
> Hippo-cms7-user mailing list and forums
> http://www.onehippo.org/cms7/support/forums.html


--
mailto:[hidden email]    http://www.onehippo.com     http://www.onehippo.org
Europe Amsterdam   Oosteinde 11, 1017 WT, Amsterdam  +31 (0)20 522 4466
USA    Boston      1 Broadway, Cambridge, MA 02142    +1 877 414 4776 toll free
_______________________________________________________________________________
This e-mail may be privileged and/or confidential, and the sender does not
waive any related rights and obligations. Any distribution, use or copying of
this e-mail or the information it contains by other than an intended recipient
is unauthorized. If you received this e-mail in error, please advise me (by
return e-mail or otherwise) immediately.

_______________________________________________
Hippo-cms7-user mailing list and forums
http://www.onehippo.org/cms7/support/forums.html