Skip to main content
Participant
June 26, 2010
Question

Cairngorm 3 Simple Application doubt

  • June 26, 2010
  • 1 reply
  • 596 views

Either I am missing something OR there might be a good reason for the following:


SaveContactEvent/SearchEvent etc does not extend any Event class, then why we should be calling them events. It is ambiguous and leads to a lot of confusion. These could be appended with something else, but not event.

More about Cairngorm 3 (in general):


There are multiple libraries such as Observer 1.8 and ObserverParsley 1.8.

Do I need both of them to be included in my app OR one of them will fullfil my need based on some preconditions?


Cairngorm 3 provides guidelines and various approaches to handle multiple problems, but same time it is much more confusing to get started with a simple application.


Every lib has it's own docs, but atleast they all could be combined under an umbrella "cairngorm docs" providing a single landing page to get an access to all the different libs.

Thanks.

This topic has been closed for replies.

1 reply

Participating Frequently
June 26, 2010

Some of our projects append them with *Message as they are really Parsley Messages not Flex events. Would you prefer that better or do you have another suggestion? Insync indented to use the Event suffix in a more logical meaning. Technically, they could also be subclassing flash.events.Event, but Parley's messaging doesn't require that.

Can you explain in what situation that caused you confusion though? Did you try to dispatch a Parsley message via the display list?


Regarding the Observer libraries, we should improve our documentation to make this clearer. If you read the how-to document, only the last paragraph: "Loosely Coupling Parsley Domains - Parsley Extension" describes an extention that lives within ObserverParsley and therefore requires Parsley. The rest of the Observer library is framework independent and contains all the other components described.


Have you seen the Introduction paragraph in Guidelines? Those explain the core concepts. Many of the libraries are optional so we don't want to imply users "have" to use all of them. The libraries section is the single entry point for all libraries.