This repository has been archived by the owner on Jul 22, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathtodo.txt
98 lines (49 loc) · 2.39 KB
/
todo.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
== TO - DO ==
*confirm that persistant login works and makes sense
**then commit it
*allow someone to link from spike and play as logged in student
*BUG - when submitting three names it doesn't complain :(
*email notifications when your partner has gone
*add email address to prisoner
*add new user signup form
*connect to LLGroup so that any wharton person can be a prisoner
*make create/join new game options for users
*use label tags where appropriate
*have a think about CSRF and escaping of input
*make prisoner list and game list sortable...jquery???
*allow player to revise their decision as long as the other player hasn't gone
*have a think about real time play and how to improve....not require refreshing every few seconds
*why doesn't it complain when :on => :save is specified for prisoner password validations
Further study
*study and improve with CSS
*study and improve with jQuery
*make a mobile version???
== DONE (sorted by date in descending order) ==
*make sure a person can only get to their allowed games
*take prisoner out of URL so it can't be tampered with
*finish convert the plead guilty/non-guilty to form rather than links
*complain when someone sets a password to less than the password limit!!
*make the reset of a password optional when editing a prisoner
*separate admin from regular play
*modify games views/controllers to allow the adding of prisoners
*create is_admin attribute for prisoner
*authentication
**add password to the edit and create prisoner forms
**set up an access controller
**set everyone's password to "test" but with different salt
**set up some login views
**put filters in appropriate places
March 28th
**set up a virtual attribute, "password"
*more descriptive output when password is too short... now it is very confusing... silent error
**added attribute protection
**set up some convenient salting and hashing functions
**migrate Users to have fields necessary for user authentication, put in separate migration
*Add links "modify pris" and "modify games" so you can go anywhere
*Feb 23 2012
*decided to store game/player information in URL
* change display play_game based on game state
* get plead guilty to update database successfully
* fix things so that you see only games that belong to a certain user
* is there a better way to relate two players to a game without order?
** how do relationships work in this situation?