Task Breakdown: Difference between revisions
Jump to navigation
Jump to search
(New page: ==Life Guide Project Breakdown== ==Delivery before 5th Jan 2009== ===Intervention Builder=== • Main Application Framework • Integrate Page Editor • Page Logic Compiler (Convert + S...) |
No edit summary |
||
| Line 1: | Line 1: | ||
==Delivery before 5th Jan 2009== | ==Delivery before 5th Jan 2009== | ||
===Intervention Builder=== | ===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 | |||
===Player and Manager=== | |||
*Emailing Support | |||
*Timing Bug | |||
*Auto Login Support for Email link | |||
==Delivery after 5th Jan 2009== | |||
===Page Editor=== | |||
Stage 1: | |||
* | *Inline elements and containers | ||
* | *Validation | ||
==Known Issues== | ==Known Issues== | ||
* <s>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...</s> | * <s>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...</s> | ||
* 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. | * 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. | ||
Revision as of 14:50, 14 November 2008
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
Player and Manager
- Emailing Support
- Timing Bug
- Auto Login Support for Email link
Delivery after 5th Jan 2009
Page Editor
Stage 1:
- Inline elements and containers
- Validation
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.