[Arp] Another ModelLocator Question
info at nyls.nl
Wed Dec 20 07:25:44 PST 2006
The modellocator (ML) is a singleton so there is only one instance of it in
your app. This is your single entry point to your data/ models from
everywhere in your app.
I tend to use the ARPX -systemcontroller from Grant , So I let views listen
to the systemcontroller for 'update' events.
So when a command get's it's result it fills a model through the ML and
dispatches an systemEvent
And in the appropriate views I listen for thos system events and grab the
model from the modellocator
CHANGE, Proxy.create(this, navigationModelChanged));
var navModel =
That's how I do it,
Is this of help ??
Van: arp-bounces at ariaware.com [mailto:arp-bounces at ariaware.com] Namens COLIN
Verzonden: Wednesday, December 20, 2006 2:37 PM
Aan: arp at ariaware.com
Onderwerp: [Arp] Another ModelLocator Question
I'm (as ever) hoping someone can help me out with an ARP issue. I've been
using arp for a few months now and just when I think I'm get it something
else comes along and I question my own understanding :(
I've been looking at the ModelLocator pattern, I have read previous post's
about this and found some sample files although it does seem a little
confusing. I downloaded the arpx classes
http://www.herrodius.com/upload/arp_extensions.zip which contain quite a
comprehensive version with databinding etc, I've also seen and much simpler
single class version which I have been trying to use.
I have a number of ArpForms which compose my views. Within these forms are
other Arpforms which effectively are like components.
What I'm struggling with is how to populate mx components in my component
forms, is it good practice to import my modelLocator class and then have an
update method which gets called from the main application class when the
model gets populate or create a listener on each form for update events from
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Arp