Changes between Version 1 and Version 2 of GROUP_CHANGES_R0

Timestamp:

05/21/09 13:51:48 (16 years ago)

Author:

deyan

Comment:

--

GROUP_CHANGES_R0

@@ -4 +4 @@
 
 = Analysis =
-^(Give as much as possible of the needed information for designing and implementing the task in the following sections.)^
 
 == Overview ==
-^(Provide a brief overview of the whole task in its first revision. Stick to the current revision of the task, but keep an eye to the whole task progress, and stay alert for possible smells.)^
+ * Changes should be split into significant and non-significant. Significant means that the change will be shown to the user as one change. For example - resizing of frame by mouse should be shown to the user as one change on mouse drop. 
+ * Changes should allow undo/redo/skip and unskip
+  * Undo/Redo/Skip.. should undo/redo/skip... significant changes, for later revisions
+ * Changes should be split into primitive and complex changes.  Complex changes are groups of primitive changes. Groups are defined by developers.
 
 == Task requirements ==
-^(List the necessary requirements that the task must fulfill.)^
-
+ * Create a list with common significant changes, what is present to the user as one change on mouse drop, after timeout, etc.
+ * In Design section create a table with primitive changes 
+ * Define basic complex changes and what primitive changes do they contain. 
 == Task result ==
 ^(List the end product of the task (for example "Source code", "Wiki page", etc.))^