<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>The Cappuccino Blog - Latest Comments in Getting Started With Cappuccino and Ruby on Rails</title><link>http://cappuccino.disqus.com/</link><description></description><atom:link href="https://cappuccino.disqus.com/getting_started_with_cappuccino_and_ruby_on_rails/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sat, 11 Jul 2009 10:06:46 -0000</lastBuildDate><item><title>Re: Getting Started With Cappuccino and Ruby on Rails</title><link>http://cappuccino.org/discuss/2008/11/11/cappuccino-and-ruby-on-rails/#comment-12501564</link><description>&lt;p&gt;Thanks for this guide.  I'm working on my first Cappuccino UI and this is pretty neat stuff.&lt;/p&gt;&lt;p&gt;I had never heard of JSONP but am excited to start working with it in my first Cappuccino app.  &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alex</dc:creator><pubDate>Sat, 11 Jul 2009 10:06:46 -0000</pubDate></item><item><title>Re: Getting Started With Cappuccino and Ruby on Rails</title><link>http://cappuccino.org/discuss/2008/11/11/cappuccino-and-ruby-on-rails/#comment-8195688</link><description>&lt;p&gt;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.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">MacKuba</dc:creator><pubDate>Tue, 14 Apr 2009 10:19:31 -0000</pubDate></item><item><title>Re: Getting Started With Cappuccino and Ruby on Rails</title><link>http://cappuccino.org/discuss/2008/11/11/cappuccino-and-ruby-on-rails/#comment-3681240</link><description>&lt;p&gt;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.&lt;/p&gt;&lt;p&gt;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.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sean Eby</dc:creator><pubDate>Tue, 11 Nov 2008 12:46:26 -0000</pubDate></item><item><title>Re: Getting Started With Cappuccino and Ruby on Rails</title><link>http://cappuccino.org/discuss/2008/11/11/cappuccino-and-ruby-on-rails/#comment-3678294</link><description>&lt;p&gt;Nice article.&lt;/p&gt;&lt;p&gt;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:&lt;/p&gt;&lt;p&gt;    render :json =&amp;gt; @movies.to_json(:only =&amp;gt; [:title, :description])&lt;/p&gt;&lt;p&gt;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 &lt;a href="http://api.rubyonrails.com/classes/ActiveRecord/Serialization.html#M001417" rel="nofollow noopener" target="_blank" title="http://api.rubyonrails.com/classes/ActiveRecord/Serialization.html#M001417"&gt;http://api.rubyonrails.com/...&lt;/a&gt; for details.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cypher</dc:creator><pubDate>Tue, 11 Nov 2008 09:30:00 -0000</pubDate></item></channel></rss>