Upgrade to Pro — share decks privately, control downloads, hide ads and more …

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

D37e5ab989819a805126efe1535d08da?s=47 Kod.io
October 26, 2013

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

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

D37e5ab989819a805126efe1535d08da?s=128

Kod.io

October 26, 2013
Tweet

More Decks by Kod.io

Other Decks in Programming

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. None
  7. so what we did • Models • Structure • Code

    reuse, components • Templating • Event handling • Data binding • Routing • …
  8. Models But you can still use them :) WHAT IF

    I TOLD ! YOU YOU DON’T ! NEED THEM
  9. Structure well, just be smart about it :)

  10. Code Reuse - Components Inheritance everywhere, code reuse

  11. Templating Creating your app in small chunks.

  12. Event Handling either as options or lazily by ::on OR

  13. Data binding that’s it.

  14. Routing that’s it.

  15. None
  16. Koding UI Framework to be continued… @sinanyasar This was by

    Sinan Yasar ui-ux lead at koding.com