--- "J.Pietschmann" <[EMAIL PROTECTED]> wrote:
>
> Both collapsed and separated borders are supported,
> the latter
> actually better because collapsing depends on
> neighboring cells,
> which changes at breaks. Extreme settings may even
> cause
> layout oscillations.
>
I updated the compliance.
Glen Mazza wrote:
Technically speaking, if properties were *inherited*
properly, setting border-width on fo:table-row would
propagate to a child fo:table-cell that didn't have
that property already set, correct?
No. Border properties are not inherited:
http://www.w3.org/TR/xsl/slice7.html#common-bo
--- "J.Pietschmann" <[EMAIL PROTECTED]> wrote:
> Dead wrong, properties are inherited properly, if
> you
> ask the property list manager you'll get correct
> values.
Technically speaking, if properties were *inherited*
properly, setting border-width on fo:table-row would
propagate to a child fo:ta
Great!
--- Victor Mote <[EMAIL PROTECTED]> wrote:
> Glen Mazza wrote:
>
> > But if you don't mind taking care of this with
> > JBuilder's refactor task, please do--you're anyway
> > more familiar with Document in case something
> comes
> > up.
>
> All done.
>
> Victor Mote
>
>
--
Glen Mazza wrote:
> But if you don't mind taking care of this with
> JBuilder's refactor task, please do--you're anyway
> more familiar with Document in case something comes
> up.
All done.
Victor Mote
-
To unsubscribe, e-mai
--- Victor Mote <[EMAIL PROTECTED]> wrote:
>
> Actually my
> JBuilder has a nice refactor task that does this for
> almost free, so, unless
> you have something similar at hand, perhaps I should
> do that.
>
> Victor Mote
>
I use JEdit which has a pretty good global S&R
feature.
But if you don't
Glen Mazza wrote:
> > > your coding easier, you may just want to place
> > that
> > > class in apps and not bother with the Control
> > package.
> >
> > I'm don't care much which package it is in. I kind
> > of thought that you and
> > Jeremias were heading toward having apps only have
> > command
--- "J.Pietschmann" <[EMAIL PROTECTED]> wrote:
> Dead wrong, properties are inherited properly, if
> you
> ask the property list manager you'll get correct
> values.
> Have a look at the code: the problem is how border
> definitions at different levels interfere.
> Suppose your table has a top-bord
Glen Mazza wrote:
year) was the case where I wanted to put borders
around each cell in table. Efficiently defining that
at table-level was not implemented in FOP, it was only
defined at individual cell-level, meaning something
is/was wrong with the inheritance, perhaps.
Dead wrong, properties are
--- Victor Mote <[EMAIL PROTECTED]> wrote:
> IMO, changes to properties would seem to
> be low priority, since it works. However, a
> reasonable case can be made that cleaning it up
> simplifies layout, which is very,
> very important.
> At the very
> least, please tell us
> what your plans are
Glen Mazza wrote:
> From my perspective, apps is pretty well cleaned up
> now. (I'll try my luck at the properties and the
> AWTRenderer next.)
Peter has done some work on properties, but I am not clear on what the
status of that is. If I understood, he was going to place the properties as
field
--- Victor Mote <[EMAIL PROTECTED]> wrote:
> I mention this because I know that Glen is
> trying to get apps
> cleaned up. I think creation of "control" should
> help.
>
>From my perspective, apps is pretty well cleaned up
now. (I'll try my luck at the properties and the
AWTRenderer next.)
Do
12 matches
Mail list logo
