In my last article, I made mention that you should at least include a basic mobile stylesheet for your site. The easiest way to accomplish this is to piggy-back your print style. What? You say you don’t have a print stylesheet? Bad developer. In this article, we’re going to run through the very basics of a print style, and move on to basic mobile in the next.
Over the past year at Notre Dame, we’ve really started to embrace and experiment with offering a mobile experience for a number of the projects that have made their way through our offices. There are a couple of obstacles that make this process difficult.
- A separate “m.” address is not an option
- Creating and testing mobile styles is rarely part of the project budget
This has led to some commonly used shortcuts that have allowed us to, at the very least, provide a serviceable mobile experience with very little effort.
One of our production Rails apps is running on Ruby 1.9. The problem this introduces is that our dev environments must be able to run multiple versions of Ruby side-by-side. There’s nothing unique about this, it comes with the Ruby/Rails territory. After upgrading to Snow Leopard, I decided to give Ruby Version Manager a try. The install of RVM and the subsequent Ruby installs were a breeze. However, when it came time to install the MySQL gem, I ran into a brick wall. No matter what I tried, I kept getting install errors.
Let’s say you’re serializing a ruby object for later use in a field of another model.
class Foo < ActiveRecord::Base serialize :bar end
If you’ve used Rails 2.1 at all, you will no doubt be aware due to the incessant notifications, that Rails 2.2 will be dropping its MySQL driver. Therefore, in order to use Rails 2.2, you will need to install an updated version of MySQL. I found one good resource that got me most of the way there, however, after the upgrade, most of my tests, in all of my apps were failing.
Let’s talk for a moment about style. More specifically, CSS style. Every web developer I’ve met has had a personal way they write their style declarations. And typically if you have five developers in the room, you’ll have five distinct styles. It’s probably safe to say these styles are developed early on in a developers career and tend to change ever so slightly as time goes on to suit individual preference. I know that I had basically the same style for the first seven years of my CSS using web career (I’m talking post table/font= days).
I wanted to get in on the iPhone action as soon as v1 came around, but due to budget constraints, that just wasn’t possible. Shortly after the release of the 3G model, a number of stars aligned and I picked up an 8gig 3G. This has turned out to be one my best tech purchases ever. There were several times this summer where the Google map feature helpfully guided myself and others to an elusive destination, and caught Kodak moments when I didn’t have my camera with me.
Back when I first started with Rails, I noticed there were a lot of times I just needed to know the Ruby/Rails equivalent of some PHP function. It started me thinking that it would be great to have a resource similar to PHP.net where you could just append the function name to the end of a url, and get some relevant Ruby/Rails examples. Well, somebody beat me to it.
I had the best of intentions. I wanted to give you words. Words to make you laugh. Words to make you cry. Words to excite, enlighten and inspire.
So what happened?