> On Tue, 2002-11-12 at 12:00, Kevin O'Neill wrote: > > > I just added a Form XObject but it needs some work (eg. bounds). > > > > How do you intend to pass xobject hits from the fo processor. I had > > thought about a fop specific attribute that was a hint on block level > > objects.
What does your xsl:fo input look like? Standard xsl:fo according to specs? > Von: Keiron Liddle [mailto:keiron@;aftexsw.com]> I'm not sure what situation you might be talking about. So to speculate: > If it is to use xobject when there are things repeated across pages > (static areas, table header, svg) then it could be done through the > layout managers. If the content may be repeated and does not depend on > the page then it could set a value on the area tree saying that the area > (and contents) should be placed in a xobject. When the same area occurs > again, indicated by a key or something, then it will render the xobject > again. > What do PDF XObjects, Bookmarks, form fields have to do in the area tree? How about device independence? How will the PCL and AWT renderers process XObjects? A layered distiction between the jobs of a (device independent) fo formatter and the renderers (generation of device dependent graphic streams, caching, ressource management) will keep the system maintainable. This can be achieved by instream-foreign-objects: the fo proscessor calculates page numbers/positions, reserves presentation spaces and passes foreign-object contents/control unchanged and unchecked to renderers. Hansuli Anderegg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
