Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- After my recent move, I've been sorting through old papers. I just found this page of notes I had
- prepared before meeting @wycats and @tomdale for lunch to discuss SproutCore vs Backbone. It's
- undated, but from around March 2011.
- I remember very vividly the passion they showed over that meal. They knew they had a long road
- ahead of them to convince the web-developer community of the value of this framework and that
- many substantial changes would be needed. But they had a vision and a group of people that were
- willing to give them a chance.
- - why `#getEach` instead of `#pluck`?
- - where do resources for all languages (e.g. layouts) go?
- - where do globals (e.g. root API URL) go?
- - "all views must have a parent view except `SC.Pane`" -- don't you mean, "except `SC.MainPane`"?
- - why do some views take a first argument of `SC.Border`?
- - why are you putting font-weight, color, size, etc. in JS?
- - where is the reference for `SC.ANCHOR_BOTTOM`, etc?
- - can I specify padding on a parent view instead of positioning all children?
- - Autocomplete component?
- - Form builder?
- - asset packaging
- - environment-specific configuration?
- - Model relations?
- - URL hash Δs?
- - best strategy for complex view? Templating? A new `View` Class? -- if so, ex's?
- - how to swap out children of a parent view (e.g. for completing Δing the layout when navigating to a new § of the site)
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement