I’m happy to announce the release of CappuccinoResource (CR), a library dedicated to interfacing between a Cappuccino front-end and a Rails back-end.
CR should feel very familiar to Rails developers. Its interface is akin to ActiveResource and it borrows heavily from the (very good) ObjectiveResource library for the iPhone.
All basic CRUD operations are supported, and you can perform advanced finds with arbitrary parameters. A brief example of fetching a record, modifying it, and saving it:
var post =[Post find:@"42"];[post setTitle:@"Why X is Better than Y"];[post save];
Check out the README on the project’s page on GitHub for more details and usage examples.
Live Demo
I also created a demo application which is a simplified clone of OS X’s Address Book. The demo is live on Heroku. Check it out. The source for the demo is also on GitHub.
If you’re a Rails developer waiting for a good opportunity to try out Cappuccino, there’s no better time than now.
If you’re a Cappuccino developer looking for an easy-to-use, powerful back-end for your applications, Rails might be the answer for you.
CR is a young project, but it drives one of my client applications that is production-ready (albeit not deployed), so I believe it is ready for prime time. Please try it and let me know how it goes.
Writing a web app using Cappuccino has a lot of benefits, one of which is a really nice message passing system wherein certain objects can register to observe events and take action when other objects post notifications of those events.
Here is a very basic way to test if your app is posting event notifications as you expect it to. First, create an Observer class inside a test helper file, which will be included into your tests: Read the rest of this entry »
The much anticipated 280 Atlas developer beta is under way and I recorded a brief screencast introducing the basic concepts of creating applications with Atlas.
In it I build a simplified version of the payment calculator from chapter 2 of Cocoa Design Patterns.
Topics covered include creating a Cib-based project, laying out an interface and binding outlets/actions to working code.
Picking up a new framework can be a daunting task, especially if you’re simultaneously learning a new language. I’ve done this before when I learned Ruby & Rails all in one fell swoop. It was not easy. I’m doing it again with Objective-J and Cappuccino.
Along the way I’ve compiled a list of valuable resources. I believe many others will be taking this same journey in the coming days (especially once Atlas drops), so I’m sharing my findings for the benefit of all.
I just launched CappuccinoFlow: a community driven link blog for the Cappuccino framework. If you’re at all interested in this amazing new technology out of 280north, make sure to subscribe to the RSS feed, follow along on Twitter, and post cool Cappuccino-related links to the flow!
In Detail:
It has been a little quiet around these parts lately. I blame Cappuccino.
For the uninitiated, Cappuccino is a framework for writing web applications (for example). It is built on Objective-J, which is an Objective-C-esque superset of JavaScript. It is completely rad. Also, it’s all client-side so I still get to use Rails on the back-end. I believe the apt word is: woot.
I wanted a link blog to support the small, but growing, Cappuccino community. I’m a big fan of RubyFlow so I contacted its creator, Peter Cooper, and asked him if I could set one up for Cappuccino. He was gracious enough to say yes, and he had conveniently open-sourced an old version of his site awhile back. I forked it on GitHub and the result is CappuccinoFlow.
I’ll probably have to modify my blog’s headline soon, because once I become proficient in Objective-J & Cappuccino you’ll probably see some posts about it.
