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

Improve the display of Poll entries #4

Closed
evalica opened this Issue Nov 22, 2017 · 6 comments

Comments

Projects
None yet
3 participants
@evalica
Copy link

evalica commented Nov 22, 2017

We can improve the way the display the sheet, by better displaying the columns.
Current
current

@evalica evalica changed the title Meeting's Calendar link broken for French translation REUSE ME Nov 22, 2017

@evalica evalica changed the title REUSE ME Improve the display for Flash entries Nov 22, 2017

@evalica evalica changed the title Improve the display for Flash entries Improve the display for Poll entries Nov 22, 2017

@evalica evalica changed the title Improve the display for Poll entries Improve the display of Poll entries Nov 22, 2017

@acotiuga acotiuga added this to the 1.8 milestone Nov 23, 2017

@acotiuga acotiuga modified the milestones: 1.8, 1.9 Feb 2, 2018

@acotiuga acotiuga removed this from the 1.9 milestone Jul 5, 2018

@CostiChD CostiChD self-assigned this Aug 22, 2018

@CostiChD

This comment has been minimized.

Copy link

CostiChD commented Aug 22, 2018

After #17 was solved, the name label does not appear anymore in view mode. Also, I would like to know if we should(or not) show empty properties(check the "DESCRIPTION" in the image above).

@evalica

This comment has been minimized.

Copy link

evalica commented Aug 22, 2018

This issue is more about improving the sheet of the Polls. For example, the Status could be displayed in another column, similar to what we have for the Meetings.
Also WebHome should not be displayed, in case that happens.
Regarding the display of empty properties. I don't have a clean answer for this. For some of our applications we are hiding some fields, where for other we don't.

  • On one hand you want to hide fields that you know the user will not need and they are display not that good, by being empty. A solution for this would be to display an "empty message" like "No description" or something, that could take the value of the placeholder, if the value is empty.
  • On the other hand you want to display that there are fields there, in order to be discoverable and encourage the user to add that information.

I guess it also depends on the field. Some fields are mandatory, others are not. If in a meeting application, you have added a group, you might not need to add users, so that field could be not displayed. While you kind of always need the Description of the Poll, on order to know what's the point of the Poll.

So in this particular application and use case, I would not hide the fields, since they are minimal and mandatory. But I would enhance the display of the sheet in view mode, by having an "empty state" text.

@CostiChD

This comment has been minimized.

Copy link

CostiChD commented Aug 22, 2018

It looks like the problem about showing "WebHome" is fixed here: #11 . I'm going to add another column(trying to see which way is better) and also the "empty state" text/translation.

@CostiChD

This comment has been minimized.

Copy link

CostiChD commented Aug 27, 2018

I rearranged the labels and moved the "Status" in a second column. I also added a temporary xhint for the "Status" property. I still need to add some translations(for the empty values) .
xpoll-edit
xpoll-view

@CostiChD

This comment has been minimized.

Copy link

CostiChD commented Aug 27, 2018

Another thing that we should consider is improving the tables view. Long proposals(long strings) can cause some problems(bad display).

@CostiChD

This comment has been minimized.

Copy link

CostiChD commented Sep 6, 2018

Moved description after proposals and status:
xpoll_after_edit
xpoll_after_view

@CostiChD CostiChD added this to the 1.10 milestone Sep 12, 2018

@CostiChD CostiChD closed this Sep 12, 2018

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