Title: ModelLocator
Exactly. I found after implementing the
ModelLocator, I pretty much wiped out the need for ViewHelpers. The only thing
I use the ViewHelpers for now is setting focus on fields! It makes things a
lot more organized and simplified. You are right though. Just initial
@yahoogroups.com
Subject: RE: [flexcoders]
ModelLocator
Exactly. I found after implementing
the ModelLocator, I pretty much wiped out the need for ViewHelpers. The
only thing I use the ViewHelpers for now is setting focus on fields! It
makes things a lot more organized and simplified. You are
: Array;
public static var
organization : OrganizationalUnitVO;
}
From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of Mehdi, Agha
Sent: Tuesday, August 23, 2005
12:15 PM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders]
ModelLocator
Great
Behalf Of Mehdi, Agha
Sent: Tuesday, August 23, 2005
12:15 PM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders]
ModelLocator
Great. That sounds exciting and a very
good approach. The way I’m implementing is that I have a ModelLocator,
which has models as properties. Now should those
What about something like this?
[Bindable]
public class ShopModelLocator implements ModelLocator
{
private static var modelLocator : ShopModelLocator;
public static function getInstance() : ShopModelLocator
{
if ( modelLocator == null )
modelLocator = new ShopModelLocator();
return modelLocato
Does your VO class have the "[Bindable]" at the top of it?
-Original Message-
From: flexcoders@yahoogroups.com on behalf of Douglas Knudsen
Sent: Thu 7/6/2006 11:05 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] modellocator and double bindings
Ok, before the big hoorah relase
thanks! yes, I am certain.
It seemed to only effect VOs 'owned' by the main VO.
for example, homeAddress is a VO that is a member of myVO.
mymodel.myVO.homeAddress.address1
each VO extended Cairngorm's ValueObject and is tagged Bindable.
DK
On 7/7/06, Dimitrios Gianninas <[EMAIL PROTECTED]> w
Binding seems to take even if local controls haven't been
created yet. So if you're double-binding is between a null control and an
always-available model locator, the values in the model locator should be
corrupted before the control is created.
On the other hand, if a local variable is
holy creations batman! sounds like a good reason. Now, would adding a creationPolicy="all" to the root application tag address this maybe?DKOn 7/7/06,
Moishe Groger <[EMAIL PROTECTED]> wrote:
Binding seems to take even if local controls haven't been
created yet. So if you're double-b
riday, July 07, 2006 3:42 PMTo:
flexcoders@yahoogroups.comSubject: Re: [flexcoders] modellocator and
double bindings
holy creations batman! sounds like a good reason. Now, would
adding a creationPolicy="all" to the root application tag address this
maybe?DK
On 7/7/06, Moishe
Groger &l
10 matches
Mail list logo
