In this case, the value of the label is bound to a property of the detailController class. SproutCore has already generated this class, in the controllers folder, so to get this working it is only necessary to add the property:
sMessage: 'Some text here'
Now the function fires whenever that property changes.
There is a range of stylish user-interface objects, including a grid, a list and a tab view; and there is support for drag-and-drop. A test framework and test runner are integrated into the development tools. It also makes use of the jsdoc toolkit, to enable documentation to be generated from comments in your code. SproutCore builds on Prototype for cross-platform support, so it will not be entirely unfamiliar to Prototype users.
SproutCore springs to life
On the negative side, the SproutCore documentation is thin, the project is unfinished, and it does not feel ready for mainstream use. Still, it has huge promise and should mature rapidly now that it has the support of Apple and the attention of others.
Instinct says the latter, but SproutCore makes an impressive case for at least considering the AJAX alternative.®
Nice thing it was ... until I read 'Ruby'. Straight to the trashcan.
I just don't understand Apple's aversion to Java, its exclusion from the iBone is just idiotic. And why, oh why would they go for Ruby ??? I'd rather see Obj-C on the RIA iPhone apps than the horrible Ruby thingy. And I am *not* an Obj-C fan either! (In fact, I think ObjC is kind of Smalltalk disguised as C.)
That other Objective-J sounds better than this, though ... if only because it has _no Ruby_.
cappucino = extra froth?
A mix of java and cocoa would be a mocha, not a cappucino.
Not convinced by SproutCore
I have been using various frameworks in the past year or so and have quite some experience in it.
I don't think that SproutCore deserved all the credits it's currently getting. The only real application so far deployed on some decent scale is Apple Web Gallery (or rather .Mac), and honestly performance are lacking badly.
It's remind me a lot almost Microsoft here with how much vaporware stuff is being written when no one for sure has seen a final working app. I think that July 11 is going to show what I suspect : beautiful user interface (classic Apple) but poor performance.
Here is what I suggest when everything is available : let's check browser memory footprint and overall application response time for loading and using it... I think that until we have something to see and use, it's a lot of wasted bandwidth to claim that SproutCore is solving every problem of the web !
As mentioned in an earlier post, Cappuccino is way more oriented toward Cocoa than SproutCore !
SproutCore force you to use Ruby for your development : this is a no go for many folks.