[Arp] Populating a form

[Sam Shrefler]

I'm still a little confused.  Rich: What exactly are you doing that you wish
you weren't?

Chris, are you saying that changes are needed to ModelLocator to reduce the
coupling?  Christophe uploaded changes that have functions built into them
to do binding.  My question was and still is, are they different than just
saying

mycomponent_cb.dataProvider = modelLocator.getInstance
().getModel("MYCOMPONENTMODEL");
or
dataGlue.bindFormatStrings(mycomponent, modelLocator.getInstance
().getModel("MYCOMPONENTMODEL"), "#Name#","#ID#");

If they are different, why?  and what advantage is there to using them?  If
when using standard components there is no difference, wouldn't it make
sense to write all components to have an auto-update feature on a dataChange
rather than changing the way binding is done?

Thanks

Sam


On 1/25/06, Rich Rodecker <flashape at gmail.com> wrote:
>
>
>
> >
> > The reason for binding is to reduce coupling. Without binding, there
> > would need to be references between objects that retreive or modify an
> > VO and the views that need to refresh themselves with the modified VO.
>
>
>
> which is what I am doing now...and i wish i wasnt.
>
>
>
>
>
> _______________________________________________
> Arp mailing list
> Arp at ariaware.com
> http://ariaware.com/mailman/listinfo/arp_ariaware.com
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ariaware.com/pipermail/arp_ariaware.com/attachments/20060126/229e0835/attachment.htm