JKB050120

In no particular order,

Take the idea of a profile one step further: have pre-defined "tasks",
like "automatic full backup", "automatic differential backup",
so the user clicks on the task button, and performs the action using
the predefined settings. E.g., user starts KDar for the first time,
and without entering an archive name, or anything, just clicks
"Make full backup", and three hours later they have their system
backed up on disk. Even better, get KDar to prompt the user for
DVDs or CDs and they have a fully-tested backup that they can
store in their strong box. Also have a boot CD, with an X-windows
enabled linux live distro that boots directly to KDar and can
do a full restore with no detailed questions asked...
There could still be the "advanced" options available if the user
needs them.

Disable KDE Wallet if it isn't available? Or should we insist that
KDE-3.3.x be used?

Get encryption support working properly. i.e., use a forthcoming
libdar method of querying an archive for the encryption type.
The current workaround is a hack.

Remove all dependence on "extern" variables.

In About dialog window, use green checkmarks and red x's to
indicate the compiled-in library capabilities.

Implement an archive database manager.

Make KDar run in daemon mode, and allow user to schedule a backup
profile for periodic execution. Daemon mode may be as simple as 
minimizing KDar into an applet in the taskbar system tray.

Get progress bar to work with all libdar operations (not just creation).

Improve GUI layout. Suggestions? Comments?
Suggestions for new logo/icons for KDar are always welcome.

Implement input, output pipes, etc.

Fine-tune context menu. Allow a single directory, or entire subtree to 
be restored.

Make icons in archive browser more specific (jpg, xcf, etc.).

Popup window to show archive properties (size, number of files,
compression ratio, creation date, computer and root directory that
it was created from, whether it has been validated, date of last diff,
creation options, etc.)

Allow user to preview the restored directory tree, before they do
the actual restoration. Should update in response to changes in
the file and directory filters.

Given a directory to backup, show a tree of that directory, and highlight
or otherwise mark the directories and files that will be archived.
This should update in realtime as user changes directory, file and 
compression filters.

I welcome your feedback on KDar. Any suggestions?

