Why I had to write a client side framework for Koding.

By Sinan Yaşar
http://kod.io

Transcript

1. Koding UI Framework Why I had to write a client side framework @sinanyasar
2. the Others. • Backbone.js • Angular.js • Ember.js • Cappuccino • KnockoutJS • Dojo • YUI • more???
3. Backbone.JS You start writing your app with HTML
4. AngularJS You start writing your app with HTML
5. Ember.js (formerly SproutCore) You start writing your app within HTML
6. …
8. so what we did • Models • Structure • Code reuse, components • Templating • Event handling • Data binding • Routing • …
9. Models But you can still use them :) WHAT IF I TOLD ! YOU YOU DON’T ! NEED THEM
10. Structure well, just be smart about it :)
11. Code Reuse - Components Inheritance everywhere, code reuse
12. Templating Creating your app in small chunks.
13. Event Handling either as options or lazily by ::on OR
14. Data binding that’s it.
15. Routing that’s it.
17. Koding UI Framework to be continued… @sinanyasar This was by Sinan Yasar ui-ux lead at koding.com