to recap, in hindsight, if you had to rewrite th webware class layout today would you guys make the same decisions?
Well, I can't speak for Chuck, but I will anyways ;) He's said he'd use properties if they'd been available. So would I. But to do it now would mean a large number of changes to the API, even if each change is very small, and I'm not sure how to reasonably support both interfaces at the same time (adapters?)
i see. so if i would use properties on my project an "actions" property how would be written? i was thinking of something like:
def _getActions(self): return ['foo', 'bar']
actions = property(fget=_getActions, doc='blah blah')
given that actions is read-only porperty. sub-classes would simply
override _getActions method to provide custom implementation. at this
point maybe _getActions() should really made "private" with the double underscore: __getActions()? mmm, but maybe it's just my sick Java instinct striking again.
later, deelan
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
