l 26, 2002 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
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 wi
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
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.
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
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: fo:in
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
you are the POC for work being done
> in that package. You are the arbiter of disputes. We could even combine this
> with BugZilla ownership, possibly.
>
> Comments? If folks are agreed or at least not against it I can set up what
> needs to be setup.
>
> Arved
>
> >
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
> ki
Hi Peter,
Well, it certainly is due to some kind of communication problem, and I
think it's largely my "fault" if fault there is. I have a really hard
time committing havf-finished bits of code, so no one's heard a peep
from me in a while. And I think the long BreakPoss design doc I
submitted in
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 times
Hi Keiron,
On the one hand, I'm happy to see new work in the LayoutManagers.
On the other hand, it turns out, I have been plugging (unfortunately
really slowly) away at the Break Possibility ideas I mentioned a while
back and just this very evening I had gotten the Line and Text
LayoutManagers t
Very cool. I will try to pry away from my other project and also doing my
income taxes and put in some quality time checking this out this weekend.
Sounds like we are basically at the point where a bunch of us can usefully
pitch in. :-)
As far as the Unicode bidi algorithm is concerned, yup, no k
13 matches
Mail list logo
