[TIMOB-10967] Blackberry: Design Module Framework
GitHub Issue | n/a |
Type | Story |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2012-12-18T04:05:05.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Release 3.1.0, 2012 Sprint 25, BB Preview 3 |
Components | BlackBerry |
Labels | n/a |
Reporter | Ingo Muschenetz |
Assignee | Pedro Enrique |
Created | 2012-09-18T16:36:15.000+0000 |
Updated | 2017-03-07T19:52:01.000+0000 |
Description
Design the module framework that will be used for implementing both our core modules (ex: UI, Network) and third party modules.
Requirements
- Each module should be contained in its own folder (Ex: modules/ui)
- Use the CommonJS API for loading both JS and native modules.
- Define a native API for exporting modules. When a native module
library is loaded and "init" method should be invoked providing
an exports object. This is simliar to how JS modules export APIs.
- Provide an ABI stable interface to maintain module compatibility with platform releases.
While providing ABI safety across all platform versions may be impractical,
we should still provide compatibility at least between minor version releases
(ex: compile module against 3.0 remains compatible with 3.1, but not 4.0).
- Build system to compile modules and package for deployment.
- Ability to export asset files (ex: images) for use at runtime.
Architectural Designs
References to any architectural documents and diagrams
that will serve as guidelines during the project.
Comments
JSON Source
Closing ticket due to support for Blackberry no longer being offered.