i have just been looking about to see is there any stable/mature typesettign
system where we can borrow the algorithm. I have just started looking at Tex
and groff. Do u think its a good place to start? I would like to see what
has been done in these systems to do intelligent page layout. Since the
layout is what needs changing most, I suggest that bug-fixes for those
portions of fop which will not need major tweaking of layout related code,
can continued to be fixed. Problems like row-span, floating objects could be
postponed for the revamped fop.

I would be starting to do the reachitecturing of fop-layout, and anything
positive that might come out shall be discussed and committed with FOP.

regards
Seshadri
FOP Support
www.mindfiresolutions.com/fopservices.html




----- Original Message -----
From: Keiron Liddle <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 13, 2001 6:04 PM
Subject: Redesign Questions


> Here are some questions I think we should ask ourselves when attacking the
> redesign.
>
> - What is the timeframe?
> Start after the next release and continue for approximately 3 months.
>
> - How will it be handled?
> Do we create a branch and continue bug fixes for the current FOP. Would
> this waste time.
>
> - Who will do what?
>
> - Is the Rendering mechanism sufficient?
> I think it is close but not perfect, no major changes should be needed.
>
> - Is the area tree correct?
> No. This should be written to handle the area tree more closely, with the
> correct structure, data. It should not contain any layout logic (eg. line
> area and hyphenation). It should be as independant as possible from the FO
> objects. Also need to be able to adjust positions when layout changes.
>
> - Is the FObj tree creation sufficient?
> I think so.
>
> - Is the Property handling sufficient?
> Not quite. The refinement of properties doesn't appear to be very easy
> (functions, merging etc.).
>
> - Is the layout sufficient?
> No. This is the main area that needs redoing.
>
>
> -------------
> Layout Questions.
>
> How do we handle forward references?
>
> How do we handle out of line objects (footnotes, floats, conditional
> areas)?
>
> How do we handle stacking constraints (space, breaks, keeps)?
>
> How do we handle descendant rules?
>
> How do we handle situations where layout needs redoing (columns, line area
> alignment, footnotes etc.)?
>
> -------------
> sufficient - means we can continue development with the same design.
>
> -----------------
>
> So I think there are at least a few areas that need development for this
> redesign.
> Once we have a clearer idea of what to do there should be a number of
> relatively independant areas.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>


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

Reply via email to