You're thinking of Balsamiq Mockups - or, if you're looking for one to mock up desktop applications (and aren't opposed to using software from the Evil Empre), Viso.
>> I am attempting to teach myself Rails and have also made a concerted effort to understand Ruby.
There's your problem number one - trying to use and excel at Rails without understanding Ruby means that even if you become a moderately proficient Rails user, you won't know what you're doing, and will be unable to process past something you have a cookbook answer for. You can drive a car without understanding how an engine works (and assume that when you press the pedal down, "magic happens" and you accelerate), but to become a great driver you have to understand what makes the car go, and how to react to and optimize your behaviors for that.
Ruby is a language that does more than Rails.
Rails is a framework that's written in Ruby.
Learn the language first; then you'll know what's actually happening with Rails and what those commands mean. Net result is that you'll be a better Rails user, and you'll be able to use Ruby for many other things and in novel ways.
Separately, learn about database normalization and design. For this, start with the mantra "down, not across" - your tables should be much longer than they are wide, even if this means multiple tables.
Sound advice. I recommend 4 books: Black's ruby for Rails and Matz's first edition in English Ruby in a Nutshell. Black's book is a great intro to exactly the techniques of method_missing, mixins, class_eval, #included, etc, you need to understand the world of rails source and plugins/gems. 1st edition Ruby in Nutshell covers ruby 1.6, is small enough that you can read the whole thing carefully several times. The 2nd edition, by Flanagan and Matz, is also a must-have reference, but not something you read straight through.
Also recommended: the ruby/metaprogramming chapters in Ediger's "Advanced Rails" (oreilly) and Rappin's "Professional Rails" (Wrox). All excellent resources
Also, for javascript/ ajax: Flanagan's JS reference, and Crockford's "JS, the Good parts"
