Changes between Version 7 and Version 8 of PAGE_ELEMENT_GROUPING_R0

Timestamp:

05/20/09 12:30:06 (16 years ago)

Author:

kyli

Comment:

--

PAGE_ELEMENT_GROUPING_R0

@@ -7 +7 @@
 
 == Overview ==
-( The idea is to have groups of page elements in the model. Selecting page elements is one thing and creating a group of the selected elements is the thing that this task is about. Grouped elements should be persisted and restored when opening the book. A page element should be part of no group or one group only - page elements cannot be part of different groups. )
 
-Every book view has a work area related to it. It must contain the corresponding page, as well as the book extras, attached to it. Pages can contain frames or groups of frames. Extras will have similar abilities in the near future. The groups should be a method for organizing frames and other groups for easy manipulation - for example, we can group several frames to move/resize them together, change their background, etc. If we go further, groups should contain frames and/or other groups. Grouping 2 elements (groups an/or frames) together means making a group, containing both of them. Ungrouping of group is detaching its top-level elements from each other. Groups should not contain both frames and stickies (for example), so it would be better if book extras were at the same grouping level as the page itself. ''To be continued..''
+Every book view has a work area related to it. It must contain the corresponding page, as well as the book extras, attached to it. Pages can contain frames or groups of frames. Extras probably will have similar abilities in the near future. 
+The groups should be a method for organizing frames and other groups for easy manipulation - for example, we can group several frames to move/resize them together, change their background, etc. If we go further, groups should contain frames and/or other groups. Grouping 2 elements (groups an/or frames) together means making a group, containing both of them. Ungrouping of group is detaching its top-level elements from each other. Groups should not contain both frames and stickies (for example), so it would be better if book extras were at the same grouping level as the page itself. A page element (frame, sticky, etc.) can be in only one group at one time. 
 
 == Task requirements ==
  * Define how grouping should be introduced in the model.
- * Save groups along with the book.
- * Load groups along with the book.
+  * Groups must be persistable along with the book.
+  * Groups must not conflict with the current template model.
+  * A group cannot contain both frames and extras.
   * If a group is loaded it should be represented as selected elements in the view.
  * Create a halo button that will create a group of elements from the currently selected ones when clicked in the view.
@@ -22 +23 @@
 == Task result ==
  * code
+
 == Implementation idea ==
- * In the class for page in the model, create a value list property containing groups of elements.
- * Implement the group of elements as s class.
-  * It should be able to contain different kinds of elements.
+ * Get into the current group model, get familiar with its negatives.
+ * Watch this [http://asteasolutions.net/videos/2009-05-16-Discussion05(bg%20audio).MPG video], see the new design ideas for the grouping.
+ * Use the current tests written for grouping.
+ * In order to make a group persistable, it would be best to be implemented as a resource.
   * It may contain different properties that are common for the group like background(for background supported elements), border color, border size etc.
   * It may have a size and position. This is the bounding rectangle for the elements in the group.