jmoiron.net

PacMan; the Slackware Package Manager; version 0.3, previously codenamed "Dartmouth", has been completed. I figure I can have codenames if Intel can. Here's a changelog since v0.2:

Changelog

• creation of main window tabbed user interface with...
  • an "Installed Packages" tab that behaves like the program always did
  • a "search for packages" tab that will be used to search for online
  • a "Browse Packages" tab that will be used to browse online packages. this tab will have features that make it superior for browsing over the "search for packages" tab
  • a "Removed Packages" tab that behaves much like the "Installed Packages" tab, but displays information on removed packages
• fixed spelling errors pointed out by Brander
• settings -> pacman now has a dialog
• changed package description to a tab widget with defaul "description" tab and an "installed files" tab
• made "close when done" checkbox in remove dialog work
  • implemented and moved "remove" right click action blocking I/O to a different thread
  • created and moved "file -> update" blocking I/O action to a different thread
• enhanced startup speed by ~300 ms by moving initial package desc reading to a different thread

Todo

• move "installed files" I/O to a different thread so UI doesn't block in packages with many files (eg. devs, kdeartwork, ET al)
• "settings -> pacman" should save settings somewhere besides memory (~/.pacman?)
• help->about -- should this have a "cancel" or "close" button?
• change and finalize UI for the "Browse" and "Remove" packages windows; more features should be built into the UI than are at present time; but I want to retain a clean, uncluttered feeling
• "name:", "version:" in "Installed Packages" is redundant, but explanatory and perhaps good for initial usability. Should I keep it or dispose of it?
• create "slapt-get" configuration dialog
• design pacman config file

If you have any comments, questions, corrections, or requests, don't be a stranger: email them to me. The next version of PacMan, v0.4, is code-named "Harcourt". I follow a x.y.z, where x is a major revision, y is minor revision, and z is development revisions.