RE: [flexcoders] ActionScript Components

Thu, 07 Apr 2005 08:03:42 -0700

Title: Message
Well, flex is whining about subclassing mxml components wich have children with other mxml components containing children:
 
The component mx.controls.Button may not be used as a child of erik.extend.panel because the erik.extend.panel is a container with internal children.
[panel.mxml]
<mx:Panel xmlns:mx="http://www.macromedia.com/2003/mxml">
 <mx:Button label="crazy" />
</mx:Panel>
 
[panelSub.mxml]
<panel xmlns:mx="http://www.macromedia.com/2003/mxml" xmlns="erik.extend.*">
 <mx:Button label="yellow" />
</panel>
 
Greetz Erik
 

From: JesterXL [mailto:[EMAIL PROTECTED]
Sent: donderdag 7 april 2005 16:48
To: [email protected]
Subject: Re: [flexcoders] ActionScript Components

Can you be more specific?  I don't have any problems sub-classes my MXML components.
 
----- Original Message -----
Sent: Thursday, April 07, 2005 5:42 AM
Subject: RE: [flexcoders] ActionScript Components

A good reason to make pure actionscript components is that they can be subclassed.
 
When u create an mxml component, u cant extends a custom mxml component wich has children.
 
Greetz Erik

From: Gordon Smith [mailto:[EMAIL PROTECTED]
Sent: donderdag 7 april 2005 9:04
To: '[email protected]'
Subject: RE: [flexcoders] ActionScript Components

It is essentially a matter of preference. There are no performance differences that I know of.
 
I generally recommend creating components in MXML because it makes several things easier, such as creating internal subcomponents, laying them out, and assigning event handlers to them. For example, if I was creating a LoginPanel, I would certainly do it in MXML.
 
Can you explain what is "a bit messy" about MXML components?
 
- Gordon

Yahoo! Groups Links

Reply via email to