Re: Models...
Magnus Lie Hetland <[email protected]>
| Newsgroups | gmane.comp.python.anygui.devel |
|---|---|
| Message-ID | <[email protected]> |
Samuele Pedroni <[email protected]>: [snip] > fair enough :). In the end I think my point was that just a subset > of attrs for > comp.attr behave as "proper" attributes at the cost of introducing mutable > numbers and the modify idiom. Hm. I'm not sure I understand your use of "at the cost of" here. How is one related to the other? If we remove the aliases, or reimplement the rule engine, how does that affect the MVC issue? Do you mean that no attributes should be "proper", i.e. all just use copy semantics etc.? It's certainly a possibility... But we could drop mutable numbers and the modify idiom regardless; that's only an MVC thing. (See separate post about alternative MVC implementation.) Frankly, I'm starting to agree with Joe (or, actually, I have agreed with him for quite a while ;) that the MVC stuff is mainly a pain. Now... If we drop the current MVC scheme, should we also consider dropping in-place modification? It's not needed anywhere in the current functionality anyway... -- Magnus Lie Hetland Practical Python The Anygui Project http://hetland.org http://ppython.com http://anygui.org ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf