“Rubymine can’t call git ls-files in gemspec”
This should have been fixed a while ago in the developer image.
“Anyone built ruby 1.9 from source? I’m not sure what options to configure it with.”
Check to see what options RVM is using when it builds 1.9.
Two-Subject Monte: Consider the following RSpec code:
describe "fruit" do
let(:subject) { "banana" }
context "rounder" do
subject { "orange" }
it { should == "orange" }
end
end
Does it pass? The answer is no. The implicit subject evaluates to “banana” from the let(:subject) { } at the top, and is not overridden by the subject { } later on. This can be considered a bug in RSpec, but it’s also pretty weird to assign subject with let(). This was a mistake which RSpec should probably warn you about.
CSV fixtures are gone in Rails Edge, and will presumably be gone in 3.1. No announcement of this is available at press time, but the code for it is gone. Incidentally, CSV fixtures also don’t preserve whitespace at the beginning or end of each of your values. If you’re using them, this would be a great time to move to YAML fixtures.
(Title: Standup 7/18/2011: I Bless the Rains Down in Africa)
“I want a super-lightweight rack-based CMS/blogging setup. Any thoughts?”
Try out Toto a light-weight git-powered blog engine.
Your app now has mobile-friendly views. Do they have any Webkit-specific functionality that you want to test in-browser? Or rather, why are you testing your mobile views in desktop Firefox? Is it because Capybara/Selenium support for Webkit browsers was sketchy? Worry no more. Chrome 12, Capybara 1.0, and Selenium 2 are your new best friends.
So install Chrome, make sure your Gemfile has Capybara set to >= 1.0, bundle install and let’s get configuring.
You have to tell Capybara that you want to use Selenium/Webdriver and Chrome. Put this in your spec_helper.rb file
Capybara.register_driver :selenium_chrome do |app| Capybara::Selenium::Driver.new(app, :browser => :chrome) end
chromedriverWhile there’s been limited Selenium support in Chrome for a while, with release 12 there is an entirely new and complete automation interface to Chrome. To use it you need a platform-specifc chromedriver binary in order to connect Webdriver and Chrome. Download it, make sure it’s executable, and put it on your path.
Chrome likes to update, so stay on the general release (if you can) to reduce update frequency. You can even take steps to prevent Chrome from updating, but I’ll leave that as an exercise for the reader.
That should be enough to get your Capybara specs to start using Chrome. You’ll want to play with your setup and maybe only run some specs with this driver.
Webdriver does not appear to support Safari. This may matter to you if you’re using this setup to approximate Mobile Safari. But for the types of tests you’re likely writing for Selenium it should be good enough. After all, every mobile Webkit build is slightly different.
While complete (in terms of browser features) and far faster than previous Selenium-Chrome pairings, it’s still slow-ish – for example, typing isn’t nearly as fast as Firefox. So you might not want to make this your default stack for your entire Rails app.
You might make it your only stack if you’re testing a Webkit & JavaScript only framework, say an HP webOS application using Enyo.
But that’s another post.
Does anyone know of a library or canonical source for three-digit airport codes?
Edit: Pivots came up with http://www.airportcodes.org/ and http://www.halfgaar.net/localized-world-airport-codes
Ruby 1.9.2.p290 was released last night. Looks like it fixed some YML-related problems.
A pair was having problems with Sass on their production environment on Heroku this last week. They’ve discovered a bug and created a sample project/bug report for it, which will be linked here when it’s posted.
Sure, you can launch your Android app in IntelliJ’s debugger, but that’s slow. IntelliJ allows you to dynamically attach the debugger to a running device using the “Attach debugger to Android process” button. That’s fast!
If you’re working in an environment with a noisy background, Skype’s über-friendly automatic gain control can drive you crazy (open up sound preferences and watch your input levels change like magic)
Here’s a fix (that still works in Skype 5):
http://jon.smajda.com/2011/04/19/disable-automatic-gain-control-in-skype
tl;dr?
Open up ~/Library/Application Support/Skype/shared.xml in a text editor, find the <VoiceEng> section (w-a-a-a-a-y at the bottom), and add <AGC>0</AGC>. Like so:
<VoiceENG>
<AGC>0</AGC>
... [One or more <MicVolume>'s. Leave them alone.]
</VoiceEng>
P.S. If you did read the article, <EC> is the Echo cancellation mode. I like to leave it on, but YMMV, especially if you’re wearing headphones and have no need for it.
Pivotal Labs NYC is happy to host a day of the Rails 3.1 hackfest from 10am-8pm on Saturday July 23rd.
Our office is located in Union Square: 841 Broadway, 8th floor.
Ample food and drink will be provided, just bring your computers and yourselves. I’ll be hacking all day on documentation patches.
Read more about the hackfest on the Rails Blog
“Firefox still doesn’t support text-overflow: ellipsis. What to do?”
Looks like Mozilla has been slow on picking up this text overflow property. It’s due to be supported in Firefox 7. In the meantime, JT suggests the use of the AutoEllipsis jQuery plugin
“@pivotalnyc”
For those that aren’t aware, the Pivotal New York office occasionally tweets as @pivotalnyc.
“caniuse.com”
Ian passes along a good resource to check out the availability of CSS properties on various browers, which can be found at http://caniuse.com.
Jasmine 1.1.0.rc3 has been released!
Check it out on github.
One pair was having problems getting custom Devise views for the sessions controller to appear. StackOverflow suggests that when using a custom extension of a Devise controller, new views must be placed into app/views/controller_name/ as appropriate.