[[BackLinksMenu]]

[[TicketQuery(summary=GROUP_CHANGES_R0, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|)]]

= Analysis =

== Overview ==
 * 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 ==
 * 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.))^

== Implementation idea ==
^(Provide some rough implementation idea(s).)^

== Related ==
^(Add links to related tasks that could be useful or helpful.)^

== How to demo ==
^(Provide instructions for demonstration of the task.)^

= Design =
^(Describe your design here.)^

= Implementation =
^(Describe and link the implementation results here (from the wiki or the repository).)^

= Testing =
^(Place the testing results here.)^

= Comments =
^(Write comments for this or later revisions here.)