ok ;-)
-Message d'origine-
From: Maurice Amsellem
Sent: Friday, March 08, 2013 2:46 PM
To: dev@flex.apache.org
Subject: RE: An Eventbus for Apache Flex applications
You are right, flex dev list is not the right place. We can follow this
conversation privately, if you li
ice Amsellem
Sent: Friday, March 08, 2013 11:26 AM
To: dev@flex.apache.org
Subject: RE: An Eventbus for Apache Flex applications
Hi Fred,
I am not using modules in my app because the whole app functionality is
required at startup (may I should :-) )
I am using hierarchical contexts for a very spe
y, March 08, 2013 11:26 AM
To: dev@flex.apache.org
Subject: RE: An Eventbus for Apache Flex applications
Hi Fred,
I am not using modules in my app because the whole app functionality is
required at startup (may I should :-) )
I am using hierarchical contexts for a very specific use that I
Envoyé : jeudi 7 mars 2013 17:44
À : dev@flex.apache.org
Objet : Re: An Eventbus for Apache Flex applications
Hi Maurice,
Good to know, yes I was a bit scared about the reflexion-based injection, when
you talk about Multiple hierarchical IOC contexts, do you mean, using modules ?
-Fred
-Messa
Hi,
> questions really is how to not tightly couple our components
MXML/AS components that dispatch events (and event bubbling) works quite well
for that.
Justin
: dev@flex.apache.org
Subject: RE: An Eventbus for Apache Flex applications
Hi, I have developed a rather heavy mobile app using Parsley, which is
running with very good performance.
I am using all the features of Parsley ( Injection, Message/Event bus,
Commands, Multiple hierarchical IOC contexts) and the i
.
Maurice
-Message d'origine-
De : Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
Envoyé : jeudi 7 mars 2013 16:28
À : dev@flex.apache.org
Objet : Re: An Eventbus for Apache Flex applications
100% true but I guess if you want a light weight app to run on mobile, you will
vant to avoi
100% true but I guess if you want a light weight app to run on mobile, you
will vant to avoid the weight of an IoC.
-Fred
-Message d'origine-
From: Christophe Herreman
Sent: Thursday, March 07, 2013 3:55 PM
To: dev@flex.apache.org
Subject: Re: An Eventbus for Apache Flex applica
From: John Cunliffe
> Sent: Thursday, March 07, 2013 3:11 PM
> To: dev@flex.apache.org
> Subject: Re: An Eventbus for Apache Flex applications
>
>
> I think Sebastian knows these frameworks like most flex developers. The
> questions really is how to not tightly couple our compone
me else has a better solution.
-Fred
-Message d'origine-
From: John Cunliffe
Sent: Thursday, March 07, 2013 3:11 PM
To: dev@flex.apache.org
Subject: Re: An Eventbus for Apache Flex applications
I think Sebastian knows these frameworks like most flex developers. The
questions really is
I think Sebastian knows these frameworks like most flex developers. The
questions really is how to not tightly couple our components WITHOUT an
extra framework. And so far I've only seen the Singleton pattern solution -
which imho is an anti-pattern really as soon as testability is required...
but
Hi Sebastian
I never been motivated anymore to build my own multicore MVC framework as
soon as I've seen the one of puremvc back in 2009 IIRC (with the use of
multiton combined with async command or piped events), then, I used the
Parsley approach which I prefered from far as it integrated the
I was not aware of that EventBus. It looks interesting.
Here's how I've handled modules:
The module is controlled by a mediator in the main app which handles all events.
The module should implement an interface do it can be typed and remain
decoupled. The mediator controls the module directly b
When I build apps without using a microarchitecture, I use a singleton which
sends all events to the view (call it the main model). That singleton observes
other singletons which handle various parts of the business logic. I tend to
not use a controller at all and just make request commands "dir
Singletons and events work fine, but I usually prefer using a
microarchitecture... Let's say... I like the order feeling of using a top
level framework.
At this time I am finishing a simplified architecture (I call it Uriana)
based upon a resources and controller pattern which I think fits properl
15 matches
Mail list logo
