I've decided to get better organized in 2008, so I've been trying out task management solutions for the Mac.

What I'm looking for is a well-designed application with powerful features that cleanly integrate with the Mac operating system. I want to be able to group my varied tasks into project groups that are easy to view and are logically organized. I want tag my list items so they are easy to find and search. I want one central place where I can quickly see what I have to do today and what I have to do next. I want a central place to store everything in my head. Above all, I want to enjoy using this application. No, more ... I want an application that makes me want to use it. A tall order, perhaps, but this is what the Mac user experience is all about.

Seeking Alternatives to Apple's Mail/iCal

Unfortunately, I think Apple missed the mark with their improved Mail/iCal 'to do' management introduced with Mac OS X Leopard. Granted, it's better than what existed in Mac OS X Tiger and all other previous OS X versions (which, essentially, was nothing). But it's still not there. I tried using the 'Apple option' for a couple of weeks before I abandoned it. While the Mail/iCal solution is simple and well-integrated and may be enough for many people, it's just not working out for me. It doesn't feel right. I don't like the overly simplistic to-do list in Mail. I can't group items into bigger categories or projects. I can't tag items. I can't easily archive completed items. I don't like how it integrates with iCal. As for iCal, the to do list view is fine is you just have a few items, but it quickly becomes unwieldy and hard to read as more are added. I could go on. Suffice it to say that Apple's offerings seemed underpowered to me, so I moved on.

The good news is that there are an overwhelming number of third-party task management applications out there for the Mac user (there are also a number of plug-ins available to enhance Mail and iCal task management and a host of web-based solutions to help manage your life). That's the great thing about the Mac - the third-party developers who make applications for Mac OS X are unmatched on any platform. I truly believe that.

The bad news is that it's hard to know where to start because there are so many choices. My solution? I chose to focus on a peculiar subset of task management applications based on a system called Getting Things Done. Why? Because many geeky mac users that I respect are oddly enthusiastic about this model, and have been for quite some time.

Getting Things Done on the Mac

If you follow the mac community buzz, you may have heard of David Allen's 'Getting Things Done' framework for, well, getting things done. Over the course of the past year, it seemed I couldn't escape the chatter about this revolutionary way to manage one's daily and long-term tasks. Intrigued by the noise, I checked out an audiobook of 'Getting Things Done' from the library. Allen's ideas are indeed innovative and clever.

In essence, GTD is a systematic way to organize your thoughts that begins with dumping out the contents of your brain in an 'inbox,' then organizing those things along the lines of when you plan to get to them (e.g. today, next week, someday), in what context you will do these things (e.g. at the computer, at work, on the road), and how you group these things (into different projects). GTD is way of capturing all these little bits of 'things I want to do' and 'things I need to do' so you don't have to worry about remembering them all. Once you get all those thoughts down, GTD offers up a nifty way to organize it in a meaningful way over time.

At some point, Mac developers who adhered to the GTD model began creating clever applications and scripts to capture this process. While I haven't closely followed the evolution of this development, I noticed that it seemed to really get going in mid-2006 ... and this most certainly had something to do with organization guru Merlin Mann of 43 Folders, whose tireless efforts helped to popularize this system, particularly on the Mac platform.

Over the course of 2007, I came to associate GTD with Mac task management as more and more applications based on this model began to appear. Over time, I've watched as available mac-based GTD programs evolved from the relatively simple (see kinklessGTD) to the increasingly sophisticated (see OmniFocus, iGTD).

The 2008 showdown

As the options continue to evolve and refine, I think we're heading for a final shake out in 2008. My prediction: this will be the year for the Killer Task Management Application for the Mac, and that application is going to be based on the GTD model.

This will be the year when a small handful of really great Mac-based task managers vie for the mainstream — you may never have heard of GTD, but if these task managers are successful, you won't need to know anything at all about David Allen's system. All you'll have to do is pick your favorite and start getting organized.

Here are the applications that I will compare: iGTD, Cultured Code Things, Midnight Inbox, coalmarch Park and OmniFocus from OmniGroup.

As the dust settles over the next year, I think that one application will stand out above the rest. I've made my choice, but I'll save my opinion for the end of this series.

How I will review these apps

