Skip to content

Instantly share code, notes, and snippets.

@jamesarosen

jamesarosen/sproutcore-notes.md

Created July 1, 2016 06:07
Show Gist options
  • Save jamesarosen/0ec292ffad6ee49d910426298cf3e9f7 to your computer and use it in GitHub Desktop.
Save jamesarosen/0ec292ffad6ee49d910426298cf3e9f7 to your computer and use it in GitHub Desktop.
Download ZIP
Some notes I just found on SproutCore
Raw
sproutcore-notes.md

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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment