Re: I'm still here...
"Samuele Pedroni" <[email protected]>
| Newsgroups | gmane.comp.python.anygui.devel |
|---|---|
| Message-ID | <051901c263da$f74352c0$6d94fea9@newmexico> |
From: Magnus Lie Hetland <[email protected]> > I guess this is the main point of contention (or one of the main > points). > > It may well be that you (Samuele and Dallas) are right about this. > > But if we do use the model installation approach, I think also > attribute _access_ should retrieve the value (and not the model) -- > doesn't that make sense? > > IOW, proxy.installFooBarModel(model) would make model.value mirror > proxy.fooBar? Sounds like an OK solution to me. > > What do you say? Is this an acceptable version of the scheme? the whole question is what in the presence of a model should L=[...] comp.items=L L.insert() comp.push('items') do get what I presume you mean with mirror you need the above comp.items=L to have reference-rebinding semantics, whereas a changed model modifying items could do that with copy semantics or throw L away and replace the reference, depending on the choice you have different behaviors? > 1. installFooModel() for making a model mirror an Attrib attribute. > > 2. Use link() and 'update' events explicitly to implement the > mirroring. > > I'm still pretty open regarding which is better (or whether there are > other alternatives that are even better than these). under your mirror interpertation of 1. they are more or less equivalent. > BTW: Could installFooModel be used to install more than 1 model? (The > link() scheme could.) This could make sense, but could also be a bit > weird... I guess the models would then be sync'ed with each other > through the Attrib object... I would vote for weird, rather weird :). ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf