PanaGeek

I know, long time, no post.  Contact me offline to receive a refund for your subscription to this blog.

Just a quick post to talk about a cool website called Hulu.  This is a great and legal place to see video clips, full length TV shows, and even movies.  As I said, it is a legal service (there are others out there that look a little questionable) that is supported by a few short ads in each show.

One of the things I really like about it is that the site can remember where you were in watching a show, so you don’t have to watch a show from beginning to end in one sitting.

There are only two (very small) negatives: first, the selection is currently limited – not every episode of every show is available.  Second, you can’t save what your watching, so downloading a show to watch on a plane isn’t possible.

Overall, the plusses are strong and the negatives aren’t show stoppers.  Hulu is a great way to catch up on some great shows!

Shoes, as I’ve mentioned before, is a great little GUI for ruby applications. I ran across an article last week about Google Translate and a command line interface for Linux called tw, and thought that I might be able to build something in Shoes with it. Well, I couldn’t get tw to build on OS X, but I found a ruby gem called rtranslate that works great! So, over an hour or so, I threw a quick little translator together in Shoes. It’s over at the ShoeBox. Please let me know if you try it (and like it – I don’t like criticism).

I used to be a die-hard Camino fan (starting back in the Chimera days). A few weeks ago I started using Safari. The reason is that I can copy snippets with text and images from Safari into Mori, where Camino only lets copies the text. Anyway, I decided to do an empirical test, to see how the browsers use resources. I’ve done this in the past, and Camino usually won. Now, Safari is getting the better of Camino in both CPU and RAM usage. I opened six identical web sites on both browsers and here’s what I’m getting:

Browser | CPU | RAM Camino 46.6% 72.4M Safari 25.6% 49.6M

and Camino is not responding, according to Activity Monitor. It makes me a little sad, considering that I’ve been a Camino fan for so long. Oh well, the browser of the day is Safari.

Well, I committed my Documents folder to a Subversion repository on my network storage device and dutifully checked it out onto my laptop again yesterday. Today, when I went to sync Quicken, I found that I couldn’t open the data file. This web site thankfully had the answer. Quicken uses resource forks on OS X (resource forks were a big thing pre-OS X, I didn’t think anything still used them). After running through the commands as shown on the site, I was more-or-less happily broke to the last penny again. While this wasn’t meant to be a subversion bashing, it reinforces my desire to move to a DVCS – specifically Bazaar. More on that in the future.

Test post from my Nokia 770.

Shoes is a lightweight GUI framework for Ruby, created by _why. I don’t always understand his unique sense of humor, but he has created a great little package for creating simple GUI’s.

To use it, download the package and install it where ever you want. I put it in “Applications” on OSX, and in my user directory on Windows. Then just double click the icon; this will bring up a menu allowing you to select a file to run. Shoes comes with a healthy collection of samples that you can work through to learn the Shoes syntax.

The basic syntax is pure Ruby goodness – clean and simple. Here is a simple example of a button and a text field:

Shoes.app :height => 200, :width => 200 do
stack :margin => 10 do
button “Button One” do
@mytextfield.replace “Button One pressed!”
end
@mytextfield = para “This is a test.”
end
end

Which looks like this when it runs:

Try it out. I think it’s a great tool for creating simple GUI’s!

I know, long time, no post – and now just a short post. Well, things have been pretty busy here, and I have a lot of things to post about, so here goes.

A couple of months ago, a friend showed me his Nokia 770. And I thought, “I don’t need anything like that.” So, it was only a matter of days before I found one on eBay. The bottom line is that it is like a ‘92 Jeep Cherokee – sure there are newer, fancier models out there, but this one got it right.

In a nutshell, it’s a handheld PC that runs Linux. It’s not a PDA by design, but it has a lot of really neat apps that make it a great all around geek must-have. I can sync my Google calendars, read spreadsheets and documents, download Google maps, and even make phone calls with Gizmo!

These listed for several hundred dollars when they first came out, but since they have been superseded by the Nokia 800 and 810, they are a real bargain on eBay.

I saw this bundle for TextMate a couple of days ago, and it’s great! I’ve been taken with the concept of wikis ever since I listened to Andy Hunt talk about them at a NoVaLUG meeting several years ago. For those that might not know, wikis are kind of self-shaping databases, generally using words in CamelCase as links to other wiki pages.

The main drawback to most wikis (from my point of view) is that most are web based. I’m a little leery about posting too much info online (believe it or not). The best solutions that I had found before now were thew emacs wiki-mode and TiddlyWiki. They work, after a fashion, but never completely scratched my itch. But now I can have the best of both worlds – a plain text wiki, and TextMate. This may be the start of something great!

(if this were a review I’d go into more detail, but it’s not, and I’m tired, so that’s it for now)

I’ve been working on the GTD bundle, and gave it a couple of new features. The first is syntax coloring – now the different states of tasks have different colors. Not a huge change, but I like it. Second, I added a new state – priority (!). It works via a tab command, like all of the other state changes. Again, not spectacular, but nice to have. I have some other things in the works, and another GTD bundle user has provided some really nice templates for viewing and printing lists. If you are interested in the GTD bundle, stay tuned!

I have written about TextMate before. In a nutshell, I find that TextMate is a great text editor for OS X (I think it is the best, but I don’t want to start a flame war). One of the things that makes it such a great application is its extensibility. Even a user with limited coding skills (like me) can easily add new features or modify how existing features work. I created a GTD bundle for it, using other bundles for code and coding examples. Perhaps the most difficult part of creating a new bundle is sorting through the TextMate blog, wiki and mailing list for help. The answers are there; Allan Odgaard (the creator) and the mailing list regulars are extremely helpful. The only problem was that you needed to search for answers. I say this in the past tense because a new book brings all of the answers together.

TextMate: Power Editing for the Mac, by James Edward Gray II, is more than a collection of the tips and tricks that you can find on the various web sites; it is a users guide and a programming guide too. The users guide section is great – James really emphasizes the importance of key commands. This is good for those coming to TextMate from the emacs world and miss the arcane “control-c control-x” functionality. It is also good for new users who like TextMate in general but may be overwhelmed by the plethora of key commands. The book them goes into a discussion of the basic bundles that everyone should know.

The second half of the book is the programming guide. This starts with the basics of snippets and tab commands and goes on to walk through creating language files – the place where the grammar of a language is described. The importance of language files is that they tell TextMate how to highlight text in a given language. One nice feature is that James builds a non-trivial example of a bundle as he goes through this section. The example bundle is like a picture – it’s worth a thousand words of explanation!

The bottom line is that this is a great book. I thought I pretty much knew everything I needed to know to develop bundles for TextMate, but I was wrong. After going through the book, I realize that I had only scratched the surface of the features of TextMate. I now have many ideas for new and improved features for my GTD bundle!