Changes between Version 7 and Version 8 of FullHistory
- Timestamp:
- Aug 22, 2006, 12:47:27 AM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FullHistory
v7 v8 5 5 '''Features: almost there''' (21.08.2006) 6 6 7 At the moment the contrib.history is quite useful l. Examples below should work.7 At the moment the contrib.history is quite useful. Examples below should work. 8 8 9 9 '''NOTE: Comparing and merging should be done by user and is not automated (yet).''' … … 21 21 22 22 ||'''Task'''||'''Status'''|| 23 ||Getting the code to work generical y (on every given model)||'''DONE'''||23 ||Getting the code to work generically (on every given model)||'''DONE'''|| 24 24 ||Getting the code to a working state||'''DONE'''|| 25 25 ||Getting the API to work as described below||'''DONE'''|| … … 34 34 == Introduction == 35 35 === 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 useful lwhen you would like to revert a change or even see what whas changed.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 useful when you would like to revert a change or even see what whas changed. 37 37 38 38 === The main idea === 39 I am trying to write a different impleme tation 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.39 I 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. 40 40 41 41 == Usage == 42 42 === Models === 43 43 How to enable history tracking? 44 Enabli g history tracking for a particuralmodel is just like adding Admin functionality - add an inner class as shown below:44 Enabling history tracking for a particular model is just like adding Admin functionality - add an inner class as shown below: 45 45 46 46 {{{ … … 99 99 {{{ 100 100 #!python 101 # NOT IMPLEMENTED!!! User should do the m reging, comparing and reverting manualy.101 # NOT IMPLEMENTED!!! User should do the merging, comparing and reverting manually. 102 102 }}} 103 103