You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Karen Lease <kl...@club-internet.fr> on 2001/03/14 22:56:40 UTC
STATUS - next project
Hi all,
Since I started to change the allocation/content width code in Areas,
I'm planning on going back and trying to do this "right", ie making
allocation and content width correspond to the concepts in the CR. I'm
not sure quite what I'm going to do yet; I thought about this quite a
while back, but there have been rather a lot of changes in the fo and
layout packages since then.
Another thing I want to do is improve border rending in PDF (the half
line-width offset problem) and especially in tables, where our current
approach is quite far from what the CR says it should be (notably,
borders should only be rendered on cells and not on rows and columns!).
Anybody else already mucking about in either of these? If so, just yell
and I will find some other playground.
Cheers,
Karen
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Writing-mode and reference-orientation
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
At 11:44 PM 3/22/01 +0100, Karen Lease wrote:
>Arved,
>
>Judging by your recent RFC, you've gotten away from
>reference-orientation and writing-mode for the moment. I found when I
>started looking at modifying the allocation-width and content-width
>traits on Area that it was probably going to touch the same code as any
>kind of ref-orientation work. Are you still swimming around in there, or
>shall I go for it?
Yeah, I deviated away from those 2 for the moment. Since I did the last work
with breaks, it has bugged me considerably that keeps are still in limbo -
and the ability to do this properly and efficiently ties right into
footnotes, floats etc etc. I am finding it difficult to work on anything
else as long as the above is outstanding.
Regards,
Arved
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Writing-mode and reference-orientation
Posted by Karen Lease <kl...@club-internet.fr>.
Arved,
Judging by your recent RFC, you've gotten away from
reference-orientation and writing-mode for the moment. I found when I
started looking at modifying the allocation-width and content-width
traits on Area that it was probably going to touch the same code as any
kind of ref-orientation work. Are you still swimming around in there, or
shall I go for it?
Karen
Arved Sandstrom wrote:
>
> On Thursday 15 March 2001 21:35, Karen Lease wrote:
> > KL: Let's say "inline-progresion" aspect, at least concerning allocation
> > and content "width". By the way, have you thought any more about
> > writing-mode independence?
>
> Yeah, some. I figure we want to do "reference-orientation" and "writing-mode"
> all at the same time. I also think that:
>
> (1) it may not be as bad as probably all of us think; and
> (2) it'll help us do everything else properly (because we will hardcode less
> stuff).
>
> I think what I will do is just dive in. I'll start with
> fo:simple-page-master, and make sure that both of the above properties work,
> and then carry on to regions. Now that all 5 regions are implemented this
> makes more sense. I really don't think that doing this stuff here is all that
> complex compared to the really nasty stuff. But I don't know for sure, and
> there is only one way to find out.
>
> Regards,
> Arved
>
> P.S. Been a bit spotty over the past week because of upgrading to Mandrake
> 7.2 and then upgrading to latest KDE/Gnome stuff on top of that. This combo,
> on a fast PC with lots of RAM, just rocks. :-)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
> For additional commands, email: fop-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: STATUS - next project
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
On Thursday 15 March 2001 21:35, Karen Lease wrote:
> KL: Let's say "inline-progresion" aspect, at least concerning allocation
> and content "width". By the way, have you thought any more about
> writing-mode independence?
Yeah, some. I figure we want to do "reference-orientation" and "writing-mode"
all at the same time. I also think that:
(1) it may not be as bad as probably all of us think; and
(2) it'll help us do everything else properly (because we will hardcode less
stuff).
I think what I will do is just dive in. I'll start with
fo:simple-page-master, and make sure that both of the above properties work,
and then carry on to regions. Now that all 5 regions are implemented this
makes more sense. I really don't think that doing this stuff here is all that
complex compared to the really nasty stuff. But I don't know for sure, and
there is only one way to find out.
Regards,
Arved
P.S. Been a bit spotty over the past week because of upgrading to Mandrake
7.2 and then upgrading to latest KDE/Gnome stuff on top of that. This combo,
on a fast PC with lots of RAM, just rocks. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: STATUS - next project
Posted by Karen Lease <kl...@club-internet.fr>.
Hi Arved,
A few comments below...
Arved Sandstrom wrote:
>
> At 10:56 PM 3/14/01 +0100, Karen Lease wrote:
> >Since I started to change the allocation/content width code in Areas,
> >I'm planning on going back and trying to do this "right", ie making
> >allocation and content width correspond to the concepts in the CR. I'm
> >not sure quite what I'm going to do yet; I thought about this quite a
> >while back, but there have been rather a lot of changes in the fo and
> >layout packages since then.
> >
> >Another thing I want to do is improve border rending in PDF (the half
> >line-width offset problem) and especially in tables, where our current
> >approach is quite far from what the CR says it should be (notably,
> >borders should only be rendered on cells and not on rows and columns!).
> >
> >Anybody else already mucking about in either of these? If so, just yell
> >and I will find some other playground.
>
> I'm still interested in space-specifier resolution...I'm not planning, and
> hadn't been, to deal with the above-mentioned stuff. Except peripherally.
OK. I'll try to keep out of your way.
> I put some thought into your previous long email. My thinking parallels
> yours. I am looking at how we deal with FO storage in the FO tree, and how
> we can leverage that better, in conjunction with making easier and better
> decisions about page-breaks (due to all factors). I believe we are having
> difficulties and doing unnatural things because we are oriented strongly
> towards the Page as the unit of layout processing, and it is probably better
> (IMO) if we key off formatting objects, or groups of formatting objects, for
> layout. It's not black & white, obviously.
>
> This is fuzzy - I can think it better than I can describe it. :-)
KL: Yeah, I have that problem too... I agree 100% about the "unnatural
things"!
> I hope to have code coming out soon. It sounds like you'll be dealing with
> the horizontal aspect of layout, and I'll be dealing with the vertical. Fair
> assessment?
KL: Let's say "inline-progresion" aspect, at least concerning allocation
and content "width". By the way, have you thought any more about
writing-mode independence?
Regards,
Karen
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: STATUS - next project
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
At 10:56 PM 3/14/01 +0100, Karen Lease wrote:
>Since I started to change the allocation/content width code in Areas,
>I'm planning on going back and trying to do this "right", ie making
>allocation and content width correspond to the concepts in the CR. I'm
>not sure quite what I'm going to do yet; I thought about this quite a
>while back, but there have been rather a lot of changes in the fo and
>layout packages since then.
>
>Another thing I want to do is improve border rending in PDF (the half
>line-width offset problem) and especially in tables, where our current
>approach is quite far from what the CR says it should be (notably,
>borders should only be rendered on cells and not on rows and columns!).
>
>Anybody else already mucking about in either of these? If so, just yell
>and I will find some other playground.
I'm still interested in space-specifier resolution...I'm not planning, and
hadn't been, to deal with the above-mentioned stuff. Except peripherally.
I put some thought into your previous long email. My thinking parallels
yours. I am looking at how we deal with FO storage in the FO tree, and how
we can leverage that better, in conjunction with making easier and better
decisions about page-breaks (due to all factors). I believe we are having
difficulties and doing unnatural things because we are oriented strongly
towards the Page as the unit of layout processing, and it is probably better
(IMO) if we key off formatting objects, or groups of formatting objects, for
layout. It's not black & white, obviously.
This is fuzzy - I can think it better than I can describe it. :-)
I hope to have code coming out soon. It sounds like you'll be dealing with
the horizontal aspect of layout, and I'll be dealing with the vertical. Fair
assessment?
Regards,
Arved
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org