Cairngorm Code

Experiment with style inheritance.

Module library change: Style inheritance working for Spark components. API change on ParsleyModuleDescriptor.domain > applicationDomain. ModuleViewLoader and ParsleyModuleDescriptor now expose more module configuration parameters. ModuleViewLoader takes precedence.

Experiment with style inheritance.

Updating the sample with more scenarios

* Adding a new view loader called 'ModuleViewLoader' specifically written as a custom Spark component.
It provide a separate skin based on 4 states (normal,loading,error,loaded). The Default skin is ModuleViewLoaderSkin

the ModuleViewLoader component benefits from new features such as external Loading Policy strategies.
The lib provides 2 Load Policy:
- BasicLoadPolicy: load module on addedToStage and unload on removeFromStage
- LazyModuleLoadPolicy: load module on demand based on the moduleId property of the message. As soon as a message with a corresponding moduleId is dispatched, the module is loading itself automatically.

* Refactoring the SDK3 ViewLoader to reflect the same features as the new Spark ViewModuleLoader except that the SDK3 ViewLoader do not include states to display different views as the Spark component does.

* Refactoring the ModuleTest sample project to use the new features/components

-Change initialization objects of Cairngorm Parsley extensions to Parsley convention (i.e. CairngormModuleLib>CairngormModuleSupport). Every initialization object has a static initialize method and implements Parsley's ContextBuilderProcessor, which allows it to be specified within a ContextBuilder definition.
-API Change in Navigation library: Changed -FirstEnter metadata to Enter(time="first"), -Enter metadata to Enter(time="next") and -EveryEnter metadata to Enter(time="every")
-Added convenience isValid get accessor to ValidationGroupEvent

headers update and new main root build

- Fixing a bug in the case where a Message is dispatched without a ModuleId defined to a Module type which is not yet instantiated.
- Updating the sample to show this use-case.

fixing bug in Module lib + updating the Module Test sample to remove any ambiguities.

Improving the inter-communication module messages by adding new behaviors:
- Ability to dispatch a message to a unique module instance thru the [ModuleId] tag defined in the message.
- Ability to dispatch a message to all modules of a same type (defined by a ParsleyModuleDescriptor) by providing the reference of the Descriptor in the ModuleMessageInterceptor decorator.
- Ability to dispatch a message to all instantiated modules if none of the above is defined.

Updated the ModuleTest samples to use these new behaviors.