Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS
Download as PPTX, PDF0 likes679 views
The document discusses the implementation of view models to effectively share user interface code between OS X and iOS applications. It presents a proof of concept using a bookstore application, highlighting advantages such as improved code reuse, better readability, and enhanced testability. The conclusion emphasizes that combining view models with traditional MVC can significantly enhance code reuse while addressing concerns related to framework class usage and bidirectional bindings.
Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS
- 1. Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS Dileepa Jayathilake SATURN 2013
- 3. Product for both OS X and iOS With a significant part in common How to reuse code maximally?
- 5. Is it possible to share UI code?
- 7. View Models implement common part of UI View Models are shared View hooks into View Model Controllers hold platform specifics Bidirectional bindings are platform-specific
- 8. View Models contain view data and common UI behavior Models are exposed to Views through View Models 1 2
- 9. Common & Platform-specific components of the solution
- 11. Use of the solution in Book Store application
- 12. Advantages • Improved code reuse • Better readability • Better Separation of View Logic • Enhanced testability Concerns • Framework class usage • Bi-directional bindings
- 13. CONCLUSION View Models combined with traditional MVC can improve code reuse significantly while providing other advantages for applications targeting both OS X and iOS.
- 14. QUESTIONS