<?xml version="1.0" encoding="UTF-8"?>
<posts type="array">
  <post>
    <body>Today I needed to add pagination to our Danish beta application for handling your accounting called [Hurtigmoms](http://hurtigmoms.dk). Since we're developing in Rails it was a logically choice to use &quot;will_paginate&quot; to support pagination.

Our prototype layout is using a Facebook header and so I wanted my pagination control to mimick their style. If you need something similar you might want to take a look at my CSS styles which are using the default class names used by will_paginate.


		.pagination {
			font-size: 11px;
			float: right;
			margin: 0;
			padding: 3px 0 4px;
		}
			.pagination a,
			.pagination span {
				padding: 3px 3px 2px;
			}
			.pagination .disabled {
				background:none repeat scroll 0 0 transparent;
				border:medium none;
				color:#999999;
				cursor:default;
			}
			.pagination a {
				color:#3B5998;
				cursor:pointer;
				text-decoration:none;
			}
			.pagination a:hover {
				background-color:#3B5998;
				border-bottom:1px solid #3B5998;
				border-color:#D8DFEA #D8DFEA #3B5998;
				color:#FFFFFF;
				text-decoration:none;
			}
			.pagination .current {}
				.pagination .current {
					border-bottom:2px solid #3B5998;
					border-color:#3B5998;
					color:#3B5998;
					font-weight:bold;
					padding-left:2px;
					padding-right:2px;
				}
				.pagination .current a:hover {
					background-color:#3B5998;
					color:#FFFFFF;
				}
	
			.pagination .prev_page {
	
			}
			.pagination .next_page {
		
			}

Just copy and paste it into your application css file and you're done.

This is how it looks:

&lt;img src=&quot;http://theill.com/stuff/screenshots/facebook-pagination-css-style-20100127-114918.png&quot; /&gt;
</body>
    <created-at type="datetime">2010-01-27T00:00:00Z</created-at>
    <id type="integer">6</id>
    <slug>facebook-css-for-will-paginate-gem</slug>
    <title>Facebook CSS for will_paginate gem</title>
    <updated-at type="datetime">2010-01-27T10:50:44Z</updated-at>
  </post>
  <post>
    <body>I have bought a touchatag RFID reader and a couple of touchatag RFID tags and was wondering how I could use these to track my daily intake in lifestyleapps.

&lt;img alt=&quot;Underneath&quot; src=&quot;/images/underneath.jpg&quot; style=&quot;float: right&quot; /&gt; 

I noticed a Twitter application already has been developed which post a message from a configured account. Since lifestyleapps already integrate with Twitter it was a simple matter of associating a direct message and prefixing it with &#8220;h&#8221; or &#8220;having&#8221; to let lifestyleapps know you are reporting an intake.

Many cups of coffee are consumed on a daily basis by me and I thought I would make tracking this easier for myself by configuring a touchatag with a Twitter message of &#8220;d reporting having Coffee, instant, prepared with water&#8221;. This means &#8220;d&#8221; for direct message, &#8220;reporting&#8221; for the Twitter user receiving our message (used by lifestyleapps), &#8220;having&#8221; to tell lifestyleapps you are reporting an intake and &#8220;Coffee, instant, prepared with water&#8221; to make lifestyleapps look up this specific intake and figuring out its nutrition values.

&lt;img alt=&quot;Ontouchatag&quot; src=&quot;/images/ontouchatag.jpg&quot; style=&quot;float: left; margin-right: 10px;&quot; /&gt; &lt;img alt=&quot;Website&quot; src=&quot;/images/website.jpg&quot; style=&quot;float: left; margin-right: 10px&quot; /&gt; 

Now whenever I drink a cup of coffee I just need to place my coffee mug on a touchatag reader and it will automatically trigger a Twitter message which will be read by lifestyleapps. And this can by done using no code at all.

This is a pretty sweet thing and I&#8217;m planning to put a couple of tags on my breakfast food items since I almost eat the same breakfast every morning. It would be nice to be able to just put a bottle of milk, a bag of bread and a jar of jam on my reader to track my breakfast within lifestyleapps.

If you don&#8217;t know about lifestyleapps you are welcome to sign up for a free account at [http://lifestyleapps.com](http://lifestyleapps.com). Read more about touchatag at [http://www.touchatag.com](http://www.touchatag.com).</body>
    <created-at type="datetime">2009-04-03T00:00:00Z</created-at>
    <id type="integer">5</id>
    <slug>tracking-coffee-intake-with-touchatag-and-lifestyleapps</slug>
    <title>Tracking coffee intake with touchatag and Lifestyleapps</title>
    <updated-at type="datetime">2010-01-27T09:51:01Z</updated-at>
  </post>
  <post>
    <body>Today, we have taken over development of ConquerCam. ConquerCam is a low-priced (less than twenty bucks) webcam software package for Windows having quite a few cool features such as built-in web server, motion detection and scheduled uploads via FTP.

&lt;img alt=&quot;Main ConquerCam application window&quot; src=&quot;/images/shtmainwindow.gif&quot; /&gt;

ConquerCam was initially developed by me back in 1998 and at that time it was surely one of the very best in its category. Lacking time I stopped active development in 2003 but didn&#8217;t really give up on it since I continued to get feedback. ConquerCam is still being downloaded by 100+ users a day so I know it is still popular though it is now behind some of its competitors.

That will change now! ConquerCam will be developed professionally starting April 1th and that will generate some faster release-cycles in the future. This is great news for ConquerCam and its user-base out there.

For more information about ConquerCam visit its web site at [http://conquercam.com](http://conquercam.com)</body>
    <created-at type="datetime">2009-03-19T00:00:00Z</created-at>
    <id type="integer">4</id>
    <slug>today-we-have-taken-over-development-of-conquercam</slug>
    <title>Today, we have taken over development of ConquerCam</title>
    <updated-at type="datetime">2010-01-27T09:51:01Z</updated-at>
  </post>
  <post>
    <body>Our [lifestyleapps][] project (still in very early beta) was running Rails 2.2.2 with the Rails Engines plugin ten minutes ago. Today, Rails 2.3.2 was released so I decided to try if I could easily upgrade it and avoid using the Rails Engines plugin anymore. It was beautiful simple and took me less than ten minutes.
    
[lifestyleapps]: http://lifestyleapps.com

First, I had to update our Apache Passenger module with a version supporting Rails 2.3 so I did a

    $ gem update passenger

and then run the install to build our apache module

    $ passenger-install-apache2-module

In my config/environment.rb I changed

    RAILS_GEM_VERSION = '2.2.2' unless defined? RAILS_GEM_VERSION

to

    RAILS_GEM_VERSION = '2.3.2' unless defined? RAILS_GEM_VERSION

and asked Rails to update my various script files by issuing

    $ rake rails:update

Finally I remembered the application.rb should be named application_controller.rb now so I issued an explicit task for this as well

    $ rake rails:update:application_controller

In the Rails Engines plugin you need to have the &#8220;routes.rb&#8221; file in the root of your plugin but with Rails 2.3.2 you should have it in the &#8216;config&#8217; folder under your plugin and its content should be wrapped in &#8220;ActionController::Routing::Routes.draw do |map|&#8221; as the root routes.rb. So I changed this from

    /vendor/plugins/life_intake/routes.rb

to

    /vendor/plugins/life_intake/config/routes.rb

The contents of this routes.rb was changed from

    map.resources :foods

to

    ActionController::Routing::Routes.draw do |map|
      map.resources :foods
    end

Finally I had to update the root &#8220;routes.rb&#8221; to avoid using the &#8220;from_plugin&#8221; call e.g. I simply removed lines such as

    map.from_plugin :life_intake

Now I don&#8217;t need the Rails Engines plugin anymore so I removed it with

    $ ./script/plugin remove engines

That&#8217;s it .. I was now able to run my tests and start up my project and have it run on Rails 2.3.2.

Enjoy!</body>
    <created-at type="datetime">2009-03-16T00:00:00Z</created-at>
    <id type="integer">3</id>
    <slug>upgrading-rails-engines-project-to-rails-2-3-2</slug>
    <title>Upgrading Rails Engines Project to Rails 2.3.2</title>
    <updated-at type="datetime">2010-01-27T09:51:01Z</updated-at>
  </post>
  <post>
    <body>We are developing Rails applications on Mac OSX and a command which isn&#8217;t used enough in my opinion is &#8220;pbcopy&#8221;. This command will allow you to grab the standard input from a terminal and put it on the clipboard.

I find myself using commands such as &#8220;pwd | pbcopy&#8221; all the time. This will grab my current working directory and make it available in my clipboard allowing me to easily paste it into another terminal or application. This avoids the need for you to grab your mouse to paste a simple line.

Just a quick tip for developers switching between terminal and desktop applications on a regular basis.</body>
    <created-at type="datetime">2009-03-12T00:00:00Z</created-at>
    <id type="integer">2</id>
    <slug>extend-your-shell-toolbox-with-pbcopy</slug>
    <title>Extend your shell toolbox with pbcopy</title>
    <updated-at type="datetime">2010-01-27T09:51:01Z</updated-at>
  </post>
  <post>
    <body>You&#8217;ve found our blog &#8220;Command through simplicity&#8221;. This blog will post behind-the-scenes information about applications released by [Commanigy][].
    
We have moved our beta applications [Lifestyleapps][] and [Observer][] to new and faster servers. These applications are almost updated daily so keep an eye on this blog, our [Twitter account][twitter] or our [Friendfeed room][friendfeed].

[commanigy]: http://commanigy.com
[lifestyleapps]: http://lifestyleapps.com
[observer]: http://observerq.com
[twitter]: http://twitter.com/commanigy
[friendfeed]: http://friendfeed.com/commanigy</body>
    <created-at type="datetime">2009-03-08T00:00:00Z</created-at>
    <id type="integer">1</id>
    <slug>our-blog-is-live</slug>
    <title>Our blog is live</title>
    <updated-at type="datetime">2010-01-27T09:51:01Z</updated-at>
  </post>
</posts>
