That's not quite what I was talking about : )
How about just extending buttons with enable/disable and serialize?
(and i.e. keeping getValue/setValue logic consistent)
Are there other ones that would make sense?

- kangax

On May 7, 12:27 pm, John-David Dalton <[EMAIL PROTECTED]>
> Patched to work with getValue, 
> setValue.
> Unit 
> tests:
You received this message because you are subscribed to the Google Groups 
"Prototype: Core" group.
To post to this group, send email to
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at

Reply via email to