else.)
>>>>>
>>>>> 2. I’d like to have a clearly documented lifecycle for beads. There
>>>>> are
>>>>> some standard bead types such as Model, Controller, View, Content
>>>>> View.
>>>>> When should each of these be created and how? At critical points i
Hi,
You may want to look into using the decorator pattern [1]. It's a nice way of
adding one or more pieces of functionality to a class without using
inheritance. Here’s an AS example i did ages ago [2] for a state machine that
you can add logging or event dispatching or both to.
Thanks,
Justi
t;> the strand know to let the appropriate beads know about an event. The
>>>> beads should send a notification with the necessary payload if one is
>>>> needed. Other beads can modify this payload and/or change the
>>>> notification type if necessary. The p
gt; Thoughts?
>>> Harbs
>>>
>>>>
>>>> On Jul 13, 2017, at 7:34 PM, Alex Harui
>>>> wrote:
>>>>
>>>> Yes, that's how I think of it. You are right that getting one bead in a
>>>> multi bead set to list
is a "beadsAdded" event that can be
>>> used.
>>>
>>> Maybe as more folks implement multi-bead sets we'll see patterns emerge
>>> and make it is simpler and faster.
>>>
>>> My 2 cents,
>>> -Alex
>>>
>>>
gt;>> Generally speaking it feels like sometimes I need to insure the order
>>>of
>>> invocation. Since beads communicate with one another through events
>>>it’s
>>> difficult to achieve. Regarding the upload response data I understand
>>> your suggesti
PAYG which Greg started.
Thank you with sharing with us all of that!
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Re-git-commit-flex-asjs-refs-heads-develop-Add-FileUploaderWithResponseData-tp63051p
t?
>>
>>
>> From: Alex Harui<mailto:aha...@adobe.com.INVALID>
>> Sent: Wednesday, July 12, 2017 9:58 AM
>> To: dev@flex.apache.org<mailto:dev@flex.apache.org>
>> Subject: Re: git commit: [flex-asjs] [refs/heads/develop] - Add
>> FileUploa
l one
(ControllerForResponse + ControllerForWithoutResponse).
This is what I meant when I said we're being forced out of composition into
inheritance.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Re-git-commit-flex-asjs-refs-heads-develop-Add-FileUploaderWithRe
gt;Is that right?
>
>
>From: Alex Harui<mailto:aha...@adobe.com.INVALID>
>Sent: Wednesday, July 12, 2017 9:58 AM
>To: dev@flex.apache.org<mailto:dev@flex.apache.org>
>Subject: Re: git commit: [flex-asjs] [refs/heads/develop] - Add
>FileUploaderWithResponseData
>
&g
he.org<mailto:dev@flex.apache.org>
Subject: Re: git commit: [flex-asjs] [refs/heads/develop] - Add
FileUploaderWithResponseData
I think I still don't understand.
It is ok for beads to require other beads. If a ResponseData bead
requires a model with a slot for responseData and a cont
I think I still don't understand.
It is ok for beads to require other beads. If a ResponseData bead
requires a model with a slot for responseData and a controller that knows
to record that data, that's how you are supposed to "re-compose"
components. There doesn't have to be one model or control
mplicated to read and
maintain.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Re-git-commit-flex-asjs-refs-heads-develop-Add-FileUploaderWithResponseData-tp63051p63139.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
I guess I still don't understand.
Is the goal to expose the responseData? Why does the bead need to record
the response data? Why can't it just get it when someone asks for it?
I'm by no means an expert on Aspects. I think beads should be able to do
some of what I understand aspects do without
that. I hope to update the wiki Greg wrote when I’m
> done with this. Maybe I can pass on some of my experiences.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Re-git-commit-flex-asjs-refs-heads-develop-Add-FileUploaderWithResponseData-tp63051p63136
What problem are you referring to?
-Alex
On 7/11/17, 7:03 PM, "yishayw" wrote:
>Since this type of problem has been bugging me for a while (see also
>FileBrowserWithFilter which raises the same question) I started reading
>about this. To me it seems that we may need aspects [1]. The JS
>impleme
.247.n4.nabble.com/Re-git-commit-flex-asjs-refs-heads-develop-Add-FileUploaderWithResponseData-tp63051p63131.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
done with this.
Maybe I can pass on some of my experiences.
From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
Sent: Monday, July 10, 2017 8:40 PM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: Re: git commit: [flex-asjs] [refs/heads/develop] - Add
FileUploaderWith
Hi Yishay,
I'm wondering whether it is possible to have it bead instead class ? What
do you think ?
Thanks, Piotr
2017-07-10 18:30 GMT+02:00 :
> Repository: flex-asjs
> Updated Branches:
> refs/heads/develop c6a24011b -> 54d00a044
>
>
> Add FileUploaderWithResponseData
>
>
> Project: http://g
19 matches
Mail list logo
