Its Beging To Look A Lot Like Christmas

So in my new diggs at least I can look out side and its snowing!  I like snow cause then I can play with my snowblower.  I know this sounds like a dorky thing but I actually like snowblowing and even mowing the lawn from time to time.  But at least with snowblowing I can make a big mound of snow!

Office Remodel

So here I sit in a random cube across the office from where I usually work. The cube is a little different than what I am used to. My really old office used to be in a computer lab and when I transfered from UW-Stout to UW-Eau Claire we were working a room in the basement of one of the buildings. Then we got moved to a large cube were all of the students work in another building. In our new diggs they decided to build a wall now so we are scattered throughout the entire office area in random cubes. It's not bad working on my laptop because I am mobile, everyone else is crammed into one regular cube which is way to hot for me.



I have been working on a housing listing site and just started to implement the advanced search feature. I found that I had not handled all the edge cases in my tests. Have no fear its up and working and of course I have some code to show you.




Here it is:

def self.search(params = {})

      composed_cond = EZ::Where::Condition.new
      
      cond_number_of_bedrooms = EZ::Where::Condition.new :properties do 
          number_of_bedrooms == params[:search][:number_of_bedrooms]
      end
    
      cond_min_price = EZ::Where::Condition.new :properties do 
        if !params[:search][:min_price].blank?
          price >= params[:search][:min_price]
        end  
      end
    
    
      cond_max_price = EZ::Where::Condition.new :properties do 
        if !params[:search][:max_price].blank?
          price <= params[:search][:max_price]
        end  
      end
               
  composed_cond << cond_number_of_bedrooms
  composed_cond << cond_min_price
  composed_cond << cond_max_price
  

  @properties = Property.find(:all, 
                              :include =>[:amenities, :utilities],
                              :conditions => composed_cond.to_sql) 
end

-CH

Elf List Goes Live

I really don't have much to say, but Elf List is live and ready for use.  Its in the pre-beta release with features to arive daily.  So check it out, http://www.elflist.net

-CH

Godfather on Wii

So time for another one of my reviews. Last week I finally picked up a copy of Godfather for the Wii on the recommendation of a friend. I really can't say more than this game rocks. I have had a great time playing it even though it has sucked me in for many hours already (as if I didn't have a million other things to do). So if your going to get it make sure you have a few hours of free time on your hands as the missions are completable but not overly hard making the game play very enjoyable from the start. Speaking of Godfather I better get back to my game.


-CH

find or create by

So today I was working on a venture application I am trying to develop, when I cam across the need to only create a product if its not in the database. In this case I want to create the product only if the name of it is not in the database. While this is dangerous because of spelling but I am trying to keep it open for local (community) use. Slang terms may come up for one area so they need to be allowed. However I was having a difficult time looking at the pile of code for actually doing this.

 if Product.find_by_name("spotted cow")
  product = Product.find_by_name("spotted cow")
else
  product = Product.create(:name => "spotted cow")
end

So I found out about this method from someone in the rails chat on irc.freenode.net (there is always someone willing to help in that chat room.)

Product.find_or_create_by_name( params[:product][:name],
                          :category_id => params[:product][:category_id],
                          :for => 'creation' )

So now the product will be either found or created by the name of the product and if it is going to be created it adds the category_id just like a normal create.

Here is the test that proves this works.

  def test_find_or_create_by_name
  assert Product.find_or_create_by_name("spotted cow",
                                        :category_id => 1,
                                        :for => :create)
  assert Product.find_or_create_by_name("spotted cow",
                                        :category_id => 1,
                                        :for => :create)
    assert Product.find_or_create_by_name("spotted cow",
                                        :category_id => 1,
                                        :for => :create)
    assert Product.find_or_create_by_name("spotted cow",
                                        :category_id => 1,
                                        :for => :create)
 
  products = Product.find_all_by_name("spotted cow")
  assert_equal(1, products.length)
end
 

-CH

CVNUG (Chippewa Valley .Net User Group)

Last night I was able to explain the basics of Ruby on Rails to the .Net group that I belong to. It was really a great experience and was greatly received by the group. I was nervous about the response I would get initially from the group as some members of the Rails community come across as arrogant bastards.

