Sticky Note Experiment by EepyBird from Eepybird on Vimeo.

The second IT guy replied, “Well, I was walking along yesterday minding my own business when a beautiful woman rode up on this bike. She threw the bike to the ground, took off all her clothes and said, ‘Take what you want.’

The first IT guy nodded approvingly, “Good choice, The clothes probably wouldn’t have fit.”

TamWiki Main/Great Example Of A Pop Up Meta Link.

TamWiki Main/Inactivity Timeout On A Page.

erupting volcano birthday cake.

Seriously, an *erupting* volcano cake?? I mean, dang, that’s a lot of ingenuity and work.

Wil Quits w00tstock! – w00tstock.

Oh an totally agree with commenter Mary Mactavish: that should have been Marian Call in that picture!!

Normally, Quicksilver doesn’t index bin directories. In fact, you can’t even specify /usr in a path when selecting folders to search in. (Not sure where that limitation lies, perhaps with Apple). But the following bit of info on the Quicksilver site provided the answer:

You can also run Unix commands from the Command Window, and even pass arguments to Unix commands or shell scripts. To do this you need the Terminal plug-in.

If you want to run a Unix command, you need to make sure that the commands you want access to are scanned in the Catalog. Since Unix paths (like /bin and /usr/bin) are not shown in Finder, you can’t select the path to the Source in the Catalog using the normal method (see Catalog). However, there is a trick to allow you to do it. Click the ‘+’ button at the bottom of the Catalog window to create a new source. For now, select any folder in the Open dialog. Open the information drawer for the new item by clicking the ‘i’ button. Choose “Source Options” from the drop-down menu. The panel directly below the label “Path” shows the path of your Source, but what isn’t obvious is that this path is editable. Click in the panel, type the path you require (for example, /usr/bin) and press Tab to enter the path.

Now you can access Unix commands in the Command Window:

1. Activate the Command Window, type a shortcut to find the command (for example, top to find /usr/bin/top, and press Return or Enter.
2. A new Terminal window opens running your command.

To pass arguments to a shell script or Unix command:

1. Activate the Command Window, and type a shortcut to find a shell script or Unix command (see previous steps).
2. Press Tab and choose Run [with arguments].
3. Press Tab again, then enter text mode and enter your arguments in the text box in the third field.
4. Quicksilver executes your command, and places the output in a text clipping in the first field for you to do with as you wish.

Command-line devotees will immediately be able to see the amazing potential of this feature. One word of warning though; don’t try to use Run [with arguments] on an interactive command that doesn’t exit until you tell it to. For example, if you pass arguments to top in this way, it will output the first lines to a text clipping and then hang waiting for input, so that you will have to kill the process manually. Remember – always practice safe command-line techniques.

See, the key that makes this work is something which is here-to-fore hidden in Quicksilver. It is not at *all* obvious that the Path field is editable!! (It just looks like a normal label.) Anyway, score one more for Quicksilvery Productivity Goodness.

Now I can easily use my todo list manager, the ever helpful [todo.cli](http://lifehacker.com/5155450/todotxt-cli-manages-your-tasks-from-the-command-line) written by the ever wonderful Gina Trapani.

(more after the break…)

What I shouldn’t have done is take some existing calendaring application and try to repurpose it to this application. That was a strategic error. We all look for things to reuse, but I think I will draw that line at repurposing full-blown applications from now on. There was just too much to have to reconstruct in the new way of organizing things.

Since I’ve turned it over, I’ve been looking at many technologies that would have made this go a lot better. I am really liking the look of Smarty templates for php. They do the good thing of separating code from presentation. This appliation I just finished had it all jumbled up together, like we used to do in the olden days. I vow never to do it that way again. It reminded me of the worst of ColdFusion programming, when that was the way they taught you how to do it.

Also, I’m even more firmly convinced of the MVC style of coding data-driven applications. I have been so spoiled with Rails doing that that I really missed it here in PHP. I know there are some MVC frameworks out there for PHP. I have looked into both Zend Frameworks and CakePHP. Both look promising. But I don’t necessarily need a specific prebuilt framework if I keep my code organized.

That’s also true of a templating system. While Smarty is cool and whizzy, it’s not really 100% necessary. PHP is itself a templating system. One just has to enforce the discpline to separate the code from the presentation, event with PHP.

This is accomplished by writing model handlers for all the logic of the application, basically all the CRUD stuff, while leaving the views to a separate set of scripts, one for each view, which can include other scripts for things like headers, footers, and other common elements.

Just fantastic!!

Enjoy: James Hance – Relentlessly Cheerful Art.