Comments on: Ruby on Rails with Google Gears http://www.mrblack.co.uk/blog/2007/05/31/ruby-on-rails-with-google-gears/ Thu, 20 Nov 2008 11:04:13 +0000 http://wordpress.org/?v=2.5.1 By: hiutopor http://www.mrblack.co.uk/blog/2007/05/31/ruby-on-rails-with-google-gears/#comment-29326 hiutopor Tue, 18 Sep 2007 09:28:05 +0000 http://www.mrblack.co.uk/blog/2007/05/31/ruby-on-rails-with-google-gears/#comment-29326 Hi all! Very interesting information! Thanks! Bye Hi all!

Very interesting information! Thanks!

Bye

]]> By: Aspen http://www.mrblack.co.uk/blog/2007/05/31/ruby-on-rails-with-google-gears/#comment-25642 Aspen Sat, 18 Aug 2007 23:35:46 +0000 http://www.mrblack.co.uk/blog/2007/05/31/ruby-on-rails-with-google-gears/#comment-25642 hi i enjoyed the read hi i enjoyed the read

]]> By: Alex http://www.mrblack.co.uk/blog/2007/05/31/ruby-on-rails-with-google-gears/#comment-21150 Alex Fri, 29 Jun 2007 01:58:17 +0000 http://www.mrblack.co.uk/blog/2007/05/31/ruby-on-rails-with-google-gears/#comment-21150 I think the potential for this technology is absolutely amazing. I look forward to using it in the future.. I think the potential for this technology is absolutely amazing. I look forward to using it in the future..

]]> By: Martin Sadler http://www.mrblack.co.uk/blog/2007/05/31/ruby-on-rails-with-google-gears/#comment-16643 Martin Sadler Tue, 05 Jun 2007 10:58:08 +0000 http://www.mrblack.co.uk/blog/2007/05/31/ruby-on-rails-with-google-gears/#comment-16643 Hey there. Interesting stuff. There is a Ruby to Javascript library that Paul Battley wrote: http://po-ru.com/diary/convert-ruby-to-javascript/ Using REST is probably best bet for syncing or something like acts_as_syncable: http://www.eribium.org/?p=119 I don't really have a need for Gears at the moment but I'm keeping an eye on it. I reckon there would be some traction with a plugin for it. Hey there. Interesting stuff.

There is a Ruby to Javascript library that Paul Battley wrote:
http://po-ru.com/diary/convert-ruby-to-javascript/

Using REST is probably best bet for syncing or something like acts_as_syncable:
http://www.eribium.org/?p=119

I don’t really have a need for Gears at the moment but I’m keeping an eye on it. I reckon there would be some traction with a plugin for it.

]]> By: site admin http://www.mrblack.co.uk/blog/2007/05/31/ruby-on-rails-with-google-gears/#comment-15315 site admin Fri, 01 Jun 2007 17:52:11 +0000 http://www.mrblack.co.uk/blog/2007/05/31/ruby-on-rails-with-google-gears/#comment-15315 Yes Decklane, it is too complex. Just throwing around the idea. The thing being that helper methods to produce javascript which acts as database controllers can only really be useful and resuable if there is an activerecord type thing going on in either rails producing the javascript (with all the sql) or within the javascript itself. Alas, its a weekend task to explore. I really haven't given much thought to any of this. Yes Decklane, it is too complex. Just throwing around the idea.

The thing being that helper methods to produce javascript which acts as database controllers can only really be useful and resuable if there is an activerecord type thing going on in either rails producing the javascript (with all the sql) or within the javascript itself.

Alas, its a weekend task to explore. I really haven’t given much thought to any of this.

]]> By: Jason Belec http://www.mrblack.co.uk/blog/2007/05/31/ruby-on-rails-with-google-gears/#comment-15302 Jason Belec Fri, 01 Jun 2007 16:45:18 +0000 http://www.mrblack.co.uk/blog/2007/05/31/ruby-on-rails-with-google-gears/#comment-15302 I think this is interesting, after all it came up in my Google. I will be exploring this and psot back anything I dsicover, hope you will as well. I think this is interesting, after all it came up in my Google.

I will be exploring this and psot back anything I dsicover, hope you will as well.

]]> By: Decklane http://www.mrblack.co.uk/blog/2007/05/31/ruby-on-rails-with-google-gears/#comment-15265 Decklane Fri, 01 Jun 2007 14:08:13 +0000 http://www.mrblack.co.uk/blog/2007/05/31/ruby-on-rails-with-google-gears/#comment-15265 From my limited uderstanding of Google gears, I believe you're looking to make something too complex for it to be useful with rails. If you're having to replicate full databases on the client you start running into all the deployment issues you were trying to avoid by making a web app. Might as well write a real desktop client then or a completely Javascript application. However it would probably be quick to create helpers in rails to leverage the caching facilities in gears so you can still consult data offline as well as limited use of the local DB to allow saving of form 'submissions' (i.e. email, comments etc..) on the client until a connection is reestablished and they are committed to the webserver. I'm talking about viewing this from the client perspective, not replicating the server to the client. Allowing network connections to be dropped without causing big pains. From my limited uderstanding of Google gears, I believe you’re looking to make something too complex for it to be useful with rails. If you’re having to replicate full databases on the client you start running into all the deployment issues you were trying to avoid by making a web app. Might as well write a real desktop client then or a completely Javascript application. However it would probably be quick to create helpers in rails to leverage the caching facilities in gears so you can still consult data offline as well as limited use of the local DB to allow saving of form ’submissions’ (i.e. email, comments etc..) on the client until a connection is reestablished and they are committed to the webserver. I’m talking about viewing this from the client perspective, not replicating the server to the client. Allowing network connections to be dropped without causing big pains.

]]> By: Mark Holton http://www.mrblack.co.uk/blog/2007/05/31/ruby-on-rails-with-google-gears/#comment-15126 Mark Holton Fri, 01 Jun 2007 02:33:04 +0000 http://www.mrblack.co.uk/blog/2007/05/31/ruby-on-rails-with-google-gears/#comment-15126 nice post. Thank for the info. I don't believe it will always be that "webservers technically don’t have to store information at their end, ever, just relying upon the users own store." There will be many cases (performance being one of them) where we as developers will engineer the ability to handle requests in a way that was much more efficient in the client-server environment. For instance, in the same manner that Ajax submits only bits and pieces of data to the server as an efficiency improvement over traditional-submit-the-whole-page... Gears/Apollo grant the new technique of submitting/saving information to local, then submitting to the server to synch at the developer's discretion. This could be very powerful in terms of the perceived performance of web applications as they will react in an increasingly more responsive way (no need to wait for server response in many cases ) nice post. Thank for the info.

I don’t believe it will always be that “webservers technically don’t have to store information at their end, ever, just relying upon the users own store.”

There will be many cases (performance being one of them) where we as developers will engineer the ability to handle requests in a way that was much more efficient in the client-server environment. For instance, in the same manner that Ajax submits only bits and pieces of data to the server as an efficiency improvement over traditional-submit-the-whole-page…

Gears/Apollo grant the new technique of submitting/saving information to local, then submitting to the server to synch at the developer’s discretion. This could be very powerful in terms of the perceived performance of web applications as they will react in an increasingly more responsive way (no need to wait for server response in many cases )

]]>