neobappy / django-voting

Automatically exported from code.google.com/p/django-voting
Other
0 stars 0 forks source link

Ability to track votes over time #20

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Enhancement Request.
1. The ability to track a vote with a timestamp for computing the score at
any given time.

Please provide any additional information below.

I'm going to start some work on this but help is greatly appreciated. 
Hopefully this can be committed so that others can use it.

Original issue reported on code.google.com by arocki...@gmail.com on 16 Jan 2009 at 9:24

GoogleCodeExporter commented 8 years ago
I see some of this functionality in SOClone (bet you thought nobody reads that 
stuff
:-)):

http://code.google.com/p/soclone/source/browse/trunk/soclone/models.py?spec=svn1
4&r=14

I'll try adapting some of that stuff for porting here.  My goal is actually to 
have:

Events (django-events)
Possible Outcomes of Events (similar to 'answers' in SOClone)
Votes on Possible Outcomes of Events (django-voting once this ticket is done)
History of Votes on Possible Outcomes of Events (django-voting once this ticket 
is done)

I'm going to work on this over the next week but would love to coordinate with
somebody so that there is a reusable chunk of code. 

Adam - adam@varud.com

Original comment by arocki...@gmail.com on 16 Jan 2009 at 11:23

GoogleCodeExporter commented 8 years ago
This diff does three very small things:

1. Comments out redundant ctype variable setting in managers.py (that line 
could just
be deleted).
2. Saves '0' votes so we know, for instance, if somebody ever voted.
3. Adds 'created_on' field so that we know when the the vote was made.

I'd really love it if these small changes can be made to the voting app - 
otherwise
I'm going to have to fork it (although perhaps I could extend these classes?).  
I'm
fine with another field name for 'created_on' in #3.

Original comment by arocki...@gmail.com on 2 Feb 2009 at 4:50

Attachments: