Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

E-Ticket: Layout suggestions for ordered items #827

Open
philip-n opened this issue Jun 18, 2016 · 4 comments
Open

E-Ticket: Layout suggestions for ordered items #827

philip-n opened this issue Jun 18, 2016 · 4 comments

Comments

@philip-n
Copy link
Collaborator

Suggestions for layout of ordered items, applied step-by-step.

Current layout

01-current-status

Move checkboxes left

Easier to see checkboxes, clearer layout
02-checkboxes-left

Text changes

Suggestions for avoiding ambiguities
03-text-changes

Condensed clothes list

Putting all information in one line

  • makes it easier to see what value belongs to what item
  • allows for printing many items per e-ticket
  • does not become too long for one line (Woman, XXL, Windmill should be the longest description)
    04-clothes-condensed

Remove unordered things

If people have not ordered something and it is not planned to check their orders by the printout, can't we can just leave out the unordered things?
05-only-ordered-items

@BigAndini
Copy link
Owner

For some points I'm absolutely at your side. I already changed the checkboxes to appear in front of the item and the short way of showing the clothes.

The text is the description of the product. I thought it would be enough to simply show the product description as in the frontend, but maybe there is the need for separate description fields for the e-ticket.

I think one of the big advantages of having all products on the e-ticket is that every e-ticket looks similar. Yes it could be that there is unneeded content on the e-ticket but this makes the work of the volunteers at the registration desk much more easier. If they've seen one e-ticket they've seen "all". There are no new elements nothing that confuses them and therefore less question on what to do. Therefore I would vote to keep all products on the e-ticket.

@BigAndini BigAndini removed the easy label Jun 19, 2016
@philip-n
Copy link
Collaborator Author

philip-n commented Jun 19, 2016

Thanks for doing the changes!

The text is the description of the product.
Then let's leave it like that, at least for the moment! In the long run, maybe a separate field for E-Ticket description can be helpful... but also, maybe not.

Keep all items on each ticket so they look similar
As I understand it, currently the information displayed on the tablets is the "ground truth" (which is used by the volunteers for handing out stuff) and the printed tickets are just a confirmation letter for the person who registered. In that case, I think it is easier to just show the items which were actually ordered. It's also a (very) small step towards avoiding that people start photoshopping their tickets by replacing an unchecked box with a checked box.

However, I think that both versions are fine and that we do not need to change anything for the current version.

@BigAndini
Copy link
Owner

BigAndini commented Jun 19, 2016

I like the additional ideas of this issue but I think for now (EJC 2016) this would work. Therefore I will not put that much time into sorting out the unneeded items. I want to keep this issue open for later fixing.

@philip-n
Copy link
Collaborator Author

Just tested on preprod (0.4.63). Works as expected, but for one cosmetic thing: It would be great to have only the checkboxes aligned left and all other text starting at the same offset from left. See images:

Current

06-current

Proposed

07-desired

This might be easily achieved by just adding an invisible (white) graphics with the same dimensions as the checkbox graphics at the start of each line.

Bonus: Give the "empty checkbox" graphics the same dimensions as the "checked checkbox" (currently, text after empty checkboxes start very close to the checkbox).

And yes, I know that these are no pressing problems :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants