Re: Row and Colspan
Andreas L. Delmelle wrote: Not exactly. I'm referring to the grouping into CommonBorderAndPadding / CommonMargin etc. There is also a group of TableProperties in the spec, but the properties seem to be treated rather loosely instead of being handled together in a group, like the others. Oh I understand now. Perhaps it is just an oversight, and should be changed. Chris
RE: Row and Colspan
> -Original Message- > From: Chris Bowditch [mailto:[EMAIL PROTECTED] > Are you asking if they should be created at the same time the > FO tree is built? > Not exactly. I'm referring to the grouping into CommonBorderAndPadding / CommonMargin etc. There is also a group of TableProperties in the spec, but the properties seem to be treated rather loosely instead of being handled together in a group, like the others. > A quick look at fo.flow.Block makes me believe they probably all work > like this. I'm not sure what the pros/cons of changing it would be, but > if it aint broke, why fix it? Nothing broke, but just checking to see if there's unfinished business in there. Cheers, Andreas
Re: Row and Colspan
Andreas L. Delmelle wrote: Another, property-related question (not specifically for you, Chris, but *if* you have an idea...): Is it the intention that the 'Table Properties' are in someway moulded into a class (like now the Common*Properties are), or is the way I see them defined/used now in the relevant classes in fop.fo.flow the intended end-result? The LayoutMgr classes makes use of the Common*Properties for Table objects. They are created by the FO Tree classes (see Table.setup for example) Are you asking if they should be created at the same time the FO tree is built? A quick look at fo.flow.Block makes me believe they probably all work like this. I'm not sure what the pros/cons of changing it would be, but if it aint broke, why fix it? Chris
RE: Row and Colspan
> -Original Message- > From: Chris Bowditch [mailto:[EMAIL PROTECTED] > > Hi Andreas, > > i hope you dont mind a little feedback on this. > Hi Chris, Not at all! Thanx for the fine input. I'll definitely get a lot closer to what I'm (and FOP is) after. (Support for the number-columns-spanned, number-columns-repeated and column-number is indeed *very* easily added to Table.addChild(), for columns, but that gets us more than halfway there). Another, property-related question (not specifically for you, Chris, but *if* you have an idea...): Is it the intention that the 'Table Properties' are in someway moulded into a class (like now the Common*Properties are), or is the way I see them defined/used now in the relevant classes in fop.fo.flow the intended end-result? Later, Andreas