To keep things simple, I evaluated these power organization apps with a few questions in mind:

• Could I figure out how to use the application with minimal fuss (preferably without referring to documentation)?
• Was I still enthusiastic about using the application after a week of use? 
• How well does the app integrate into the Mac OS? 
• How well could I manage all of my tasks (work, home, play, etc.) 
• How did the program 'feel?' How 'mac-like' is it?

This last point may need a little clarification. You may have heard or read that a particular program is 'mac-like.' What this means is this: Apple software is generally renowned for simplicity, consistency, lack of clutter, and a great user interface. A 'mac-like' application, then, exemplifies these qualities. I also consider a program to be 'mac-like' if the interface is instantly familiar and obvious because it's similar to other Apple programs I use, such as the Finder or iTunes. Last but not least, a good mac application should integrate seamlessly with the rest of the Mac OS.

In the next post, I'll begin the comparison.

I recently completed a project that began with installing VMware Fusion on my Intel iMac and (unexpectedly) ended with an old Compaq Presario laptop running Linux. If you’re an adventurous type and wish to reclaim an old PC, or if you just switched to a mac and now have an old PC collecting dust, read on. In my case, a friend donated an old Compaq laptop to me (she switched to an iMac) so I could use it to test out websites on Internet Explorer. It did the job … but just barely. Windows XP just doesn’t run well on 58MB of RAM! My workflow went like this: launch Explorer, go for a snack, take a bathroom break, play with the cat, then arrive back at the laptop to either (a) load the page I wished to preview or (b) discover the machine had inexplicably froze.

Thankfully, my intel-based iMac is now handily running Windows XP and the old laptop is now obsolete. Or so I thought. On a whim, I installed Ubuntu Linux on my iMac (again, using virtual machine wizadry) just to test it out. I was amazed - it was fast, enjoyable, and very useable. One nice thing about Linux is that the OS shares the same Unix underpinnings as Mac OSX, so if you’ve been using X for a while, you’ll feel fairly comfortable in the new environment. When I started learning more about Linux, I was surprised at the dozens of ‘flavors’ of this OS and the vaster number of open source (free) software applications that run on it (all of which can run on Mac OS too, by the way). I am in awe that there are so many people out there developing this stuff out of sheer passion and dedication. How cool is that?

It was then that inspiration struck. Why not install Linux on my old Compaq paperweight? What a great way to use an old machine, and to learn more about Linux (and Unix) - skills that will make me a better Mac user too. I was not dissapointed. Linux turned my Compaq into a very usable machine that is suprisingly responsive (I won’t say it’s speedy - but it runs like lightning compared to running Windows). For the first time in my life, I actually enjoyed using a Compaq (despair over a Compaq drove me to switch to a mac in 2000!). I now have a risk-free platform on which I can learn about Linux and develop my Unix skills. It also serves, simply, as an extra PC around the house. True, I can also learn Unix commands via the Terminal on my mac (on Mac OSX or using a virtual machine to run Linux), but it gives me greater peace of mind to explore the inner workings of Unix on a totally separate machine. I can try things I would be hesitant to try on the mac. And if I really mess something up on my Compaq (and I already have), I don’t really care. I just reinstall the operating system and try again.

The Linux version I’m using — Puppy Linux — is under 100MB, so it’s quick to reload. A warning to you, though: it took me (a Unix novice with no prior Linux experience) several days of experimentation to get everything up and running on the laptop. Now that I have the process down, I can reformat the partition of the hard drive and reinstall a clean version of Linux in about 15 minutes. But you should know that you may have to get under the hood and expirement to get it working (here, I’m mainly talking about the drivers for your USB plug-ins, network connection, or printer) … but that’s what makes it so much fun. It’s a good way to learn.

To be fair, I think my experience had a lot to do with the Compaq and my inexperience and little to do with the Linux packages I tried (searching user forums, I discovered that many people aptly refer to these old Compaq laptops as ‘craptops’). If you are installing Linux on a newer laptop (newer than my Presario 1200 running at 500Mhz with 58MB RAM) or perhaps on a laptop of higher quality, you may have no trouble at all. I had plenty of trouble. And that leads us to the first rule to follow before you start any project like this: backup any data on the target machine that you wish to keep! I’ll post about how I choose a Linux version to install and the steps I took to get it running very soon. I want to end on this note: you will not get a laptop out of this that can run all your mac or pc applications. You’ll be using freeware versions of applications that do much of the same thing. So what’s it good for? You get a machine for light text work, email, and web browsing on a machine that was formerly unbearable to use. You get to experience an operating system that is increasingly used around the world because it’s free and it works well. And you get a platform on which you can learn Unix. Not bad for a PC I formerly considered trash.

I had two problems with this website over the weekend.

First, I was unable to view or send files to this site for over 48 hours. I was able to see my files via the online 'control panel' of my web host. However, I could not connect using HTTP (viewing from a web browser) or FTP (transferring files using an FTP application). I only had this problem for this specific website. My internet connection was working just fine, and I could connect to my other sites without a problem.

Second, when I viewed the files for this site via the online host 'control panel' of my web host (during the period of no-access, I could still see the files this way and only this way), I discovered that my style sheet...the one I had painstakingly and lovingly created over weeks...was zero kilobytes in size. All of my CSS information was gone. My most recent backup was a week old, and I had changed a lot during that week. Mea culpa. I probably will never know why this file was erased. It could have been an FTP transmission error, it could have been the fault of the (previous) company hosting this site. The point is it does not matter – I should have had it backed up.

I'm happy to say that my problems are solved. My connection is up and running on a brand new web host. I decided to switch to a new host as a result of this bad experience. I also have my style sheet back in order, which I had to manually re-create. Here are the lessons learned.

Lesson #1

If you're having a weird connectivity problem, check your router first (if you have one). It turns out my problem was not with my service provider, but was with my router. For some reason it was blocking my access to this specific server space on my web host only. My host (1&1) never figured this out, and I wasted a weekend talking to tech support. All they could tell me was that it must be my problem because they could not find any errors on their end (more on how they told me this later).

My solution was not as simple as resetting the router. I tried this early on. I unplugged it, then plugged it back in. I rebooted my mac. I tried to force a change to my external IP address in case that address was being blocked by 1&1. Nothing worked. Then, over two days later, I thought, 'Hey, what if I plugged my Ethernet cable directly into my primary mac?' If you are a network-saavy person, perhaps that would have been the first thing you might have tried. For me (definitely not network-saavy), it didn't occur to me to take the router entirely out of the equation. Why? I had online access for all my macs in the house through this router, and I could access all sites ... except this ONE SITE. I thought resetting it would fix any issues.

At any rate, my connection worked just fine after I connected my ethernet directly to my mac, and now I had isolated the problem to my router. The lesson here is this: if you try resetting your router and rebooting your mac and you still have a connectivity problem, it's worth a shot to take your router out of the loop to see if that helps (and thus isolate your problem). This is easy to do and it's a good first step before you call tech support. In my case, I discovered that there was a firmware update available for my router (I'm using the Linksys WRT54G). Once I updated my firmware, the problem was solved. I'm not sure if the fix was the firmware or because the firmware wiped out some corrupt settings or data. In either case, I learned that there is no way to tell if you router is up to date unless you go online and manually check. There's no auto 'check for update' feature in this wireless router model, at least.

Since we're talking about routers, I'll add that a hardware router is your best firewall defense - it effectively hides your internal addresses and devices from the outside world. In other words, all the outside world sees on my home network is my router - nothing else. It's worth getting one, in my opinion; and it's necessary if you want wi-fi in your home and/or you are sharing one connection with multiple macs). The built-in Mac OS firewall is good (don't forget to TURN IT ON - it's not on by default when you install Leopard!), but you're first and best line of defense is a hardware router. My Linksys was cheap ($50) and it's worked well for me, save for this weekend. When I'm in the market for a new wireless router, I think I'll go with an Apple product. Why? Ease of setup, ease of configuration. Period. If you have a Linksys, you know what I mean. The browser-based interface isn't very intuitive. (Note to Linksys wireless router owners, check your web-based admin panel for the link that says 'firmware update' if you find you need such an update. It's pretty straight-forward).

Lesson #2

Choose a web host carefully.

