Andreas L Delmelle wrote:
snip/
Those components/resources that apply to all types of renderers, can be
handled in AbstractRenderer.
AbstractRenderer could provide a generic createResource() method, which
can be overridden or re-implemented in the specific renderer types to
handle the
Adrian,
when you've found and fixed the current problem in the AFP renderer, I'd
appreciate if you could make sure it is adjusted to the changes in
revision 612815. While the AFP renderer is a descendent of
AbstractPathOrientedRenderer it provides its own renderBlockViewport
method. Why that is
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=44247.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
On Thu, Jan 17, 2008 at 12:27:11AM +0100, Andreas L Delmelle wrote:
Right now, the element list is constructed as the result of recursive calls
to getNextChildLM.getNextKnuthElements().
/The/ return list upon which the page breaker operates is the one that is
ultimately returned by the
On Jan 17, 2008, at 09:55, Chris Bowditch wrote:
Andreas L Delmelle wrote:
snip/
Those components/resources that apply to all types of renderers,
can be handled in AbstractRenderer.
AbstractRenderer could provide a generic createResource() method,
which can be overridden or
On Jan 17, 2008, at 20:57, Simon Pepping wrote:
On Thu, Jan 17, 2008 at 12:27:11AM +0100, Andreas L Delmelle wrote:
Right now, the element list is constructed as the result of
recursive calls
to getNextChildLM.getNextKnuthElements().
/The/ return list upon which the page breaker operates is
