Been going through the cropper JavaScript plugin for cropping images for days. Can't figure it out. I'm a php person and JavaScript looks like Greek to me. Seems all the examples I've seen from google search assume the reader actually are familiar with JavaScript and I'm not. My challenge is which of the cropper methods actually stores the dataurl and how do I retrieve it to pass to a php script for processing into an image or to a JavaScript function to display on the same page as an image.
fig cropper download
Download Zip
https://9rubi-hybra.blogspot.com/?bk=2x2i5B
As it is now, when designing a site, usually for each type of image we use 3 crops one for each device, ie large, medium and small devices. But each crop is for a particular case, for instance a header can have a background image of 1920x680 px for large devices, etc.But if the image is for a news photo could have another crops.If i define each crop in the image cropper as it is now, when the user edits an image may see lots of possible crops and its hard to know the crop that will be used for that situtation. But the media picker knows the context and situation.I guess this could be a good improvement for the media picker.
The first property Image Crops has a select box. This allows you to select any data type you've previously created that is of type "image cropper". After selecting the data type, you're shown a list of crop sizes available. You can toggle each one of these on/off.
I know that some people create multiple data types across their site for image croppers. I tend not to do that. As jarring as it is to see 20 crops when you select any media item from the backoffice, I think crops existing that you cannot find anywhere is confusing and more detrimental to the backoffice editing experience. (EDIT: I use the media section.)
I have an RGB image, once I run it through the segment cropper, only 1 channel remains. Is it something I am doing wrong, or is it just the node that has limited functionality? I guess I could split my image first into the 3 channels, do 3 segment croppers, joiners, and then the merger node, but this seems like a bit of a hassle.
Well the problem is just that it is a simple RGB image. I don't see why the segment cropper should handle them as three seperate channels instead of 1 image. Perhaps it is also possible to implement the selections that are implemented in the splitter node. So that we can say if they need to remain together, or not.
Edit: I manually added the same selection to the other channels in the Interactive Annotator as well, so now the segment cropper also works on 3 channels. Perhaps you guys could program it in such a way that the IA automatically duplicate over a selected dimension, channel or time for example.
I agree that there seems to be a bug in the segment cropper: if you view the image in the image viewer and inspect the pixel values by moving the mouse over the data, there is "value=0" shown on some regions where some gray value other than black is displayed.
35fe9a5643