Re: Release 0.2a0?

From: Magnus Lie Hetland <[email protected]>


> Samuele Pedroni <[email protected]>:
> >
> >
> > > What major obstacles remain before such a pre-release? Dallas: How are
> > > the models coming along?
>
> Just a quick note about models: If they are proving problematic,
> perhaps we should leave them out of 0.2a0 too? (I'm just interested in
> getting something out that works, as soon as possible.)
>
> It seems that there may be more than one challenge in updating these
> for 0.2. (E.g. getting them to work properly with push/pull; I seem to
> recall something about the in-place modification in pull() being
> broken or not implemented?)
>
> > Am I seeing right that the infinite recursion avoidance mechanism in
> > event send is not enough to avoid spurious push with models?
>
> Hm... That may be.
>
> > A) if prop1 of a component is bound to model mod modifying prop1 will
> >
> > [Attrib.modify]
> >
> > change value of mod
> >   this will trigger a change event
> >    one of the handlers is: push  prop1 for comp [1]
> >    ... other handlers ...
> > push prop1 [2, aggregate push at the end of Attrib.modify]
> >
> > Is this correct ?
>
> Hm. Modifying the model shouldn't affect the component that holds it
> as an attribute in any other way than the normal route. Per default,
> the component should not observe the model. (Maybe I'm just not
> following your argument here...)
>
> > We could avoid to add the names of props bound to models in the name list
> > passed in [2], but when changing more than one single prop, the best thing
> > would be to avoid to call [1].
> >
> > B) retrieving comp.prop1 can pull the value from the widget, then if prop1
is
> > bound to a modal its value is (should be) changed but this would trigger a
> > spurious push...
>
> Why? I don't see why modifying the model should trigger a push?

Because the model when bound to a prop in a component will install an handler
for its change event that will call push
for the prop on model. (That's what Assignee.assigned should be there for,
althoug at the moment the implementation is obsoleted and incorrect (and for
that there's FIXME) )

Such that when one modify the model value the comp (widget) will change too.

regards.



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf