Hi Karen,
Its seems that there are gotcha's no matter what direction we take.
I will try to present the reasons behind the approach I am taking.
I welcome your input and I will look at the code to see how your code
works.
It seems we need a set of tough cases that we need to be able to handle
I agree.
That's why I want to get through this stage so that it is possible to
concentrate on smaller self contained parts.
For now I think these are the parts:
- come up with our best line layout manager process
- create a block/pagination process
- document possible difficult cases, this
9:19 PM
To: fop-dev
Subject: Re: line layout commit
K, K, A and other developers,
Regular chat sessions would probably have been useful here, and I think
that they might still be useful. Probably every interested party but me
is in the time zone spanned by Keiron and Arved. Anyone in the US
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Karen Lease
Sent: April 27, 2002 12:20 PM
To: [EMAIL PROTECTED]
Subject: Re: line layout commit
[ SNIP ]
At any rate, I'm certainly not averse to having some more structured
kind of communication
Hi Foppers,
I've gone ahead and committed the major part of the Break Possibility
approach to layout managers which I have developped. It leaves Keiron's
new code intact (except for a couple of changes I needed to make to be
able to subclass his LineLayoutManager). It's also not activated; to do
Hi Keiron,
Here are a few comments on your new layoutmgr stuff (which is definitely
more advanced than mine in most ways) :
1. I can't figure out how/where you manage space-start, space-end,
border, padding, background etc (ie, any non-inherited properties) for
non leaf node inline FO, ie:
Arved Sandstrom wrote:
What we lack is ownership. We could even combine this
with BugZilla ownership, possibly.
Creating an assigned bugzilla entry (ENH) works for
other projects. I still think it's not quite sufficient
for broad-scoped changes like the current redesign, but
it might work
Arved,
See comments below.
Arved Sandstrom wrote:
1. I can see a place for structured (that is, planned) communication:
conference calls, scheduled meetings on a system like Peter describes, use
of something like MSN Messenger, setting up an IRC channel and everyone
getting together there. But
]]On Behalf Of
Karen Lease
Sent: April 27, 2002 12:20 PM
To: [EMAIL PROTECTED]
Subject: Re: line layout commit
[ SNIP ]
At any rate, I'm certainly not averse to having some more structured
kind of communication about where to go from here be that a chat or just
some discussion on the list of where we
Hi Developers,
I just committed a bunch of changes to the line layout.
I think it now has a reasonable basis to further develop the inline level
areas and build line areas.
If you run it over alignment.fo or instream.fo you will see that it mostly
works for these examples.
It does the spacing
, no kidding. :-) Have
you looked at the Java reference implementation for it? :-) Not a trivial
thing.
Arved
-Original Message-
From: Keiron Liddle [mailto:[EMAIL PROTECTED]]
Sent: April 26, 2002 10:16 AM
To: [EMAIL PROTECTED]
Subject: line layout commit
Hi Developers,
I just
, yup, no kidding. :-) Have
you looked at the Java reference implementation for it? :-) Not a trivial
thing.
Arved
-Original Message-
From: Keiron Liddle [mailto:[EMAIL PROTECTED]]
Sent: April 26, 2002 10:16 AM
To: [EMAIL PROTECTED]
Subject: line layout commit
Hi
K, K, A and other developers,
Regular chat sessions would probably have been useful here, and I think
that they might still be useful. Probably every interested party but me
is in the time zone spanned by Keiron and Arved. Anyone in the US? It
should be possible for you to arrange some
13 matches
Mail list logo
