Changes between Version 14 and Version 15 of GROUP_CHANGES_R0

Timestamp:

05/28/09 14:17:18 (16 years ago)

Author:

meddle

Comment:

--

GROUP_CHANGES_R0

@@ -109 +109 @@
    * The UndoChange and RedoChange for now will be part of the ResourceChangeManager, because they are connected with the manager of their changes and automatically will register themselves in it. may be in the future the SkipChange will be the same.
    * The manager will construct itself with a Resource, it's Resource.
+ * GlobalResourceChangeManager : It will be used for grouping for the user changes from more than one ResourceSpaces.
+  * It will be one for all the Resources, so it will be singleton, it will group the changes for the current book hierarchy, to be nice for the user. Good AutoChanges must be written from the developers...
+  * It will work in this way:
+   * If global group must be opened (For every new set of changes or change it will open such a global group) it opens one with root Change the first change of the new set. The method shouldOpenGlobalGroup is used to check that. If there is already a root Change for the global group it will return false, otherwise true.
+   * If there is already opened global group it will add the incoming change to it, for that will be used hasOpenedGroup.
+   * If global group must be closed (The change that opened the group is closing itself) all the sub groups will be closed and the global group will be closed, so the root Change of the manager will be null. That's the purpose of the willCloseGroup method.
+   * All the changes grouped globally will be retrievable through the getAllChangesForResource method.
+  * All the global groups are virtual, they are not saved in the History of the Resources and are used only for displaying the list of the changes to the users nicely.