[PATCH] remove UDSEntry from the public KIO API?

nf2 nf2 at scheinwelt.at
Sat Jul 28 16:14:32 BST 2007


Kevin Ottens wrote:
> Le vendredi 27 juillet 2007, nf2 a écrit :
>   
>> Kevin Ottens wrote:
>>     
>>> Le lundi 23 juillet 2007, nf2 a écrit :
>>>       
>>>> As GVFS is not finished yet, i think it would be great for KIO and SOLID
>>>> developers to check out the sources from Alexander Larssons GIT and have
>>>> a close look how it works. And maybe participate by subscribing
>>>> gnome-vfs-list at gnome.org. :-)
>>>>         
>>> If someone can tell me how it's linked to libsolid I'm ok to take a look.
>>> But honestly I doubt it has anything to do with solid.
>>>
>>> Regards.
>>>       
>> Well, apart from providing a VFS layer, GVFS also manages drives,
>> volumes etc,... I guess there is a lot of know-how and also code that
>> could be shared (to avoid pulling stuff into the desktop-layer again,
>> which doesn't really belong there).
>>
>> So don't hesitate to do a "git-clone
>> http://www.gnome.org/~alexl/git/gvfs.git/"...
>>     
>
> As I suspected it's not the same job than libsolid. That said the part 
> managing "drives and volumes" looks more like what we have in kfile. I'm not 
> sure it can be shared though, we used to have it in kio and it proved to be 
> painful imo. So at that point I'm more in keeping the way I'm preparing it 
> for 4.0.
>   

I see, but there is some kind of relationship between kfile and 
libsolid. I reckon this has to change when plugging GVFS in. In this 
case, Kfile should probably use the gvfs API for drives and volumes 
instead...

Aside from that, a kind of "composite" gvfs-slave would be necessary 
(which handles more than one protocol - file:, smb:, ftp:...). Don't 
know if thats possible. Would you need an interface to query gvfs, which 
protocols it can handle? Or just direct all unknown protocols to the 
gvfs-slave...?

Btw, did you read Alexander Larssons design document vfs-ideas.txt? I 
found it quite interesting (its in the "txt" folder of the GIT).

> Note, that technically it would still be possible to use the gvfs stuff if we 
> find it useful at a later point.
>
>   

Hopefully! But also take care that it *will* be useful (accompany its 
development). :-)

I'd love to start hacking gvfs into KIO, but unfortunately i don't have 
time until november... And i believe there are people around, which are 
more experienced with everything related to KIO and file-management...

>> Apart from that, i don't know if SOLID also intends to manage FUSE
>> mounts. If so, this might be quite useful:
>>
>> http://www.scheinwelt.at/~norbertf/devel/fusi/
>>
>> I tried to separate the GUI from the implementation. Therefore others
>> could also use it.
>>     
>
> Also not the job of libsolid. It could be done higher in the stack.
>
>
>   
an extension to kfile?






More information about the kde-core-devel mailing list