Developers:

There are features not available in pgst that you may desire. In some cases, I desire them too but either do not know how to implement them, or do not have the time at this moment, or am still considering the way in which to implement such features. Therefore, I ask you to please consider assisting me with advice and commentary at the SourceForge project website for pgst:

http://www.sourceforge.net/projects/pgst

Please also note that I have an extremely hectic life with an IT operations day job that often means late night hours and weekend work, unfortunately. That's just the state of the American economy as it tries to blend in with the global economy and rid itself of protectionism. I'm stuck in that situation. If you have more time than I, then please consider being a part of the pgst project.

Desirable Features:

* Consistent way to put an icon on the KDE and GNOME menus for multiple OSes, without having to make a version just for a particular Linux. (And by that, I mean versions of Linux past the date of RH9.) I currently do not know how to do this and am generating icons in the $HOME/.gnome-desktop and the $HOME/Desktop folders. I noticed on FC2 Linux that an icon in $HOME/Desktop did not immediately show up and I wonder if it means that I must edit the GNOME "registry" (aka GCONF). (By the way, that's something that makes me irritable -- that GNOME has to have a "registry" rather than ordinary text files!)

* RPM generation. I have no idea how to do this. If you look on the Internet, one person has already begun this and I have appealed to them to be part of the pgst project.

* Password field on the Connect Server dialog. This would play with the .pgpass file that is explained in the PostgreSQL help. Although passwords are possible on your databases, and are compatible with pgst as long as you create a proper .pgpass file, I am considering adding a password field to the Connect Server dialog, nonetheless. The technique would be that if they put in a password, then pgst would create a .pgpass file if it does not exist. If it does exist, it would read it and determine if the proper host:port:database:user:pass line was in there. If not, it would append it. Editing the pgst.glade file and implementing this change in the pgst.py file takes some time, which is a precious commodity to me, so I have not implemented it yet.

* Fix the odd copy/paste problem, both on the Edit menu and the context menu. Sometimes this works as expected. Occasionally, and very unusually, this does not work as expected and I cannot figure out why.

* If someone ever comes out with a standard X-based GUI setup druid application that could be used over and over for multiple projects and which is standard with most Linuxes, then it would be great if my install would detect this and use that instead. Without it, however, I am bound to use my Bash file install. As a suggestion to you developers out there, why don't you consider making an X-based project like this on SourceForge for all applications, using POLaR programming (Path Of Least Resistance), of course.

* Preferences dialog for font choices, remembering window placement toggle, etc.

* File Browse button on backup and restore dialogs.

* Improved PDF printing using a separate, GTK-based project, and putting an optional dependency on that. GGV just doesn't cut it, you know?

* Remove dupes from History menu.



