Changes between Version 2 and Version 3 of NFR_TEXT_PERFORMANCE_R0


Ignore:
Timestamp:
11/08/09 20:49:07 (16 years ago)
Author:
kyli
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NFR_TEXT_PERFORMANCE_R0

    v2 v3  
    3232 
    3333= Design = 
    34 ^(Describe your design here.)^ 
     34The current auto-chaining algorithm is ineffective. It adds a page to the book, in another auto action inserts a frame in it, in another one applies the template and chains it to the head frame. If then the text is not laid out completely, repeats the steps. Every action causes updates in che GUI, adding a head text frame to a chain even destroys the old view and creates a tail view, which then recomputes. This can be avoided if the static helper methods are not used - we can create a tail text frame and add it to the chain directly. Furthermore, all the pages can be added at once - for this action we need a helper method in HotLayout which makes a "dry-run" of the layout in order to calculate the count of needed areas. Unfortunately, adding all the frames in one action does not have any effect - every add causes an update. But head frames will not be created, frame kinds will not be changed and all the pages will be added at once. This is much faster.  
    3535 
    3636= Implementation =