I'm very much interested in support for remote file systems provided by GIO/ GVfs in Thunar, and possibly other Xfce applications. I would think implementing an additional Vfs backend in Thunar seems like the way to go. It could be conditional to the available Glib version. I'm not really familiar with the sources of Thunar, but from a look it should be fairly straightforward to add a new backend, ie. one that is used as a fallback after local and trash path schemes.
Per a short discussion with Christian on IRC: <kalikiana> Hm.. I wonder if it would be possible to implement GIO in ThunarVfs to support GIO in Thunar and all apps that use ThunarVfs [...] <kelnos|work> Corsac, kalikiana: no, the intention is to scrap thunar-vfs entirely, iirc <kalikiana> kelnos|work: Ah, but that would only be feasible in the far future, or not? Since GIO 2.16 or 2.18 isn't exactly old yet <kalikiana> So I figure, for the moment implementing GIO inside the Vfs would avoid the dependency question <kelnos|work> kalikiana: well given our release cycle, it doesn't really matter <kelnos|work> turning thunar-vfs into an abstraction layer / optional implementation sounds gross to me <kelnos|work> waste of time that could be spent on actually making thunar awesomer <kelnos|work> the vfs is boring <kelnos|work> thunar's interface is what matters <kelnos|work> m8t: what are you trying to do? i don't think i really understand <kalikiana> kelnos|work: Fair enough, I wouldn't mind personally. I was merely assuming that compat would be favoured <kelnos|work> compat in this case would be "if you don't/can't have gio/gvfs, don't upgrade thunar" (Minor clarification: I mean the vfs is boring *to users*. It should just work, and IMHO the place to spend time -- after we have a full-featured vfs layer [gio/gvfs] in use -- is in the interface, and adding new, innovative stuff that helps people get stuff done.)
Working on it.
Close bug reports of archived products.