Peter B. West wrote:
> Convergence problems like your page 99 scenario occur in other contexts;
> notably the "last page" problem. The last page in a sequence is allowed
> a different page-master, but the only way to discover the last page is
> to lay it out. Oops, last page. Lay it out agai
Joerg,
You have highlighted one of the nastinesses of page formatting. A Q&D
solution often suggested is to allow a fixed width for the page numbers,
but I don't see how this can stand as a final solution. The gaps are
going to be obvious in something purporting to be a high-quality
rende
"Nicola Ken Barozzi" <[EMAIL PROTECTED]> wrote:
> Anyway, these forward references are a pain in the ass :-/
Very true. Imagine the worst case: Someone puts a
"(See page )"
into the text at page 1. The formatter has to allocate some
space for the unknown number, lets say a "n" space. The
referen
Fops,
This forwarded message is a response to Nicola which was accidentally
sent to him only. Since I sent it the notes I refer to have been
installed in the CVS.
Peter
Nicola,
Most of the design docs I have prepared have been noted on this list in
the past few months. Real Soon Now, th
-Original Message-
From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]]
Sent: March 19, 2002 11:48 AM
To: [EMAIL PROTECTED]
Subject: Re: development status
From: "Keiron Liddle" <[EMAIL PROTECTED]>
> Retrieve Markers?
IMHO yes, since you can make a forwar
From: "Keiron Liddle" <[EMAIL PROTECTED]>
> On 2002.03.19 16:47 Nicola Ken Barozzi wrote:
> > So we absolutely need to stop output and cache events if there is a
> > forward
> > reference.
> > If we find it at the end, all the pages must remain in memory, and now I
> > see
> > that this can make
On 2002.03.19 16:47 Nicola Ken Barozzi wrote:
> So we absolutely need to stop output and cache events if there is a
> forward
> reference.
> If we find it at the end, all the pages must remain in memory, and now I
> see
> that this can make FOP behave no better than it does now.
Thats not true. W
From: "Keiron Liddle" <[EMAIL PROTECTED]>
> On 2002.03.19 14:45 Nicola Ken Barozzi wrote:
> > I would consider the possibility (configurable) of having FOP make just
> > sensible assumptions to continue processing and sacrifice some things it
> > should do later.
>
> That sounds very vague.
> So
Hi Peter,
The font information is obtained from the renderer at the start before
building any of the area tree.
There should be no further need for communication except of course in the
case when handling dynamic effects (but lets not get into that right now).
On 2002.03.19 13:37 Peter B. West
On 2002.03.19 14:45 Nicola Ken Barozzi wrote:
> I would consider the possibility (configurable) of having FOP make just
> sensible assumptions to continue processing and sacrifice some things it
> should do later.
That sounds very vague.
So what will you do if someone has a table of contents as t
Keiron Liddle wrote:
...
> To serialize between the Area Tree and the Renderers there are some
> serious problems that would get in the way:
> - in many cases the area tree will need to be complete before sending
> anything across, this defeats the whole purpose and will use a lot of
> memory
I agree with the configuration in general but not with the cocoon concept.
The parts like configuration, logging, etc. could help us with the
functionality and the architecture.
To serialize between the Area Tree and the Renderers there are some
serious problems that would get in the way:
- in
From: "Keiron Liddle" <[EMAIL PROTECTED]>
> At this stage of the design very few core problems can be solved in
> isolation. So if someone wants to implement for example keeps or a colour
> property, it has an impact on almost everything else in the layout.
>
> So what is needed and what will mak
I'm not exactly sure what you want to know or why but I will attempt to
clear a few things up.
First a bit of history. About 1.5 years ago FOP reached a stage where the
original design could not support adding functionality. It started
approaching a "big ball of mud". More effort was put into
On 2002.03.15 08:27 Nicola Ken Barozzi wrote:
> I think that the FOP community needs an explanation of my intrusion.
> I am a committer on the POI, Cocoon and Forrest projects, and a happy
> user
> of FOP for work.
> I wrote an XML semantic WYSIWYG editor in java that uses Avalon and
> specifies s
From: "Peter B. West" <[EMAIL PROTECTED]>
> Nicola Ken Barozzi wrote:
> >Don't get me wrong, maybe I don't understand something, but still I'm
very
> >puzzled.
> >
> Nicola,
>
> Your criticism here distresses me somewhat. How is anyone without
> commit access able to branch the code? I have bee
Nicola Ken Barozzi wrote:
>From: "Arved Sandstrom" <[EMAIL PROTECTED]>
>
...
> I read the FO spec fully at
>least 3 times ;-)
>
Impossible!
Peter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [E
Nicola Ken Barozzi wrote:
>From: "Peter B. West" <[EMAIL PROTECTED]>
>
>>There is very active development on FO Tree building, property
>>resolution and layout models. A lot of that development is desisn
>>speculation, such as the design notes I have been posting, and there is
>>also a fair bit
From: "Arved Sandstrom" <[EMAIL PROTECTED]>
> You're 100% right - Apache XML is not just about Java. But programming
> language is not the reason xslfo-proc is not a sideproject to FOP. It is
all
> about community. If this codebase was side-by-side with FOP right now it
> would be a distraction a
Comments below.
-Original Message-
From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]]
Sent: March 14, 2002 11:07 AM
To: [EMAIL PROTECTED]
Subject: Re: development status
From: "Peter B. West" <[EMAIL PROTECTED]>
[ SNIP ]
> Arved is, as you know, engaged in a
> C/
From: "Peter B. West" <[EMAIL PROTECTED]>
> There is very active development on FO Tree building, property
> resolution and layout models. A lot of that development is desisn
> speculation, such as the design notes I have been posting, and there is
> also a fair bit of code, all of which resides
Keiron,
You have pre-empted my last post on this topic.
Keiron Liddle wrote:
> On 2002.03.14 10:55 Nicola Ken Barozzi wrote:
>
>> Ok, nice. This seems more like evolution than revolution, am I right?
>
>
> You could say that.
> The code is forming a revolution, not the people. We needed to go b
Nicola,
Comments interspersed.
Nicola Ken Barozzi wrote:
>From: "Keiron Liddle" <[EMAIL PROTECTED]>
>
>>There was a notice of this a number of months ago. Admittedly we have it
>>the other way around. Maintenance releases are made from a branch. So the
>>main branch is where the active develop
On 2002.03.14 10:55 Nicola Ken Barozzi wrote:
> Ok, nice. This seems more like evolution than revolution, am I right?
You could say that.
The code is forming a revolution, not the people. We needed to go back a
bit and approach things from a different angle.
> Are there any projects underway to
From: "Keiron Liddle" <[EMAIL PROTECTED]>
> (as a guess I would say you haven't beed subscribed long enough :)
;-)
> There was a notice of this a number of months ago. Admittedly we have it
> the other way around. Maintenance releases are made from a branch. So the
> main branch is where the ac
(as a guess I would say you haven't beed subscribed long enough :)
There was a notice of this a number of months ago. Admittedly we have it
the other way around. Maintenance releases are made from a branch. So the
main branch is where the active development is happening.
So where are we:
I am
26 matches
Mail list logo
