Sorry, you're just going to have to read code to understand the current
implementation. There are some (dated) design notes under
http://wiki.apache.org/xmlgraphics-fop/DeveloperPages that may help you get
started. FOP is a DIY exercise, especially if you want to make a major
change like you suggest.

Regards,
Glenn


On Thu, Jun 20, 2013 at 6:46 PM, sdridi <sdr...@iptech-group.com> wrote:

> Hello people,
>
> I'm working on an extension for FOP similar to  Whitespace management
> <http://wiki.apache.org/xmlgraphics-fop/WhitespaceManagement>  . I want to
> start as simple as possible, so my XML extension *<fox:best-fit-block>* is
> only allowed to contain one *<fox:alternative>* which has an *<fo:block>*.
> The layout manager should be simple to implement and most calls will be
> delegated to the appropriate children, but I'm not sure which methods to
> implement in /AbstractLayoutManager/. Also, could you briefly explain how
> to
> implement /getNextKnuthElements()/? And do I even need to implement
> /getChangedKnuthElements()/?
>
> Thank you in advance for your time
>
> Best Regards
>
> Seifeddine Dridi
>
>
>
>
>
>
>
>
>
> --
> View this message in context:
> http://apache-fop.1065347.n5.nabble.com/Adding-a-new-layout-manager-tp38757.html
> Sent from the FOP - Dev mailing list archive at Nabble.com.
>

Reply via email to