List of things that should/could be done to improve OpenVAS-Client: 2009-01-09 Felix Wolfsteller <felix.wolfsteller@intevation.de> * Indicate that a scan was not finished if it was cancelled or an error occured. So far, the report look as if everything went fine (and if you push STOP SCAN early enough there are no holes, warnings, whatsoever). 2009-01-02 Felix Wolfsteller <felix.wolfsteller@intevation.de> * Rename nessus/prefs_dialog and modules inside it. File and function names in there became unbearable and misleading. 2008-10-21 Felix Wolfsteller <felix.wolfsteller@intevation.de> * GUI/usability: Add context-menus on right mouse button click. * GUI/usability: Plugin-info dialog is just available via double-click; communicate this possibility more (menu entry, button). * GUI/usability: Plugin-info dialog does not allow mark and copy for the text fields like CVE. Allow it. 2008-07-01 Michael Wiegand <michael.wiegand@intevation.de> * Relating to Jans entry on 2006-01-23: The menu item "Save Global Settings" is probably redundant and confusing as the global settings are saved anyway on exit. The only thing the menu item does apart from saving the global settings is saving the plugin preferences. So if I make a plugin selection and change the plugin preferences, but forget to use "Save Global Settings" the plugin selection will be saved, but not the plugin preferences. 2007-09-24 Jan-Oliver Wagner <jan-oliver.wagner@intevation.de> * Establish a w32 cross-compilation environment and the automatic building of Windows installer packages via nsis (replacing the current manual creation guided for InnoSetup). Ideally, the system should work similar to Gpg4win (www.gpg4win.org) where on Linux a single "make" will build everything for windows as well. 2006-01-23 Jan-Oliver Wagner <jan-oliver.wagner@intevation.de> * Explicit saving of preferences Currently, the preferences are saved implictley (general options when leaving a task/scope, plugin preferences only after a executing a scan) This induces problems such as: * Non-default preferences for Nmap (NASL wrapper) set under global settings are not remembered between sessions.·· * If non-default preferences are set for Nmap (NASL wrapper) under global settings, and then a new task is created, the new task has the default settings not the modified ones. No estimate how much work this would mean and what to do exactly, but estimated to be a comprehensive change.