Rails Envy Podcast – Episode #087: 07/15/2009

Posted over 2 years back at Rails Envy - Home

Episode 87. We bring you the latest news in the Ruby and Rails world. By we I mean I. The greatly delayed podcast 85 will be out in the next couple of days and features a couple awesome surprise co-hosts.

Subscribe via iTunes – iTunes only link.
Download the podcast ~11:30 mins MP3.
Subscribe to feed via RSS by copying the link to your RSS Reader



Runway is a GTD-style action management web application made by geeks for geeks. Created by the folks at Cogent, try a free demo at http://www.runwayapp.com.

Sponsored by New Relic
NewRelic not only provides rails performance monitoring with RPM, but they also produce Rails Lab, a website dedicated to advice on tuning and optimizing Rails apps.

Show Notes

paranoia and split personalities, for your models!

Posted over 2 years back at blog.to_html :

  is_paranoid is exactly what I’ve been looking for.  It’s like acts_as_paranoid, but up to date with ActiveRecord’s new default scopes, which simplifies the gem quite a bit.

One idea I really like was brought on by seeing this example:

 

  class Pirate < ActiveRecord::Base
    is_paranoid :field => [:alive, false, true]
  end

  class DeadPirate < ActiveRecord::Base
    set_table_name :pirates
    is_paranoid :field => [:alive, true, false]
  end

 

Here we have the same table acting like two models based on a default scope.  So simple, yet brilliant.  Why didn’t I think of this earlier?

Consider this:

 

  class User < ActiveRecord::Base
    is_paranoid
  end

  class UserArchive < ActiveRecord::Base
    set_table_name :users
  end

 

You could use the User model for every day use, and if you need to specifically look at inactive users, you use UserArchive.  Spectacularly to the point.  Of course this has uses outside the scope of is_paranoid.

 

6 Free Ruby Icons For Your Projects

Posted over 2 years back at Ruby Inside

rubyicons-1.gif

Several weeks ago, stock icon company Iconshock offered to design some icons for Ruby Inside to give to its readers. Initially skeptical, I was convinced to give it a try after seeing some of their other work. Now, the first 6 icons are back and.. they're totally free for you to use. Grab this ZIP file that contains PNG and EPS (ideal for Illustrator) versions of the icons and give them a go!

The six icons signify Ruby on Rails, Ruby itself, two file types (Ruby and RubyGems), an application, and a generic cog. All can be used as you see fit. Iconshock told me that there are "no special terms or conditions" and that they can be used "for personal and commercial projects." They'd be cool to use in logos for Ruby libraries, on your blog, or anywhere else where Ruby related imagery would come in useful. Giving Iconshock credit is optional but appreciated.

What icons do you want to see next?

Iconshock have already expressed an interest in producing a second set of icons for Ruby Inside. What do you want to see? The first set were based on my ideas, but next time around they can produce the icons that you really want or think would be useful to the Ruby and Rails communities. What sort of icons could you use for your Ruby related Web sites, blogs, libraries, events, and so forth? Leave a comment against this post.

So who are Iconshock anyway?

iconshock.png

Ruby Inside has no financial relationship with Iconshock - we get some cool icons to give away in return for pointing out that Iconshock made them, and that they have plenty more (700,000+!) for sale on their site. They seem quite experienced in producing icons for applications and all of the icons I've browsed through in their catalog have been impressive so far.

So, check Iconshock out if you're interested in buying some icon sets or getting your own custom icons done (for $50 each if you want three or more). Perhaps they'll keep making us some cool free icons to give away..

paranoia and split personalities, for your models!

Posted over 2 years back at blog.to_html :

  is_paranoid is exactly what I’ve been looking for.  It’s like acts_as_paranoid, but up to date with ActiveRecord’s new default scopes, which simplifies the gem quite a bit.

One idea I really like was brought on by seeing this example:

 

  class Pirate < ActiveRecord::Base
    is_paranoid :field => [:alive, false, true]
  end

  class DeadPirate < ActiveRecord::Base
    set_table_name :pirates
    is_paranoid :field => [:alive, true, false]
  end

 

Here we have the same table acting like two models based on a default scope.  So simple, yet brilliant.  Why didn’t I think of this earlier?

Consider this:

 

  class User < ActiveRecord::Base
    is_paranoid
  end

  class UserArchive < ActiveRecord::Base
    set_table_name :users
  end

 

You could use the User model for every day use, and if you need to specifically look at inactive users, you use UserArchive.  Spectacularly to the point.  Of course this has uses outside the scope of is_paranoid.

 

