<?xml version="1.0" encoding="UTF-8"?>
<!--Generated by Squarespace Site Server v5.0.0 (http://www.squarespace.com/) on Fri, 05 Sep 2008 15:24:02 GMT--><?xml-stylesheet type="text/css" href="/universal/styles/feed.css"?><rss version="2.0"><channel><title>Eric's Ruby on Rails Blog - Comments</title><link>http://blogs.ericmethot.com/rails/</link><description></description><copyright></copyright><language>en-US</language><generator>Squarespace Site Server v5.0.0 (http://www.squarespace.com/)</generator><item><title>Eric Methot comments on Using SproutCore: Demo App</title><author>Eric Methot</author><pubDate>Tue, 08 Jul 2008 05:07:34 +0000</pubDate><link>http://blogs.ericmethot.com/rails/2008/6/19/using-sproutcore-demo-app.html#comments</link><guid isPermaLink="false">191113:1845625:comment/1603217</guid><description><![CDATA[<p>Thanks for the irony but you don't get it. Sure today it's trivial, at the time it wasn't. This was posted just after WWDC and when you googled &quot;sproutcore&quot; you got squat worth your while with regards to demo code. Except perhaps for the demo apps for which, we had no source code (or none easily accessible). In less than a month there has been quite a lot going on with sproutcore. Today you will find much more relevant posts for developers than then. With hindsight it's always easier...</p>]]></description></item><item><title>so nice for him comments on Using SproutCore: Demo App</title><author>so nice for him</author><pubDate>Mon, 07 Jul 2008 22:22:45 +0000</pubDate><link>http://blogs.ericmethot.com/rails/2008/6/19/using-sproutcore-demo-app.html#comments</link><guid isPermaLink="false">191113:1845625:comment/1602635</guid><description><![CDATA[<p>Wow.  I have a suggestion for your next post...<br/>And when I turn the handle water comes out of the faucet.</p>]]></description></item><item><title>Nicolas Chapados comments on Strongspace Look &amp; Feel</title><author>Nicolas Chapados</author><pubDate>Tue, 18 Mar 2008 12:37:31 +0000</pubDate><link>http://blogs.ericmethot.com/rails/2008/2/25/strongspace-look-feel.html#comments</link><guid isPermaLink="false">191113:1845625:comment/1363244</guid><description><![CDATA[<p>Très beau blog Éric!  J'aime le look.  Qu'est-ce que tu utilises pour le tenir  à jour?</p>]]></description></item><item><title>Aditya comments on Datebalks: a slimmer datebocks</title><author>Aditya</author><pubDate>Tue, 22 Jan 2008 17:41:33 +0000</pubDate><link>http://blogs.ericmethot.com/rails/2008/1/13/datebalks-a-slimmer-datebocks.html#comments</link><guid isPermaLink="false">191113:1845625:comment/1239509</guid><description><![CDATA[<p>Right, i've posted you the file. You may want to diff it to see the exact set of changes. </p><p>I use the same partial for new as well as edit, so when we have existing values in date field, they should also be stored in the hidden field, else they'll become blank during the subsequent update.</p><p>Cheers,<br/>Aditya</p>]]></description></item><item><title>Eric Methot comments on Datebalks: a slimmer datebocks</title><author>Eric Methot</author><pubDate>Tue, 22 Jan 2008 11:16:19 +0000</pubDate><link>http://blogs.ericmethot.com/rails/2008/1/13/datebalks-a-slimmer-datebocks.html#comments</link><guid isPermaLink="false">191113:1845625:comment/1238867</guid><description><![CDATA[<p>That's a good point to use local variables for the IDs to support multiple date fields (I should have thought of that myself) and thanks for pointing out the typo. I've added a &quot;Send me a file&quot; link to the sidebar so that you can send me your modifications. I'll update the datebalks.js script and post an update.</p><p>Thanks, </p>]]></description></item><item><title>Aditya comments on Datebalks: a slimmer datebocks</title><author>Aditya</author><pubDate>Tue, 22 Jan 2008 07:03:27 +0000</pubDate><link>http://blogs.ericmethot.com/rails/2008/1/13/datebalks-a-slimmer-datebocks.html#comments</link><guid isPermaLink="false">191113:1845625:comment/1238709</guid><description><![CDATA[<p>Cheers mate!!<br/>Thanks for the quick reply!</p><p>Playing around with this, bought up a couple of issues.</p><p>1. This doesnt quite work if you have multiple dateselects on your page. The solution is to not use the &quot;global&quot; sml_id and inp_id in the observers/calendar updates. In my mod, i derive sml_id and inp_id from element in the callback functions. </p><p>2. Typo in the spelling of tomorrow. It shouldnt be tommorow.</p><p>3. My issue it that i've got a form with a whole bunch of date fields, so for me to &quot;except&quot; out a whole bunch of them is slightly painful. What I did was exclude the input textbox value from the Model's hash. So, input textbox name is due_at_date_text not, customer[due_at_date_text]. I did this by playing with regex in your &quot;appendPopupAndText&quot; function.</p><p>I can post my version if you like? If yes, let me know where i can send it.</p>]]></description></item><item><title>Eric Methot comments on Datebalks: a slimmer datebocks</title><author>Eric Methot</author><pubDate>Mon, 21 Jan 2008 20:16:28 +0000</pubDate><link>http://blogs.ericmethot.com/rails/2008/1/13/datebalks-a-slimmer-datebocks.html#comments</link><guid isPermaLink="false">191113:1845625:comment/1237812</guid><description><![CDATA[<p>Hello Aditya, I'd say that the simplest way is to remove the _date attribute from the hash before doing the update. It requires only one method call. Here is an example:&lt;/p&gt;<br/><code><br/>bq.project = Project.find(params[:id])<br/>bq.project.update_attributes(params[:project].except(:due_at_date))<br/></code><br/>I think that that's the simplest way to go about it. Another way would be to toy around the javascript so that it produced and send only what you wand but that would be a bit more involved.</p>]]></description></item><item><title>Aditya comments on Datebalks: a slimmer datebocks</title><author>Aditya</author><pubDate>Mon, 21 Jan 2008 16:59:14 +0000</pubDate><link>http://blogs.ericmethot.com/rails/2008/1/13/datebalks-a-slimmer-datebocks.html#comments</link><guid isPermaLink="false">191113:1845625:comment/1237385</guid><description><![CDATA[<p>Hi Eric!</p><p>This is wonderful!! Many thanks! Amazing! </p><p>However, is there a way to prevent the sending of the field with the _text? It kind of goes and screws up the ActiveRecord update call because the attribute with _text does not exist on the Model. </p><p>Cheers,<br/>Aditya</p><p></p>]]></description></item></channel></rss>