let's drop model support
"Samuele Pedroni" <[email protected]> Wed, 25 Sep 2002 15:41:28 +0200
| Newsgroups | gmane.comp.python.anygui.devel |
|---|---|
| Message-ID | <00eb01c26499$403feba0$3c47ca3e@newmexico> |
From: Greg Ewing <[email protected]> > Magnus Lie Hetland <[email protected]>: > > > In-place modification was one of the main reasons for push/pull, and > > if we drop that (which I think well we might) we might end up with an > > architecture that is much easier to understand, explain, and > > maintain. > > This would be good. This would be very, very good. You > need simplification. You need it very badly. For the > last few months, I haven't been able to follow *any* > of these discussions... What can I say, the only way I was able, after my hiatus, to make sense of the discussions was to read the code. Honestly the whole problem is that supporting models only optionally is probably more complicated than making models the only working approach, because then we should support things like: comp.items=L L[0]=... comp.push('items') and deal with questions like what comp.prop should return that makes sense both in the presence of a model or in its absence, [and after further thinking I don't know whether comp.prop returning the model even for immutable values is the right thing ...]. And in general we have to support two operative modes, with models and without, and cope with the abstract question of how to allow to write code that works in both cases. Now given that it seems we don't have a strong use case for models, and that layering models on top of an architecture, whose point is decoupling from toolkit widgets [and models would problably need the the contrary, that means strong coupling to work effectively], is not trivial and does not produce a mechanism simple to understand, I think we all agree that making models the only operative mode would be overkill. So maybe we should simply drop model support ... we already have canvas, tagging for text, events, menus, backends to complete and to develop... ang bugs to fix I have not researched whether I was a proponent for supporting models in the past, I know I have not written related code and ask pardon to the people whose code I'm proposing to drop... I don't know what Magnus or the other think ... For the rest, if we come, instead of dropping it, to a next incarnation of an approach for supporting models I offer to implement it ... regards. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf