Changes between Version 1 and Version 2 of GROUP_PRO_LIB_PERFORMANCE_R0

Timestamp:

04/24/09 16:52:01 (16 years ago)

Author:

gogov

Comment:

--

GROUP_PRO_LIB_PERFORMANCE_R0

@@ -15 +15 @@
 Another case is when you deal with skins. Skins are basically maps between keys and values. At a certain time an AutoProperty might be interested to monitor only the list of all pairs of keys and values which have the key "meddle". So if this list remains the same while the whole ProList which contains it changes, this AutoProperty shouldn't get recomputed. [[BR]]
 
-Devise and implement a concept how to deal with such problems.
+ * Devise and implement a concept how to deal with such problems.
+ * Refactor ProList, BaseProList and ListEntry code to fix design issues from previous tasks.
+ * Refactor all client code to meet new implementation.
+ * Think of tests which measure new performance against the current.
 
 == Task result ==
-^(List the end product of the task (for example "Source code", "Wiki page", etc.))^
+ * New functionality code
+ * Nice unit tests
 
 == Implementation idea ==
-^(Provide some rough implementation idea(s).)^
+Introduce aspects.
 
 == Related ==
-^(Add links to related tasks that could be useful or helpful.)^
+[wiki:PRO_LIB_MODEL_PRO_LISTS_R0]
 
 == How to demo ==
-^(Provide instructions for demonstration of the task.)^
+ * Show previous unit tests don't break
+ * Show performance improvement
 
 = Design =