On Wednesday 19 Sep 2007, [EMAIL PROTECTED] wrote:
> That´s exactly what I want to prevent with the second suggestion. In this
> inheritence usage I have to add manually ALL components on stage as a
> public property and set the id as attribute as you already mentioned.

It's worth doing to make the separation of code and view as clean as it does.
A typical view only has a few, maybe a dozen, controls - if not, you should 
refactor *anyway* even if you're not doing code behind.
Everything has a cost. You have to ask is it worth it. 
I happen to think for all but trivial views it is.

> The point I´m not sure about is class extends mxml vs. mxml extends class.
> Shall the MXML extend the CodeBehind class as suggested in the examples, or
> the CodeBehind class extend the MXML.

If you do something other people don't (like this backwards-code-behind) you 
make it harder for other people to work with you.
This may or may not be a problem.

-- 
Tom Chiverton
Helping to adaptively improve high-end initiatives
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.

Reply via email to