Cheapest is not always best. I know this to be true, but I admit I choose 1&1 because of the price. I have to say it worked well for me until I needed support. I called 1&1 three times this weekend. Each time, a live person answered the phone within a minute. That was impressive, but my experience went downhill from there. When I called 1&1 on Friday, I was told to wait four hours before trying to connect to viewfromthedock.com and it would probably work. When I tried to get a bit of an explanation of why this might be so, I was told that I must have been trying to connect to my files too many times in too short of a period of a time. Because of this, my IP address was temporarily blocked. I thought this was strange, since I was doing nothing out of the ordinary. Alas, twelve hours later I had the same problem. I called 1&1 again. This time I was asked to try a 'traceroute.' The tech support guy then proceeded to explain how to do this on a PC. When I said I was on a mac, he told me to forget it and that my issue would be sent to 'Level 2' tech support. I was also told I would be contacted. Lastly, he told me to wait for 24 hours until I tried to connect to my site again. Quite frustrating. I was annoyed that I still could not transfer files to my site. And I was annoyed that my use of a mac seemed to stop tech support dead in their tracks - this despite me telling him that I knew how to do traceroute and could take a screenshot for him of the result. By Sunday night, I had still not heard from anyone, so I called again. This tech support helper seemed to have no prior knowledge of me ever contacting 1&1. I don't blame him, of course. I do fault whatever tracking system they are using. All he could tell me was that the problem was likely located at my computer, not with 1&1. This was actually quite helpful, and led me to the router solution. I then switched to 1&1 to Bluehost.

Why? I had actually been pondering a move to this hosting company for a while. This gave me the push I needed. Bluehost is known for good customer service, and they are known to be mac-friendly. The biggest reason for me, though, is that they support Ruby on Rails development. 1&1 does not officially support this. Since I'm trying to learn Ruby on Rails, it made sense to jump to a host with good built-in support. Price-wise, it's not that much more expensive if you sign up for the two-year package. I'm not crazy about the two-year lock-in, but it did lower the price to the equivalent of $6.95 a month. That equates to $50 more than 1&1 for a two year time block. Not too bad. The control panel is a little confusing. My friend Brandon, a Bluehost user, pointed this out. The vote's still out for me. I can say that I love the ease with which one can backup files and databases with Bluehost. As you might imagine, I checked out this feature first! I'll post on my Bluehost experience more at a later date after I've used it for awhile. I think the web is lacking good third-party reviews of hosting services. If you've ever searched for an independent review of a web host, you know what I mean. Search engines generally return dubious 'top 10' lists — I say 'dubious' because I don't trust these sources.

Lesson #3

Transferring a WordPress installation from one host to another is surprisingly simple.

The easy part is copying all your WordPress files from the old server to the new one. There's nothing to it: you just copy them over. The more difficult part is transferring your MySQL database. Conceptually, it goes like this: you copy all of your files over. Then you export your MySQL database that holds all your WordPress posts, comments, etc. Then you import that information into a new MySQL database on your new host. Lastly, you change your WordPress configuration file so it properly points to this new database (if you use Wordpress, this is the same wp_config.php file that you modified when installing WP. I've included four screenshots here to illustrate what this looks like. Note that your host may have a set-up that looks different than mine, but the options will be the same if your host uses MySQL and phpMyAdmin. For a quick checklist, check out these Wordpress Codex instructions.

Lesson #4

Develop your site design locally on your mac, then transfer the finished theme over to your live site. Fortunately, this is easy on a mac. Why did I not do this for my site? I actually did, but once I uploaded my 'finished' theme I decided to totally change it. I was lazy, in short. I decided to just kept editing my live WordPress installation directly on the server using the Panic Transmit. The easy mac solution for running a virtual server on your mac is called MAMP. It's dead simple to set up. It includes a dashboard widget that allows you to easily start and stop your local server. What a cool tool. And it's free.

That's it for this post. Oh, and don't forget to back up your data .

I encountered yet another Dvorak bug today. For the benefit of those (ok, probably all of you) who do not know what Dvorak is, it’s an alternative keyboard layout. It’s generally considered faster and more efficient than the standard QWERTY layout.

