Page-wide preview

[GoogleCodeExporter]

Some products are just too small in that side-image. They need full content 
width to make sense. Also, in-preview in a separate theme is causing us 
maintenance problems.

Let's change it to a bit more dynamic configuration.

1. merge everything in into 1 theme
2. add options to w2p tab for the way the preview is presented:
* store default
* small, default position
* full-width, above details
Wrap the call to MEDIA into IFs to choose the right place to output it.
An alternative is to move MEDIA to above .product-shop and add a class selector 
somewhere inside our code to show it one way or the other.

3. add options to w2p tab for fields / in-preview editing
* store default
* disabled
* enabled
If in-preview editing was selected the w2p form should be collapsed by default.

4. If in-preview was selected and the image showing on the page is in its full 
size there is no point showing a fancy box - allow editing right in there.

5. Add these new layout options for w2p admin as a default. Most likely they 
will be configured per site.

6. assume "store default" value for any pre-exiting products before this 
upgrade.

7. Update documentation. 

8. Explain the product title can go under large preview (stays inside 
.product-shop) or go above it, but then will need to go outside with necessary 
style changes.

Original issue reported on code.google.com by zetapri...@gmail.com on 4 Mar 2011 at 5:34

[GoogleCodeExporter]

Looks like one heck of a task.

Need a mock-up for a button that toggles the form with input fields.
"Show preview fields" / "Hide preview fields"

Original comment by zetapri...@gmail.com on 4 Mar 2011 at 5:38

• Added labels: Help-X, Unit-1, Wiki-X

[GoogleCodeExporter]

Original comment by ad...@zetaprints.com on 11 Apr 2011 at 3:52

• Added labels: Unit-2
• Removed labels: Unit-1

[GoogleCodeExporter]

Original comment by agur...@gmail.com on 11 Apr 2011 at 12:08

Attachments:

• D2_collapsed.png
• D2_expanded.png
• form_expand_sprite.png

[GoogleCodeExporter]

Original comment by ad...@zetaprints.com on 7 Jun 2011 at 10:12

[GoogleCodeExporter]

This seems to me more like 5+ units task then 2.

Original comment by jamb...@gmail.com on 16 Jun 2011 at 7:49

[GoogleCodeExporter]

Also I think the logic is wrong here, there are so many theme variations that 
it is out of question to make an universal solution.
I would go for a separate personalization page either normal or in popup. This 
way you have your own page, and don't depend on theme quirks.

Original comment by jamb...@gmail.com on 16 Jun 2011 at 7:53

[GoogleCodeExporter]

Original comment by ad...@zetaprints.com on 16 Jun 2011 at 9:19

• Changed state: OhHold

[GoogleCodeExporter]

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

• Added labels: Mockups

[GoogleCodeExporter]

I think the idea is flawed. We need to have a common approach with in-preview 
editing here.

Original comment by ad...@zetaprints.com on 3 Oct 2011 at 8:25

• Removed labels: Mockups

[GoogleCodeExporter]

Original comment by ad...@zetaprints.com on 16 Feb 2012 at 10:52

• Changed state: WontFix