Great article - I've been building recently with backbone / jasmine using client-side fixtures. Architecture is a bit different than Sproutcore, so the data fixtures come need to match with server rest calls (vs client-side data store). This means mocking both the ajax calls and the html as fixtures.
I'm curious of other experience using Sproutcore (particularly Sproutcore 2 since there has been a large refactor of code).
- How useful are the widgets in a rapid prototyping situation?
- Upon initial inspection, the state-model of Sproutcore records seems to be overly complex (ie, not very elegant). How does this design pattern work in the real world?
- If I build a webapp with Sproutcore, will it be easier to deploy this same app to mobile devices vs something like backbone.js?
I'm curious of other experience using Sproutcore (particularly Sproutcore 2 since there has been a large refactor of code).
- How useful are the widgets in a rapid prototyping situation?
- Upon initial inspection, the state-model of Sproutcore records seems to be overly complex (ie, not very elegant). How does this design pattern work in the real world?
- If I build a webapp with Sproutcore, will it be easier to deploy this same app to mobile devices vs something like backbone.js?