--- In [email protected], "Tim Hoff" <[EMAIL PROTECTED]> wrote:
>
>
> Hi Steve,
>
> Usually you would use Cairngorm events for application wide user
> gestures; like making a service call, or for gestures that require a lot
> of calculations or that navigate. However, to reduce the amount of
> custom events, you can certainly use local flex or flash events for user
> gestures that are local to a view; like click a button and change the
> view state of the component or view. Nothing wrong with using Cairngorm
> events for everything, but the more that you can keep a component
> self-contained, the better.
>
> -TH
>
> --- In [email protected], "stephen_anson" <[EMAIL PROTECTED]> wrote:
> >
> > Hi, I'm fairly new to cairngorm,
> >
> > I have an app that produces many events via 'user gestures', so for
> > example I produce a group of items one of which can be selected for
> > further editing of its properties via a form.
> >
> > Should cairngorm I produce custom events and hookup to the front
> > controller for every single mouse click etc, or is it best to reserve
> > the cairngorm architecture for specific parts of an application such
> > as sending and receiving data to the server.
> >
> > thanks Steve
> >
>
much appreciated thanks
Steve
