On Wed, 2002-08-21 at 23:29, Karen Lease wrote:
Hi Keiron,
Keiron Liddle wrote:
snip/
The line height calculation and alignment is only very basic at the moment.
The idea is that the LineLM gets certain information to find the offset to
baseline and total line height and when the
Hi Karen,
On Mon, 2002-08-19 at 23:57, Karen Lease wrote:
Hi Keiron etc,
I'm really happy to see all this movement going on and folks from the
maintenance branch getting into the redesign to help you out. I'm
hoping to be able to start contributing again too, perhaps not right
away,
Karen Lease wrote at 20 Aug 2002 23:07:46 +0200:
That would be good. I haven't looked at it for a month or so, but I had
(as usual) some questions about various statements in the XSL-FO spec
concerning the interpretation of the various properties. Perhaps we
could go over those issues
Hi Tony,
Thanks for the advice. I have already started to look at the OpenType
standard, in particular the parts describing the various baselines.
Unfortunately I don't suppose I'll be attending the Unicode conference
but perhaps someone here will be and could listen to Steve's talk and
Hi Keiron,
Keiron Liddle wrote:
snip/
The line height calculation and alignment is only very basic at the moment.
The idea is that the LineLM gets certain information to find the offset to
baseline and total line height and when the InlineLM add areas they use this
information to set the
Karen Lease wrote:
..., since a BreakPoss is
really just a potential Area.
Just nitpicking: It is the state of a LM tree, and in that sense
certainly a bit more than a potential area.
The equivalent of that logic on the block stacking level could be to
have all block-level LM except the
On Mon, 2002-08-19 at 22:58, J.Pietschmann wrote:
Keiron Liddle wrote:
- Add markers to page when areas added
Is this really a good idea? Markers may be referenced
long after they have been defined, tying them to the
Page object would require keeping the pages in memory
(see 0.20.5cvs:
On Mon, 2002-08-19 at 23:13, J.Pietschmann wrote:
Keiron Liddle wrote:
- Implement table layout
The table layout will use the same technique as the block layout. It
will locate suitable breaks between rows or inside rows until table
finished or end of bpd reached.
Actually, what
:
-Original Message-
From: Karen Lease [mailto:[EMAIL PROTECTED]]
Sent: August 19, 2002 6:58 PM
To: [EMAIL PROTECTED]
Subject: Re: Tasks - layout
[ SNIP ]
With regard to the line-height calculations, is anybody in the group
interested in getting into the gory details of the baseline stuff
On Sun, 2002-08-18 at 02:07, J.Pietschmann wrote:
Keiron Liddle wrote:
I don't think we should expect or even want people to understand
everything.
I think it's preferable that people hacking around in the
code understand *something*.
Of course, but how can we make it understandable.
Keiron Liddle wrote:
- Add markers to page when areas added
Is this really a good idea? Markers may be referenced
long after they have been defined, tying them to the
Page object would require keeping the pages in memory
(see 0.20.5cvs: forward page references are *required*
to force keeping
Keiron Liddle wrote:
- Implement table layout
The table layout will use the same technique as the block layout. It
will locate suitable breaks between rows or inside rows until table
finished or end of bpd reached.
Actually, what *are* valid breaks within a table apart from breaks
between
Hi Keiron etc,
I'm really happy to see all this movement going on and folks from the
maintenance branch getting into the redesign to help you out. I'm
hoping to be able to start contributing again too, perhaps not right
away, but hopefully in September. There may even be some possibility of
-Original Message-
From: Karen Lease [mailto:[EMAIL PROTECTED]]
Sent: August 19, 2002 6:58 PM
To: [EMAIL PROTECTED]
Subject: Re: Tasks - layout
[ SNIP ]
With regard to the line-height calculations, is anybody in the group
interested in getting into the gory details of the baseline
Keiron Liddle wrote:
- Add static areas to page
The static areas will need to be handled in a similar way to the flow
except the bpd is unlimited and it will need to reset and repeat for
each page.
I looked at it. Is static content supposed to be handled
by a FlowLayoutManager too? It
On Mon, 2002-08-12 at 21:17, J.U. Anderegg wrote:
o Are there specified packages, classes to be programmed? Are the
interfaces/interface objects specified?
Mostly yes, and if someone wants more information I can go into more
detail.
o Are prerequisite packages or test drivers available?
On Mon, 2002-08-12 at 13:44, Kevin O'Neill wrote:
These are just some of the things, I will add them to the todo list.
If there is a decent response then there are more that can be added.
Any PDF tasks?
- Encryption and signing
- Reusing pdf objects that links create
- form XObject
Those
Now that we have some pagination there are lots of areas that people can
work on.
If you want to implement any of these and have any questions then just
ask.
Once we can get a few of these done then we could do a developers
release.
- Add static areas to page
The static areas will need to
These are just some of the things, I will add them to the todo list.
If there is a decent response then there are more that can be added.
Any PDF tasks?
--
If you don't test then your code is only a collection of bugs which
apparently behave like a working program.
Website:
19 matches
Mail list logo
