Last modified 16 years ago
Last modified on 01/29/09 15:03:09
Analysis
Overview
This task is about the base timelines support that is in the model.
Task requirements
- Timelines should somehow be provided as part of the model.
- consider that a timelines manager will be present at some time in the future.
- consider that timelines have different channels.
- consider that timelines are constructed of primitives:
- entries.
- channels with entries.
- provide a base class hierarchy representing the timelines.
- it should define a timelines general structure.
- it should define a way to control timelines generally - start, stop, pause etc. (We may have a TimelinesManager included in the TIMELINE_MANAGEMENT tasks to do these.)
- it should provide a vision about timelines persistence.
- Provide a design diagrams backed up with explanations about the general concept.
- Notes:
- The task is tightly connected with other tasks about timelines which will occur at iterations 4, 5 and generally 6.
- Considering this task's effort and that other tasks that are connected will appear later:
- Come up with general design in the model about timelines.
- It may be slightly changed at the time other tasks appear.
- It should be finished at the time all R0s of other tasks are completed.
- Come up with general design in the model about timelines.
Task result
- wiki page.
Implementation idea
- see other tasks in the task index that are about timelines.
- examine Sophie 1.0 timelines that are managed through the bottom flap. (see http://sophieproject.org/download/, http://sophieproject.org/tutorials, http://sophieproject.org/node/235 to get some ideas about the design of timelines.)
- create the wiki page and fill in the concepts and design.
Related
- INTERACTIVITY_COMMONS_R0
- the task is related to TIMELINES with all their sub-tasks. (see http://sophie2.org/trac/wiki/TASK_INDEX for more information).
- a link to a particular task cannot be provided since none of the above are started yet (except for INTERACTIVITY_COMMONS_R0).
How to demo
- show the wiki page and explain the stuff there.
Design
Implementation
(Implementation results should be described and linked here (from the wiki or the repository))
Testing
Comments
(Write comments for this or later revisions here.)