Changes between Version 1 and Version 2 of TEXT_CHAINING_BEHAVIOUR_R0

Timestamp:

04/03/09 16:42:56 (16 years ago)

Author:

dido

Comment:

--

TEXT_CHAINING_BEHAVIOUR_R0

@@ -10 +10 @@
  * The user should be able to point witch text frame is linked with current flow and witch is not.
  * There should be automatic linking when flow text frame is used.
-  * If there is no other flow text frame on the page and the text overflows, than the next page is created with flow text frame with the same properties as the first one. The bought frames are linked.
+  * If there is no other flow text frame on the page and the text overflows, than the next page is created with flow text frame that have the same properties as the first one. The bought frames are linked.
   * If the user adds 2 flow text frames to the current page, they should be linked as the default behavior. However user should have the ability to break the linking.
-  * If they are two flow text frames that are not linked and the user adds third, the default linking should be with the one that is first added. However this should also be fully noticeable for the user. Same if they were 3 frames at the beginning and so on. 
+  * If they are two flow text frames that are not linked and the user adds third, the default linking should be with the one that is first added. However this should also be fully noticeable for the user. Same if they were 3 frames at the beginning and so on.
+  * If they are multiple pages that have linked text frames, and flow text frame is added to the one of the pages(not the last one), the new frame is linked after the last frame on the page and before the first page on the next page. However if happens that the last page or the last few pages became empty, they shouldn't be removed.
+ * If they are 3 linked flow text frames user should have the opportunity to easily reorder them.
 
 == Task requirements ==
-^(List the necessary requirements that the task must fulfill.)^
+ * Create a prototype of text chaining behavior with automatic linking.
 
 == Task result ==
-^(List the end product of the task (for example "Source code", "Wiki page", etc.))^
+ * The result should be code
 
 == Implementation idea ==
@@ -24 +26 @@
 
 == Related ==
-^(Add links to related tasks that could be useful or helpful.)^
+[wiki:TEXT_FRAME_SCROLLBARS_R0]
 
 == How to demo ==
-^(Provide instructions for demonstration of the task.)^
+ * Run the application
+ * Create a book
+ * Place flow text frame inside the first page and populate text that overflows (http://www.lipsum.com/)
+ * See if second page is created with text frame inside
+ * Place second flow text frame on the first page and check if the application acts as it supposed to 
 
 = Design =