Tim Morgan is a web developer working in Tulsa for a non-profit community service agency. He spends most of his time dreaming up new projects and programming in Ruby.
Tim and his wife Jennie are very active in their local church and focused on equipping believers to utilize technology in meaningful ways.
It’s an internal DSL, meaning it uses plain Ruby syntax, like this:
Being just Ruby, of course, you can mix in variables, arithmetic, require external code, hit the database, or whatever.
The guys on the Tulsa.rb mailing list have provided some great feedback, and from that I’ve released the the second gem version (0.2.0). If this looks interesting to you, head over to the GitHub project and check it out. Please let me know what you think.
sudo aptitude install libavahi-compat-libdnssd-dev sudo gem install technomancy-dnssd -s http://gems.github.com
irb > require 'rubygems' > require 'dnssd'
This is a picture I took a few years back. I attempted to turn it into a lolcat, but my caption-writing abilities are pretty lacking. Any ideas for a funny caption?
moar funny pictures
I didn’t find this information anywhere, so here it is for the Google archives…
To get Prototype to run after squeezing it through ShrinkSafe, you need to put back every instance of the variable $super. ShrinkSafe replaces variable names with shortened versions, and because of some Prototype voodoo, it breaks on this one name. There are about 8 places you’ll find it, and unfortunately, it takes some manual hunting once ShrinkSafe has changed a bunch of names, but there you have it.
I suppose someone smarter than I could tweak ShrinkSafe to ignore this variable name, but for me, this works.
I build web apps. Almost every one has a screen or two somewhere that shows a listing, and at the bottom it has pagination links, e.g. next page, page 3, etc. For a recent app I’ve been working on, the interface is very search-driven, i.e. the user enters some criteria the results are displayed.
As an experiment, I left off the pagination links. In this app, there is no “next page.” Instead, if the results are not on the first page, then the user must refine their search.
If you think about it, how often do you scroll through a Google search results page and then choose to change your search query rather than click on the next page? If you’re like me, a lot. Even if you do click the next page, I would bet you don’t click much past page 2.
For users who see the Web and web apps as a necessary evil, they might be more apt to page through thousands of results rather than think about what they’re looking for and change the query. Ditching the pagination links lights up a different part of the brain I would guess (of course I have no idea considering I am only a web geek).
What do you think? Am I evil? Can it work?
By the way, I haven’t had any complaints yet. We’ll see…
We’re gearing up for the upcoming, very first Tulsa Ruby Workshop.
Of course, all you need to know is on the website, but in short, it’s a beginner’s conference all about Ruby and Rails. If you’re new to Ruby and/or Rails, this is for you (if you’re in or near enough to Tulsa, Oklahoma that is). Tell everyone you know!
I still plan on writing the final part in the Git series on this blog, but in the meantime, on a related note, we now have a page up on the OneBody wiki about Using Git. It includes some instructions for using Git on Windows and some other commands that may be helpful to noobs.
Oooo I really like the new Firefox 3 beta. It’s zippy and it looks great.
My only beef was the new fancy address bar… Being an uber web geek, I tend to recognize things by their URLs instead of page titles, so this was slowing me down to much:
So, to get things back all barebones FF2 style, I installed this and set
true. Much better.