November 2009
10 posts
“One tricky thing about Closure is that you can’t look at all of the widgets and...”
– Dion Almaer sums my feelings also on Closure. As with all libraries, parts of closure are well baked, other’s aren’t. I’m glad Google is sharing.
JavaScript over the long run needs to become more like Ruby or Python - there are hundreds of libraries that each do one specific...
Get Time Tracker Source Code in SproutCore
Bruz Marzolf is writing a series of blog posts implementing a simple time tracking app in various client-side rich web app frameworks. He just finished his example in SproutCore and including some source code.
Here’s what he had to say:
SproutCore provides a higher level abstraction that manages when objects are changed and need to be updated, and when they’re busy and shouldn’t be...
SproutCore Is Now on Gemcutter →
Gemcutter is the new replacement for RubyForge. It is faster and more reliable, which is great if you just want to install SproutCore and not worry so much about the Ruby.
The sproutcore gem will be published on both Gemcutter and standard RubyGems so you don’t have to change anything.
If you want to try using the Gemcutter service, just follow the instructions on the Gemcutter home page...
SC.Response and JSON
martinottenwaelter:
SproutCore’s SC.Response was recently rewritten and I patched it to avoid an exception to be thrown when a malformed JSON string was parsed. The standard way to write you data source didFetch method is now:
didFetch: function(response, params) {
var results;
if (SC.ok(response) && SC.ok(results = response.get('body'))) {
...
} else {
...
“From where we sit now, the code is shaping up quite nicely. Soon enough, if you...”
– Mozilla developer Kevin Dangoor goes in depth on the Bespin Reboot and SproutCore
Bespin Builds on SproutCore →
Mozilla’s Bespin team announced their first preview release of the new Bespin Embedded script and, I’m happy to report, also the first version of Bespin based on SproutCore.
The Bespin team just started to adapt their code to use SproutCore a month or so ago. I’m very excited to see their work progress.
Get the Preview »
SproutCore Performance at Velocity OLC in December →
I’ll be talking about one of the techniques we have used to make SproutCore faster (deferred JavaScript Evaluation covered previously on this blog) at Velocity OLC in December. Hope to see you there (virtually).
SproutCore 1.0 Documentation Binge Part I →
Docs for SproutCore 1.0 are coming along quite nicely. I just finished the first draft of docs covering SproutCore’s psuedo-classical system, properties, universal accessors, and property observing. Check it (and please edit/leave feedback):
Runtime Overview
Objects and Classes
Copying, Freezing, and Comparing
Key Value Coding (KVC)
Key Value Observing (KVO)
Bindings
Inheritance Patterns in JavaScript →
Interesting points on using pseudo-classical inheritance pattern vs the functional pattern. SproutCore is pseudo-classical based, just like Closure, primarily because of memory concerns. Nice to see folks at Google went down the same direction.
