--- In flexcoders@yahoogroups.com, Alex Harui <[EMAIL PROTECTED]> wrote:
>
> I know I shouldn't step in here, but I'd like to ask for a cease-
fire.
>
> Faithful Flex developers may know that Amy was the guinea pig for
Gordon and my first article in Flex Authority magazine where we
discussed the
when we know how many we need.
-Alex
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Amy
Sent: Thursday, October 30, 2008 11:38 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: UI component, a set function & creationComplete
--- In flexcoders@yaho
--- In flexcoders@yahoogroups.com, "Michael Schmalle"
<[EMAIL PROTECTED]> wrote:
>
> Amy,
> I have read all that you have written. 2 years of sales, no
complaints on
> the algorithm I use.
>
> > So it very much matters where you create children when _other
people_ are
> going to be subclassing
Anyone taking bets?
-TH
--- In flexcoders@yahoogroups.com, "Amy" <[EMAIL PROTECTED]> wrote:
>
> --- In flexcoders@yahoogroups.com, "Michael Schmalle"
> teoti.graphix@ wrote:
> >
> > Amy,
> > > These functions are in place for very good reasons, and if you
> try to
> > circumvent them you have a
Amy,
I have read all that you have written. 2 years of sales, no complaints on
the algorithm I use.
> So it very much matters where you create children when _other people_ are
going to be subclassing your work.
I have created a sub template in commitProperties(); That can
be overridden from any s
--- In flexcoders@yahoogroups.com, "Michael Schmalle"
<[EMAIL PROTECTED]> wrote:
>
> Clarification;
> > Children can be created at any time AFTER super().
>
> Since we all design software with a design, any property committal
in a
> super() call has nothing to do with an instance of a child you
--- In flexcoders@yahoogroups.com, "Michael Schmalle"
<[EMAIL PROTECTED]> wrote:
>
> well big mouth has to say one more thing,
>
> Imagine commitProperties() committing property states :) , all of
your
> properties have been committed. Children can be created at any time
AFTER
> super().
>
> W
--- In flexcoders@yahoogroups.com, "Michael Schmalle"
<[EMAIL PROTECTED]> wrote:
>
> Amy,
> > These functions are in place for very good reasons, and if you
try to
> circumvent them you have a
> really good chance of running into problems.
> I will happily disagree with you on this and not say m
Clarification;
> Children can be created at any time AFTER super().
Since we all design software with a design, any property committal in a
super() call has nothing to do with an instance of a child you create in the
subclass (this is bad design). Thus, the above logic holds true.
Mike
On Thu, O
well big mouth has to say one more thing,
Imagine commitProperties() committing property states :) , all of your
properties have been committed. Children can be created at any time AFTER
super().
What you fail to see is commitProperties() is a glorified createChildren().
This only thing "cool" ab
Amy,
> These functions are in place for very good reasons, and if you try to
circumvent them you have a
really good chance of running into problems.
I will happily disagree with you on this and not say much else. I don't feel
like getting into a pissing match with documentation, as I am sure this
Thanks, Amy.
I have decided that my own model is more convoluted than is healthy. So, I have
reworked
things on my side and stuck with createChildren(). I was tempted to try Mike's
suggestion
- and, had I felt really good about my implementation, I might have.
At this point, with more checks
--- In flexcoders@yahoogroups.com, "Michael Schmalle"
<[EMAIL PROTECTED]> wrote:
>
> Hi Eric,
> > So, my question is does your approach address this by creating
children
> in
> commitProperties()
> Yes,
>
> This is basically what I do with all renderers in my commercial
components.
> I rarely u
Hi Eric,
> So, my question is does your approach address this by creating children
in
commitProperties()
Yes,
This is basically what I do with all renderers in my commercial components.
I rarely use createChildren(). The only time I use createChilren() is when
the composite is 100% owned by it's p
Mike,
I am wondering if what I am experiencing with createChildren() is similar to
what you've
described below. I am subclassing UIComponent - and I read that it is best to
create
children in a createChildren() method.
However, I am tying into someone else's existing code and she has done some
15 matches
Mail list logo
