IMHO it would be great to have voting with more than 1 point, I mean:

- change the vote process(vud_vote) to allow process more than 1 point
- think how to pass the information to the widgets
- implement a widget that support +N/-N on votes

Now we want to make a stable 2.x, so let's do that for the next major version.

Comments

marvil07’s picture

Version: 6.x-2.x-dev » 6.x-3.x-dev
Status: Postponed » Active
marvil07’s picture

Title: allow voting with more than 1 point » +N/-N votes on widgets

I think the right place to handle the "N" would be on the widget creation.

Update: If you choose N for a widget, then the widget votes are allowed to be from -N to N

marvil07’s picture

After reading an eaton comment I'm reconsidering this, but I still think it will work, because the points(N) can not be changed since they will be set at code on the widget definition.

Any feedback would be appreciated.

BTW let's remember that we use points and not percentage for storing each vote, so +4 of a possible +5/-5 will mean 4 votes instead of 80% "agree", this can affect the idea of the votes we are creating.

Soren Jones’s picture

+1

I don't see a reason for limiting Vote up/down to 1 point in either direction.

I used a heavily hacked Fivestar in a proof of concept where users could vote a node up by a maximum number of points and cast a limited total number of up votes.

It's been a while, so I'm not sure, but I think I chose Fivestar for its basic UI. I liked that users could change a vote from zero to five points with one click. HOWEVER, Vote up/down would have had two advantages over Fivestar: 1) Vote up/down uses points and 2) the "up/down" metaphor is really more relevant in that use case than the "rating" metaphor.

BTW let's remember that we use points and not percentage for storing each vote

IMHO that's a good thing. At the same time, now that there are separate positive and negative vote totals, it seems that it would be easier to get percentages if people want them. (I'm showing percentages in one place that I'm using a derivative of Vote up/down -- again just a proof of concept.)

marvil07’s picture

Status: Active » Postponed

No more features for 6.x-3.x now that it is the stable branch, moving to 7.x-1.x as postponed until basic port is ready.

marvil07’s picture

Version: 6.x-3.x-dev » 7.x-1.x-dev
marvil07’s picture

Issue summary: View changes
Status: Postponed » Active