On Thursday 20 Sep 2007, [EMAIL PROTECTED] wrote:
> You just saw it :)
Bizarre. I wonder why they said that ?
> > is rewritten to code behind.
> > Besides a 'code generator' is only an Eclipse plugin away.
>
> It's not a point in how long it takes, it's just not meant to be used
> like that. If it would be, there'd be mechanisms to do that.
If Adobe didn't take the view that Flex Builder in general and Flex in
particular should be framework/pattern neutral, yeah.
> > > Second and more important, you can't use data binding that way which
> > > is one of the most powerful features of Flex.
> > Eh ?
> > We use data binding with code behind all the time. It's fine.
> You can use it of course, but not in the way you would use with code
> in mxml. It requires more fiddling.
*Eh* ?
Here's a data bound control in the MXML from one of our code-behind views:
<mx:Form defaultButton="{searchButton}">
<mx:FormItem label="Fee Earner:">
<mx:TextInput id="feInput"/>
</mx:FormItem>
<mx:FormItem label="Claimant:">
<mx:TextInput id="claimantInput"/>
</mx:FormItem>
<mx:Button id="searchButton" label="Search"/>
</mx:Form>
or, alternatively, to get at a variable (aCase) defined in the AS:
<mx:GridRow>
<mx:GridItem>
<mx:Label text="Client code:"/>
</mx:GridItem>
<mx:GridItem>
<mx:Text text="{ aCase.client }"/>
</mx:GridItem>
</mx:GridRow>
so I'd love to know what's 'more fiddling'.
> > > And there is also third, which is Cairngorm. Cairngorm is ment to use
> > > mxmls as classes, so you treat them as a class. There's more to
> > > Cairngorm than this of course but if you'd like to implement it don't
> > > use code behind approach.
> > WTF ?!?
> > We also use Cairngorm with code behind all the time (not ViewLocator
> > though).
>
> > It works fine.
> > There is no difference between MXML and AS classes, once compiled.
>
> It's not after they are compiled, the difference as I see it, is in
> the development and organizational approach. Cairngorm never advocates
> code behind.
No, but that's not what you said. What you said came across as Cairngorm not
working with code behind.
Their both patterns, not hard and fast rules. It's perfectly possible to use
both, and still have a nice elegant application.
> Of course you can implement similar architecture with all
> the patterns, but Cairngorm is not purely about patterns but also how
> you organize the project, classes, views, etc.
Yeah, IIRC it says sensible things about small simple views, and how views
should transmute Flex events like 'click on button' into application-specific
events like 'LoginEvent'.
Here's what we do:
In the constructor of the AS class, define a creation complete event handler.
In the creation complete event handler, add event handlers to buttons etc. for
clicks or what have you.
In a particular handler, we might create a new Cairngorm Event and dispatch()
it.
This is hardly different at all to how it works if there is just an MXML file
for the View, but keeps all the implementation details out of the MXML file,
which just defines layout. This is good separation of concerns and code
isolation.
I'd love to hear the details of why iteration::two/Adobe don't think that fits
with Cairngorm.
> I'm almost convinced
> that code in mxml is better solution than code behind, though it does
> seem clumsy at times.
If it were as bad as you seem to have it, I would too :-)
--
Tom Chiverton
Helping to elementarily streamline open-source bandwidth
on: http://thefalken.livejournal.com
****************************************************
This email is sent for and on behalf of Halliwells LLP.
Halliwells LLP is a limited liability partnership registered in England and
Wales under registered number OC307980 whose registered office address is at St
James's Court Brown Street Manchester M2 2JF. A list of members is available
for inspection at the registered office. Any reference to a partner in relation
to Halliwells LLP means a member of Halliwells LLP. Regulated by the Law
Society.
CONFIDENTIALITY
This email is intended only for the use of the addressee named above and may be
confidential or legally privileged. If you are not the addressee you must not
read it and must not use any information contained in nor copy it nor inform
any person other than Halliwells LLP or the addressee of its existence or
contents. If you have received this email in error please delete it and notify
Halliwells LLP IT Department on 0870 365 8008.
For more information about Halliwells LLP visit www.halliwells.com.
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/flexcoders/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
