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

Introducing Ember.js

zohararad
February 26, 2012

Introducing Ember.js

zohararad

February 26, 2012
Tweet

Other Decks in Programming

Transcript

  1. Ember is an OVS framework. OVS stands for Object-View-Something Its

    roots originate from SproutCore It uses Handlebars template engine Hello Ember
  2. Ember introduces several core concepts: 1. Flexible, observable, extensible objects

    2. No routing mechanism 3. Unified App namespace 4. No explicit Models and Controllers Hello Ember
  3. Why this shift you might ask? A unified Object mechanism

    breaks the conventional MVC paradigm. We are not forced to think in terms of Models and Controllers We can plan our app more flexibly Hello Ember
  4. Create classes by extending Embed.Object Instantiate by calling MyClass.create Reopen

    class to add more functionality Create sub-classes by calling MyClass.extend Ember Objects
  5. Ember Views support Partial Views Bound properties DOM Events binding

    Custom helpers courtesy of Handlebars Ember Views
  6. Pros Excellent flexibility thanks to Object abstraction Convenient component binding

    and syncing Great Enumerable utils Flexible and extensive template engine Strong team (Yehuda Katz) and origins (SC) Ember Impressions
  7. Cons jQuery-dependent Documentation is still immature Handlebars uses <script> based

    templates No routing (coming....) Changes native Javascript array Ember Impressions
  8. Will I use it for my next project? Probably not

    just now (still not ready).... jQuery dependency and Handlebars are too limiting in my opinion Documentation is still lacking..... But.... you should definitely give it a try! Ember Impressions
  9. I thought about doing a Todo App And about an

    Odot app (Todo in reverse) Finally, I made a Bookmarking app Ember Demo