links to this page:    
View this PageEdit this PageUploads to this PageHistory of this PageTop of the SwikiRecent ChangesSearch the SwikiHelp Guide
Bug Fixes Archive Viewer, v. 1.1
Last updated at 1:13 am UTC on 17 January 2006
Enjoy! I built this tool to help me explore the goodies hidden in the archive, and to help harvest fixes and enhancements. I think it's fun to use.

Version 1.1 is much faster, more usable and more useful than version 1.0. It has a lot of built-in queries for navigating and organizing a local copy of the Bug Fixes Archive; the default view on the Archive shows [FIX] and [ENH] posts going back several months.

Once you've installed the load script, open the BugFixArchiveViewer from the "open..." menu. This opens the default view on the Archive ( you can get the same result from this do-it: "BugFixArchiveViewer viewGsugSwikiFixesArchive" ). The viewer will take a few minutes to load updates.

Once the viewer opens, try out some of the filtering options. There are lots of filtering options in version 1.1 – see the tiny-menu in the top pane. Try filtering for groups with "weakness" in the title or body text. Also, try filtering for just groups that have a post from "ned@bike-nomad.com". Try filtering for groups with 3 or more posts. Finally, try resetting all filters to their defaults.

The BugFixArchiveViewer allows you to send an email directly from the viewer, or to edit your comments in CommentNotePad, a helper application that is designed to help with automating alot of the annoying details about posting to the Bug Fixes Archive (QA tags, using parens correctly, getting the title exactly the same, etc). Play with the the CommentNotePad via the "edit comments in note pad" mouse menu option. Try "edit summary comments" in the tiny-menu; also try setting some of the QA options like "SLint-Approved"; then try sending the comment as an email.

Hope you enjoy this tool. It's definitely a beta product. Let me know what you think of it.

This release is very HTTP-focused; partly because the current Bug Fixes Archive is accessible over HTTP; partly because HTTP is a convenient way to update the local archive when a mail server isn't available. Future versions may offer update-from-MailDB capabilities, if folks are interested.