jmalanche / magento-w2p

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

Datasets, full on #737

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Issue #669 implemented datasets in a simple way with inter-dependent drop-downs 
and comboboxes.
The main problem with that approach is the lack of multiline support.

The idea is to have a table in a fancybox with all the values similar to how it 
works on ZP.

All the data is already in Mage. We only need to agree on the button to open 
the dataset and the design of the table.

Cells can be selected individually or as a row depending on the settings.
See #669 for b/g info.

Original issue reported on code.google.com by ad...@zetaprints.com on 16 Jan 2012 at 9:29

GoogleCodeExporter commented 9 years ago
The dataset button goes on top of the text input form (ds_button.png).

1. The FancyBox default min size is 500 x 300 px (ds_min_size.png). Top row 
background is #93b4df, text color is #204a87. Table border color is #c6c4c5. 
Both corner buttons have the same function - close the FancyBox with the text 
fields populated with whatever the user had selected before closing the 
FancyBox.

2. All rows have a maximum height of one line of text. If the text can't fit in 
one line - we show it on cell hover (ds_hover.png). Hover box has background 
#e9f2fd and border #c6c4c5.

3. Users can select the entire row or cells from different rows - depending on 
the setting from ZP. Selected cells are highlighted by changing their 
background color to #e9f2fd (ds_min_size.png).

4. When a entire row is selected, the first column has the icon changed to the 
checked version included in this sprite (dataset_row_ico.png). This is only 
when the entire row is selected, a single cell selected in a different row 
results in no checked icons in the first column at all.

5. When a entire row is selected, it is expanded to show the full text inside 
those cells. This happens if the text doesn't fit in the default "single line" 
cell height. Background color of selected row is #e9f2fd

6. When the dataset table is larger than the default (500x300px) FancyBox size, 
we add scrolls and a "Maximize" button in the corner (ds_cropped.png). The 
"Maximize" button expands the FancyBox to whatever the required size of the 
dataset table is, it can get as big as the browser window. If the dataset table 
is even bigger, the maximized FancyBox retains the scrolls as well.

Note. If required, there was some more discussion on the same subject as part 
of 
http://code.google.com/p/web-to-print-scripts/issues/detail?id=58

Original comment by agur...@gmail.com on 18 Jan 2012 at 12:58

Attachments:

GoogleCodeExporter commented 9 years ago
Atanas, we need to make a few changes to the mockups.

1. The color scheme doesn't quite go with the default mage theme. Customers 
will make their own, but lt's keep it as neutral as possible.

2. Standard fonts?

3. The checkbox needs to be the standard one, no arrow. Flatten it.

We need 2 templates for testing.

1. Allow selection of individual cells.
2. Enforce row selection.

Original comment by ad...@zetaprints.com on 19 Jan 2012 at 9:53

GoogleCodeExporter commented 9 years ago
If the row selection is enforced the fields included in the DS should be locked 
(no manual input). In this case clicking on the field pops up the dataset for 
selection same as clicking on DS button.

Don't bother with dropdowns and checkboxes. A properly constructed template 
will have only text inputs for fields included in the dataset.

Original comment by ad...@zetaprints.com on 19 Jan 2012 at 9:53

GoogleCodeExporter commented 9 years ago
Here's the mockup with the new colors (D3-1.png).

Info:
Header cells background color: #0a263c
Header cells text: #a7c6dd
Highlighted cells background color: #e2e9eb

Note. Max had an idea of using Magento native class names so that when a new 
theme is installed, the colors of this dataset table automatically fits any 
theme.

Liberal dataset template:
http://d1.zetaprints.com/magedev/index.php/sample-stationery/subcategory-01/busi
ness-card.html
Enforced dataset template:
http://d1.zetaprints.com/magedev/index.php/sample-stationery/subcategory-01/busi
ness-card-enforced-dataset.html

Original comment by agur...@gmail.com on 19 Jan 2012 at 11:22

Attachments:

GoogleCodeExporter commented 9 years ago
Enforcement example:

