Intervention Manager: Difference between revisions
Jump to navigation
Jump to search
(→Player) |
|||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 17: | Line 17: | ||
===Backend=== | ===Backend=== | ||
* Bugs in flow logging (jumps not always recorded properly) | * <s>Bugs in flow logging (jumps not always recorded properly)</s> | ||
* Investigate IE handling of backwards (might need to generate unique urls...) | * <s>Investigate IE handling of backwards (might need to generate unique urls...)</s> | ||
* Timing bugs - total time is really broken if you go back | * 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 | * 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??? | * Investigate possibility of using virtual host for a particular intervention - what needs to be done to support this??? | ||
| Line 29: | Line 29: | ||
* Improved popup windows | * Improved popup windows | ||
* Email scheduling from intervention | * Email scheduling from intervention | ||
* | * [[LM_Player_Testing|Testing]] | ||
==Known Issues== | ==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... | * <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. | ||
Latest revision as of 12:16, 6 November 2008
Screenshots
Grouped by event, so that we have a chronological record
TODO
Frontend
- Personal messaging - i.e. when you have been added to an intervention, etc....
- Improved rendering of sequence chart - show offsite jumps, etc -> re-implement in Flex?
- Improved rendering of overview weighted digraph -> re-implement in Flex?
- Pages for deploying and editing interventions
- Emailer pages
- More stats in the information boxes!!
- Forum
- Forum and wiki registration linked with manager
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/08List 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.