January 26th, 2010 » No Comments »
If you need a quick and dirty lightbox using jQuery for Ruby on Rails, give Facebox by FamSpam a try. Facebox is a jQuery-based, Facebook-style lightbox which can display images, divs, or entire remote pages. It’s simple to use and easy on the eyes.
January 19th, 2010 » No Comments »
It is pretty common that you need to store settings in a rails applications. You might do this via global variables/constants or other more complex mean. Two recent rubygems have set out to solve this problem. The first is rails-settings an ActiveRecord like storage of settings in the database. It allows you to keep track of any global setting that you dont want to hard code into your rails app. You can store any kind of object. Strings, numbers, arrays, or any object.
Configatron is another alternative. It is a super cool, simple, and feature rich configuration system for Ruby apps. You can set defaults, use hashes, use yaml and even namespace configurations. You can even do temp, delayed or dynamic configurations. If you are currently using global variables/constants do yourself a favor and check one of these gems out.
January 18th, 2010 » No Comments »
This last weekend Rails Bridge put together a Do One Thing For Rails 3 Bug Mash. It was the first I had heard of Rails Bridge. It was great to see all that they are trying to do for the community. Need Rails Courseware? Non-profit looking for help? Maybe you are new and just need a Mentor? Kids need to learn Rails too right? Need content to put together a workshop? Maybe you just want a good Ruby Challenge? Well, it’s a good thing Rails Bridge exists because it tackles all of this!
January 15th, 2010 » No Comments »
It almost seems inevitable that you have a project that has authentication (such as Authlogic) and have bolted some role based implementation on to it. Then the product owner starts request various authorization schemes for those roles. Normally, this is where you start to pull your hair out, but with CanCan many of these problems go away. It implements a simple authorizations solution to restrict what a give user is allowed to access.
Want to get started? Watch the Screencast.
January 7th, 2010 » No Comments »
Our cucumber expert, Clayton LZ is talking about his new favorite feature of Cucumber, Table Transformations. He frequently use tables to build up complex objects and has found that the regular old tables can be a little ugly, especially when your attribute names don’t make much sense on their own. He also noticed that building up associations can be a little wonky, usually requiring more steps than seem necessary. Clayton wrote up how to use cucumber’s table transformations to easily build complex objects in a way that is easy to read and understand for both clients and developers.
January 2nd, 2010 » No Comments »
Chris Young, our resident Scrum Master, in quest for excellence created a gem (NetRecorder) to help ease the pain of API testing. This is his first gem and so he would love your feedback. He also wrote a tutorial based on his experience building a gem.
The netrecorder gem works with fakeweb to record your requests and responses automatically. This way you can build your test suite against a live api and just flip a switch to use the local recorded data instead, saving time and unnecessary network calls. Visit the github page to see the source code and learn how to use netrecorder.
January 2nd, 2010 » No Comments »
“How to build a ruby Gem” tutorial by our Scrum Master Chris Young.
This weekend I built my first ruby gem. The stuff out there on the internet is pretty confusing so hopefully this post will make it exceedingly clear. The most complete source I found was the Railscast, “Making a gem”
Here are the steps I took:
1. Create the library
2. Use the echoe gem to create a rake file that will generate your gem spec
3. Use rake to create the manifest and gemspec
4. Install your gem locally
5. Create a self-signed certificate
6. Update the gemspec with the certificate information
7. Use ‘gem build’ to create the gem
8. Add your project to github
9. Use the gemcutter gem to host your gem on gemcutter
Create the library
Our library will have one method HelloWorld.say_hello that will write out ‘hello world’ when called. We’ll store the method in a module called “HelloWorld”, as suggested in the screencast.
1. > mkdir -p hello_world/lib
2. > touch hello_world/lib/hello_world.rb
2. Add this code to hello_world/lib/hello_world.rb:
module HelloWorld
def self.say_hello
puts 'hello world'
end
end
Create a rake file using echoe
There are a lot of gems out there that are made to make gem building easy. I went with what was recommended in the screencast and tried out the “echoe” gem.
1. > gem install echoe
2. > touch hello_world/Rakefile
3. Add this code to hello_world/Rakefile
require 'rubygems'
require 'rake'
require 'echoe'
Echoe.new('helloworld', '0.0.1') do |p|
p.description = "A gem that illustrates how to build a gem"
p.url = "http://github.com/tombombadil/hello_world"
p.author = "Chris Young"
p.email = "beesucker @nospam@ gmail.com"
p.ignore_pattern = ["tmp/*", "script/*"]
p.development_dependencies = []
end
Now you can type rake -T and get a bunch of tasks to help you manage your gem.
Create a manifest and gemspec
A manifest just lists which files should be included in your gem and the gemspec has everything gem needs to manage versioning. Echoe is partial to rubyforge, but this didn’t keep me from being able to use it with github.
1. > cd hello_world
2. > rake manifest
3. > rake build_gemspec
Install your gem locally
Let’s make sure the gem works. Running this command will install your gem on your computer so you can test it.
1. > rake install helloworld.gemspec
2. start irb and test
>> irb
> require 'rubygems'
> require 'hello_world'
> HelloWorld.say_hello
hello world
It works!
Create a certificate
We’ll sign the gem with a self-signed certificate.
For some reason, the install moved the gemspec to the pkg directory. Let’s create it again.
1. > rake build_gemspec
2. > gem cert –build youremail@example.com
3. Important! Move the gem-private_key.pem file to a secure location
Update the gemspec with the certificate information
Add this code to hello_world.gemspec (use your own paths, of course):
s.signing_key = '/Volumes/Secure/Certificates/gem-private_key.pem'
s.cert_chain = ['gem-public_cert.pem']
Create the gem
Now we’re getting close. This command will build the gem with your certificate.
> gem build hello_world.gemspec
Add the project to git
1. create the repository on github
2. > git init
3. > git add .
4. > git commit -m “initial commit”
5. > git remote add origin git@github.com:tombombadil/hello_world_gem.git
6. > git push origin master
Host your gem on gemcutter
1. Create a gemcutter account
2. > gem install gemcutter
3. > gem push hello_world-0.0.1.gem
December 30th, 2009 » No Comments »
One thing almost every customer hates to see is http://domain/resource/id. They will complain that they look bad. They will cite that they can’t remember the URL because of some number that doesn’t mean anything. They get nervous that investors or others will know they only have a certain number of records. They will get nervous that people will just try random numbers and get data that doesn’t make sense. Savvy clients even will complain that it will hurt their ability to rank well on search engines for their content.
There are lots of ways to work around this, but there are a lot of little gotchas. Data can change and your URL’s can break and disrupt your SEO. If there is lots of similar content there is difficulty in making sure URLs stay unique. As an application grows it can become a pain to maintain friendly URLs. Don’t forget possible name spacing issues.
A plugin by Norman on Github called FriendlyId solves all the problems at once. If you need to do Friendly URLs, permalinks or want slugs check out this plug-in.
Some nice features
- Slugged/Non-Slugged Models
- Slug Versioning
- Unique Slug Names
- Reserved Names
- Slug Caching
- Scoped Slugging
- Text Normalization
- Diacritic-sensitive Normalization
- Unicode URLs
- Custom Slug Generation
December 28th, 2009 » No Comments »
We have had several projects over the years that have needed to plot points on a google map. Rails pre-1.0 didn’t have a ton of options and we always just dealt with the javascript directly as it wasn’t all that bad. It was verbose, but not too painful. We had talked about putting together a plug-in to abstract out the grunt work, but never got around to it. It always seemed that enough time would pass between projects that the pain was never high enough.
Working a project this weekend I decided to check what options where out there and stumbled upon google_maps plugin by bhedana on GitHub. In a few minutes I had it installed and rendering maps without any of the pain in setting up maps manually. This plug-in gives you moderate control of the map. You can customize controls, center, zoom, add custom markers and plot polyline routes.
If you are doing anything with plotting points on a Google Map in Ruby on Rails you should look at this plugin-in. If you have a better plug-in for maps please let us know.