sproutcore, first excercise
분류없음 2009/06/17 00:06 E
Sproutcore is one of javascript MVC framework that takes care of client side UI like full-blown desktop application. So far, Sproutcore is used in Apple's otherinbox.
Ever since the library is open to public, I wanted to have an hands-on experience. And this post is about it.
I wanted to make a web-based queue checking page that takes my keyword and list all the jobs in the queue contains such keyword. Server-end is quite simple: grab output from system call "ssh server | grep keyword". However, build a front-end UI using sproutcore was little tricky. I wasn't even ambitious to make the UI fancier, but I ended up spending more than 6 hours, I guess.
One of the big drawback was lack of documentation. There are few examples available in their website, but they are just too simple, and API reference only have some obvious explanation. Sproutcore is a framework, so it works like a black box. In that sense, I think the main developer should provide comprehensive examples that shows various usage of the framework and utilities. They could also provide general overview on how things are intertwined so that a developers who use the framework can attain better insight on how to add functionality.
Sproutcore is one of javascript MVC framework that takes care of client side UI like full-blown desktop application. So far, Sproutcore is used in Apple's otherinbox.
Ever since the library is open to public, I wanted to have an hands-on experience. And this post is about it.
I wanted to make a web-based queue checking page that takes my keyword and list all the jobs in the queue contains such keyword. Server-end is quite simple: grab output from system call "ssh server | grep keyword". However, build a front-end UI using sproutcore was little tricky. I wasn't even ambitious to make the UI fancier, but I ended up spending more than 6 hours, I guess.
One of the big drawback was lack of documentation. There are few examples available in their website, but they are just too simple, and API reference only have some obvious explanation. Sproutcore is a framework, so it works like a black box. In that sense, I think the main developer should provide comprehensive examples that shows various usage of the framework and utilities. They could also provide general overview on how things are intertwined so that a developers who use the framework can attain better insight on how to add functionality.
Javascript frameworks like Sproutcore and Cappuccino clearly draw lines between server-side backend and client-side frontend. No more template and other types of nasty distinction between view and model-controller layer in server-side language is needed once this takes off, which is a still big issue between web developers. To go there, I think, one thing is missing; visual layout editor. And people in 280north are working very hard to bring Atlas, a javascript visual layout editor for Cappuccino, public, so let's keep my hope on.
My source codes are uploaded to GitHub.