paranoia and split personalities, for your models!

Posted over 2 years back at blog.to_html :

  is_paranoid is exactly what I’ve been looking for.  It’s like acts_as_paranoid, but up to date with ActiveRecord’s new default scopes, which simplifies the gem quite a bit.

One idea I really like was brought on by seeing this example:

 

  class Pirate < ActiveRecord::Base
    is_paranoid :field => [:alive, false, true]
  end

  class DeadPirate < ActiveRecord::Base
    set_table_name :pirates
    is_paranoid :field => [:alive, true, false]
  end

 

Here we have the same table acting like two models based on a default scope.  So simple, yet brilliant.  Why didn’t I think of this earlier?

Consider this:

 

  class User < ActiveRecord::Base
    is_paranoid
  end

  class UserArchive < ActiveRecord::Base
    set_table_name :users
  end

 

You could use the User model for every day use, and if you need to specifically look at inactive users, you use UserArchive.  Spectacularly to the point.  Of course this has uses outside the scope of is_paranoid.

 

paranoia and split personalities, for your models!

Posted over 2 years back at blog.to_html :

  is_paranoid is exactly what I’ve been looking for.  It’s like acts_as_paranoid, but up to date with ActiveRecord’s new default scopes, which simplifies the gem quite a bit.

One idea I really like was brought on by seeing this example:

 

  class Pirate < ActiveRecord::Base
    is_paranoid :field => [:alive, false, true]
  end

  class DeadPirate < ActiveRecord::Base
    set_table_name :pirates
    is_paranoid :field => [:alive, true, false]
  end

 

Here we have the same table acting like two models based on a default scope.  So simple, yet brilliant.  Why didn’t I think of this earlier?

Consider this:

 

  class User < ActiveRecord::Base
    is_paranoid
  end

  class UserArchive < ActiveRecord::Base
    set_table_name :users
  end

 

You could use the User model for every day use, and if you need to specifically look at inactive users, you use UserArchive.  Spectacularly to the point.  Of course this has uses outside the scope of is_paranoid.

 

paranoia and split personalities, for your models!

Posted over 2 years back at blog.to_html :

  is_paranoid is exactly what I’ve been looking for.  It’s like acts_as_paranoid, but up to date with ActiveRecord’s new default scopes, which simplifies the gem quite a bit.

One idea I really like was brought on by seeing this example:

 

  class Pirate < ActiveRecord::Base
    is_paranoid :field => [:alive, false, true]
  end

  class DeadPirate < ActiveRecord::Base
    set_table_name :pirates
    is_paranoid :field => [:alive, true, false]
  end

 

Here we have the same table acting like two models based on a default scope.  So simple, yet brilliant.  Why didn’t I think of this earlier?

Consider this:

 

  class User < ActiveRecord::Base
    is_paranoid
  end

  class UserArchive < ActiveRecord::Base
    set_table_name :users
  end

 

You could use the User model for every day use, and if you need to specifically look at inactive users, you use UserArchive.  Spectacularly to the point.  Of course this has uses outside the scope of is_paranoid.

 

paranoia and split personalities, for your models!

Posted over 2 years back at blog.to_html :

  is_paranoid is exactly what I’ve been looking for.  It’s like acts_as_paranoid, but up to date with ActiveRecord’s new default scopes, which simplifies the gem quite a bit.

One idea I really like was brought on by seeing this example:

 

  class Pirate < ActiveRecord::Base
    is_paranoid :field => [:alive, false, true]
  end

  class DeadPirate < ActiveRecord::Base
    set_table_name :pirates
    is_paranoid :field => [:alive, true, false]
  end

 

Here we have the same table acting like two models based on a default scope.  So simple, yet brilliant.  Why didn’t I think of this earlier?

Consider this:

 

  class User < ActiveRecord::Base
    is_paranoid
  end

  class UserArchive < ActiveRecord::Base
    set_table_name :users
  end

 

You could use the User model for every day use, and if you need to specifically look at inactive users, you use UserArchive.  Spectacularly to the point.  Of course this has uses outside the scope of is_paranoid.

 

paranoia and split personalities, for your models!

Posted over 2 years back at blog.to_html :

  is_paranoid is exactly what I’ve been looking for.  It’s like acts_as_paranoid, but up to date with ActiveRecord’s new default scopes, which simplifies the gem quite a bit.

One idea I really like was brought on by seeing this example:

 

  class Pirate < ActiveRecord::Base
    is_paranoid :field => [:alive, false, true]
  end

  class DeadPirate < ActiveRecord::Base
    set_table_name :pirates
    is_paranoid :field => [:alive, true, false]
  end

 