http://cname.zetaprints.com/?page=template-xml;TemplateID=87AE32CE-BDE1-4100-B58
E-1D1926A8556F

<TemplateDetails TemplateID="87AE32CE-BDE1-4100-B58E-1D1926A8556F" 
CorporateID="F431141D-27EA-4A35-9B0A-C10962CDC98C" Comments="This product has a 
description." GeneratePdf="1" Download="allow" 
AccessURL="http://cname.zetaprints.com/?page=template;TemplateID=87AE32CE-BDE1-4
100-B58E-1D1926A8556F" ProductReference="" VersionLatest="20110707000000" 
DatasetIntegrityEnforce="1" MissedPages="">

@DatasetIntegrityEnforce="1"

Original comment by ad...@zetaprints.com on 1 Feb 2012 at 12:41

GoogleCodeExporter commented 9 years ago
Please, test with 2.0.1.0alpha2 release.

Original comment by Anatoly....@gmail.com on 2 Feb 2012 at 7:43

GoogleCodeExporter commented 9 years ago

Original comment by Anatoly....@gmail.com on 2 Feb 2012 at 8:11

GoogleCodeExporter commented 9 years ago
Atanas, prepare one more dataset with long values and a large table. We need to 
see how resizing and multiline selection works.

Original comment by ad...@zetaprints.com on 2 Feb 2012 at 10:54

GoogleCodeExporter commented 9 years ago
Tested on /magedev/
web_to_print_store_incl_theme   2.0.1.0alpha2 (alpha)

Here are the issues I ran into:

1. Dataset button appears same as other Magento buttons. It's not that it is a 
bad design or whatever, it just looks too prominent. "Update preview" and "Add 
to cart" buttons are far more important, they should be more prominent, not 
same as DS one. This is why the mockup contained that "default" style of button.

2. The cursor should change into a pointer on cell hover (dataset_01.png).

3. When an entire row is selected, the over-flooded cells should expand to show 
the full text in them. Just the ones that are in the selected row and the ones 
that are selected on their own.

