From 74aaf315542d5971831c4f0ad66a1dc1d9fedab0 Mon Sep 17 00:00:00 2001 From: Volker Lanz Date: Sun, 11 Apr 2010 14:28:19 +0000 Subject: [PATCH] updated svn path=/trunk/extragear/sysadmin/partitionmanager/; revision=1113693 --- TODO | 28 ++++++++++++++++------------ 1 file changed, 16 insertions(+), 12 deletions(-) diff --git a/TODO b/TODO index a133c0c..6115b10 100644 --- a/TODO +++ b/TODO @@ -1,26 +1,15 @@ Plans and ideas for 1.1: -* Information about file system on a separate tab in the properties, unique - to the file system in use. - * Check if no of sectors fits in an unsigned 32 bit int for msdos partition tables. -* save msdos mbr? - -* 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. - * offer a) no alignment of partition boundaries at all or b) legacy cylinder alignment or c) sector based alignment (the name is misleading, though) * don't hardcode any support for libparted-related stuff like shrinking fat16 in the file system classes. -* support KLocale::BinaryUnitDialect and use KLocale's formatting methods +* use KIO where possible =============================================================================== @@ -51,7 +40,22 @@ For releases after 1.1: 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. +