X-Git-Url: https://sipb.mit.edu/gitweb.cgi/wiki.git/blobdiff_plain/050e3ae71c25c9fdbfa66e31268c7987b78638f0..75e2c2b1a700a2228ca26e021e282d4b6c1af4fd:/projects/clockworks.mdwn
diff --git a/projects/clockworks.mdwn b/projects/clockworks.mdwn
index bebdc68..f32acab 100644
--- a/projects/clockworks.mdwn
+++ b/projects/clockworks.mdwn
@@ -16,10 +16,14 @@ Our Git repository is located in AFS in the clockworks locker: /mit/clockworks/c
Doodle clone. 100% duplication of Doodle functionality. Modifications to improve usability as necessary.
+### Pitfalls to avoid
+
What do people not like about Doodle?
* Too much clicking
+ * We can deal with this by collapsing the three-page wizard Doodle has into a single page. Be careful not to sacrifice too much simplicity for such a setup.
* No obvious "I can, but would rather not"
+ * Alleviated also by the above; this might want to be the default poll setup.
### What to do?
@@ -30,15 +34,24 @@ What do people not like about Doodle?
* 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 TurboGear's templating interface (would like XSLT, but I don't think anyone else will like that)
+* 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)
+* Polish up and get SSL authentication working with TurboGears Identity (the two should be integrated together in a sane manner.)
### Architecture
-* Python and Turbogears
-* Git repository
-* Use 15 minute timeslices to simplify interface (?)
-* AJAX (?)
+* **Language**: Python
+* **Framework**: TurboGears
+* **SCM**: Git
+* **JavaScript**: Mochikit
+* **Database**: SQLite for development, ? for production
+* **ORM**: SQLAlchemy (possibly Elixir?)
+* **Templating**: Genshi
+
+Other ideas:
+
+* Use 15 minute timeslices to simplify interface
### Principles
@@ -54,27 +67,27 @@ To be transferred from the whiteboard
List of "screens" in Doodle
-* Home page
-* Help pages (screencasts, interactive JavaScript, etc.)
-* Schedule event (should be one-page-able)
+* **/**: Home page
+* **/help**: Help pages (screencasts, interactive JavaScript, etc.)
+* **/new**: Schedule event (should be one-page-able)
* General info (title, description, name, email)
* Days (calendar, should be AJAX)
* Times (timezone (JS fill-in), add more timeslots, copypaste first row)
* Options (yes-no-ifneedbe, hidden poll, limit OKs)
* Poll created (admin, participant links)
-* View poll (timezone, name, times, information, functions)
- * Edit entry (completely wiki!)
+* **/events/*event-name***: View poll (timezone, name, times, information, functions)
+ * **/events/*event-name*/edit**: Edit entry (completely wiki!)
* Delete entry
- * Add a comment
- * Calendar export (both ways)
+ * **/events/*event-name*/comment**: Add a comment
+ * **/events/*event-name*/export**: Calendar export (both ways)
* File export (excel, pdf)
- * Subscribe (atom, and then social feed services)
- * Embed poll (iframe)
-* Admin poll (participation link)
- * Edit poll (all original options)
- * History
- * Delete all participants/comments
- * Delete poll
+ * **/events/*event-name*/feed**: Subscribe (atom, and then social feed services)
+ * **/events/*event-name*/embed**: Embed poll (iframe)
+* **/events/*event-name*/admin**: Admin poll (participation link)
+ * **/events/*event-name*/admin/edit**: Edit poll (all original options)
+ * **/events/*event-name*/admin/history**: History
+ * **/events/*event-name*/admin/reset**: Delete all participants/comments
+ * **/events/*event-name*/admin/delete**: Delete poll
## Phase 2