[ALOY-161] Allow developers to create controllers with no associated view or style
| GitHub Issue | n/a |
|---|---|
| Type | Improvement |
| Priority | High |
| Status | Resolved |
| Resolution | Fixed |
| Resolution Date | 2012-08-17T10:34:27.000+0000 |
| Affected Version/s | 2012 Sprint 17 |
| Fix Version/s | 2012 Sprint 17, Release 3.0.0 |
| Components | Runtime, XML |
| Labels | n/a |
| Reporter | Tony Lukasavage |
| Assignee | Unknown |
| Created | 2012-08-07T06:57:56.000+0000 |
| Updated | 2018-03-07T22:25:35.000+0000 |
Description
Right now a controller is only processed if it has a corresponding view. The relationship is 1 to 1. We should allow controllers to be processed independently.
This will be useful when developers start making use of the controller inheritance available in Alloy. It also allows developers to write their controllers in pure code outside the context of Alloy and still operate in Titanium applications.
Developers are asking to be able to create things in pure code already. Granted, we should try to guide them in Alloy usage to avoid this whenever possible using device queries, lifecycle events, etc... but there will likely always be cases where people want full control of the code: https://github.com/appcelerator/alloy/issues/33