I understand that messing around with FOP is not a good idea. But what to
do, I doesn't get any solution till. I'll put the problem in greater detail

   I will be having FO templates, that specify the style of the report. 
                Let's say the template is like:

                        <?xml version="1.0" encoding="utf-8"?>
                                <!-- defines the layout master -->
                                   <fo:region-body margin-top="50pt">
                                  <fo:region-before extent="50pt">
                                 <fo:region-after extent="25pt">

                           <!-- starts actual layout -->
                           <fo:page-sequence master-reference="first">
                                   <!-- Static content goes here -->
                                <fo:flow flow-name="xsl-region-body">
                                <fo:block white-space-collapse="false"
font-weight="bold">##########</fo:inline>" +

        There will be templates like above where the hashpart(#######) is
the hole area where the programs fill the data. The data will be got from
the database and the client program supplies the server with the data and
the sever program takes the data and for every write call the client program
says, the server creates a new "fo:block" element and places the data
supplied in the hash portion. The client proceeds in this fashion. 
           The client program may supply large amount of records, can be
around 15,000 records also. So, it is not advisable to make the user wait
till all the data is supplied and the entire FO constructed. There is an
assumption made now, say we can show 40 records per page. The client
supplies 40 records to the sever, which renders the page using FOP API. But,
the problem comes if the data supplied will not fit in the single line. If
the data spans more than 1 line, then the assumption becomes incorrect and
the remnant portion of the data ( a small chunk, could be one or two lines)
comes in the second page. This is not good. 
        There actually will be number of templates and client filling out
the templates. So, I'm trying to find a solution where in which at any point
of time client should be able to know that
                 "Still how many lines of display remain?". With that the
client can hold until the server gives it a ready signal again.

        I hope I'm clear now... I'm not finding how to solve the above
problem... I think this type of viewing is common in business
            For now, it is assumed that the page size is 8.5in * 11in and
portrait mode. Is it possible?

        I'll be waiting to hear for a solution...

-----Original Message-----
From: Jeremias Maerki [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 08, 2002 8:54 PM
Subject: Re: Page details support?

The font classes could help you here, too. But I wonder if that helps
you a lot. Questions like that often indicate that someone is trying to
work around a problem that is actually supposed to be worked out in a
different way. If you experience a deficiency with FOP, first try to
find out, if it's XSL:FO that doesn't provide what you need or if it's
FOP. If it's FOP, tell us what you want to accomplish. We may (!) be
able to help you find another solution that doesn't involve messing
around with FOP. And if you really decide to hack into FOP, be aware
that your solution will lose portability because you're restricting
yourself to a particular software and that may be as bad as buying
proprietary software. :-) I hope this helps.

>       Is it possible to through FOP API to find the number of lines ( for
> a defined font and page) that can be rendered?

Jeremias Märki

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