Sounds like a job for an MVC pattern. Of course that may be too much work
depending on the future plans for this app. Probably best to combine the
model and controller as Jason mentioned.
On Wed, Feb 18, 2009 at 10:47 AM, Weyert de Boer wrote:
> Hi Glen,
>
> I would just let the button bubble th
Hi Glen,
I would just let the button bubble the events upwards to one of the
parent objects and then handle the event there. Easiest ;)
Yours,
Weyert
___
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/
book.
-Original Message-
From: flashcoders-boun...@chattyfig.figleaf.com
[mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Glen
Pike
Sent: Wednesday, February 18, 2009 10:18 AM
To: Flashcoders@chattyfig.figleaf.com
Subject: [Flashcoders] Which way is best...
Hi,
I am loo
Hi,
I am looking into the architecture of an application where
components are instanciated and configured generally at runtime,
although some components maybe placed on the stage at author time and
"wired up" runtime. The application is pretty much an interface to
control system which we
4 matches
Mail list logo