I can certainly type quite fast and, since the Dvorak keys are not in the same place as the QWERTY keys, I learned to type without ever looking down … it wouldn’t help anyways. Never needing to look down is a plus in my book. Anyhow, it turns out that TextExpander does not support the Dvorak-Qwerty keyboard layout. Dvorak-Qwerty is a Mac OS option (available via the International/Input Menu preference pane) that allows one to type in Dvorak but still access the command shortcut keys in their designated QWERTY positions. That means that I can type in Dvorak, but still use the QWERTY Command-C/V/Q etc. The tech support guy (who responded to my query very quickly, I should add) said that the add this support to the feature request list, although he was not authorized to say if it would or would not be fixed to add this support.

So what’s the bug? When the keyboard setting is DQ (that’s short for Dvorak-Qwerty), TextExpander cannot expand text. You type in the short cut, and your shortcut is replaced by … nothing. You just get an empty string where your expanded text should go. This is frustrating. Sometimes I feel like I’m the only Dvorak user out there, though I’m sure I am not. A great feature of the Mac OS is the built in Dvorak support with QWERTY command keys. While Windows supports Dvorak as an option, it does not (and apparently will never) support the QWERTY command function.

Even though I use this alternate layout, I am a slave to Mac keyboard shortcuts (the QWERTY style shortcuts). The Mac OS has long supported this, recognizing the need amongst mac users to have command-C map to the ‘C’ character printed on the physical keyboard, even though it’s not the ‘C’ character in the Dvorak layout is located where the I character is printed. Make sense? Windows does not have this. I was using a freeware program called Hotkeyz on my Windows (work) machine to remap my keys. This solved the PC problem beautifully. But, alas, my IT staff made me take it off because of my workplace ‘no shareware or freeware policy.’ Blah.

Anyhow, most mac programs work fairly well with Dvorak-Qwerty. Except for TextExpander, and except for Adobe CS3 (actually, I don’t believe Adobe products have ever supported Dvorak-Qwerty … and except for Mac MS Office (which I don’t use - iWork handles Dvorak quite well). What this means for me is that I have to turn Qwerty on when using Photoshop, because Command-C otherwise does not work. I could re-learn the shortcuts for the remapped Dvorak keys, but I don’t want to. I like the shortcut keys mapped to what’s printed on the keyboard. Besides, I’m so conditioned to type the Command key shortcuts that it would take major reconditioning to learn the alternate locations. The bottom line for me is this: I know there aren’t many of us out there, but there are people out there that rely on Dvorak-Qwerty. The combo, exclusive to the mac, is one of those little things that makes my mac experience better than my work-a-day PC experience. I can’t imagine it would take much of a code fix to support this feature … it is built in to the OS, after all. So, Adobe and Smile on My Mac … please support the DQ keyboard layout!!

By the way, I found this nice little freeware app that fixes one annoying DQ layout problem - the inability to use command+shift in DQ

Now that I've finally settled on a layout for this new site (after toying with it for a few weeks), I am going to polish it up so I can offer the basic design as a free Wordpress template. Trust me, it needs some serious polishing. But I think it's almost there. I've got to know Wordpress pretty well during the exercise of designing 'View from the Dock'. I'll share some of what I learned in Wordpress in future posts. Next, I'm going to migrate this design to RapidWeaver. The RW site will be a little different, because I want to offer it up with user-controlled colors and such.

I've been using Wordpress and RapidWeaver for about the same amount of time. In future posts, I'm going to talk about the strengths and weaknesses of each. In the end, I hope to provide a good overview of the capabilities of each platform. I can say that, while I really love the countless ways I can modify and tweak a Wordpress theme (this site began life as the Kubrick Default theme that we all start out with when installing WP), I miss the simplicity and style that RapidWeaver offers. However, RapidWeaver isn't quite as extensible or as easy to bend to your will. Which is the better choice? The answer, of course, depends on your needs. Certainly these two platforms are not the same animal, but they do offer roughly the same capabilities — I know that some might argue that WP is a blogging platform while RW is a web design tool that includes the ability to add blogs ... While this is true, I've found that both packages can, more or less, do the same thing. More to come on this. I've spent pretty much this entire weekend on this site design, so I'm going to call it a night and get away from the mac for a while.