[ALOY-404] Create an Alloy model type that uses no persistence
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | Medium |
| Status | Resolved |
| Resolution | Fixed |
| Resolution Date | 2013-01-29T17:43:53.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Alloy 1.0.0, 2013 Sprint 03 |
| Components | Runtime, XML |
| Labels | notable |
| Reporter | Tony Lukasavage |
| Assignee | Unknown |
| Created | 2012-11-30T16:13:43.000+0000 |
| Updated | 2018-03-07T22:26:08.000+0000 |
Description
update (1/29/2013)
A new adapter type was not created. Instead, a test app was created showing how you can use plain old Backbone models and collections and still leverage Alloy data binding. it can be found here: https://github.com/appcelerator/alloy/tree/master/test/apps/models/binding_no_persistenceoriginal
It is assumed that if you are using Alloy Models that you want to use local/remote persistence as well, as the only choices for adapter are sql, properties, and localStorage. We should make an adapter that abides by the normal Alloy Model conventions that has no persistence, an adapter that simply allows devs to take advantage of model-view binding. The adapter type will likely be "*none*" and will be the default when an adapter is not specified. Another consideration is just making plain old backbone models/collections work with Alloy's bindingComments
- Tony Lukasavage 2013-01-29 Created a test app that shows how to use plain old backbone models with alloy binding: https://github.com/appcelerator/alloy/tree/master/test/apps/models/binding_no_persistence