search

EmreSarikaynak / magento-w2p

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

Remove fields overlays from small preview #652

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Shall we remove field overlays from the thumbnails?

It sort of makes no sense. I can't really do anything with them, the image is 
obscured, etc, etc

I think we should replace it with an icon that says: click to enlarge or click 
to edit, depending if in-preview is enabled or not.

Shall we have an icon under the thum to tell users CLICK HERE TO ENLAGE OR EDIT?
Maybe a magnifying glass or pencil. Otherwise they don't know it can be edited. 

Let's start with mock-ups.

Original issue reported on code.google.com by ad...@zetaprints.com on 9 Sep 2011 at 3:41

GoogleCodeExporter commented 8 years ago 
I guess you mean overlays of the main preview image, right?

Original comment by agur...@gmail.com on 9 Sep 2011 at 7:27

GoogleCodeExporter commented 8 years ago 
I meant the main product image.

Original comment by ad...@zetaprints.com on 10 Sep 2011 at 1:44

GoogleCodeExporter commented 8 years ago 
Atanas, we need mockups for this!

Original comment by ad...@zetaprints.com on 2 Oct 2011 at 7:36

GoogleCodeExporter commented 8 years ago

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

GoogleCodeExporter commented 8 years ago

Original comment by ad...@zetaprints.com on 3 Oct 2011 at 10:20

GoogleCodeExporter commented 8 years ago 
Atanas, it's holding us back.
Let's get the mockups sorted and sprites uploaded.

Original comment by ad...@zetaprints.com on 10 Oct 2011 at 6:01

GoogleCodeExporter commented 8 years ago 
Default screen in most cases. In-preview personalization activated, input form 
is collapsed by default but available.

Original comment by agur...@gmail.com on 14 Oct 2011 at 1:53

Attachments:

GoogleCodeExporter commented 8 years ago 
In-preview is disabled (Editor is Enlarge). Form is expanded by default and 
even though it is the only personalization option, users can use "Form" button 
to show/hide the form.

Original comment by agur...@gmail.com on 14 Oct 2011 at 1:55

Attachments:

GoogleCodeExporter commented 8 years ago 
In-preview is activated but user decided to use the input form and click 
"Update Preview" button under the image. The image gets dimmed and spinning 
loader with hint shows up while processing.

Original comment by agur...@gmail.com on 14 Oct 2011 at 1:55

Attachments:

GoogleCodeExporter commented 8 years ago 
All buttons are active. Multipage template, preview was just generated, 
In-Preview is enabled.

Original comment by agur...@gmail.com on 14 Oct 2011 at 1:56

Attachments:

GoogleCodeExporter commented 8 years ago 
Static page. One can only zoom or move to the next one.

Original comment by agur...@gmail.com on 14 Oct 2011 at 1:56

Attachments:

GoogleCodeExporter commented 8 years ago 
Worst case scenario. Vertical design and preview image and a static page to 
boot.

Original comment by agur...@gmail.com on 14 Oct 2011 at 1:57

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by agur...@gmail.com on 14 Oct 2011 at 6:02

Attachments:

GoogleCodeExporter commented 8 years ago 
We need to give theme designers 2 options:

1. insert individual buttons
2. a function that inserts the buttons automatically

Both need to be documented.

Original comment by ad...@zetaprints.com on 14 Oct 2011 at 8:27

GoogleCodeExporter commented 8 years ago

Original comment by agur...@gmail.com on 18 Jan 2012 at 2:19

GoogleCodeExporter commented 8 years ago

Original comment by agur...@gmail.com on 18 Jan 2012 at 2:20

GoogleCodeExporter commented 8 years ago

Original comment by ad...@zetaprints.com on 15 Feb 2012 at 10:49

GoogleCodeExporter commented 8 years ago 
Diffs: http://code.google.com/p/magento-w2p/source/detail?r=1914

Original comment by Anatoly....@gmail.com on 1 Mar 2012 at 10:01

GoogleCodeExporter commented 8 years ago 
Please, test it with 2.0.1.0alpha6 release.

Original comment by Anatoly....@gmail.com on 1 Mar 2012 at 10:33

GoogleCodeExporter commented 8 years ago

Original comment by ad...@zetaprints.com on 1 Mar 2012 at 10:55

GoogleCodeExporter commented 8 years ago 
There is a fair bit of work needed before it's ready.
Let's post new issues for the test results. 
I'll dump my gripes here for now.

1. I think we need animation for showing / hiding form and buttons. I miss 
what's happening. It was .... something ... then blink .... and it's something 
else. Go figure!

2. Clicking Editor should TOGGLE the popup. Form toggles the form, so lets keep 
it consistent.

3. Template 
http://d1.zetaprints.com/magedev/index.php/magentot-02/4xpage-sign.html
Updated the arrow, which updated 3 pages at once. Why do we show update preview 
on the other 2 dependent pages? They have no fields of their own.

4. We need a button to restore the original preview. Not sure what should 
happen to the input fields then. Clearing them may do more harm than good.

5. I don't understand why we are suggesting they should update the preview when 
nothing was entered? Maybe not as much as disabling it, but at least keep it 
sort of greyed out. Kind of don't invite a click. This is true only where the 
in-preview editor is enabled.

6. Image fields have the snake for uploading a file spinning on opening the 
field.

7. Why do we hide NEXT PAGE until they update this one? What if I'm happy with 
the defaults? I was looking at the screen thinking - oh, where to now? 

