OLD | NEW |
1 TODO file: | 1 TODO file: |
2 ---------- | 2 ---------- |
3 | 3 |
4 COMPATIBILITY fixes: | 4 COMPATIBILITY fixes: |
5 | 5 |
6 1. COMPATIBILITY: dual-mode devices, i.e. devices exposing both an MTP | 6 1. COMPATIBILITY: dual-mode devices, i.e. devices exposing both an MTP |
7 and a USB Mass Storage Device Class (flashdrive) interface are and | 7 and a USB Mass Storage Device Class (flashdrive) interface are and |
8 have always been problematic. We must find a way to get this to work, | 8 have always been problematic. We must find a way to get this to work, |
9 eventually. The problem is that the in-kernel mass storage driver hogs | 9 eventually. The problem is that the in-kernel mass storage driver hogs |
10 the device before the MTP mode gets a chance of being used, whereas | 10 the device before the MTP mode gets a chance of being used, whereas |
(...skipping 36 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
47 atleast a call to the cache update function. | 47 atleast a call to the cache update function. |
48 | 48 |
49 3. FEATURE: Mechanism to retrieve the device icon device property, else if not | 49 3. FEATURE: Mechanism to retrieve the device icon device property, else if not |
50 present, look for DevIcon.fil (Windows ICO format) and | 50 present, look for DevIcon.fil (Windows ICO format) and |
51 DevLogo.fil (PNG Format) images from the device (if available). | 51 DevLogo.fil (PNG Format) images from the device (if available). |
52 | 52 |
53 4. FEATURE: Shared device access so that multiple client applications can have | 53 4. FEATURE: Shared device access so that multiple client applications can have |
54 an open connection to the device at the same time via a handle. For example, | 54 an open connection to the device at the same time via a handle. For example, |
55 it should be somehow possible to run mtp-detect at the same time as amarok or | 55 it should be somehow possible to run mtp-detect at the same time as amarok or |
56 mtpfs is connected to a device. This would require some form of resource | 56 mtpfs is connected to a device. This would require some form of resource |
57 sharing, discussions have centered on a D-Bus based connection arbiter | 57 sharing. |
58 daemon. | |
59 | 58 |
60 5. FEATURE: Implement an OpenSync backend for devices which have | 59 5. FEATURE: Implement an OpenSync backend for devices which have |
61 calendaring, contact etc support. http://opensync.org/ | 60 calendaring, contact etc support. http://opensync.org/ |
62 | 61 |
63 | 62 |
64 THOSE ARE ALREADY DONE: | 63 THOSE ARE ALREADY DONE: |
65 | 64 |
66 1. FEATURE: Make an API that can return several devices and let the user | 65 1. FEATURE: Make an API that can return several devices and let the user |
67 choose which one to operate, not just connect to the first one... | 66 choose which one to operate, not just connect to the first one... |
68 | 67 |
(...skipping 35 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
104 9. SPEEDUP: The recursive function that builds the folder tree is | 103 9. SPEEDUP: The recursive function that builds the folder tree is |
105 O(n^2)! Atleast remove all non-folders (PTP associations) from the | 104 O(n^2)! Atleast remove all non-folders (PTP associations) from the |
106 list before we start sorting and building that tree. We walk the | 105 list before we start sorting and building that tree. We walk the |
107 entire list for each group of siblings right now! | 106 entire list for each group of siblings right now! |
108 | 107 |
109 10. FEATURE: program to autoprobe device interfaces on connection. | 108 10. FEATURE: program to autoprobe device interfaces on connection. |
110 | 109 |
111 11. FEATURE: accomodate Googles uncached device needs. | 110 11. FEATURE: accomodate Googles uncached device needs. |
112 | 111 |
113 12. FEATURE: rudimentary event interface. | 112 12. FEATURE: rudimentary event interface. |
OLD | NEW |