Code

Changes between Version 7 and Version 8 of FullHistory


Ignore:
Timestamp:
08/21/06 22:47:27 (8 years ago)
Author:
JayKlehr
Comment:

type-os

Legend:

Unmodified
Added
Removed
Modified
  • FullHistory

    v7 v8  
    55'''Features: almost there''' (21.08.2006) 
    66 
    7 At the moment the contrib.history is quite usefull. Examples below should work. 
     7At the moment the contrib.history is quite useful. Examples below should work. 
    88 
    99'''NOTE: Comparing and merging should be done by user and is not automated (yet).''' 
     
    2121 
    2222||'''Task'''||'''Status'''|| 
    23 ||Getting the code to work genericaly (on every given model)||'''DONE'''||  
     23||Getting the code to work generically (on every given model)||'''DONE'''||  
    2424||Getting the code to a working state||'''DONE'''|| 
    2525||Getting the API to work as described below||'''DONE'''|| 
     
    3434== Introduction == 
    3535=== The problem === 
    36 The changelog-type of history in its current implementation, would write log only when using Admin and log would include only information about the change but not the content that was changed. This is not very usefull when you would like to revert a change or even see what whas changed. 
     36The changelog-type of history in its current implementation, would write log only when using Admin and log would include only information about the change but not the content that was changed. This is not very useful when you would like to revert a change or even see what whas changed. 
    3737 
    3838=== The main idea === 
    39 I am trying to write a different implemetation that will be independent of Admin and will store the content as well. This way developers will be able to save, compare and revert any changes made in any particular model. 
     39I am trying to write a different implementation that will be independent of Admin and will store the content as well. This way developers will be able to save, compare and revert any changes made in any particular model. 
    4040 
    4141== Usage == 
    4242=== Models === 
    4343How to enable history tracking? 
    44 Enablig history tracking for a particural model is just like adding Admin functionality - add an inner class as shown below: 
     44Enabling history tracking for a particular model is just like adding Admin functionality - add an inner class as shown below: 
    4545 
    4646{{{ 
     
    9999{{{ 
    100100#!python 
    101 # NOT IMPLEMENTED!!! User should do the mreging, comparing and reverting manualy. 
     101# NOT IMPLEMENTED!!! User should do the merging, comparing and reverting manually. 
    102102}}} 
    103103