The presentation when off with out a hitch thanks to the help of Brian Hogan (http://www.napcs.com/) who was there to answer questions and explain information more in depth as I demonstrated building a "Cookbook" application. I stripped down a version of Brian's cookbook tutorial and turned it in to a demonstration.

I want to give a shout out to CVNUG (http://cvnug.wi-ineta.org/) for letting me present to them the wonders of working with Rails. I would also like to thank Brian for helping me out with the presentation.

-CH

Connecting to ms SQL from OS X

This one got me again today as I usually do not use SQL Server for my rails apps.  I was having a hard time remembering the steps for updating my odbc connector for SQL server.  Brian Hogan over at New Auburn Personal Computer Services has a great post on how to do this so check it out here: 
http://www.napcsweb.com/blog/2007/03/08/15/#more-15

Rock N' Roll Jesus

I recently purchased Kid Rock's new album, "Rock N' Roll Jesus"  So far I have really enjoyed this album.  All I can really say is this is a great album and Kid Rock is keeping up his tradition of keeping the southern-rock-rap-country mix flowing.  Like every other Kid Rock album it's going to be a main stay in my car and on my ipod!

Installing CS3 in OS X

Today I was upgrading my Adobe products to CS3 from CS2 and ran into a problem.  There was an issue with my "payload" so the installer could not function properly.  After an hour of searching I found the CS3 Clean application from adobe.  It clears out all of your previous adobe information and allows the install of CS3 to work like a charm.  I figured someone else maybe having this same problem so here is the direct link.
http://www.adobe.com/support/contact/cs3clean.html

-CH

Ok Seriously I need to keep blogging

Well Rails Rumble is over, and we have our site up. http://www.elflist.us If you want to check it out. The weekend was great, we had a super team just ran out of time. If there is something that I learned from this contest it is that if you put your mind to something you can get it done. We plan on working on Elf List in the next couple months and I hope we can take the beta version live to the public for use around the beginning of November. For information on the development of Elf List check out http://www.icanhaztrofy.com where you will find our team blog.

In other news I am almost finished with LauraSaidYes.net sometime next week I should have the site live. Its been such a crazy last couple of weeks with the start of school and the Rumble but now that everything has calmed down back to my crazy life I can concentrate on a million things rather than a million and one. :)

One more news worthy note, in October I will be presenting Ruby on Rails to the Chippewa Valley .Net User Group (http://cvnug.wi-ineta.org). This should be an exciting presentation opening some .Net developers to my world as they open me up to theirs every month.

-CH

Busy Busy

The last few weeks I haven't been able to post because I have been super busy. Coming up next weekend is the Rails Rumble (http://www.railsrumble.com) I have joined up with 2 other developers and a really good graphic designer. You can find out more about our project at http://www.icanhaztrofy.com we have a simple blog up that will be used during the 48 hour contest.

In other news I recently got engaged this past weekend. It really has been a blessing to have Laura in my life and her continuing support for me and everything I do.

Lastly I am presenting RoR to a group of .Net developers that I meet with every month. I will try and get my slidedeck up here as soon as I finish it for others to take a look at. Since I have been trying to learn .Net I think this will be a good communication point for me. I will say this, after programing in Ruby it makes it harder to want to give it up for another language. Because everything just makes sense.

Well stay tunned for more to come, as the fall semester is about to start I will inevitably find more information to share with the world.

-CH

Back to Search Results

So today I encountered a problem that I seem to encounter in every web application I develop. Most web applications require a search and a way to view each results details. When you view the details you most of the time want to go back to your search results and not have to re-enter all of the fields of your search form.

There are a few ways to do this.

First you can use the quick and dirty way that will not work all the time.

  input value="Go" onclick="history.go(-1)" type="button"

The javascript function history.go is very useful if the client has javascript enabled. If they do not have javascript enabled this button will do absolutely nothing and frustrate your user beyond all means

The second option is to use the server to store the search params

# staff_controller.rb
 def view_applications
   if params[:type] == "requery"
     search_params = session[:search_params]
   else
     search_params = params
     session[:search_params] = params
   end
   @applications = Staff.find_applications_by_params(search_params)
 end

As you can see when the view_applications method is called the params are checked for a variable called type, if this is being called from the original search that field would be empty and the else portion kicks in causing the params to be stored in session. Below you will see the link_to example from the page that shows the details of a record. You will notice that the params have a type that is set to requery, which triggers the function to use the params from session to display the results.

 link_to "<< Back to Search Results", :action => :view_applications, :type => "requery"

There you have it, a way in rails to use the search results from before. If you have any other ways of doing this please post a comment.


Enjoy,
-CH

"Chocolate Rain" space150 intern REMIX

Guitar Hero III

So I found this post on digg........

RoR Gotchas

So today I was working on re-factoring an application that I was handed. The application had everything plugged in the controller initially so in the name of MVC I started to move things to the model file. While in the model I had a method that looked like this:

  def self.find_applications(params)
    composed_cond = Caboose::EZ::Condition.new
    
      cond_three_letter_code = Caboose::EZ::Condition.new :programs do 
          three_letter_code  === params[:find_only_program_codes]
      end
      
      cond_status = Caboose::EZ::Condition.new :study_abroad_applications do
        status === params[:find_only_statuses].
                   to_s.downcase.gsub(" ", "").gsub(",", ";").split(";")
      end
      
      cond_terms = Caboose::EZ::Condition.new :deadlines do
        term_year === params[:find_only_terms].
                      to_s.downcase.gsub(" ", "").gsub(",", ";").split(";")        
      end
    
    composed_cond << cond_three_letter_code
    composed_cond << cond_terms
    composed_cond << cond_status

    @applications = StudyAbroadApplication.find(:all, 
                    :include=>[{:deadline => :program}, :user],
                    :conditions => composed_cond.to_sql, :order => "deadlines.id")
 
 unless @applications == 0
  puts "Size: #{@applications.size}"
 else
      flash[:notice] = "There was an error retrieving your application records"
     redirect_to :action => "index"
 end
end

With me being a noob to RoR I completely forgot about my background in procedure based programing and thought nothing of the last statement. Hell if it puts out the size of the array thats what I wanted right? Well that was what I got, but what I didn't get was the @applications array that I wanted to display in my view. So there you have it just make sure that the last thing in your method is what you want to return. Learn from my mistakes and save your self some tail chasing. :)

-CH

Funny Friday

I got this in an email and it was actually funny!

-CH

The following is an actual question given on a University of Washington
chemistry mid-term.

The answer by one student was so "profound" that the professor shared it
with colleagues, via the Internet, which is, of course, why we now have
the pleasure of enjoying it as well.

Bonus Question: Is Hell exothermic (gives off heat) or endothermic
(absorbs heat)?

Most of the students wrote proofs of their beliefs using Boyle's Law
(gas cools when it expands and heats when it is compressed) or some variant.
One student, however, wrote the following:

"First, we need to know how the mass of Hell is changing in time. So we
need to know the rate at which souls are moving into Hell and the rate
at which they are leaving. I think that we can safely assume that once a
soul gets to Hell, it will not leave. Therefore, no souls are leaving.

As for how many souls are entering Hell, let's look at the different
religions that exist in the world today. Most of these religions state
that if you are not a member of their religion, you will go to Hell.
Since there is more than one of these religions and since people do not
belong to more than one religion, we can project that all souls go to
Hell. With birth and death rates as they are, we can expect the number
of souls in Hell to increase exponentially.

Now, we look at the rate of change of the volume in Hell because Boyle's
Law states that in order for the temperature and pressure in Hell to stay
the same, the volume of Hell has to expand proportionately as souls are added.

This gives two possibilities:

1. If Hell is expanding at a slower rate than the rate at which souls
enter Hell, then the temperature and pressure in Hell will increase
until all Hell breaks loose.

2. If Hell is expanding at a rate faster than the increase of souls in
Hell, then the temperature and pressure will drop until Hell freezes
over.

So which is it? If we accept the postulate given to me by Teresa during
my Freshman year that, 'It will be a cold day in Hell before I sleep with
you,' and take into account the fact that I slept with her last night,
then number two must be true, and thus I am sure that Hell is exothermic
and has already frozen over.

The corollary of this theory is that since Hell has frozen over, it
follows that it is not accepting any more souls and is therefore,
extinct...leaving only Heaven, thereby proving the existence of a divine
being which explains why, last night, Teresa kept shouting 'Oh my God.'"

THIS STUDENT RECEIVED THE ONLY "A"

First 10 Minutes With IronRuby

So yesterday after reading John Lam's blog (http://www.iunknown.com/2007/07/a-first-look-at.html) post about IronRuby I thought I would give it a try. I downloaded the source and built the project using visual studio 2005. Next I opened up Scott Guthrie's blog (http://weblogs.asp.net/scottgu/archive/2007/07/23/first-look-at-ironruby.aspx) and was looking at his example of using IronRuby with WPF. I soon had 'hello world' put out on the console and in a dialog box.

After getting 'hello world' out there I wanted to start playing. First I wanted to display the current time out to the screen so I tried out the ruby command Time.now, no dice. I got a message saying "uninitialized constant Time", I thought Time.now was automatically initialized by system.

The next thing I tried that didn't work was using instance variables. I tried to use the statement: @msg = 'Hello World' and soon my console was filled with error messages. I was however able to use this statement: msg = 'Hello World'. I don't know if they plan on letting you use instance variables in IronRuby or not.

So over all I was not greatly impressed with IronRuby but am still excited for new versions to come. I guess 'Rome wasn't built in a day' and the progress the IronRuby team has made is in the right direction. Again I only played with this for 10 minuets thus am not an expert. So go out try it and let me know what you think.

-CH

Using ez_where

While reading the documentation for the ez_where plugin in rails I got a little confused as I am a noob to rails. So once I figured out how to use this plugin I was able to develop tests and search functionality for an eight field search in under 5 hours. This was amazing to me coming from a classic asp background where this type of functionality would have taken a few days at least since some of the relationships would have required a very complex sql statement. But enough of my rambling lets get to the code.....

First off you'll want to get the ez_where plugin (http://opensvn.csie.org/ezra/rails/plugins/dev/ez_where/) inside the readme file the author provides several examples that are great and what I based my search off of. The nice part about this plugin is the way it extends active record. Rather then doing a Class.find(:all) you use Class.ez_find(:all) these will return the same results the fun part comes when you have two tables with related data that you want to search on. I'm going to use the authors examples and explain them a little more so thanks to Ezra Zygmuntowicz & Fabien Franzen for this great plugin.

First example:

articles = Article.ez_find(:all, :include => :author) do |article, author|
 article.title =~ "%Foo Title%"
 author.any do
  name == 'Ezra'
  name == 'Fab'
 end
end

So first off we have the variable that we want to store the results in, in this case were looking for articles so were going to search using the main class of Article by implementing the ez_find method we are looking for all articles and also including the author association. This is what got me confused, as I stated I come from a procedural programming background using classic asp and the way I would have done this in asp would have been to write a humongous sql statement to search across the tables. So when I was reading the example I mistook the include => author for include the author table not the association that article. This was the biggest thing that I struggled with. So drop your associations in place and then build your logic for the search. I'm going to include my search as another example of how to implement this plugin.

def self.search(params)@alum = Alum.ez_find(:all,
 :include => [:majors, :minors, :industry, :job_function])
 do |alums, majors, minors, industry, job_function|
  unless params[:search][:major].nil?
    majors.id == params[:search][:major]
  end

  unless params[:search][:minor].nil?
    minors.id == params[:search][:minor]
  end

  unless params[:search][:industry].nil?
    industry.id == params[:search][:industry]
  end

  unless params[:search][:job_function].nil?
    job_function.id == params[:search][:job_function]
  end

  unless params[:search][:employer].nil?
    alums.employer == params[:search][:employer]
  end

  unless params[:search][:city].nil?
    alums.city == params[:search][:city]
  end

  unless params[:search][:state].nil?
    alums.state == params[:search][:state]
  end
end
end

And now a test case example:

def test_search_for_employer_dimeo_family
alum = Alum.search(:search => {:employer => "DiMeo Family"})
assert_equal(3, alum.size)
assert alum.detect {|a| a.first_name == "Tony"}
assert alum.detect {|a| a.first_name == "Bobby"}
assert alum.detect {|a| a.first_name == "Christopher"}
end

And Finally the controller action:

def search_results
 @alums = Alum.search(params)
 render :action => "list"
end

There you have it, another example and my two cents.

Enjoy!
-CH

Night Time

Night time on the Milwaukee River.