Changes between Version 3 and Version 4 of PRO_CHANGE_INFOS_R0


Ignore:
Timestamp:
01/26/09 15:40:35 (16 years ago)
Author:
gogov
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PRO_CHANGE_INFOS_R0

    v3 v4  
    66 
    77= Analysis = 
     8== Overview == 
     9The goal of this task is to develop a concept of describing Changes with useful end-user information. 
    810 
    9 == Overview == 
    10 The aim of this task is to visualize information, when have the properties been changed. 
     11This includes: 
     12 * Reviewing current implementation for information and descriptions associated with Changes 
     13 * Giving ideas for new types of Change descriptions which will be useful for the end-user 
     14 * Devising a mechanism to implement the ideas above internally 
     15 
    1116== Task requirements == 
    12    * Visualize information, when have the properties been changed [[BR]] 
    13    EXTRA 
    14    * Create new tests 
     17 * Information about changes should be classified by types and implemented: 
     18  * Description 
     19   * When the user is undoing/redoing a change, this results in a top-level change which should have meaningful description 
     20   * Internal side effect changes could also have useful descriptions 
     21  * Whether the change is a main or a side effect 
     22  * Unique sequence id of the change 
     23   * When Changes occur, they are sorted in order of appearance so each Change should have a unique id 
     24   * The smaller the id of a Change, the earlier in time it has occurred 
     25  * When the end-user views a top-level change, besides description there should be also a timestamp of the Change, e.g. when it has occurred 
     26 * Develop a UI tool which shows the tree of Changes for debugging purposes 
     27 * Develop a proper way to visualize what kind of effects undoing/redoing a Change would have 
     28 * Create new unit tests 
    1529 
    1630== Task result == 
    17 The result of this task is UI which visualize information . 
     31 * Description of the information a Change provides in the wiki page 
     32 * New code to implement the desired functionality 
     33 * Description of the UI tool in the wiki 
    1834 
    1935== Implementation idea == 
    20    * This task is related with undo manager 
    21    * You can create an applet which visualize information like change inspektor or simple text. 
     36 * Use the Inspector for a base of the UI tool 
    2237 
    2338== Related == 
    2439[wiki:PRO_CHANGE_UNDO_MANAGER_R0] 
     40[wiki:PRO_CHANGE_MANAGER_R0] 
     41[wiki:PRO_CHANGE_COMMONS_R0] 
    2542 
    2643== How to demo == 
    27 Working tests, which are showing how the appet is working. 
     44 * Undo/redo some actions in Sophie 2 and show the descriptions 
     45 * Show the UI tool 
     46 * Run the unit tests 
    2847 
    2948= Design =