Re: svn commit: r615251 - /xmlgraphics/fop/trunk/src/java/org/apache/fop/layoutmgr/table/RowPainter.java

2008-01-27 Thread Vincent Hennebert
Hi Jeremias,

Jeremias Maerki a écrit :
> Given so many regressions lately in the table layout code, wouldn't it

?! It’s debatable I guess, but I’m not sure something like 5 should be
considered as that many, especially compared to the features added in
the same time.

> be worthwhile to construct a few more test cases? All following the
> pattern: bug, create test case to reproduce, fix until test case passes.

Yes, and that’s usually what I’m doing. I did consider writing
a testcase for this one, but given the nature of the bug I didn’t feel
like it. It’s better caught by a unit test rather than by a layout
engine test, but we don’t have a unit test framework for the layout
code. The bug appeared after a change in the logic of creating
CellParts, now that it’s fixed it’s not likely to reproduce, even after
further refactorings. And the method might well eventually disappear
anyway.

Vincent


-- 
Vincent HennebertAnyware Technologies
http://people.apache.org/~vhennebert http://www.anyware-tech.com
Apache FOP Committer FOP Development/Consulting


Re: svn commit: r615251 - /xmlgraphics/fop/trunk/src/java/org/apache/fop/layoutmgr/table/RowPainter.java

2008-01-25 Thread Jeremias Maerki
Given so many regressions lately in the table layout code, wouldn't it
be worthwhile to construct a few more test cases? All following the
pattern: bug, create test case to reproduce, fix until test case passes.
I know it's not always easily possible but the bug fixed here sounds
easy enough to reproduce on a small scale.

On 25.01.2008 16:52:55 vhennebert wrote:
> Author: vhennebert
> Date: Fri Jan 25 07:52:53 2008
> New Revision: 615251
> 
> URL: http://svn.apache.org/viewvc?rev=615251&view=rev
> Log:
> Fixed a bug in computeContentLength when there are empty cells
> 
> Modified:
> 
> xmlgraphics/fop/trunk/src/java/org/apache/fop/layoutmgr/table/RowPainter.java




Jeremias Maerki