[Jeremias Maerki]
Perfect, Finn! I've just hacked together a little test extension that
lets me evaluate properties and write failure messages to a singleton
which a JUnit test case could process. It's very rough right now, but
with a little more work this could really be cool for checking the
On 26.08.2005 09:09:45 Finn Bock wrote:
[Andreas L Delmelle]
Any hint appreciated.
I have added support for the default values in a TableBorderPrecedence
property maker class.
Cool. It's so good to see names other than mine on the commits list.
Since I have added a new file to SVN
Finn Bock wrote:
[Andreas L Delmelle]
Any hint appreciated.
I have added support for the default values in a TableBorderPrecedence
property maker class.
Since I have added a new file to SVN must I do something to make line
ending right?
Yes you need to set the SVN property
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2005, at 23:32, Andreas L Delmelle wrote:
On Aug 23, 2005, at 22:09, Finn Bock wrote:
So if it is possible at all, I would prefer to see that the
inheritance issues is implemented in the PropertyMaker classes,
instead of the FObjs (or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 24, 2005, at 19:15, Andreas L Delmelle wrote:
Wouldn't inheritance still work as desired --by the Property
subsystem-- if the default value is set in the FObj's bind() method?
Hmm. ATM, it doesn't seem to be working...
I tried using
On 23.08.2005 21:01:13 Andreas L Delmelle wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
Back from holiday, and just started work on the collapsing border model
(something I discussed thoroughly with Jeremias a while ago --don't
worry, I'm not going to start all over :-)
Andreas L Delmelle wrote:
Hi all,
Back from holiday, and just started work on the collapsing border model
(something I discussed thoroughly with Jeremias a while ago --don't
worry, I'm not going to start all over :-) ) Let me just say that, where
earlier on I didn't have a clear idea on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2005, at 22:09, Finn Bock wrote:
Andreas L Delmelle wrote:
The type should be a number with added 'force' enum. The number
property will then coerce a 'force' value into an EnumNumber which is
a number that also holds a enum value,
