NEW: GNOME-VFS from Open/Save/Export
I'm trying out the bulia-style announcement.
I applied a simple patch that allows us to use non-local URIs in addition to local paths via Gnome-VFS by using GTK file chooser on the Open, Save ___, and Export dialogs. This means you can use webdav shares, samba mounts, sftp/ssh shares, now...basically, any backend that gnome-vfs supports, we should be able to use. So, in effect, one could work on files from a bluetooth phone filesystem (if so inclined ;).
Before, Gnome-VFS support, Bryce setup as a configure-time option, --with-gnome-vfs, which appears to be turned on by default (even without the configure-time option). And, one could open any URI that gnome-vfs supported from the commandline. So, now we have the added capability
So, please test this out. Also, I'm curious if/how this works on Windows and Mac OS X.
Jon
Jon Phillips wrote:
I'm trying out the bulia-style announcement.
I applied a simple patch that allows us to use non-local URIs in addition to local paths via Gnome-VFS by using GTK file chooser on the Open, Save ___, and Export dialogs. This means you can use webdav shares, samba mounts, sftp/ssh shares, now...basically, any backend that gnome-vfs supports, we should be able to use. So, in effect, one could work on files from a bluetooth phone filesystem (if so inclined ;).
Woah! Great news! - Andreas
On Sun, 2007-02-11 at 20:46 +0100, Andreas Nilsson wrote:
Jon Phillips wrote:
I'm trying out the bulia-style announcement.
I applied a simple patch that allows us to use non-local URIs in addition to local paths via Gnome-VFS by using GTK file chooser on the Open, Save ___, and Export dialogs. This means you can use webdav shares, samba mounts, sftp/ssh shares, now...basically, any backend that gnome-vfs supports, we should be able to use. So, in effect, one could work on files from a bluetooth phone filesystem (if so inclined ;).
Woah! Great news!
- Andreas
I should add that this is hopefully going to enable some great things with Open Clip Art Library (clipart browser) and other sites, projects (OLPC/OpenMoko), to enable browsing of content, etc...
Jon
Jon Phillips wrote:
I'm trying out the bulia-style announcement.
I applied a simple patch that allows us to use non-local URIs in addition to local paths via Gnome-VFS by using GTK file chooser on the Open, Save ___, and Export dialogs. This means you can use webdav shares, samba mounts, sftp/ssh shares, now...basically, any backend that gnome-vfs supports, we should be able to use. So, in effect, one could work on files from a bluetooth phone filesystem (if so inclined ;).
Before, Gnome-VFS support, Bryce setup as a configure-time option, --with-gnome-vfs, which appears to be turned on by default (even without the configure-time option). And, one could open any URI that gnome-vfs supported from the commandline. So, now we have the added capability
So, please test this out. Also, I'm curious if/how this works on Windows and Mac OS X.
Jon
Hmm . If I recall, Gnome-VFS only provides the virtual paths, right? The underlying framework (like Gnome itself) actually does the protocol and stream handling?
bob
On Sun, 2007-02-11 at 15:05 -0600, Bob Jamison wrote:
Jon Phillips wrote:
I'm trying out the bulia-style announcement.
I applied a simple patch that allows us to use non-local URIs in addition to local paths via Gnome-VFS by using GTK file chooser on the Open, Save ___, and Export dialogs. This means you can use webdav shares, samba mounts, sftp/ssh shares, now...basically, any backend that gnome-vfs supports, we should be able to use. So, in effect, one could work on files from a bluetooth phone filesystem (if so inclined ;).
Before, Gnome-VFS support, Bryce setup as a configure-time option, --with-gnome-vfs, which appears to be turned on by default (even without the configure-time option). And, one could open any URI that gnome-vfs supported from the commandline. So, now we have the added capability
So, please test this out. Also, I'm curious if/how this works on Windows and Mac OS X.
Jon
Hmm . If I recall, Gnome-VFS only provides the virtual paths, right? The underlying framework (like Gnome itself) actually does the protocol and stream handling?
I believe Gnome-VFS handles all, but is an abstraction. Check the specs and confirm: http://developer.gnome.org/doc/API/2.0/gnome-vfs-2.0/
bob
Check this http://www.gnome.org/start/2.12/notes/en/rndevelopers.html
Note: there is support for gnome-vfs for windows since 2.12 of gnome and 2.8 of gtk.
And, most are using GNOME 2.16 now: http://www.gnome.org/start/2.16/notes/en/
Jon
On Sun, 2007-02-11 at 19:43 +0000, Jon Phillips wrote:
I applied a simple patch
I think that it should be noted that Ed Catmur was the author of the patch. Thanks Ed!
that allows us to use non-local URIs in addition to local paths via Gnome-VFS by using GTK file chooser on the Open, Save ___, and Export dialogs. This means you can use webdav shares, samba mounts, sftp/ssh shares, now...basically, any backend that gnome-vfs supports, we should be able to use. So, in effect, one could work on files from a bluetooth phone filesystem (if so inclined ;).
I'm a bit concerned about this patch. Mostly it adds the ability to browse gnome-vfs filesystems with the file browser. But, the only file input method that supports using it is the SVG one. It seems very confusing that you can see files you can't open.
I'm not saying "back it out," as much as, this needs to be fixed before a release or we need to disable it.
--Ted
On Mon, 2007-02-12 at 23:02 -0800, Ted Gould wrote:
On Sun, 2007-02-11 at 19:43 +0000, Jon Phillips wrote:
I applied a simple patch
I think that it should be noted that Ed Catmur was the author of the patch. Thanks Ed!
Yes, big thanks to Ed! I added him to the AUTHORS file as well :)
that allows us to use non-local URIs in addition to local paths via Gnome-VFS by using GTK file chooser on the Open, Save ___, and Export dialogs. This means you can use webdav shares, samba mounts, sftp/ssh shares, now...basically, any backend that gnome-vfs supports, we should be able to use. So, in effect, one could work on files from a bluetooth phone filesystem (if so inclined ;).
I'm a bit concerned about this patch. Mostly it adds the ability to browse gnome-vfs filesystems with the file browser. But, the only file input method that supports using it is the SVG one. It seems very confusing that you can see files you can't open.
I'm not saying "back it out," as much as, this needs to be fixed before a release or we need to disable it.
--Ted
Bryce, you might comment as well on the original implementation...
I swear for the life of me I can't track down the original patch in the tracker to cc the author. Otherwise, I should look into as well... ;)
Jon
On Mon, Feb 12, 2007 at 11:37:20PM -0800, Jon Phillips wrote:
On Mon, 2007-02-12 at 23:02 -0800, Ted Gould wrote:
that allows us to use non-local URIs in addition to local paths via Gnome-VFS by using GTK file chooser on the Open, Save ___, and Export dialogs. This means you can use webdav shares, samba mounts, sftp/ssh shares, now...basically, any backend that gnome-vfs supports, we should be able to use. So, in effect, one could work on files from a bluetooth phone filesystem (if so inclined ;).
I'm a bit concerned about this patch. Mostly it adds the ability to browse gnome-vfs filesystems with the file browser. But, the only file input method that supports using it is the SVG one. It seems very confusing that you can see files you can't open.
I'm not saying "back it out," as much as, this needs to be fixed before a release or we need to disable it.
Bryce, you might comment as well on the original implementation...
I swear for the life of me I can't track down the original patch in the tracker to cc the author. Otherwise, I should look into as well... ;)
Yeah, when I added gnome-vfs, I just stuck it directly into the svg export extension, since at that time my purpose was just to have a way to do 'inkscape http://what/ever.svg' from the commandline. That was pre-firefox, so whenever artists posted cool stuff to IRC, there wasn't a way to view it except download it, launch inkscape, and pull it in.
However, there's several things that could be changed for a more proper implementation.
First, the _load_uri() routine in svg.cpp should be moved up to a higher level (maybe to input.*?) It's been kept generic and there's nothing particular to svg files, so it should work fine with all other file types.
Next, all of the input extensions should be revised to use _load_uri() instead of calling fopen() or whatever directly.
Then, for balance would be to create an analogous _save_uri(), and update all the output extensions to use it.
Further, I've noticed that if you launch inkscape with a non-existant filename (e.g., 'inkscape foobar.svg'), it currently displays an error dialog; instead it ought to create a new empty document with that filename.
Bryce
participants (5)
-
Andreas Nilsson -
Bob Jamison -
Bryce Harrington -
Jon Phillips -
Ted Gould