Louis Kessler’s Behold Blog

I have attained success at making the Everything Report “Virtual”. Now what appears to be a big huge report is simply only a porthole looking at the piece of the report you want to see. The speedup and reduction in Behold’s memory use is dramatic.

This is, of course, the way all other genealogy programs work. They only show you one person or one family at once, which is why they are fast, but limited.

Behold still appears to produce the whole report at once. It’s a bit of an optical illusion now, sort of the way motion pictures are really individual frames blurred together faster than you can see. Behold’s viewport also gets generated faster than you can see.

I’ve now also virtualized the Treeview. Now only the structure of the entire Treeview is pregenerated, and the data is only included when required for display. This also really increases speed so that 1,000,000 nodes can be added to the Treeview in a half a second.

I still have to convert the Print, Print Preview, Export and Find functionality to work with the virtualized Everything Report. Hopefully I’ll get most of that done in time for the beta release in a couple of weeks. If not, they’ll be the first things I finish off during beta.

To complete my previous post about GTD, I want to mention the fatal flaw in this methodology.

Getting Things Done tells you to determine the next action you need to do for all of the stuff/projects you need to do. That is good! Once you do that that action, you can go onto the next.

I’ve, in effect been doing that for Behold. Behold’s Future Plans list is the ToDo list of subitems I need to do to get Behold to become that “perfect” genealogy program. Once I pick the next item from the list, I determine the first programming “Action” to do to get that thing done. Another action follows that action and so on until that item is complete. Then I go onto the next item.

Do you see the problem here? It is the problem that has caused Behold to take so many years to get to this point. Each item has many actions, often many more than you (or I) would expect. Doing them one at a time and only worrying about the next one is a great way to stay sane and is one of the best things GTD teaches you. It helps you continually make progress.

But the problem is that GTD does not necessarily get you any closer to your final product. You keep adding new ideas to the ToDo, often faster than the items can get done. The product gets better and better but the end keeps getting farther away. Something is missing from Getting Things Done to focus you. Some method to prioritize and schedule what you do.

How to fix Getting Things Done

I don’t think it’s very hard to fix. Simply add Joel Spolsky’s Painless Software Schedules methodology into GTD. Joel wrote this in 2000, and now says the article is obsolete, but don’t believe him. PSS is very simple and integrates with the actions of GTD too perfectly to ignore. You need add only 5 columns to your Actions to implement it: an original estimate, a current time estimate, the time elapsed, the time remaining, and a priority column.

You only need a list with 4 to 6 simple columns to implement GTD, and only 5 more if you want to go the extra step and prioritize and schedule the things you want to do.

Remember, any system has to be simple and fun to use or you won’t use it.

Genealogy software needs a simple but useful ToDo list. I’ve now got the model to implement one, if and when I get there.

In the meantime, I’m continuing my push towards Behold’s beta.

This one has bugged me for six months, but tonight I finally solved it.

On this Blog, there are two RSS feeds. One for the Blog Entries I make, and one for all the comments. But the RSS feed for the comments never seemed to show the comments after they were made. They seemed to appear sometime later.

It was strange because it appeared the feed was correct, and validated okay. It seemed to be okay in many feedreaders. But in the feedreader included with Internet Explorer, it had this problem. I couldn’t tell if it was a feed problem, an IE problem, or a WordPress problem.

This wasn’t a critical problem for my Behold blog, but it was a bad one for the GenSoftReviews site, since that site’s RSS feed is made up of the reviews, and those are the WordPress comments. Many reviews would be added, but they wouldn’t appear in my IE feedreader.

But a few days ago, I found that the comments feed got updated, not when a new comment was added, but when a new Blog entry (or in the case of GenSoftReviews, a new program listing) got added. That got me scratching my head and led me up a few wrong alleys.

I finally traced this to a problem in WordPress that was apparently fixed over 2 years ago and another ticket that led me to it. The problem then was a stale “Last-Modified:” header in the HTTP response to the link to the comments feed.

Then when I discovered that this problem was still alive by a recent post on the WordPress Support Forum titled: New RSS entries/comments not working, then these materials all helped me to debug a solution. Pleased to find it, I posted my solution back to the Forum, with the hope that it might help others - so they won’t bog themselves down for hours like I did.

That was an elusive bug. But now my workflow will be very much helped, since I’ll no longer have to go back to my Behold Blog and to GenSoftReviews just to check for new comments or reviews. I’ll now be getting them reliably with the rest of the RSS feeds I subscribe to.

RSS is great. It lets you follow the blogs and forums that you’re interested in, and you are in control of when you want to do that. Now my own sites are back under control again. Yay!