Letractively / magento-w2p

Automatically exported from code.google.com/p/magento-w2p
0 stars 0 forks source link

Image editing testing, alpha4 #659

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Just a collection of gripes. They will need to be separate issues.

1. Menu buttons do not change appearance to active/clickable

2. The center-cross doesn't appear when fit in field is clicked, so it is 
impossible to shift the frame over the image, but I can do everything else.
They X appears after resizing the frame. You need to check both axis if there 
is any room to move the frame.

3. Resized the frame as in [2], the X appeared, tried to move it, but it could 
only move within the original area of the placeholder. I want to move it over 
the entire image.

4. The cropping area cannot be stretched to its original size/position. There 
are about 10px left, which is terribly annoying.

5. We need shortcuts: 
- fit image
- fill field
- fit width
- fit height
- make image smaller than field

6. Saving and re-opening gives a totally broken image with broken positioning. 
Updating preview 

7. Re-opening the image after editing takes way longer than it should.

8. If the image is smaller than the field it doesn't show in the image library 
scroll and is impossible to say that is was actually edited. We simply show an 
unedited thumb.

9. Opening image editor in in-preview mode works, but closing it closes 
in-preview completely. It should come back to in-preview as it does with stock 
images.

10. Remove SAVE button from the bottom and use the same red/black combo at the 
top-right corner as in stock images. It will give us a full line of white space 
which can be moved to the top and used for second level menu buttons (see [5]).

11. Incorrect DPI on all sorts of different scenarios. The algo that calculates 
it is no good. Needs a redesign.

12. "The selected area is too small for quality output. " should be red.

13. Will it work on an iPhone or Android? Curious.

14. The initial size/position of the image and field should be fit-in-fancybox. 
Both image and placeholder should be fully visible with all handles in view.

15. The initial position of the placeholder and image should be centered in 
relation to each other. We have anchor positions in the xml, but let's ignore 
it for now - just center everything.

Original issue reported on code.google.com by ad...@zetaprints.com on 2 Oct 2011 at 8:12

GoogleCodeExporter commented 8 years ago
> 1. Menu buttons do not change appearance to active/clickable

Issue #397 is about it.

Original comment by Anatoly....@gmail.com on 2 Oct 2011 at 11:51

GoogleCodeExporter commented 8 years ago
Need mock-ups for:

> 5. We need shortcuts: 
> - fit image
> - fill field
> - fit width
> - fit height
> - make image smaller than field

> 9. Opening image editor in in-preview mode works, but closing it closes 
in-preview
> completely. It should come back to in-preview as it does with stock images.

> 10. Remove SAVE button from the bottom and use the same red/black combo at the
> top-right corner as in stock images. It will give us a full line of white 
space
> which can be moved to the top and used for second level menu buttons (see 
[5]).

Original comment by Anatoly....@gmail.com on 2 Oct 2011 at 12:00

GoogleCodeExporter commented 8 years ago

Original comment by ad...@zetaprints.com on 2 Oct 2011 at 8:41

GoogleCodeExporter commented 8 years ago
> 11. Incorrect DPI on all sorts of different scenarios. The algo that 
calculates it is no good. Needs a redesign.

Issue #410 is about it.

Original comment by Anatoly....@gmail.com on 3 Oct 2011 at 8:46

GoogleCodeExporter commented 8 years ago
Mockups are uploaded as part of this issue:
http://code.google.com/p/magento-w2p/issues/detail?id=666

Original comment by agur...@gmail.com on 24 Oct 2011 at 11:11

GoogleCodeExporter commented 8 years ago

Original comment by Anatoly....@gmail.com on 12 Nov 2011 at 6:00

GoogleCodeExporter commented 8 years ago
I checked the list. Some problems are solved, other is in a separate issues.

Original comment by Anatoly....@gmail.com on 12 Nov 2011 at 7:19

GoogleCodeExporter commented 8 years ago
Yep, the issues from the list are taken care of.

As far as curiosity goes (list item 13):
No, ImageEdit does not work on Android mobile. There's no way to drag the nodes 
of the selection frame.

Original comment by agur...@gmail.com on 14 Nov 2011 at 1:36

GoogleCodeExporter commented 8 years ago

Original comment by ad...@zetaprints.com on 15 Nov 2011 at 9:51