Aren/haiku
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updated TODO, I could remove some items.

Browse Source 
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@26461 a95241bf-73f2-0310-859d-f6bbb57e9c96
This commit is contained in:
Stephan Aßmus 2008-07-17 00:25:59 +00:00
parent f97fa70dfb
commit 065e9c8f80
1 changed files with 1 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/apps/drivesetup/TODO
View File

@ -1,10 +1,6 @@
* Create an icon.
* The offsets of partitions should be used to detect free space on container partition types (disks and extended partitions). Items for these free spaces should be placed into the partition list and disk view, so that they can be selected. Only if such a space item is selected should the Partition->Create menu be enabled. If the space is on a disk, the "Primary" and "Extended" items could be enabled. If the space is on an extended partition, the "Logical" item could be enabled. Maybe the Disk Device API allows to query for the ability to create either partition type on the parent device, depending on the partitioning system in use, so that DriveSetup remains neutral towards the partitioning system.
* When the Partition->Create menu items are invoked on free space items, DriveSetup would show a simple panel asking for the size of the to be created partition. The panel could display a slider as the main means to change the size, with the slider already at the maximum position. Below the slider, there could be one text field with a popup for the unit, or three text fields, one for bytes, one for megabytes and one for gigabytes.
* Support of more advanced options, partiticularily the option to resize (shrink) existing partitions to free up space.
* Possibly support the option to do virtual changes to the disk at a higher level. Ie, write back any changes until the user invokes a command to that effect. The drawback is that warnings become more complicated and less direct. For example, if you delete a partition, there is no warning really necessary at this point, but when you later write the changes to disk, there should be a summary of warnings for all partitions you deleted, because only at this point, they really deleted. The indirection could be confusing. On the other hand, future support to resize partitions could take a long time to execute. Then it is nice to setup a list of jobs and execute them without having to sit in front of the machine.
* Possibly support the option to do virtual changes to the disk at a higher level. Ie, write back any changes until the user invokes a command to that effect. The drawback is that warnings become more complicated and less direct. For example, if you delete a partition, there is no warning really necessary at this point, but when you later write the changes to disk, there should be a summary of warnings for all partitions you deleted, because only at this point, they are really deleted. The indirection could be confusing. On the other hand, future support to resize partitions could take a long time to execute. Then it is nice to setup a list of jobs and execute them without having to sit in front of the machine.