$msg.get("polls.home.title") (Polls.WebHome)

Silvia Rusu, 2010/04/14 11:10

A friendlier error message for the wrong date order would be nice. Currently it's "polls.form.error.wrongDateOrder"

Marta Girdea, 2010/04/14 11:44

Oops, translation missing, will fix.

Silvia Rusu, 2010/04/14 11:25

For rating polls maybe we should restrict the average to 2 decimals after the "." (e.g. for "XWiki Features" one of the answers is "Extensibility", which currently has an average of 3.3333333333333335; we could make this 3.33)

Marta Girdea, 2010/04/14 11:45

Good point. It was already done in some other places, now fixed there, too.

Silvia Rusu, 2010/04/14 11:31

I think displaying the number of people that voted on a poll is a good idea. You can currently calculate the number by counting the names/the votes. However, if a poll has many voters this way of procuring the information might get difficult/inefficient.

Marta Girdea, 2010/04/14 11:45

+1, this information is useful.

Silvia Rusu, 2010/04/14 11:51

Let's say an answer appears more than once in a single poll. Those answers (the same answer repeated) will be shown as a single entry in the graphic and the votes won't appear in the image (e.g. http://incubator.myxwiki.org/xwiki/bin/view/Polls/FavoriteJamesCameronmovie )

Sergiu Dumitriu, 2010/04/15 19:50

This is a problem inside the charting plugin, it's very hard to fix on our side.

Silvia Rusu, 2010/04/14 11:58

If the option exceeds a certain number of characters only a limited number of characters will be displayed in the graphic (e.g. "camouflage green" becomes "camouf..." on FavoriteColor); Maybe we could display the option on a second line or make the graphic bigger? I am not altogether sure ab it though, since the problem would still exist for really big options.

Marta Girdea, 2010/04/14 18:36

Solution 1: rotate the label by 45° (I hope the chart macro supports this; JFreeChart surely does)
Solution 2: Assign IDs (A, B, C... or 1, 2, 3...) to the options and use these IDs in the table.
Wdyt?
- Silvia Rusu, 2010/04/14 20:42
  
  I like Solution 1 best

Vincent Massol, 2010/04/14 12:00

Really nice, well done. Under chrome I get a vertical scrollbar on the right

Sergiu Dumitriu, 2010/04/15 19:50

Fixed.

Silvia Rusu, 2010/04/14 12:05

If an user adds empty lines to a poll I think you shouldn't take them into account or you could return an error. E.g. I created a single choice poll leaving empty lines between the several options Mostproductivedayoftheweek

Marta Girdea, 2010/04/14 18:32

I thought I already did that... but apparently I missed something. Will check again, thanks.

Marius Butuc, 2010/04/14 12:31

Great app, and I really like it from the usability point of view.
I encountered one issue though: for the weighted polls, there are cases when I couldn't select a specific value e. g., I was able to slide to 49% or 51%, but not to 50%. (like in the Coffee time poll)

Possible ideas:

to make the slider wider;
allow the user to change the slider value by keys e. g., up/down, left/right, page up/down, home/end etc. (also useful for accessibility).

Marta Girdea, 2010/04/14 18:30

Will start by making the slider wider. Changing by keys is a great idea. What might also work is placing little arrows to the left and the right of the slider, with the effect of increasing/decreasing the value by 1.
Marta Girdea, 2010/04/15 13:54

In the end I implemented the increase/decrease arrows. Is this better?

Marius Butuc, 2010/04/14 12:37

Also, when the poll hasn't begun yet instead of the current "don't show the options" strategy, we could display an info stating that it's not active yet, and users could vote starting date/time X.

Silvia Rusu, 2010/04/14 12:44

The info is there "This poll is not open yet. It will be available from 15 April 2010, 12:00 to 16 April 2010, 12:00."
- Marius Butuc, 2010/04/14 12:51
  
  I didn't even notice it!
  Could it be better to emphasize more on that piece of information? Maybe bring it in an area with more focus e.g., where the options will reside upon poll activation?
  - Marta Girdea, 2010/04/14 18:24
    
    Will do.

Marius Butuc, 2010/04/14 12:44

Would it be feasible/worth it to have an open answer possibility?
e. g., Other: |text input|

Marta Girdea, 2010/04/14 18:26

Feasible - yes. Worth - probably yes, if we we want a fully featured poll app. Contributions welcome

Silvia Rusu, 2010/04/14 16:10

I'm not sure why this happens but in the tag list on this page:

when you click "favorite" + "rating" or "favorite" + "single" both tags remain selected; you may cancel any of the filters by clicking on the tags
when you click "favorite" + "weighted" only the tag "weighted" remains selected. Though the filtering is done for both tags you cannot cancel the "favorite" filter unless you cancel the "weighted" filter first

Sergiu Dumitriu, 2010/04/15 21:59

Noticed this problem too, it's a bug in the livetable.

Silvia Rusu, 2010/04/14 16:17

In the Poll table on the current page:

Sorting by start date doesn't change anything
Sorting by end date causes for the table to become empty
Sorting the "Launched by" column doesn't work properly (the entry order is changed, but entries still aren't in alphabetical order)

Marta Girdea, 2010/04/14 18:20

These must be livetable issues. I don't know yet what causes the first 2, but the "Launched by" column behaves like this because in fact the sorted values are the user names (e.g. xwiki:XWiki.marta, incubator:XWiki.SilviaRusu), which are different from the displayed values. Indeed this is confusing for an end user. Until the sorting on the displayed values can be efficiently done in the livetable, we should probably not make such columns sortable/filterable.

Ciprian Amaritei, 2010/04/16 10:21

It works and looks very nice, but I think that for Multiple choice pools it does not calculate correctly the Percentage.

Marta Girdea, 2010/04/16 10:43

Where is the percentage computed incorrectly, in the results table? Can you give more details and/or an example of wrong calculation?
Marta Girdea, 2010/04/16 10:50

I think I see what you mean. That percentage is actually the percentage of voters who chose that option (not the percentage assigned to that option). Indeed, it does not sum up to 100% if some people chose more than one option, and this can be confusing. Maybe we should change the the label, to make it more clear.
Actually, there is room for improvement from several points of view in the results section. We should decide which is the relevant information to display there.
- Ciprian Amaritei, 2010/04/16 12:11
  
  I thought that the Percentage for each choice will be : 100 / total_number_of_votes * votes_per_choice. For Single choice pools seems to work this way.
  - Marta Girdea, 2010/04/16 12:22
    
    Yes, for single choice both formulas apply. For multiple, where people are allowed to select different numbers of choices, I see several ways of aggregating the results:
    Display what percentage of participants chose each option - as it is done now (but with a label more expressive than plain 'Percentage' so that there's no more confusion)
    Consider that the voter splits his one vote evenly between the chosen options, and compute the percentage as it is done for the 'Multiple weighted choice' polls.
    Like you said, compute for each option the percentage of votes it obtained relatively to the whole number of cast votes.
    Numbers 1 and 3 both make sense and seem relevant for multiple choice, how about including them both in the results?
    
    Ciprian Amaritei, 2010/04/16 12:42
    
    Ok, actually now I see that the current formula refers to the number of people who voted and not to the votes itself. If no other people got confused by the current solution as I was, I think this is the best solution. The question could be: What has more relevance: the number of votes or the number of voters?
    
    Marta Girdea, 2010/04/16 12:47
    
    No, I think you're perfectly right, it is very likely to be confusing. And your formula is relevant, I'll include it.

Comments on $msg.get("polls.home.title")

Navigation

$xwiki.getDocument('Help.SupportPanel.Content').translatedDocument.title