This inaugural #nerdlearn will focus on THE FUTURE OF RAILS (yes, in all caps), but going forward we’ll choose topics that influence the entire sphere of being an excellent developer.

RSVP here: http://guestli.st/55083

MEET THE PANELISTS:

Pete Forde, Unspace:

In 2004 Pete founded Unspace Interactive. Not long after, he transition from proprietary Microsoft development to becoming one of the first adopters of Ruby on Rails. He was the curator of the RubyFringe and FutureRuby conferences, and hosts the popular monthly “Rails Pub Nite” developer event — of which there has been over 50 to date.

An avid traveler and occasional touring rock drummer, Pete is passionate about music and film photography. He recently co-founded BuzzData, a data publishing and collaboration hub.

Pete also likes to explore places you’re not supposed to go:

—–

TWG’s own, Scott Tadman (brought to you by the number 4):

Since 1990, before most of us had even heard of the web, Scott’s been a database manager, network engineer, system administrator, software developer, creative director, writer, and electrician. So you can bet he’s involved at every stage of the projects TWG produces.

Scott is TWG’s Senior Architect; co-founder of PostageApp.com; and 4-time Science Fair Winner when he was a kid (unfortunately no photo available).

He is also the #4 Answerer on Stack Overflow for ruby-on-rails so be sure to ask him lots of questions at #nerdlearn – http://stackoverflow.com/tags/ruby-on-rails/topusers

You can also find Scott at: twitter.com/tadmanter & github.com/tadman

—–

Kevin Faustino, Nulayer:

Kevin is a passionate programmer and craftsmanship advocate who works at Nulayer as a Senior Software Developer. He has been professionally developing for 6 years, with the last 3 years focused on Ruby and Ruby on Rails.

When not working, he is organizing the Toronto Ruby Brigade and blogging at adventuresincoding.com.

You can also find Kevin at: twitter.com/kfaustino & github.com/kfaustino

We also suspect that Kevin likes Lost:

Meet Kevin, Scott and Pete on May 19th, 6:30pm at TWG HQ: http://guestli.st/55083

Other upcoming Dev events you might be interested in:

May 20th: Ruby Job Fair at Unspace, featuring Rubyists, Employers, and Spiked Tea – http://rubyjobfair.ca

June 2nd: Technologic at UnSpace, featuring Giles Bowkett – http://technologicto.com

Plug this rake task into /lib/tasks/rcov.rake

And finally run it:

It’s so easy you have no excuse not to have it.

Actually, I don’t want to know. It’s probably awful. I might have a pretty good solution for you. Let’s take a look at a very simple nav. These examples all use HAML:

Right, that’s great. But how do I insert logic as to what link gets marked as active? To begin, let’s quickly install this random gem:

And then change our nav a bit:

And that’s pretty much it.

So, for example, if you navigate to /kittens/1-my-fluffy-kitten navigation link for ‘Kittens’ will have ‘active’ class attached to it. It’s almost like magic.

You probably noticed that ‘Home’ is highlighted as well. It happened because whatever URL you are currently on is a child of the home_path. I guess we want to mark it as active only if we find ourselves on the home page and not anywhere else. We can fix this:

Hey, wanna render a sub nav when you find yourself browsing /puppies or any page under that URL? It’s just sooo easy:

And that’s the skinny of what active_link_to is for.

For more documentation on more functionality checkout project on GitHub: http://github.com/theworkinggroup/active_link_to