commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robert burrell donkin <>
Subject Re: [betwixt] extensible optional parameters in .betwixt file
Date Wed, 07 Apr 2004 21:23:02 GMT
i've committed the basic support code for loading options (going with 
my original name since no one seconded robert's alternative name). i'll 
create some documentation and also use options to allow CDATA rendering 
to be set on a per-element basis via the betwixt file soon.

i had thought about inheritance: it would probably be useful to have 
inheritance of options from parent to children based on an attribute 
setting. unless people need this feature (or fancy volunteering to 
implement it :), it'll probably go on the TODO list for now.

- robert

On 4 Apr 2004, at 14:23, robert burrell donkin wrote:

> On 4 Apr 2004, at 13:26, Robert Leland wrote:
>>> my proposed name for the tag is 'option' (since property could be
>> how about 'behavior' ?
> to me, behaviour sounds like it implies some sort of contract, 
> requesting a particular type of behaviour. i was thinking more of an 
> optional configuration property being set in the betwixt file (rather 
> than programmatically) but if other folks out there agree with rob i 
> could live with 'behaviour'.
> - robert
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message