Re: Models...
Magnus Lie Hetland <[email protected]>
| Newsgroups | gmane.comp.python.anygui.devel |
|---|---|
| Message-ID | <[email protected]> |
Dallas Johnston <[email protected]>: [snip] > Perhaps this would aid in greater simplifying the utilisation of the > push/pull API and perhaps avoid having to employ similar coding > techniques in Models.py and Proxy.py to handle state > syncronisation?!? Or would this be too much fluff? I don't know. Factoring out a separate push/pull class might be interesting, bearing in mind that the back-end push/pull is completely different. I'm not completely sure, though. I originally saw models like this: A model such as ListModel should behave like a list, but when modified, it sends out a 'modified' event. This, of course, will no longer work now that we have lazy controller behaviour. We'd have to call proxy.pull(), assuming that prosxy.foo == model. I don't quite see why models should have push/pull methods, really... But there are different ways of approaching this model stuff, I guess. > --Dallas -- Magnus Lie Hetland The Anygui Project http://hetland.org http://anygui.org ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390