forked from skandragon/thing
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathTODO.txt
50 lines (34 loc) · 1.94 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
* Private camp locations, 2 per page, with lines to write on
* Class attendance count entry, pull-down for date and time, per location
* Filter classes displayed in track listing (for coordinators) and for
users making a custom schdedule by date.
* Sort classes displayed in track listing and for users by date, rather than
class name.
* Allow users to block out time they will NOT want to see any potential
classes for.
* Allow track coordinators to create some sort of placeholder user, which
can be used for scheduling. Also, overridding instances per-instructor
would be good. These classes might not count against the would-be
user, and act more like "additional instructors" do now.
* Revamp the topic/culture listings we use.
* Email when a class is added to a user's "watch list" of topics.
* Email when a class is moved to a track, mailing both the winning and
losing track coordinators.
* Email to instructors when instructor-visible changes occur to a class.
* Bug: database summary show classes which had N instances, but had some
removed and the count lowered, as needing to be scheduled. This is
probably a flagging issue with the scheduled flag.
* Show duration, do not show end time, for users / instructors / etc.
* Don't use military time when possible.
* Allow admin to switch users (probably one direction only, into another
non-admin user)
* On the free/busy list of rooms, clicking on a time and location should
pop up a list of classes which are pending schedule for that track,
with a search field for name and track. Selecting a class from this
list should populate an empty instance with that class. If there are
suddennly no free instances (someone else did it already) open up
the normal scheduling page with a flash indicating what happened, and
let the user fix it.
* Be more web 2.0, and use more ajax calls as appropriate. Ideally, a
javascript framework would be awesome.
* Per-instance user schedules