Comments on: Getting Started With Cappuccino and Ruby on Rails http://cappuccino.org/discuss/2008/11/11/cappuccino-and-ruby-on-rails/ Home of Cappuccino and Objective-J Thu, 29 Jul 2010 19:12:16 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Alex http://cappuccino.org/discuss/2008/11/11/cappuccino-and-ruby-on-rails/comment-page-1/#comment-418 Alex Sat, 11 Jul 2009 19:06:46 +0000 http://cappuccino.org/discuss/?p=139#comment-418 Thanks for this guide. I'm working on my first Cappuccino UI and this is pretty neat stuff. <br><br>I had never heard of JSONP but am excited to start working with it in my first Cappuccino app. Thanks for this guide. I'm working on my first Cappuccino UI and this is pretty neat stuff.

I had never heard of JSONP but am excited to start working with it in my first Cappuccino app.

]]> By: Jakub Suder http://cappuccino.org/discuss/2008/11/11/cappuccino-and-ruby-on-rails/comment-page-1/#comment-368 Jakub Suder Tue, 14 Apr 2009 19:19:31 +0000 http://cappuccino.org/discuss/?p=139#comment-368 I agree, that's the way to do it. And regarding the wrapping in a "movie" object: that can be turned off by setting config.active_record.include_root_in_json = false in environment. I agree, that's the way to do it. And regarding the wrapping in a “movie” object: that can be turned off by setting config.active_record.include_root_in_json = false in environment.

]]> By: Double Shot #331 « A Fresh Cup http://cappuccino.org/discuss/2008/11/11/cappuccino-and-ruby-on-rails/comment-page-1/#comment-235 Double Shot #331 « A Fresh Cup Thu, 13 Nov 2008 12:46:48 +0000 http://cappuccino.org/discuss/?p=139#comment-235 [...] Getting Started with Cappuccino and Ruby on Rails - That’s the Objective-J framework for desktop-like web applications. [...] [...] Getting Started with Cappuccino and Ruby on Rails – That’s the Objective-J framework for desktop-like web applications. [...]

]]> By: Sean Eby http://cappuccino.org/discuss/2008/11/11/cappuccino-and-ruby-on-rails/comment-page-1/#comment-324 Sean Eby Tue, 11 Nov 2008 22:46:26 +0000 http://cappuccino.org/discuss/?p=139#comment-324 Great start, guys. Glad to see this tutorial. I think the "harder" stuff of integrating Cappuccino w/ Rails will be dealing with multi-model and nested-model scenarios. These are more common with full-fledged applications, multiple windows, etc., all things that are possible with Cappuccino. Looking forward to the next level of examples and tips.<br><br>One other thought: It would be great to see your recommendations on organizing code for a "typical" rails app. Just as Rails creates conventions of model, views, controllers in separate folders (as well as URL resources), Cappuccino has no such hard and fast convention. Would like to see your recommendations on that. Great start, guys. Glad to see this tutorial. I think the “harder” stuff of integrating Cappuccino w/ Rails will be dealing with multi-model and nested-model scenarios. These are more common with full-fledged applications, multiple windows, etc., all things that are possible with Cappuccino. Looking forward to the next level of examples and tips.

One other thought: It would be great to see your recommendations on organizing code for a “typical” rails app. Just as Rails creates conventions of model, views, controllers in separate folders (as well as URL resources), Cappuccino has no such hard and fast convention. Would like to see your recommendations on that.

]]> By: cypher http://cappuccino.org/discuss/2008/11/11/cappuccino-and-ruby-on-rails/comment-page-1/#comment-323 cypher Tue, 11 Nov 2008 19:30:00 +0000 http://cappuccino.org/discuss/?p=139#comment-323 Nice article.<br><br>One nitpick: Your solution for serializing only certain attributes in JSON isn't very Rails-like. Instead, first load the model as you usually would, then render like this:<br><br> render :json => @movies.to_json(:only => [:title, :description])<br><br>This serializes the objects to JSON with only the title and description attributes. This method is also very flexible, e.g. you can include associations and methods that way too. See the RDoc at <a href="http://api.rubyonrails.com/classes/ActiveRecord/Serialization.html#M001417" rel="nofollow">http://api.rubyonrails.com/classes/ActiveRecord...</a> for details. Nice article.

One nitpick: Your solution for serializing only certain attributes in JSON isn't very Rails-like. Instead, first load the model as you usually would, then render like this:

render :json => @movies.to_json(:only => [:title, :description])

This serializes the objects to JSON with only the title and description attributes. This method is also very flexible, e.g. you can include associations and methods that way too. See the RDoc at http://api.rubyonrails.com/classes/ActiveRecord... for details.

]]> By: Sean Eby http://cappuccino.org/discuss/2008/11/11/cappuccino-and-ruby-on-rails/comment-page-1/#comment-234 Sean Eby Tue, 11 Nov 2008 16:46:26 +0000 http://cappuccino.org/discuss/?p=139#comment-234 Great start, guys. Glad to see this tutorial. I think the "harder" stuff of integrating Cappuccino w/ Rails will be dealing with multi-model and nested-model scenarios. These are more common with full-fledged applications, multiple windows, etc., all things that are possible with Cappuccino. Looking forward to the next level of examples and tips.<br><br>One other thought: It would be great to see your recommendations on organizing code for a "typical" rails app. Just as Rails creates conventions of model, views, controllers in separate folders (as well as URL resources), Cappuccino has no such hard and fast convention. Would like to see your recommendations on that. Great start, guys. Glad to see this tutorial. I think the “harder” stuff of integrating Cappuccino w/ Rails will be dealing with multi-model and nested-model scenarios. These are more common with full-fledged applications, multiple windows, etc., all things that are possible with Cappuccino. Looking forward to the next level of examples and tips.

One other thought: It would be great to see your recommendations on organizing code for a “typical” rails app. Just as Rails creates conventions of model, views, controllers in separate folders (as well as URL resources), Cappuccino has no such hard and fast convention. Would like to see your recommendations on that.

]]> By: cypher http://cappuccino.org/discuss/2008/11/11/cappuccino-and-ruby-on-rails/comment-page-1/#comment-233 cypher Tue, 11 Nov 2008 13:30:00 +0000 http://cappuccino.org/discuss/?p=139#comment-233 Nice article.<br><br>One nitpick: Your solution for serializing only certain attributes in JSON isn't very Rails-like. Instead, first load the model as you usually would, then render like this:<br><br> render :json => @movies.to_json(:only => [:title, :description])<br><br>This serializes the objects to JSON with only the title and description attributes. This method is also very flexible, e.g. you can include associations and methods that way too. See the RDoc at <a href="http://api.rubyonrails.com/classes/ActiveRecord/Serialization.html#M001417">http://api.rubyonrails.com/classes/ActiveRecord...</a> for details. Nice article.

One nitpick: Your solution for serializing only certain attributes in JSON isn't very Rails-like. Instead, first load the model as you usually would, then render like this:

render :json => @movies.to_json(:only => [:title, :description])

This serializes the objects to JSON with only the title and description attributes. This method is also very flexible, e.g. you can include associations and methods that way too. See the RDoc at http://api.rubyonrails.com/classes/ActiveRecord... for details.

]]>