It has been several months since I last wrote about the quirky, amazing information manager, Tinderbox (for previous entries see part 1, part 2 and part 3). There have been a couple of reasons for this, which are somewhat related. Foremost has been the fact that I came to the end of my expertise with the application after the third entry. My original purpose for writing about Tinderbox was to demonstrate that even without knowing a lot of the “under-the-hood” techniques, you could still do a lot with the program. I hope I achieved that, but to write more I felt I had to learn more about Tinderbox. And there lies the problem. We now enter the territory that earns Tinderbox its reputation as having a steep learning curve.
As an example of how I have “hit the wall” with Tinderbox, I was recently setting up a database (document in TB parlance) to track my collection of Lakeside Classic books. Using the same technique I used in part 3, I created a spreadsheet containing the book title and year of publication, then dropped that into the Map View and voila, I got this:
Now the problem. I wanted to add a Key Attribute to mark the titles that I own (Key Attributes are essentially custom fields for various types of data). Simple, right? Not so fast. I was able, of course, to add the Key Attribute to one of the notes, and I made that note a prototype. Now all I had to do was apply that prototype to all the notes. Should be simple to do, right? Not so much — at least for me.
I think there are several ways that this should be doable:
- Create an action in the parent note that makes all its children the same prototype.
- Create an agent to do the same thing.
- Create and apply a Stamp to the lot of them (more on Stamps, below).
And there are probably other methods, which I haven’t thought of.
The problem with all these methods is that in each one I have to come up with the right syntax for writing the action, and I can’t for the life of me figure that out, and the Help documentation isn’t very helpful.
Perhaps here I should give you a little background about myself, so you can determine if you might be more or less technically adept than I am. I have been using personal computers for almost three decades. Over the years I have managed to self-teach myself Lotus 1-2-3, Grandview, Pagemaker, InDesign, among many other applications. I got through a beginners programming class, but in addition to a little Basic I learned I don’t really have a knack for programming. So I would describe myself as a veteran computer user, with a blindness for scripting/programming.
If you understand this stuff and are willing to put in the time to learn how to do it in Tinderbox, you should be able to make the application work miracles on your data. The Stamps feature is a good example. Stamps are sort of like macros, I guess. You create any actions you want, add them to the Stamps list and you can then apply those actions to any of the notes in your database. It’s like programming your own menu of options.
I applaud this kind of functionality, even if it will never work for me. However, I am disappointed that certain basic actions are not already programmed for users like me. Making it easy to apply prototypes to groups of notes, for instance, shouldn’t require writing an action.
This is probably the point where some Tinderbox expert will send a comment telling me there is an easy way to mass-apply prototypes, idiot! — and, if there is, I’d like to hear it. I have avoided asking for help on the Tinderbox forum, as I think that’s cheating when evaluating the functionality of an application.
But let me be clear. I still admire Tinderbox and find it exceedingly useful, even with the limitations that make it difficult for people like me. The point here is that what limits Tinderbox for my use is that every step beyond some of the more basic functionality I described in previous posts requires combing the help documentation and a lot of trial and error. Truth be told, the help documentation is abysmal. I’m sure I could eventually figure it out, but that’s too much work.
And this gets me to the other reason I haven’t written for a while about Tinderbox: I’ve added PersonalBrain to my list of information managers. In a future installment I’d like to do a comparison of these two programs, which I think will prove somewhat instructive — or hope so, anyway.
But this story does have a happy ending. See the next installment, which I’m posting at the same time as this one.
UPDATE: The developer of Tinderbox, Mark Bernstein, provides instructions for easily applying a prototype to multiple notes in the comments section below. And he didn’t call me an idiot, which I appreciate, because he might justly have done so!