X-Git-Url: https://sipb.mit.edu/gitweb.cgi/wiki.git/blobdiff_plain/9a528150f42b376369d27141a8b0ceb107015570..f1772978beb653da7ca95fd7f5f9999982e37f0f:/projects/clockworks.mdwn diff --git a/projects/clockworks.mdwn b/projects/clockworks.mdwn index a9e01f9..9f415f8 100644 --- a/projects/clockworks.mdwn +++ b/projects/clockworks.mdwn @@ -28,16 +28,16 @@ What do people not like about Doodle? ### What to do? -* [Configure](http://docs.turbogears.org/1.0/Configuration?action=show&redirect=1.0%2FGettingStarted%2FConfiguration) the default TurboGears scaffolding * Work through the [TurboGears tutorial](http://docs.turbogears.org/1.0/Wiki20/Page1) (the tutorial seems to focus on SQLObject, which is not necessarily the best thing. Maybe someone can find some better docs?) * Setup database configuration and installer (an auxiliary issue is the presence of an installer for people). (**ezyang**) * Learn SQLAlchemy (**ezyang**) * Make sure the default scaffolding works on Scripts (this includes running TurboGears as CGI). Any work done here should be considered for a TurboGears auto-installer, the equivalent of tgsetup) (**ezyang**) * Write a .gitignore file for generated/not versionable items * Get friendly URLs working -* Learn Genshi (The new TurboGear default templating interface for 1.1+) * Setup a zephyrbot that watches the repository -* Learn [Widgets](http://docs.turbogears.org/1.0/Widgets) (we'll be using them for all of the forms in this website) +* [Configure](http://turbogears.org/2.0/docs/main/Config.html) the default TurboGears scaffolding +* Learn [Genshi](http://turbogears.org/2.0/docs/main/Genshi.html), the templating engine +* Learn [Widgets](http://turbogears.org/2.0/docs/main/ToscaWidgets/forms.html) (we'll be using them for all of the forms in this website) * Polish up and get SSL authentication working with TurboGears Identity (the two should be integrated together in a sane manner.) * Write model classes for all of our tables * Write controllers for each of the pages @@ -78,7 +78,7 @@ You can view the database schema in *model.py*. Some notable features: List of "screens" in Doodle -* **/**: Home page +* **/**: Home page (including login) * **/help**: Help pages (screencasts, interactive JavaScript, etc.) * **/new**: Schedule event (should be one-page-able) * General info (title, description, name, email) @@ -99,17 +99,31 @@ List of "screens" in Doodle * **/events/*event-name*/admin/history**: History * **/events/*event-name*/admin/reset**: Delete all participants/comments * **/events/*event-name*/admin/delete**: Delete poll +* **/signup**: Signup page +* **/myclockworks**: List of polls created by user, list of polls the user has participated in, links to creating a new event + * **/myclockworks/account** provides links to the following four links + * **/myclockworks/changeEmail** + * **/myclockworks/changePassword** + * **/myclockworks/editInformation** + * **/myclockworks/delete** + * Note: Doodle functions by creating two links per event: one for the public and one for administrator, but anyone can follow either link if they know what it is ## Phase 2 Doodle killer. Extra features. Pump it up. +* Better UI * Integration * Basic: integration with ICS calendars, GoogleCalendar, Exchange, and TechTime (for faculty) * Advanced: integration with MIT's course schedules, Facebook * Would store persistent profiles of calendar data for users * Automatically prioritize and schedule events for you * Create mobile phone friendly version +* View of a single calendar month should show "ghosts" of days from immediately previous and immediately past months, to fill out all the weeks. +* Ability to convert Yes/No polls into Yes/Maybe/No polls (and vice versa) +* When setting up a new poll, ability to copy-paste the times for any arbitrary row into any number of other arbitrary rows +* "Generic week" function + * Indicates that the response is for a weekly meeting, not a specific date. ## Developers