39 lines
1.4 KiB
Plaintext
39 lines
1.4 KiB
Plaintext
Random plans and ideas for 1.1 and beyond:
|
|
|
|
* 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. Using libraries we'd
|
|
hopefully be able to get meaningful progress status reporting while resizing,
|
|
checking and so on.
|
|
|
|
* 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.
|
|
|
|
* The KPart works but has problems: The context menus don't show up, the status
|
|
bar is missing, maybe more.
|
|
|
|
* save msdos mbr?
|
|
|
|
* don't call updatePartitions() or anything after pushing an operation to the
|
|
stack: MainWindow::on_m_OperationStack_operationsChanged() will be called and
|
|
will deal with all that. warning: this might cause problems, it calls
|
|
PartitionManagerWidget::updatePartitions() which currently clears the
|
|
selection -- maybe it shouldn't...
|
|
|
|
* let the user specify extern command locations and options in the settings
|
|
|
|
* move device scanning to backend plugin (call it from the device scanner
|
|
thread though)
|
|
|
|
|
|
Bugs:
|
|
|
|
* don't show available and used values for extended partitions
|
|
|
|
* solid and its object-created-with-parent-in-wrong-thread problem
|