Technical Architecture
This page is a working area for the SRG technical team - it will be changing over the course of SRG Prototype development.
Item Owner is/are the person(s) responsible for coordinating communication and secondary assistance to get the item done.
Status column - Done, Active or Sleeping. If Active, please fill in the notes area on where the status of the task is. It is the item owner's responsibility to make sure all active items have notes in them. Also, a task can go from Active to Sleep. If an item goes from active to sleep please not only put it in sleep but then put in that block who put it to sleep. As of this writing, item #1 has an example of this. Do remember - an item with a status of sleep with no name by it and no notes implies NO work has been done on said item. If this is NOT the case, please update the item with notes on what has been done towards completing the item and put your name by the sleep status.
If you move a status from Active to Done, please put your name next to the Done status along with the date it was completed. Done status items can open back up if needs arise.
General items to be completed
Item # |
Name |
Person/People Assigned to Work On It |
Notes |
Status |
---|---|---|---|---|
1 |
Design and implement the ability for passing form parameters into _NewItemProducer via AHAH form submission in AuthorProducer |
Damian, Gaurav |
Damian edited view parameters to allow itemId hidden form field to be submitted to _NewItemproducer. Gaurav is using this id right now in items 2 and 4 |
S - Damian |
2 |
Create a list of "information" that needs to be passed back and forth in item #1 and #3 |
Gaurav |
NOTES |
A |
3 |
Design and implement the ability for passing information FROM _Newitemproducer back to AuthorProducer |
Damian, Gaurav |
Waiting for item #2 |
S - Damian |
4 |
Moving Javascript callbacks into _NewItemProducer |
Gaurav, Damian |
NOTES |
A |
5 |
Implement Renderers (JointContainers) in _NewItemProducer |
Damian, Jim, Gaurav |
Injected ContentItemRenderer into _NewItemProducer |
S - Damian |
6 |
Persist in _NewItemProducer |
Damian, Jim, Gaurav |
NOTES |
S |
7 |
Retrieval of existing SRG |
Jim, Gaurav, Damian |
Need to sync up with view generated by AHAH |
A |
8 |
Making sure order of items when created are same as when retrieved |
Jim, Gaurav, Damian |
NOTES |
S |
9 |
Citation helper integration |
Steve, Jim, Damian, Gaurav |
Jim roughed in a renderer for CitationList (either as link or inline) |
A |
10 |
Editing an existing guide |
Gaurav, Jim, Damian |
NOTES |
S |
Tasks remaining for Prototype (phase 1)
Task |
Due |
People |
Status |
---|---|---|---|
Add to JS init method (srg.attachJS()) so that it attaches handlers to a fully-rendered research guide |
28 Feb |
Gaurav |
started |
Finish link editing in the author4.html template and Srg.js (no other tasks (persistence, rendering, etc.) depend on this) |
28 Feb |
Gaurav |
started |
XHTML cleanup - making sure the author4.html template creates compliant XHTML 1.0 (this is important for rendering content) |
28 Feb |
Gaurav |
open |
Inserting round-trip AHAH update notes in the Javascript (round-trip server call, bringing back content to insert in the DOM - notes indicate when/where this should happen) |
28 Feb |
Gaurav |
done |
Inserting one-way AJAX update notes in the Javascript (one-way server call, sending updated content to the server - notes indicate when/where this should happen) |
28 Feb |
Gaurav |
done |
Implementing round-trip AHAH updates (pulling XHTML content from the server into the DOM) can we break this down? |
 |
Damian All? |
started |
Implementing one-way AJAX updates (updating the database with content from the client) can we break this down? |
 |
Damian All? |
started |
Revising logic API's as needed to handle needs of AHAH producer to save changes made by user |
 |
Jim |
open |
Identifying which html elements produced by renderers need unique ID's |
 |
Gaurav |
open |
Getting renderers to provide unique ID's for html elements |
 |
Jim |
open |
Implementation dependencies - consolidating our work
 |
Damian |
Jim |
Steve |
Gaurav |
---|---|---|---|---|
What I'm working on |
RSF Persistence
|
RSF Rendering
|
|
Authoring Template
|
What I need from others |
 |
RSF Bindings |
 |
Direction on which XHTML snippets need to be run through RSF (AHAH) |
What I provide to others |
 |
 |
 |
Javascript-generated XHTML for all content items |
Questions
- AHAH vs. simple AJAX load
- Can we drop subsections for now?
- there are other things that might be better to work on: embedding a link in-line, drag-and-drop (via Lightbox)
Brainstorming and Action items from 12 Nov 2007
Data Object Class hierarchy (Damian)
- SRG Docs contain Data Objects; all Data Objects have common attributes
- parent - what SRG document this is a part of
- position in parent - where in the document hierarchy does this object fit in
- title
- description
- etc. ...
- SRG Data Object baseclass defines Data Objects
View SRG Data Object Class Diagram
- More specific Data Objects (i.e. Citation Lists, Canned Searches, etc.) will subclass SRG Data Object baseclass
Overall technical diagram (Gaurav)
Decision on where SRG functionality will live (Jim)
- Perhaps consult overall Sakai Roadmap docs for guidance on future direction of "things" (docs, resources, etc.) in Sakai
- Resources Helper vs. Own Tool vs. Outside Webapp integrated with Sakai vs. some combination of all
Top-level view of the authoring environment (for next week - 19 Nov)
- A toolbar with actions in it
- Add a ... (Citation List, Canned Search, Link, etc...)