You can use full qualified event names to avoid name clashes, eg.

package de.bokelberg.bigproject.myview
{
  class UpdateEvent extends Event
  {
     public static const EVENT_ID : String =
"de.bokelberg.bigproject.myview.Update";
     //...
  }
}

Cheers
Ralf.

On Dec 13, 2007 2:22 PM, Nils Millahn <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
>
> Hi everybody,
>
>  I've started using Cairngorm on a couple of projects and wondered where
>  people generally define their event type identifiers.
>
>  The FrontController/EventDispatcher setup requires unique event names
>  across the application, which is hard to control on large projects with
>  multiple developers (or when further development is done at a later stage).
>
>  So I'm thinking that it would be easier to define event names as 'static
>  const' in a single class 'CairngormEventNames, which in turn could be
>  used in the specific event classes. A bit cumbersome but easier than
>  going through each event class and checking that event names don't overlap.
>
>  What is everybody else doing in this respect?
>
>  cheers - Nils.
>
>  

Reply via email to