Changes between Version 11 and Version 12 of PAGE_ELEMENT_GROUPING_R0

Timestamp:

05/20/09 19:51:03 (16 years ago)

Author:

dido

Comment:

--

PAGE_ELEMENT_GROUPING_R0

@@ -9 +9 @@
 
 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.
+ * 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. (There is tree structure here) Also moving, rotating and resizing one group should effect the entire group. All of the child's of a group should remain their relative position, rotations and sizes. Visual result should be like they are stuck together. 
  * 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.
@@ -23 +23 @@
   * NOTE: If user selects for example 2 groups and 2 frames and press ctrl + b. This action will break(grouping) the 2 groups but won't have effect over the frames.
   * Every group of page elements (not for book extras) has a timeline.
+
 == Task requirements ==
  * Define how grouping should be introduced in the model.