4. Enforced scenario doesn't work. This template:
http://d1.zetaprints.com/magedev/index.php/sample-stationery/subcategory-01/busi
ness-card-enforced-dataset.html
has a enforced dataset. I should only be able to select entire rows, not 
individual cells. Currently, I'm able to combine cells.
Also, I should not be able to manually input text in the text fields of the 
form when there is a "enforced" dataset active (comment #3).

5. The corner button of the FancyBox is suppose to be that "Save | X" button 
like we have on selecting stock images (see mockups).

6. The fields that have no data in the dataset should also be present in the 
dataset table represented by empty cells (dataset_02.png).

7. The hint is missing from under the table (See mockups).

Original comment by agur...@gmail.com on 2 Feb 2012 at 11:40

Attachments:

GoogleCodeExporter commented 9 years ago
Here's the big dataset template:
http://d1.zetaprints.com/magedev/index.php/sample-stationery/subcategory-01/big-
dataset.html

on w2p portal:
http://cname.zetaprints.com/?page=template;TemplateID=DCDAECCE-7F21-4BAB-8D23-EC
86218F7C36

Original comment by agur...@gmail.com on 2 Feb 2012 at 12:08

GoogleCodeExporter commented 9 years ago

Original comment by ad...@zetaprints.com on 3 Feb 2012 at 10:22

GoogleCodeExporter commented 9 years ago
From comment 9

1. Dataset button appears same as other Magento buttons. ..... This is why the 
mockup contained that "default" style of button.

Can we stick we standard magento styles?
Orange is bad, but we are introducing another custom style. 
I guess we have to go with it if there is no standard alternative.

5. The corner button of the FancyBox is suppose to be that "Save | X" button 
like we have on selecting stock images (see mockups).

If it's save | X then what's the difference? Then we need to implement Save as 
save and X as cancel. No point having both doing the same thing.
Let's just leave it as is with X only as long as the values are populated on 
selection, not on closing the box.

Original comment by ad...@zetaprints.com on 4 Feb 2012 at 6:14

GoogleCodeExporter commented 9 years ago
From comment 12

> Can we stick we standard magento styles?
> Orange is bad, but we are introducing another custom style. 
> I guess we have to go with it if there is no standard alternative.

It's a standard magento style for buttons.

Original comment by Anatoly....@gmail.com on 4 Feb 2012 at 6:29

GoogleCodeExporter commented 9 years ago
Hm. Looks like 6 is going to take up space for no reason. Probably not.

Original comment by ad...@zetaprints.com on 4 Feb 2012 at 9:07

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

Original comment by Anatoly....@gmail.com on 5 Feb 2012 at 4:31

GoogleCodeExporter commented 9 years ago
Please, test it with 2.0.1.0alpha3 release

Original comment by Anatoly....@gmail.com on 6 Feb 2012 at 11:42

GoogleCodeExporter commented 9 years ago
Tested on /magedev/
web_to_print_store_incl_theme 2.0.1.0alpha3 (alpha)

All bugs listed in comment 8 are Test OK. These are new ones:

1. IE9 expands the datsets FancyBox when the mouse hover above the check-boxes 
in the first column (ie_hover.png). Just hover the mouse above the first column 
top to bottom and the you'll see the fancybox expand bellow.

2. There are these annoying hover left-overs (hover_left_overs.png) that show 
up in all browsers. It basically happens more on faster mouse movements. Select 
a cell here and there, hover above a few of them and close the fancybox. Pretty 
often a hover box will stay on the screen after the dataset fancybox closes.

3. IE7 doesn't show the scroll when the fancybox is larger than the browser 
window. It just forces the fancybox to fit in whatever space it has. When 
there's no more space, it cuts part of the dataset table. There are 18 columns 
in this screenshot (ie7_dataset.png), there should be 20.

Original comment by agur...@gmail.com on 6 Feb 2012 at 1:38

Attachments:

GoogleCodeExporter commented 9 years ago
Atanas, we are out of units on this one. Re-post as a new issue?
Also, I wouldn't be too hung up on IE7. Happy as long as it can be used, even 
if it's not perfect.

Original comment by ad...@zetaprints.com on 6 Feb 2012 at 7:37

GoogleCodeExporter commented 9 years ago
Those are not show stoppers.
The feature works good, I posted a separate issue for the minor bugs:
http://code.google.com/p/magento-w2p/issues/detail?id=745

Original comment by agur...@gmail.com on 7 Feb 2012 at 8:35

GoogleCodeExporter commented 9 years ago
Wow!

Original comment by ad...@zetaprints.com on 7 Feb 2012 at 10:17

GoogleCodeExporter commented 9 years ago
Wiki is updated: 
http://code.google.com/p/magento-w2p/source/diff?spec=svn1894&r=1894&format=side
&path=/wiki/CustomThemeNative.wiki

Original comment by Anatoly....@gmail.com on 13 Feb 2012 at 6:12

GoogleCodeExporter commented 9 years ago

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

GoogleCodeExporter commented 9 years ago
Temporary post location:
http://www.zetaprints.com/magentohelp/dataset-replacement/
to replace this one:
http://www.zetaprints.com/magentohelp/datasets-in-magento-web-to-print-products/

Original comment by agur...@gmail.com on 27 Mar 2012 at 3:52

GoogleCodeExporter commented 9 years ago
Yes, looks good. Keep the same URL?

Original comment by ad...@zetaprints.com on 28 Mar 2012 at 12:57

GoogleCodeExporter commented 9 years ago
Done:
http://www.zetaprints.com/magentohelp/datasets-in-magento-web-to-print-products/
also added the bottom row to features table:
http://www.zetaprints.com/magento-web-to-print/features

Original comment by agur...@gmail.com on 28 Mar 2012 at 9:52

GoogleCodeExporter commented 9 years ago

Original comment by ad...@zetaprints.com on 3 Apr 2012 at 12:11