[ALOY-590] Abstract platform-specific checks and functionality in Alloy to make adding platforms trivial
GitHub Issue | n/a |
---|---|
Type | Story |
Priority | Medium |
Status | Resolved |
Resolution | Fixed |
Resolution Date | 2013-04-02T17:53:36.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Alloy 1.2.0, 2013 Sprint 07 |
Components | Titanium SDK |
Labels | n/a |
Reporter | Tony Lukasavage |
Assignee | Unknown |
Created | 2013-03-26T21:52:10.000+0000 |
Updated | 2018-03-07T22:25:42.000+0000 |
Description
Blackberry support was recently added to Alloy (ALOY-424). While it wasn't terribly complicated it took a little more than a day to implement and test to make sure all the various functionality regarding platforms was accounted for. In order to make this easier with future platforms, it would be ideal to abstract the bits of platform-specific functionality into config files that will make this trivial in the future, as simple as a one-file pull request against Alloy by the platform creator.
The process of adding new mobile platforms has now been made significantly easier. For full details on what is necessary to add a new platform to Alloy and be able to leverage all of Alloy's features, check the following wiki documentation: https://wiki.appcelerator.org/display/pe/Adding+Platforms+to+Alloy This document is only available internally as a prerequisite for adding a platform to Alloy is obviously that it must have a corresponding Titanium SDK. If a community developer creates a new compatible Titanium SDK that they wish to have integrated into Alloy, I'll be more than happy to share the doc. :)