NewClassesWork

-- Classes to add:

+ CrashedApplicationInformation: (better name?)
-----------------------------------------------
* App Name
* App path
* App version
* Signal / Signal name
* PID
* Bugzilla Product and Component (mappings) ?
* Report address / mail / isKDEProduct functions
* Backtrace
* Backtrace functions
* other KrashConf members
* other process information (memory map)
* Custom usefulness value required in bugzilla (from mappings-like file) ?
* Custom details to add to the bug report (from mappings-like file) ?

+ DebuggerInformation:
-----------------------------------------------
* Debugger name
* Debugger command
* Batch commands
* Show debugger or not

+ SystemInformation:
-----------------------------------------------
* OS
* Distro
* Lsb_release handle
* Bugzilla OS and Distro mappings
* Compiled by sources KDE

+ ReportingInterface:
-----------------------------------------------
* ReportMode (CreateNew or Attach)
* Title
* Description
* Generate report's text
* Send to Bugzilla helper function
* User options (canDetail, devsCanContact)

-- Classes to delete:

- ReportInfo
- KrashConf

-- Classes to modify:

* DrKonqi singleton:
-----------------------------------------------
Nuke this class or adapt it ?
- Use it as a central point to access all the other "*Information" classes ?
- Move KrashConf::expandString to DrKonqi ??