[TIMOB-24644] Windows: Decouple Hyperloop logic and Ti SDK
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | Medium |
| Status | Closed |
| Resolution | Done |
| Resolution Date | 2017-05-30T02:10:25.000+0000 |
| Affected Version/s | Release 6.1.0 |
| Fix Version/s | Hyperloop 2.2.0 |
| Components | Windows |
| Labels | hyperloop-windows |
| Reporter | Kota Iguchi |
| Assignee | Kota Iguchi |
| Created | 2017-04-29T14:15:41.000+0000 |
| Updated | 2017-05-30T02:10:35.000+0000 |
Description
Currently Hyperloop for Windows is highly coupled with Titanium SDK even after we modularize Hyperloop (TIMOB-24093). For instance, some Hyperloop-related code generation logic and templates are done in Titanium SDK. This situation is not ideal and we want to move all Hyperloop-related logic to Hyperloop module itself, that way we can update Hyperloop _without_ updating Titanium SDK.
For now I can find following parts that can be decoupled with Titanium SDK
- TItaniumWindows_Hyperloop code generation
- Hyperloop event handling code generation
We want to move these logic to Hyperloop plugin.
https://github.com/appcelerator/titanium_mobile_windows/pull/996 https://github.com/appcelerator/hyperloop.next/pull/174