Task Breakdown

From Lifeguide Wiki
Revision as of 14:47, 14 November 2008 by 152.78.64.156 (talk) (New page: ==Life Guide Project Breakdown== ==Delivery before 5th Jan 2009== ===Intervention Builder=== • Main Application Framework • Integrate Page Editor • Page Logic Compiler (Convert + S...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Life Guide Project Breakdown

Delivery before 5th Jan 2009

Intervention Builder

• Main Application Framework • Integrate Page Editor • Page Logic Compiler (Convert + Script =>QTI) • Intervention Properties Editor (optional) • Load/Save • Intervention Logic Compiler • Logic Editor


Backend

  • Bugs in flow logging (jumps not always recorded properly)
  • Investigate IE handling of backwards (might need to generate unique urls...)
  • Timing bugs - total time is really broken if you go back... This is probably because the total time calculation isn't taking into account all the ItemStates...
  • Recording of offsite or internal html jumps
  • Investigate possibility of using virtual host for a particular intervention - what needs to be done to support this???

Player

  • Method to render page by id, rather than path -- completed 17/09/08
  • List of pages (render test through xslt)? -- basic implementation done. What other features are required?
  • Side-by-side rendering of choiceInteractions (for showing yes/no radio buttons side-by side)
  • Improved popup windows
  • Email scheduling from intervention
  • Testing

Known Issues

  • When a submit-jumpto button is pressed, LifeGuide records a move to the next page in the flow followed by a jump to the target page. This is a side effect of the button having to make sure that all validation is done on the current page before moving on (if the current page doesn't validate, then you probably don't want to fulfil the jump). TODO: It might be possible to filter the extra sequence nodes to remove the unseen page from appearing...
  • You can't jumpto anything other than an item... Sections and testParts are currently not supported - this would have to be dealt with in the item flow I believe, but would be non-trivial.