Ember 1.8 Beta

Transcript

1. ember 1.8 beta and metal-views By Martin Muñoz
2. I work at Crowdmark still @_mmun on twitter :(
3. warning: the typography of this presentation will aggravate you
4. what’s new in ember 1.8 beta?
5. i don’t actually know
6. we’re still using Ember 1.5 at Crowdmark!
7. here’s what they tell me…
8. IE 6 and 7 are deprecated.
9. [applause]
10. what does that mean?
11. we still support them. please report issues.
12. Deprecate global access to view classes from template {{view App.PostView}}
13. Deprecate global access to view classes from template {{view App.PostView}}
14. Deprecate global access to view classes from template {{view "post"}}
15. Deprecate global access to view classes from template {{view "post"}}
16. “but I use multiple namespaces :(“ window.Blahg = Em.Namespace.create(); Blahg.PostView = Em.View.extend(...);
17. np! {{view "blahg/post"}}
18. some big performance improvements…
19. Lots of string operations are now cached: - camelize/dasherize/whateverfy - a hash lookup to tell if a path is global - a hash lookup to split
20. backburner’s pushUnique got a lot of love. This has a big effect on: - Ember Data - rendering big {{each}} blocks
21. Thanks Stefan!
22. Hmm.. what else happened…
24. [ the font is called Flesh Wound ]
25. The metal-views rewrite entirely removes the dependency on the metamorph package
26. Consequently, you will no longer see metamorph script tags
27. [applause]
28. how is that even possible?
29. it’s really simple!
30. we still use script tags!
31. …but they are immediately removed and replaced with two empty TextNodes
32. I’ll talk more about it some day.
33. Today, I want to talk about bindings.
34. Today, I want to talk about bindings.
35. {{comment-list comments=model}} Specifically, how does this work?
36. obj from to Binding
37. commentListView from to Binding {{comment-list comments=model}}
38. commentListView from “comments” Binding {{comment-list comments=model}}
39. commentListView “_parentView.context.model” “comments” Binding {{comment-list comments=model}}
40. The job of bindings: • observe both sides of the binding • if either side changes, schedule an update on the runloop • break ties: down always wins.
41. {{#each item in items}} {{name-tag name=item.name}} {{/each}} how does binding to keywords work? how? :(
42. nameTagView “templateData.keywords.item.name” “name” Binding {{name-tag name=item.name}}
43. This doesn’t use bindings, but instead uses its own way to resolve keywords. {{item.name}}
44. Ok who cares?
45. Well, I think its cool but…
46. {{#each item in items}} {{name-tag name=item.name}} {{/each}} what happens when items changes?
47. Because of some complications and some others, the entire each view much be re-rendered. So we can’t do any smart React style diffing or anything at all smarter than “actually rerender everything”.
48. In order for Ember to get better, we need to improve how keywords work. It will have far reaching consequences on the composibility of components
49. Have you ever used _view or _view._parentView?
50. We can do better!
51. The solution we’re working on is streams.
52. [gasps]
53. It’s not done yet, and I haven’t figured out how to explain it very well.
54. {{myvar}} {{#if myvar}} {{myvar}}!! {{/if}} {{x-foo value=myvar}} 
 {{#each item in items}} {{name-tag name=item.name}} {{item.name}} {{/each}}
55. {{myvar}} {{#if myvar}} {{myvar}}!! {{/if}} {{x-foo value=myvar}} 
 {{#each item in items}} {{name-tag name=item.name}} {{item.name}} {{/each}}
56. (obj2, to) Stream (obj3, to) (obj1, to) source