Plans and ideas for 1.1:

* don't hardcode any support for libparted-related stuff like shrinking fat16
  in the file system classes.

* save SMART details to html file?

===============================================================================

Bugs to fix for 1.1:

* copy&paste seems broken wrt alignment when copying from cylinder aligned to
  sector aligned drives (maybe even more than that)

* resizing a newly created extended that has children (leading to a merge of
  operations) crashes in NewOperation::description(). this is intermittent
  and probably fixed in r1107315.

* make sure the default file system can indeed be created

* why is not possible to move an extended partition if it's empty?

* moving an empty extended partition is currently not allowed, but attempting
  to still moves it by a few pixels

* move/resize and aligning is badly broken, still: as long as align is on,
  moving the start beyond the first possible sector breaks. moving a partition
  to the left changes its size and probably more...

* moving a partition to the left that cannot be moved because it fills up all
  the space it can have makes it smaller and smaller because
  PartitionTable::alignPartition() always re-aligns the right end

===============================================================================

For releases after 1.1:

* write a setup-kcm in the style of k3b's so that the user can set the r/w
  permissions of the disks there; also use kauth to update the partition table
  in the kernel. that should cover all cases where we actually need root
  privileges now. -- we actually also need root privs for SMART now.

* The whole lvm/dm debacle.

* The interface between core and the file systems needs some more thought.
  Ideally we'd be free to use either external helper apps (like we do now) or
  libraries to achieve the same things. Libraries in this case being libntfs-3g
  and libext2fs. There's one for reiserfs too, iirc.

* Convert the fs implementations into plugins.

* Write a udisks backend plugin.

* Add a SMART self test operation, only available if the backend plugin
  supports that (udisks does, libparted does not).

* support KLocale::BinaryUnitDialect and use KLocale's formatting methods (how
  feasable is that? does it make sense?)

* Information about file system on a separate tab in the properties, unique
  to the file system in use.

* let the user specify external command locations and options in the settings;
  use some program and binary management setup internally like k3b has it

* parse progress information at least from e2fsck and ntfsclone (do we use the
  latter at all? if not we should); maybe others.