I usually use (b). For the error, you can call a public method in the PM from
the faultHandler in the map; as one alternative.
--- In flexcoders@yahoogroups.com, Richard Rodseth rrods...@... wrote:
Design question for any other Mate users out there. Will cross-post to Mate
forum.
I use
The map shouldn't interact with the PM (other than building it with
ObjectBuilder and injecting it into the view).
I'm leaning towards a). That way it's centralized and manager properties can
potentially be injected into multiple presentation models.
On Fri, Jul 2, 2010 at 1:56 PM, turbo_vb
I agree, but it can; since the map knows about the PM anyway. This is where
Swiz has an advantage with the Mediate metadata. In that case the PM method
can just listens for an event; which can be dispatched on fault.
-TH
--- In flexcoders@yahoogroups.com, Richard Rodseth rrods...@... wrote:
Another alternative would be to extend ArrayCollection, or whatever collection
type desired, with a status property.
-TH
--- In flexcoders@yahoogroups.com, Richard Rodseth rrods...@... wrote:
The map shouldn't interact with the PM (other than building it with
ObjectBuilder and injecting it
Haven't looked at Swiz yet, but as I mentioned, I can certainly announce an
event in the faultHandler and inject a listener for it in the PM.
On Fri, Jul 2, 2010 at 3:36 PM, turbo_vb timh...@aol.com wrote:
I agree, but it can; since the map knows about the PM anyway. This is where
Swiz has
Yeah, the cool thing about Swiz, is that this would only add 2 lines of code.
:-)
-TH
--- In flexcoders@yahoogroups.com, Richard Rodseth rrods...@... wrote:
Haven't looked at Swiz yet, but as I mentioned, I can certainly announce an
event in the faultHandler and inject a listener for it in
6 matches
Mail list logo
