Re: Do FileChooser+gnome-vfs currently work?

[Luca Ferretti <elle uca libero it>]

Il lun, 2004-03-22 alle 10:34, James Henstridge ha scritto:
> On 22/03/2004 5:20 PM, Luca Ferretti wrote:
> 
> >Il dom, 2004-03-21 alle 23:15, Jonathan Blandford ha scritto: 
> >  
> >
> >>Luca Ferretti <elle uca libero it> writes:
> >>    
> >>
> >
> >  
> >
> >>You need to do "is_local" to be FALSE on the file chooser.
> >>    
> >>
> >
> >Mhhh... first, it seem that the proper properties is "local_only" :-)
> >
> >Second, now my /opt/gnome/share/themes/Simple/gtk-2.0/gtkrc contains[1]
> >        
> >        GtkFileChooser::local_only = 0
> >        GtkFileChooser::show_hidden = 1
> >        GtkFileChooser::file_system_backend = "gnome-vfs"
> >  
> >
> These properties are object properties as opposed to style properties.  
> Putting them in your gtkrc file will have no effect. 

I don't understand.

Example: I want that all my file chooser dialogs show hidden files; I
know that this feature is driven by the 'show_hidden' properties of the
widget; I belive that this widget property can be changed as well as the
'has-secondary-backward-stepper' for GtkScrollbar, via gtkrc.

Where am I wrong? Why?

>  An application has 
> to explicitly state that it can support non-local files.  If it doesn't, 
> then the file selector will only let the user select local files.

Heermmm... sorry, I was asking for a different feature. Try to edit
gtk+/test/testfilechooser.c

@@ -410,7 +410,7 @@
  
   dialog = g_object_new (GTK_TYPE_FILE_CHOOSER_DIALOG,
                         "action", action,
-                        /* "file-system-backend", "gtk+",*/
+                        "file-system-backend", "gnome-vfs",
                         "select-multiple", multiple,
                         NULL);
Now recompile and run testfilechooser. The bookmark list now contains
physical volumes, the same available with nautilus under computer://
URI.

This is a feature that is useful for all applications, don't need any
vfs (except mount removable drives on demand), just add a visible
shortcut to all stuff under /mnt.

So, the starting question again.
The /desktop/gnome/interface/file_chooser_backend key value is
"gnome-vfs" but all file chooser dialogs still use the "gtk+". Why?


> The reason that the default is local-only=True is that the failure mode 
> is less severe.
> 
> If an app supports openning remote files but local-only=True, then the 
> app still works (but some of its functionality is hidden).  If an app 
> only supports local files but local-only=False then the user can select 
> files to open that the app can't handle, which is much worse.

As user, IMHO this is a not so smart behavior. Are you really saying
that remote/virtual fs support should be maneged via filechooser backend
AND application ???

So, when GIMP will switch to GtkFileChooser, I will not have the
ability, for example, to save an image on a ftp server if gimp
developers don't set to false local_only property?

I'm not saying that local_only is a bad property, it can be great to
prevent users to access remote stuff, but I think that its default value
should be false and it should be true only if you want to deny remote
accesses (at application or whole desktop level).