1. (installer)
I agree in principle about it being OpenSource & portable --
except by nature, installers are OS specific. And the current method of
a "not install beyond unzipping" is the best, and we should try our
hardest to preserve this.
4. (.DAT)
In addition to merely allowing extensions besides .dat, we
should move to using a unique extension for our standard. I suggest
".pwsafe"
14. (resize & safe position)
Note that it's far easier to make a dialog box resize, than it
would be to convert Pwsafe into a non-dialog based application.
19. (copy with Ctrl-C)
Yes, it should be automatic with Windows, but it's not, and it's
annoying as hell! I believe the problem is that the edit dialog had the
DLGC_WANTCHARS flags set somewhere. (It tells Windows that that the
control itself will handle all special characters)
22 & 23. (export as text, print)
In addition to the honkin' big warning, it should require
reentry of the file password. If a walk up to someone's unattended desk
& find PWS open, I shouldn't be able to print out the whole file (force
me to copy'n'paste each entry manually). Further, neither the CSV file
nor the printout should have any column headers or any indication that
it came from PWS. It a find a stray printout lying around, it shouldn't
scream "These are someone's passwords".
24. (prevent second user from modifying).
It can be done internally. We'd have to open the file with the
DENY_WRITES sharing option, and keep the file open as long as the
program is running. Additionally, we'd have to detect a failure to open
to file in read/write mode, and switch to read only (probably after
offering the user of (a) opening this read-only, (b) opening another
file read/write or (c) close this instance of the program entirely, and
activating the other instance (for people, like me, who accidentally
start PWS a second time when it's already running)
26. (configure random passwords generation)
Additionally, it like an option for "first character always
alphabetic" (no particular reason -- it just seems "right" that way)
31. (start PWS on Windows startup)
I'm not sure what they want here. A tutorial on how to put a
shortcut in the Startup folder? Further, it begs the question, in this
case, should it popup to the "Entry Password" window on Windows startup
(which will get very annoying very quickly), or do they want an
auto-sign in feature (which is a whole different and much bigger issue)
32. (hotkey)
Like 31, this is more a personal Windows configuration issue,
rather than something internal to the program. (It's set on the
properties of the shortcut in the Start Menu)
37. (always on top)
No! Please no! "Always on top" is an abomination before the
Lord! Ok, Ok... I guess I could deal with it, if (a) it's is an OPTION,
(b) it is OFF by default, (c) the option is sticky (so when I turn it
off, it STAYS off.). Also, always-on-top is of little usefulness for a
program which takes up as much screen real estate as PWS, so we should
add the windows resize feature first.
Porting:
I'd particularly like to see a PocketPC version. I'd be willing
to work on that port.
General TODO comments:
In the status column, "undone" should be "not done". "Undone"
implies that you implemented it, realized a problem, and backed the
change out.
Also, the status of #13 (XP) should be listed as "Closed" or
"not a bug", since nothing was actually "Done".
(If you want to use any of these comments in an updated, TODO list, feel
free....)
Truth,
James Curran
|
