You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Hugo Ferreira <hf...@gmail.com> on 2020/07/08 23:40:04 UTC
creationComplete event
I know that Royale is not intended to be backward compatibility with Flex.
I know that but my question is not the case.
I think that a creationComplete or if you prefer a ready event or
childrenComplete is important.
The initComplete is good to start initializing things as soon as possible
however to work with components a creationComplete is very important to
iterate with components.
There is also a childrenAdded however seems to run after initComplete and
before a possible creationComplete so it's a irrelevante event.
Re: creationComplete event
Posted by Hugo Ferreira <hf...@gmail.com>.
Thank you.
While "paying" and testing, I saw that possibility in a sample.
For now it's working.
Carlos Rovira <ca...@apache.org> escreveu no dia sexta, 10/07/2020
à(s) 09:26:
> Another option could be "beadsAdded" event ;)
>
> El jue., 9 jul. 2020 a las 20:48, Hugo Ferreira (<hf...@gmail.com>)
> escribió:
>
> > "If you’re writing a custom component, you might want to override
> > addedToParent() to achieve what you need. With PAYG there are less
> baked-in
> > lifecycle events and hooks, but there should be nothing stopping you from
> > adding these events where you actually need them."
> >
> > That's it.
> > Thank you very much.
> >
> > Yishay Weiss <yi...@hotmail.com> escreveu no dia quinta, 9/07/2020
> > à(s) 13:26:
> >
> > > If you’re writing a custom component, you might want to override
> > > addedToParent() to achieve what you need. With PAYG there are less
> > baked-in
> > > lifecycle events and hooks, but there should be nothing stopping you
> from
> > > adding these events where you actually need them.
> > >
> > > As Piotr said it would be helpful to understand a more specific
> scenario
> > > here.
> > >
> > > From: Piotr Zarzycki<ma...@gmail.com>
> > > Sent: Thursday, July 9, 2020 8:37 AM
> > > To: Apache Royale Development<ma...@royale.apache.org>
> > > Subject: Re: creationComplete event
> > >
> > > Hi Hugo,
> > >
> > > Well in the end you are in a different world after compiling
> application.
> > > initComplete is notifying you once element is added to DOM, so this is
> > real
> > > equivalent to what we had in Flex.
> > >
> > > What's the issue in your sight?
> > >
> > > Thanks,
> > > Piotr
> > >
> > > On Thu, Jul 9, 2020, 1:40 AM Hugo Ferreira <hf...@gmail.com>
> > wrote:
> > >
> > > > I know that Royale is not intended to be backward compatibility with
> > > Flex.
> > > > I know that but my question is not the case.
> > > > I think that a creationComplete or if you prefer a ready event or
> > > > childrenComplete is important.
> > > > The initComplete is good to start initializing things as soon as
> > possible
> > > > however to work with components a creationComplete is very important
> to
> > > > iterate with components.
> > > > There is also a childrenAdded however seems to run after initComplete
> > and
> > > > before a possible creationComplete so it's a irrelevante event.
> > > >
> > >
> > >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
Re: creationComplete event
Posted by Carlos Rovira <ca...@apache.org>.
Another option could be "beadsAdded" event ;)
El jue., 9 jul. 2020 a las 20:48, Hugo Ferreira (<hf...@gmail.com>)
escribió:
> "If you’re writing a custom component, you might want to override
> addedToParent() to achieve what you need. With PAYG there are less baked-in
> lifecycle events and hooks, but there should be nothing stopping you from
> adding these events where you actually need them."
>
> That's it.
> Thank you very much.
>
> Yishay Weiss <yi...@hotmail.com> escreveu no dia quinta, 9/07/2020
> à(s) 13:26:
>
> > If you’re writing a custom component, you might want to override
> > addedToParent() to achieve what you need. With PAYG there are less
> baked-in
> > lifecycle events and hooks, but there should be nothing stopping you from
> > adding these events where you actually need them.
> >
> > As Piotr said it would be helpful to understand a more specific scenario
> > here.
> >
> > From: Piotr Zarzycki<ma...@gmail.com>
> > Sent: Thursday, July 9, 2020 8:37 AM
> > To: Apache Royale Development<ma...@royale.apache.org>
> > Subject: Re: creationComplete event
> >
> > Hi Hugo,
> >
> > Well in the end you are in a different world after compiling application.
> > initComplete is notifying you once element is added to DOM, so this is
> real
> > equivalent to what we had in Flex.
> >
> > What's the issue in your sight?
> >
> > Thanks,
> > Piotr
> >
> > On Thu, Jul 9, 2020, 1:40 AM Hugo Ferreira <hf...@gmail.com>
> wrote:
> >
> > > I know that Royale is not intended to be backward compatibility with
> > Flex.
> > > I know that but my question is not the case.
> > > I think that a creationComplete or if you prefer a ready event or
> > > childrenComplete is important.
> > > The initComplete is good to start initializing things as soon as
> possible
> > > however to work with components a creationComplete is very important to
> > > iterate with components.
> > > There is also a childrenAdded however seems to run after initComplete
> and
> > > before a possible creationComplete so it's a irrelevante event.
> > >
> >
> >
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: creationComplete event
Posted by Hugo Ferreira <hf...@gmail.com>.
"If you’re writing a custom component, you might want to override
addedToParent() to achieve what you need. With PAYG there are less baked-in
lifecycle events and hooks, but there should be nothing stopping you from
adding these events where you actually need them."
That's it.
Thank you very much.
Yishay Weiss <yi...@hotmail.com> escreveu no dia quinta, 9/07/2020
à(s) 13:26:
> If you’re writing a custom component, you might want to override
> addedToParent() to achieve what you need. With PAYG there are less baked-in
> lifecycle events and hooks, but there should be nothing stopping you from
> adding these events where you actually need them.
>
> As Piotr said it would be helpful to understand a more specific scenario
> here.
>
> From: Piotr Zarzycki<ma...@gmail.com>
> Sent: Thursday, July 9, 2020 8:37 AM
> To: Apache Royale Development<ma...@royale.apache.org>
> Subject: Re: creationComplete event
>
> Hi Hugo,
>
> Well in the end you are in a different world after compiling application.
> initComplete is notifying you once element is added to DOM, so this is real
> equivalent to what we had in Flex.
>
> What's the issue in your sight?
>
> Thanks,
> Piotr
>
> On Thu, Jul 9, 2020, 1:40 AM Hugo Ferreira <hf...@gmail.com> wrote:
>
> > I know that Royale is not intended to be backward compatibility with
> Flex.
> > I know that but my question is not the case.
> > I think that a creationComplete or if you prefer a ready event or
> > childrenComplete is important.
> > The initComplete is good to start initializing things as soon as possible
> > however to work with components a creationComplete is very important to
> > iterate with components.
> > There is also a childrenAdded however seems to run after initComplete and
> > before a possible creationComplete so it's a irrelevante event.
> >
>
>
RE: creationComplete event
Posted by Yishay Weiss <yi...@hotmail.com>.
If you’re writing a custom component, you might want to override addedToParent() to achieve what you need. With PAYG there are less baked-in lifecycle events and hooks, but there should be nothing stopping you from adding these events where you actually need them.
As Piotr said it would be helpful to understand a more specific scenario here.
From: Piotr Zarzycki<ma...@gmail.com>
Sent: Thursday, July 9, 2020 8:37 AM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: creationComplete event
Hi Hugo,
Well in the end you are in a different world after compiling application.
initComplete is notifying you once element is added to DOM, so this is real
equivalent to what we had in Flex.
What's the issue in your sight?
Thanks,
Piotr
On Thu, Jul 9, 2020, 1:40 AM Hugo Ferreira <hf...@gmail.com> wrote:
> I know that Royale is not intended to be backward compatibility with Flex.
> I know that but my question is not the case.
> I think that a creationComplete or if you prefer a ready event or
> childrenComplete is important.
> The initComplete is good to start initializing things as soon as possible
> however to work with components a creationComplete is very important to
> iterate with components.
> There is also a childrenAdded however seems to run after initComplete and
> before a possible creationComplete so it's a irrelevante event.
>
Re: creationComplete event
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Hugo,
Well in the end you are in a different world after compiling application.
initComplete is notifying you once element is added to DOM, so this is real
equivalent to what we had in Flex.
What's the issue in your sight?
Thanks,
Piotr
On Thu, Jul 9, 2020, 1:40 AM Hugo Ferreira <hf...@gmail.com> wrote:
> I know that Royale is not intended to be backward compatibility with Flex.
> I know that but my question is not the case.
> I think that a creationComplete or if you prefer a ready event or
> childrenComplete is important.
> The initComplete is good to start initializing things as soon as possible
> however to work with components a creationComplete is very important to
> iterate with components.
> There is also a childrenAdded however seems to run after initComplete and
> before a possible creationComplete so it's a irrelevante event.
>