Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
releng:4.8:roadmap:thunar [2009/08/20 02:43] – created jannis | releng:4.8:roadmap:thunar [2010/04/06 03:22] – jkUKZzATWPU 194.25.187.121 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Thunar 4.8 Roadmap ====== | + | Z1h78k |
- | + | ||
- | ===== GIO/GVfs (Easy) ===== | + | |
- | + | ||
- | The goal is to finish the work done in the <code>migration-to-gio</code> branch early in the cycle and to merge it into master. It will require | + | |
- | + | ||
- | Completed: 95% | + | |
- | + | ||
- | ====== Volume Monitoring (Tough) ====== | + | |
- | + | ||
- | GVfs provides volume monitoring based on HAL (or gnome-disk-utility/DeviceKit-disks in more recent versions). However, I see it as my responsibility to maintain a feature parity before and after the migration to GIO without additional dependencies. As a consequence, | + | |
- | + | ||
- | Note that thunar-volman uses HAL and for a good integration of Thunar and thunar-volman, | + | |
- | + | ||
- | Completed: 10% | + | |
- | + | ||
- | ====== thunar-volman (Easy-Moderate) ====== | + | |
- | + | ||
- | This is not part of Thunar itself but I'd consider it an integral part of the user experience Thunar provides. It depends on HAL and only requires very few modifications to work with GIO. In fact, it only uses ThunarVFS for monitoring its config file. If we port it to xfconf it wouldn' | + | |
- | + | ||
- | If we are to use DeviceKit-disks in Thunar, we're also required to port thunar-volman to it. (This is the moderate part.) | + | |
- | + | ||
- | Completed: 0% | + | |
- | + | ||
- | ====== Integration of Remote Locations in the Side/Tree Pane (Tough) ====== | + | |
- | + | ||
- | Right now, there is no way to " | + | |
- | + | ||
- | Completed: 0% | + |