Re: Implementing Full Page Model

["W. Eliot Kimber" <eliot@xxxxxxxxxx>]

At 11:07 AM 5/10/98 +0700, James Clark wrote:
>W. Eliot Kimber wrote:

>> The reason I ask is that I may have a client willing to fund the extension
>> if they get to keep some part of the result to themselves, i.e., put the
>> extended front end back into the public domain, but keep the back end for
>> themselves.  It's just a thought.
>
>Which backend are they interested in?  It would be hard to make any of
>the existing backends support the full page-model.  It would be
>relatively routine to add the appropriate front-end support.  I think it
>would hard to implement it in a backend which wasn't a native DSSSL
>formatter.

I'm assuming the MIF back end only because I know Frame is up to the page
layout task.

By "native DSSSL formatter" I assume you mean software that interacts
directly with the flow object tree generator in order to close the feedback
loop between the front end and the back end, correct? 

If so, I guess that would require something like a very tight integration
of a formatter like XPP or Miles 33 with the DSSSL engine itself (rather
than writing flow object interpreting back end).

Thanks,

E.
--
<Address HyTime=bibloc>
W. Eliot Kimber, Senior Consulting SGML Engineer
ISOGEN International Corp.
2200 N. Lamar St., Suite 230, Dallas, TX 95202.  214.953.0004
www.isogen.com
</Address>


 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist