Re: Enabling Network locations by default in File Chooser

[Timothy Arceri <t_arceri yahoo com au>]

Thanks Colomban, these are two good points. But I still think its not a great solution to cripple systems that do have gvfs-fuse avaiable just because some other system might not have local mounts for remote locations. Is there any easy way for GTK to test for the avaliblity of gvfs-fuse and set local_only according based on the result? Or is this not the type of thing GTK would normally do?

Tim



----- Original Message -----

Le 16/11/2012 23:53, Timothy Arceri a écrit :
> Hi Guys, I'm after feedback on whether you guys think this is a good
> idea. For background I have been investigating bug
> https://bugzilla.gnome.org/show_bug.cgi?id=586367 > 
> Basically what I've found is that gtk_file_chooser_set_local_only()
> is set to TRUE by default. This makes sense if file_chooser is
> returning uri that points directly to the network locations e.g.
> smb:///blah, afp://blah, etc as you can't be sure that the
> application can handle these protocols. I'm assuming that these uri's
> are what was returnedback with gnome-vfs. However, my testing shows
> that with gvfs file_chooser returns local locations (that I believe
> are FUSE mounted) to the network locations meaning that the
> applications are always given a local location and should have no
> problem with handling the location. Hence I would assume it would be
> safe to set local only to FALSE by default. I'm not 10000% sure, but I'd say: 1) it requires gvfs-fuse;
2) what about non-Linux platforms?  Do they also have local mount for
remote locations? Regards,
Colomban > 
> 
> I guess what I'm after is the GLIB/gvfs guys to tell me if I'm
> missing something here? And whether this is a good idea or not.
> 
> Thanks for your time, Tim