Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Xmlgraphics-fop Wiki" 
for change notification.

The "WhitespaceManagement" page has been changed by SeifeddineDridi:
https://wiki.apache.org/xmlgraphics-fop/WhitespaceManagement?action=diff&rev1=15&rev2=16

  ==== 1- Fitting strategy: ====
   . The selection of the best alternative is based upon the chosen fitting 
strategy, which is just a property of fox:best-fit and can take one of the 
following set of values {“first-fit”, “smallest-fit”, “biggest-fit”}
    * ''first-fit:'' as the name implies, the first alternative that fits into 
the available space is selected, the rest will be ignored.
- 
    * ''smallest-fit:'' the best alternative is the one that occupies the least 
amount of space and can be fit inside the current page.
- 
    * ''biggest-fit:'' the best alternative is the one that occupies the 
highest amount of space and can be fit inside the current page.
  
-    . More fitting strategies will be added as I develop my concept further. 
For example, it might be useful to define strategies that select more than an 
alternative depending on certain shared traits, or if their combined width is 
less than a certain threshold.
+  . More fitting strategies will be added as I develop my concept further. For 
example, it might be useful to define strategies that select more than an 
alternative depending on certain shared traits, or if their combined width is 
less than a certain threshold.
  
  ==== 2- Best fit penalty: ====
-  . By definition, an alternative is not allowed to be broken apart across 
pages or columns; it must be put together in one chunk as if it has the 
keep-together property implicitly set to always. To achieve that, I have added 
a new penalty type (''BestFitPenalty'') that keeps record of the set of 
alternatives waiting to be evaluated. It also informs the layout manager about 
the best alternative that was chosen when ''addAreas()'' is called.
+  . By definition, an alternative is not allowed to be broken apart across 
pages or columns; it must be put together in one chunk as if it has the 
keep-together property implicitly set to always. To achieve that, I have added 
a new penalty type (''!BestFitPenalty'') that keeps record of the set of 
alternatives waiting to be evaluated. It also informs the layout manager about 
the best alternative that was chosen when ''addAreas()'' is called.
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to