Here's an e-mail I posted to dev@tasklist.netbeans.org
August 19 2002; implement it. I received one reply
from
Brett Watson who voted for it, and added that I should
make the filename a project option and listen on its
changes (effected by project changes) such that
project
switching causes tasklist switching.

Subject: An idea: browsable tasklists

I had an idea this weekend that I'd like feedback on.

Remember how I was trying to get "project specific
tasks"
accounted for in some way? I thought users would
mark specific
tasks as project specific, and then when you
switch to a project
its tasks are merged into the tasklist.

Here's an alternative idea.

Users will probably want to store the project
specific tasklist
along with the source files in the project content
anyway (after
all, the tasklist file is source data, not generated).

Let's say I do the following:
 -- I recognize tasklist files -- assign a new
icon to it etc.
    That way, when you browse your
project/filesystem content
    in the explorer, you see your tasklist file
along with your
    other files.
 -- Add actions to this node allowing you to
Import a tasklist
    into your current tasklist, OR, Open the
tasklist in a new
    window! Editing this window then edits this
tasklist.

Thus, for each project I can have a unique
tasklist. I can
open it, just like a source file, and view/edit
its tasks.
    Pros: Allows finer-granularity than projects;
I can have
five tasklists per project for example. Nice to "view"
tasklist files (since they will be part of the
project source
content) and be able to operate on it.

Cons: Not as integrated; if you switch projects
nothing happens;
you have to deliberately open the tasklist file.

Opinions on this?