On Mon, 04 Nov 2002 10:22:14 +1000 Peter B. West wrote:
> Jeremias Maerki wrote:
> > Peter
> >
> > This is an idea I was also playing with. Avalon does that, too. But
> > having multiple subprojects (that's what they are, not modules) brings
>
> My sloppy use of the term "module".
>
> > it own
On Sat, 2002-11-02 at 21:31, Rainer Garus wrote:
> A link from page A to page B is only rendered in the pdf renderer correctly if page
>B is prepared by the renderer before page A is rendered. In the following case page A
>is rendered before page B is prepared (PN (X) is the pagenumber of page X)
On Mon, 2002-11-04 at 00:36, Peter B. West wrote:
> Keiron,
>
> Re your latest commits, could you comment on what you had to do to "make
> sure area tree is serializable"? I have been curious about aspects of
> the serialization of trees for some time now.
>
> Peter
Hi Peter,
As you probabl
Jeremias Maerki wrote:
Peter
This is an idea I was also playing with. Avalon does that, too. But
having multiple subprojects (that's what they are, not modules) brings
My sloppy use of the term "module".
it own difficulties. There are several pros and cons to this:
+ Encourages loose coupling
Victor Mote wrote:
Peter B. West wrote:
Re some recent questions on this topic. As I understand it, creating a
branch in the tree off an existing file set simply involves tagging the
set of files with the new branch tag. From that point on, as long as a
particular file remains unchanged, a ch
Keiron,
Re your latest commits, could you comment on what you had to do to "make
sure area tree is serializable"? I have been curious about aspects of
the serialization of trees for some time now.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shal
I can hear a distant pounding already. :-) No seriously, good luck. I
don't think anyone will turn your offer down. And as you say, if
anything goes wrong you get to know FOP a lot better.
On 03.11.2002 20:29:34 Victor Mote wrote:
> Jeremias Maerki wrote:
>
> > The problem with this is really, th
Jeremias Maerki wrote:
> The problem with this is really, that the old layout code is scattered
> around in the FO tree (look for layout() methods). The redesign
> introduces the layout managers which is a move to separate the logic
> (layout code) from the data structure (FO tree). The keyword he
Peter B. West wrote:
> Re some recent questions on this topic. As I understand it, creating a
> branch in the tree off an existing file set simply involves tagging the
> set of files with the new branch tag. From that point on, as long as a
> particular file remains unchanged, a checkout on eith
keiron 2002/11/03 08:29:58
Modified:src/org/apache/fop/fo/flow ListBlock.java ListItem.java
ListItemLabel.java ListItemBody.java
src/org/apache/fop/layoutmgr/table Row.java
Added: src/org/apache/fop/layoutmgr/list Item.java
keiron 2002/11/03 08:24:45
xml-fop/src/org/apache/fop/layoutmgr/list - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
keiron 2002/11/03 08:24:22
Modified:src/org/apache/fop/area AreaTree.java
CachedRenderPagesModel.java PageViewport.java
Trait.java
src/org/apache/fop/datatypes ColorType.java
src/org/apache/fop/fo/flow BasicLi
Jeremias Maerki wrote:
But please, let's put our
efforts together to bring FOP to a version 1.0 as soon as possible. A
lot is already there. We can build on that.
That's what I wanted to say all the thread, +1.
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel
-
Peter
This is an idea I was also playing with. Avalon does that, too. But
having multiple subprojects (that's what they are, not modules) brings
it own difficulties. There are several pros and cons to this:
+ Encourages loose coupling and good design
+ Components that could in theory be used indep
The problem with this is really, that the old layout code is scattered
around in the FO tree (look for layout() methods). The redesign
introduces the layout managers which is a move to separate the logic
(layout code) from the data structure (FO tree). The keyword here is SoC
(Separation of Concern
Re some recent questions on this topic. As I understand it, creating a
branch in the tree off an existing file set simply involves tagging the
set of files with the new branch tag. From that point on, as long as a
particular file remains unchanged, a checkout on either branch will
retrieve a
Kevin O'Neill wrote:
Peter,
I was wondering if you have a two minute overview of the differences
between your design and the main stream one?
Kevin,
My initial response is "No", but I will give it a go. I hope you don't
mind my CC'ing the dev list, in case anyone else is curious.
My initial
17 matches
Mail list logo
