are
trying to insert the children between a menubar and status bar.
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Josh McDonald
Sent: Wednesday, July 30, 2008 4:36 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Can we subclass
a menubar and status bar.
--
*From:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On
Behalf Of *Josh McDonald
*Sent:* Wednesday, July 30, 2008 4:36 PM
*To:* flexcoders@yahoogroups.com
*Subject:* Re: [flexcoders] Can we subclass Application yet?
Alex
You can certainly subclass Application via AS. Are you trying to do it
in MXML?
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of chigwell23
Sent: Wednesday, July 30, 2008 11:51 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Can
I'm confused. You subclass Application every time you create a new Flex app,
and in MXML. What problems are there to speak of?
-Josh
On Thu, Jul 31, 2008 at 6:08 AM, Alex Harui [EMAIL PROTECTED] wrote:
You can certainly subclass Application via AS. Are you trying to do it
in MXML?
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Alex Harui
Sent: Wednesday, July 30, 2008 4:09 PM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] Can we subclass Application yet?
You can certainly subclass Application via AS. Are you trying to do it
in MXML
] Can we subclass Application yet?
I'm confused. You subclass Application every time you create a new Flex
app, and in MXML. What problems are there to speak of?
-Josh
On Thu, Jul 31, 2008 at 6:08 AM, Alex Harui [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
You can certainly subclass
Makes sense, since you're overriding Container._childDescriptors anyway. But
why on earth would you *want* to do this?
-Josh
On Thu, Jul 31, 2008 at 9:08 AM, Alex Harui [EMAIL PROTECTED] wrote:
Any attempt to subclass an MXML Component based on a container to add
other children to it usually
@yahoogroups.com
Subject: RE: [flexcoders] Can we subclass Application yet?
Any attempt to subclass an MXML Component based on a container to add
other children to it usually results in some issue or another, usually
that thing about children have already been defined, so you can't
really make a template app
Frankly I'm moving towards the root Application having nothing but enough
code to initiate framework bootstrapping and instantiate the home
component when bootstrapping is completed anyway.
-Josh
--
Therefore, send not to know For whom the bell tolls. It tolls for thee.
:: Josh 'G-Funk'
Sent: Wednesday, July 30, 2008 4:23 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Can we subclass Application yet?
Makes sense, since you're overriding Container._childDescriptors anyway.
But why on earth would you *want* to do this?
-Josh
On Thu, Jul 31, 2008 at 9:08 AM, Alex
@yahoogroups.com [mailto:[EMAIL PROTECTED] *On
Behalf Of *Alex Harui
*Sent:* Wednesday, July 30, 2008 7:09 PM
*To:* flexcoders@yahoogroups.com
*Subject:* RE: [flexcoders] Can we subclass Application yet?
Any attempt to subclass an MXML Component based on a container to add other
children to it usually
Alex,
I definitely understand the need for this, but I'd use components is all. I
can see how it'd be useful though. I'd have to poke around inside the
generated actionscript, but I'm sure this could be hacked up without *too*
much shenanigans to work with the current compiler. I might take a
12 matches
Mail list logo
