Changes between Version 2 and Version 3 of GROUP_TIMELINES_R0

Timestamp:

04/22/09 20:01:58 (16 years ago)

Author:

kyli

Comment:

--

GROUP_TIMELINES_R0

@@ -20 +20 @@
   * some actions must have duration, some not. After deciding what will be the possible actions, think of a way to store this information in the timeline entries.
  * Think about need of persisting timelines, maybe templating or something other possibilities.
- * Provide a way to manipulate a timeline - create, destroy, add entry, remove entry, play, stop.
+ * Provide a way to manipulate a timeline - list, create, destroy, add/remove channel, add/remove entry, play, stop.
  * Design diagrams are strongly recommended.
 == Task result ==
-^(List the end product of the task (for example "Source code", "Wiki page", etc.))^
+Source code, design diagram(s).
 
 == Implementation idea ==
-^(Provide some rough implementation idea(s).)^
+ * '''Model:''' a Timeline could be a ProObject, which has '''length''' and a '''list''' of one or more timeline channels. A channel can be a '''list''' of zero or more entries. Each entry can have '''startTime''', '''duration''', '''startAction''' and '''endAction''' (for example, if we drag a frame in the first channel, its start action is show and the end action will be hide). 
+ * '''Demo''': if you decide to use the bottom flap for the demonstration, keep in mind it is currently not working and needs refactoring. It could contain a palette about the created timelines and the current timeline.
+
 
 == Related ==