8. the order of updating the preview image is strange: page thumb, main 
preview, popup. So it updates where I'm not looking first. I'd do popup, 
product image, page thumb. 

9. It is really really good. I like it.

Original comment by ad...@zetaprints.com on 1 Mar 2012 at 11:31

GoogleCodeExporter commented 8 years ago 
10. I question dimming the image. I may still want to see what's in there.

11. Where do we set the initial state of the form (show/hide) ?

12. Shall we add active / inactive state of icons? E.g. if the editor is active 
the button is brighter / bolder / color, etc.

13. How does DB lookup fit into this picture? 
http://d1.zetaprints.com/magedev/index.php/sample-stationery/business-card.html

14. It's still vastly awesome.

Original comment by ad...@zetaprints.com on 1 Mar 2012 at 11:38

GoogleCodeExporter commented 8 years ago 
Tested on /magedev/
web_to_print_store_incl_theme   2.0.1.0alpha6 (alpha) 

Here are some additional bugs I found:

15. Collapsed text InPrev fields.
Replication instructions:
- Navigate to
http://d1.zetaprints.com/magedev/index.php/magentot-01/1pg-template.html
- Click on "Editor" btn to get to the InPrev
- Click on a text frame
The input field is collapsed and no way to expand it (btn_01.png)

16. In Chrome and Safari, the "Preview updating" loader is misaligned - goes 
above the image (btn_02.png)

17. If a user acts fast enough, they'll never see the InPrev shapes.
- Navigate to:
http://d1.zetaprints.com/magedev/index.php/magentot-02/4xpage-sign.html
- Click on "Editor" btn as soon as the preview image loads
The highlighter shapes do not display even after the page is loaded in full. 
Would be safest if the shapes info could load even after the large FancyBox 
preview is expanded.
This is not an issue if the page is loaded in full and then InPrev is activated.

Original comment by agur...@gmail.com on 1 Mar 2012 at 5:36

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by ad...@zetaprints.com on 3 Mar 2012 at 2:27

GoogleCodeExporter commented 8 years ago 
3 - atanas, you need to look into this and post an issue
4 - it's a can of works. 
5 - http://code.google.com/p/magento-w2p/issues/detail?id=762
10 - just remove the dimming
11 - http://code.google.com/p/magento-w2p/issues/detail?id=763
12 - http://code.google.com/p/magento-w2p/issues/detail?id=764
13 - never mind

What's happening with the other points?

Original comment by ad...@zetaprints.com on 3 Mar 2012 at 2:33

GoogleCodeExporter commented 8 years ago 
Diffs: http://code.google.com/p/magento-w2p/source/detail?r=1919

Original comment by Anatoly....@gmail.com on 5 Mar 2012 at 6:34

GoogleCodeExporter commented 8 years ago 
Please, test it with 2.0.1.0alpha7 release

1. Fixed
2. Fixed
6. Fixed
7. Fixed
8. I reorganised the code. Maybe it'll help
11. I removed overlay. But it's better if Atanas makes mockups for the new 
design. I don't like how it looks.
15. Fixed
16. Fixed.

Original comment by Anatoly....@gmail.com on 5 Mar 2012 at 9:26

GoogleCodeExporter commented 8 years ago 
Tested on /magedev/
web_to_print_store_incl_theme   2.0.1.0alpha7 (alpha)

1. Test OK
2. Test OK
3. Posted http://code.google.com/p/magento-w2p/issues/detail?id=767
6. Test OK
7. Test OK
8. Thumb updates first, big preview and pop-up update after that (at the same 
time). Pretty much same as before.
10. No good. What's wrong with having an dimmed overlay for a few seconds? I 
think it actually comes natural to the user that the preview image is going to 
change now that they've hit "Update preview". I'd bring the dimmed version back 
but up to Max, here's another solution (F2-1_dimmed.png).
15. Test OK
16. Test OK

Original comment by agur...@gmail.com on 5 Mar 2012 at 12:41

Attachments:

GoogleCodeExporter commented 8 years ago 
Looks like this one is TestOK.

I don't see any more show stoppers.
Atanas, correct me if I'm wrong.

Original comment by ad...@zetaprints.com on 5 Mar 2012 at 7:29

GoogleCodeExporter commented 8 years ago 
10. I need background for the new mockup. Rounded square and rounded left/right 
sides of text background. Please, put all of them into sprite you posted 
before. I think it's a separate issue.

Original comment by Anatoly....@gmail.com on 6 Mar 2012 at 10:00

GoogleCodeExporter commented 8 years ago 
Is this ok?

Original comment by agur...@gmail.com on 6 Mar 2012 at 12:27

Attachments:

GoogleCodeExporter commented 8 years ago 
Post the new dimmer as a new issue?

Original comment by ad...@zetaprints.com on 6 Mar 2012 at 5:56

GoogleCodeExporter commented 8 years ago 
osted:
http://code.google.com/p/magento-w2p/issues/detail?id=769

Original comment by agur...@gmail.com on 7 Mar 2012 at 5:27

GoogleCodeExporter commented 8 years ago 
We need explain when the form is showing and when not. Also, let's make a blog 
post with the stable release.

Original comment by ad...@zetaprints.com on 7 Mar 2012 at 8:12

GoogleCodeExporter commented 8 years ago

Original comment by ad...@zetaprints.com on 27 Jul 2012 at 2:14