Changes between Version 3 and Version 4 of LINKS_COMMON_R0


Ignore:
Timestamp:
01/26/09 14:24:18 (16 years ago)
Author:
dido
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • LINKS_COMMON_R0

    v3 v4  
    1818 * Frame Hidden 
    1919 
    20 Frame states are: 
     20Frame's states are: 
    2121 * up(normal) 
    2222 * over 
    2323 * pressed 
    2424 
    25 Text states are: 
     25Text's states are: 
    2626 * up(normal) 
    2727 * over 
     
    4040 
    4141== Implementation idea == 
    42 It may be a good idea to create separated module for links. Keep in mind that this module should communicate with other modules (For example the frame view is affected after a link is added, they could also control(play, pause) the timeline etc.). Also create a manager that is responsible for events monitoring, provide easy way to add and remove event listeners from a single place. Delegate the responsibility for states changes, see if it is necessary to do some refactoring over the existing modules(for example the frame view should be responsible for managing different states). 
     42It may be a good idea to create separated module for links. Keep in mind that this module should communicate with other modules (For example the frame view is affected after a link is added, they could also control(play, pause) the timeline etc.). Also create a manager that is responsible for events monitoring, provide easy way to add and remove event listeners from a single place. Delegate the responsibility for states changes, see if it is necessary to do some refactoring over the existing modules(for example the frame view should be responsible for managing different frame's states).[[BR]]It will be nice if some diagrams are added. 
    4343 
    4444== Related == 
     
    5252 
    5353== How to demo == 
    54 ^(Provide instructions for demonstration of the task.)^ 
     54 * create a test environment and see if some actions are attached and evoked correctly.  
    5555 
    5656= Design =