Here we have the same table acting like two models based on a default scope.  So simple, yet brilliant.  Why didn’t I think of this earlier?

Consider this:

 

  class User < ActiveRecord::Base
    is_paranoid
  end

  class UserArchive < ActiveRecord::Base
    set_table_name :users
  end

 

You could use the User model for every day use, and if you need to specifically look at inactive users, you use UserArchive.  Spectacularly to the point.  Of course this has uses outside the scope of is_paranoid.

 

paranoia and split personalities, for your models!

Posted over 2 years back at blog.to_html :

  is_paranoid is exactly what I’ve been looking for.  It’s like acts_as_paranoid, but up to date with ActiveRecord’s new default scopes, which simplifies the gem quite a bit.

One idea I really like was brought on by seeing this example:

 

  class Pirate < ActiveRecord::Base
    is_paranoid :field => [:alive, false, true]
  end

  class DeadPirate < ActiveRecord::Base
    set_table_name :pirates
    is_paranoid :field => [:alive, true, false]
  end

 

Here we have the same table acting like two models based on a default scope.  So simple, yet brilliant.  Why didn’t I think of this earlier?

Consider this:

 

  class User < ActiveRecord::Base
    is_paranoid
  end

  class UserArchive < ActiveRecord::Base
    set_table_name :users
  end

 

You could use the User model for every day use, and if you need to specifically look at inactive users, you use UserArchive.  Spectacularly to the point.  Of course this has uses outside the scope of is_paranoid.

 

paranoia and split personalities, for your models!

Posted over 2 years back at blog.to_html :

  is_paranoid is exactly what I’ve been looking for.  It’s like acts_as_paranoid, but up to date with ActiveRecord’s new default scopes, which simplifies the gem quite a bit.

One idea I really like was brought on by seeing this example:

 

  class Pirate < ActiveRecord::Base
    is_paranoid :field => [:alive, false, true]
  end

  class DeadPirate < ActiveRecord::Base
    set_table_name :pirates
    is_paranoid :field => [:alive, true, false]
  end

 

Here we have the same table acting like two models based on a default scope.  So simple, yet brilliant.  Why didn’t I think of this earlier?

Consider this:

 

  class User < ActiveRecord::Base
    is_paranoid
  end

  class UserArchive < ActiveRecord::Base
    set_table_name :users
  end

 

You could use the User model for every day use, and if you need to specifically look at inactive users, you use UserArchive.  Spectacularly to the point.  Of course this has uses outside the scope of is_paranoid.

 

Ruby on Rails Linked Data content negotiation skeleton code

Posted over 2 years back at RicRoberts :

Bill wrote on his blog a few days ago about an example Rails app that he created to demonstrate the basics of how we do Linked Data content negotation at Swirrl.

As he mentions in the article, Bill put this together partly in response to a discussion on the LOD mailing list about ways of implementing the content negotiation process without reliance on Apache.

Take a look at the README in the Github Repository for more details.

Change timezone of ubuntu machine from command line

Posted over 2 years back at Web On Rails


If you guys want to change timezone of your ubuntu machine then you can do it by issuing:

dpkg-reconfigure tzdata

This may be helpful if you deal with servers.

Double Shot #496

Posted over 2 years back at A Fresh Cup


It looks like the Fairy Godmother Department’s lunch hour may be over.

  • Many Ways to Tag Taggables – Tobias hunted down all the Rails tagging libraries he could find. Looks like he settled on acts_as_taggable_on, which is the one I use too.
  • fleakr – Flickr API integration gem recommended by a couple of my readers.
  • read_from_slave – Read your Rails data from a MySQL slave database, while ensuring that writes go to the master database.
  • Programming Contest! Win iPhone 3GS & $2,000 Cloud Credit – Engine Yard is planning a contest that is going to make Twitter even more annoying for a while.
  • Choosy – OS X utility ($12) to let you choose a browser when you click on a link.
  • Ruby Versions – SSH access to a bunch of new and archived flavors of Ruby.

Parties Fail to Agree on the HTML 5 Video Codec

Posted over 2 years back at InfoQ Personalized Feed for unregistered user - Register to upgrade!

Ian Hickson, the editor of the HTML 5 Specification, has recently removed the required codecs from the <video> and <audio> tags of the respective draft standard citing difficulties in reaching consensus among major companies involved in distributing video and audio content on the web. By Abel Avram



© The contents of this website are copyrighted by respective blog owners.

Designed and developed by Pratik and Anup