This release fixes a handful of bugs, updates the interface slightly, includes support for AppleScript, and introduces the new Calendar view.

I’m still working on the documentation, so please take a look at the initial introduction to get started. I will also post a follow-up blog post that describes the new features in more detail.

If you have any ideas, suggestions, or bugs to report, please post them in the comments below.

Thanks!

Work on the assistive technologies (Task Views & Shion + Pennyworth) has been steady and I’m hoping to release some updates to Pennyworth client applications soon.

Not too much has changed with Pennyworth proper. After some consideration and given some future projects coming down the pipeline, I’ve begun planning out Pennyworth 2.

In short, PW2 will be a re-implementation of the Pennyworth architecture designed to work on multiple platforms and devices. The plan is to implement the core of the system in cross-platform C and use native languages and tools to wrap the core in a user interface that “fits” on the platform.

I’m taking this approach (as opposed to the older approach of rewriting the system by scratch for each platform) for a couple of reasons:

1. As a solo developer, I don’t have the time or energy to manage and support full ports to each platform in each respective language. Assuming that the average size of a Pennyworth port is N lines of code, and I port it to P platforms, I need to manage N * P lines of code. This is too much code to maintain and continuously debug.

2. While some code will necessarily be unique to each port, I believe that the bulk will be portable across platforms. If 25% of the Pennyworth code is generic in this sense, the amount of code to manage becomes 0.25N + 0.75P By keeping N somewhat constant and only growing the P, the software development side of things will scale better as I add support for each platform.

The current Pennyworth implementation has approximately 10000 lines of code. Of that code, about a third (0.33) is a good candidate for the platform-neutral core. Using the assumption that other implementations will have a similar amount of code in the same proportion, the project will scale in the following way:

1 port: 10000 LOC (both old approach & new approach)

2 ports: 20000 LOC (old) vs. 16700 LOC (new)

3 ports: 30000 LOC (old) vs. 23400 LOC (new)

4 ports: 40000 LOC (old) vs. 30100 LOC (new)
(The 4th port is almost free when compared to the older system.)

5 ports: 50000 LOC (old) vs. 36800 LOC (new)

Since I have more 3 ports that I would like to implement, this change makes sense.

3. I also believe that sharing the core code will allow me to implement a more robust and efficient system across platforms. By including resource-constrained devices (such as mobile phones) to the mix, it easier to notice inefficient and unstable code.

To be honest, this effort is in its early phases and I probably won’t have anything ready for testing until later this year. However, I do think that the short-term pain will result in long term gain as I develop a framework and approach for getting Pennyworth on more devices.

Thank you for your patience.

This is the first public release that includes support for the list, cloud, and histogram views. This version of the software is also compatible with iCal, OmniFocus, Things, Basecamp, and FogBugz.

I’m still working on the documentation, so please take a look at the initial introduction to get started.

If you have any ideas, suggestions, or bugs to report, please post them in the comments below.

Thanks!

The application is called “Task Views” and it attempts to solve the problem that modern workers face when managing their tasks and todos. There are a variety of great task management applications (desktop and web alike), but the realities of the modern workplace is that we find ourselves using a variety of solutions to attack the same problem: getting things done.

In my own personal life, I use FogBugz to track software tasks, a Basecamp site to collaborate with clients, and OmniFocus to handle everything else. The problem with splitting things up in this way is that it leads to tunnel vision. When I’m working in FogBugz, I’ll plow through a variety of software issues, while forgetting to pick up groceries on the way home. When I’m in OmniFocus, I find it easy to overlook urgent tasks for my Basecamp client. I get things done, but often find my triumph short-lived as I discover that I didn’t do everything I needed to do, simply because I forgot to look at my other task applications.

Task Views solves this problem by offering a set of unified views that transcend individual systems. The program accomplishes this using conduits. A conduit is a bit of code that pulls tasks from another system, normalizes the fields, and imports it into the current system.

Task Views currently talks to OmniFocus, Things, iCal, Basecamp, Entourage, and FogBugz. (Support for other systems is in the works.) The conduits fetch task information and dump it into a local database.

The program provides a very basic list view that allows users to quickly identify and view individual tasks. However, as the image above shows, this list can grow really long, really quickly. To alleviate this problem, Task Views provides a filtering function that allows users to select subsets of the database:

Users can construct elaborate filters by using simple Boolean rule-based logic.

The list view shows the main weakness of the current crop of task management applications. Almost without exception, all of them use a list metaphor to display what needs doing. Even on the largest monitors, tasks scroll off the visible screen rather quickly.

A cloud view provides a simple way of displaying more content in a more space-effective manner. Where as the list above shows less than a hundred items, the cloud view shows over seven hundred. However, the items are so small, that this view is clearly suboptimal.

Task Views allows the user to bind the size of the text to a numeric or date value associated with the tasks. In the screenshot above, the date the tasks were created is bound to the text size. Tasks created farther in the past appear larger than more recently created items.

Categorical and text values may be bound to the color of the text items. In the screenshot above, I’ve bound a variety of colors to various projects. Color makes salient which projects need more attention than others.

In addition to the list and cloud views, Task Views also provides a histogram view of the task space.

The view above shows the number of tasks associated with particular projects. As the cloud view demonstrated, I have many tasks still associated with the Jarvis project.

The histogram view also provides a useful temporal perspective of the task space. In the image above, the height of the bars represent how many tasks were created on a given day. This could as easily show how many tasks were completed within a particular duration in order to better understand personal productivity patterns.

Not pictured above are the task update notifications. Task Views periodically refreshes itself and when a task changes, the application will alert you using an unobtrusive Growl notification. This is useful for discovering that a coworker has elevated the priority of particular item without taking the time to inform you.

In upcoming releases, I plan to add new views that draw upon the data visualization research and literature.

The Context Angle

Since this blog is focused on context-aware computing, there is a context angle here. I speculate that while Task Views provides a variety of views and configurations, not all of them will be appropriate in all cases. A large histogram view may be useful for when the user is planning their week, but a smaller cloud view my be more appropriate throughout the working day. Task Views is explicitly designed to be dynamically reconfigured using systems like Pennyworth. Currently, the context-sensitive portions of the application are

1. The active filter: The list of visible tasks may vary with the current activity. For example, when programming, show the incomplete items from the FogBugz database. When collaborating, show items from Basecamp. When planning the upcoming week, default to OmniFocus.

2. The active view: A larger histogram is useful when explicitly planning. When doing other things, a more ambient cloud view may be more effective.

3. Individual view configurations: Date histograms may be more effective when planning, while categorical histograms may be more effective when triaging. In some cases, it may be useful to bind the size of the text in a cloud view to the date, in other cases, priority.

At the moment, I’m in the process of prototyping and testing this system with users with ADHD. If you’re interested in testing it yourself, post a note in the comments and I’ll get back to you. The software isn’t quite ready for release yet, but I am interested in recruiting more testers.