cember 1, 2017 6:23:41 PM
> To: dev@royale.apache.org
> Subject: Re: [Royale - ASJS] PAYG list beads
>
> Update (aka, Thinking Out Loud):
>
> I think the way to go here is to have new beads like ItemsAdded,
> ItemsRemoved, ItemsChanged, added to DataItemRendererFactoryForArrayList
.
From: Peter Ent <p...@adobe.com.INVALID>
Sent: Friday, December 1, 2017 6:23:41 PM
To: dev@royale.apache.org
Subject: Re: [Royale - ASJS] PAYG list beads
Update (aka, Thinking Out Loud):
I think the way to go here is to have new beads like ItemsAdded,
ItemsRemoved, ItemsChanged,
Update (aka, Thinking Out Loud):
I think the way to go here is to have new beads like ItemsAdded,
ItemsRemoved, ItemsChanged, added to DataItemRendererFactoryForArrayList
and that bead can delegate the updating of the DataGroup to those beads,
if present. The default can be a bead that listens
Thanks for the reminder, Justin.
I had thought about the Decorator pattern; after all, beads really should
be thought of as Decorators. When we add a password protection bead to the
TextInput component, it does not change what the TextInput component is,
it merely enhances it.
The problem is
Hi,
> thinking that when you add DataProviderItemsChangeNotifier to a List strand,
> you could also replace the itemRenderer factory that is more "capable":
>
> DataItemRendererFactoryForArrayListSupportsItemsAdded
> DataItemRendererFactoryForArrayListSupportsItemsRemoved
>
