Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/Stray/robotlegs-modular-e-learning-demo
Small demo of modular application development using robotlegs.
https://github.com/Stray/robotlegs-modular-e-learning-demo
Last synced: 2 months ago
JSON representation
Small demo of modular application development using robotlegs.
- Host: GitHub
- URL: https://github.com/Stray/robotlegs-modular-e-learning-demo
- Owner: Stray
- Created: 2009-12-14T10:44:37.000Z (about 15 years ago)
- Default Branch: master
- Last Pushed: 2009-12-16T15:32:48.000Z (about 15 years ago)
- Last Synced: 2024-08-03T05:02:57.984Z (6 months ago)
- Language: ActionScript
- Homepage:
- Size: 223 KB
- Stars: 11
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README
Awesome Lists containing this project
- awesome-actionscript-sorted - robotlegs-modular-e-learning-demo - Small demo of modular application development using robotlegs. (Frameworks / RobotLegs Framework)
README
Requires robotlegs and swiftsuspenders.
This demo has 5 modules:
- ModuleManager just organises the other modules and provides them with a shared moduleEventDispatcher
- LessonLoaderModule loads and communicates with a swf lesson.
- LessonNavModule gives a simple (play / pause) control to the user.
- LoggingModule handles logging of log events.
- SkinManagerModule loads and provides skin assets for skinnable parts (LessonNavModule's PlayPauseButton is skinnable).
There is also a lesson .swf
In this version the modules are set up to be compiled into a single app. It has also been tested with the modules compiled as individual swfs loaded at runtime and works just the same.
Protocols:
- No module should access anything in the .restricted package of another module.
- Each module has a module mediator which controls the flow of events from the shared moduleEventDispatcher in and out of the module's own eventDispatcher.Notes:
Currently the 'skin' (red or blue) loaded for the LessonNavModule is random.
The lesson path is hardcoded in the LoadLessonCommand rather than passed via an event.
The lesson communicates with the LessonLoaderModule via the shared events in the loaderContext.This demo needs to be updated to fit with Shaun's newer version of utilities.modular.