Re: Release 0.2a0?
Magnus Lie Hetland <[email protected]>
| Newsgroups | gmane.comp.python.anygui.devel |
|---|---|
| Message-ID | <[email protected]> |
Joseph A Knapka <[email protected]>: [snip] > We certainly want the on-screen widget to reflect the state of > the model, correct? Seems to me that means proxies must listen > to their models, if any. Yes, I just hadn't plugged in my brain properly. Of course they must. And then we get the problem Samuele describes. > Personally, I think MVC is buying us a lot of complication for > no real benefit; I agree. I do, however, think it should be possible to build this sort of stuff on top of Anygui, which means that something like the Assignee code should probably be in place. Or maybe it would be possible to separate this sort of thing completely from the main code base. > if we concentrate on producing a simple widget > API, people can build MVC atop that. (Have I said that before? > I can't remember...) If there are people working on this (it seems that Dallas and Samuele are having a look) I think that the Model classes are great examples of how things can be done. However, I agree that other things should probably take a higher priority. Anyway, I'll probably start a round of coordinated testing soon to see where we stand wrt. the desired functionality for 0.2a0 (which I will then also define). I know that I, at least, would find it motivating to build on a release rather than simply building _towards_ a release... I suspect model functionality will not be required in the alpha-zero. > -- Joe -- Magnus Lie Hetland The Anygui Project http://hetland.org http://anygui.org ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf