Menu

/cairngorm3/trunk/libraries/ModuleTest/src/example Commit Log


Commit Date  
[r515] by auhlmann@adobe.com

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.

2010-07-01 09:49:55 Tree
[r513] by auhlmann@adobe.com

Experiment with style inheritance.

2010-06-30 14:40:52 Tree
[r433] by ledroff@adobe.com
2010-05-21 08:40:46 Tree
[r429] by yderidde@adobe.com

* 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

2010-05-20 10:56:36 Tree
[r375] by yderidde@adobe.com

Adding the use of Spark component into ModuleC to add the scenario where a Module must be able to get its default spark skin (currently this is failing due to a bug in the Module Lib)

2010-05-06 09:11:21 Tree
[r342] by ledroff@adobe.com

headers update and new main root build

2010-04-14 00:32:37 Tree
[r325] by yderidde@adobe.com

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

2010-04-09 10:17:56 Tree
[r324] by yderidde@adobe.com

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.

2010-04-09 08:46:44 Tree
[r317] by yderidde@adobe.com

Simplifying the design of the module lib by:
- Refactoring the existing mechanism to support the inter-communication between modules thru a unique identifier.
- Ability to communicate between multiple instances of the same module.
- Removed the LazyLoader which was a temporary workaround.
- Adding a new Metadata [ModuleId] which must be used within messages that are inter-communication API messages (to communicate between modules).
- Adding a message pool which basically keep all messages that need to be redirected to a module which is not yet instantiated until the module is available and ready to accept the messages.
- Redo from scratch the ModuleTest application to show the new behaviors.
- Refactored the InSync sample to use the new Module lib.

2010-03-31 12:29:35 Tree
[r159] by auhlmann@adobe.com

Migration to Parsley 2.1

2009-10-22 21:05:25 Tree
Older >
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.