Re: KIO-FUSE accesses KIO slaves in non-KDE apps

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: KIO-FUSE accesses KIO slaves in non-KDE apps
by Debian User on Wednesday 11/Apr/2007, @13:32

Except that of course FUSE is not the solution, what gives?

I already today can use OpenOffice to open files via IO-Slaves. It just takes a temporary file, created behind my back. And why not monitor that file for changes and push these backto the IO-Slave where it came from?

Admited, a lame work-around, but with inotify its going to work nicely.

Yours,
Kay

Related Links

·   Articles on KDE Public Relations and Marketing
·   Also by Debian User
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: KIO-FUSE accesses KIO slaves in non-KDE apps
by Bill on Wednesday 11/Apr/2007, @19:47

> I already today can use OpenOffice to open files via IO-Slaves.
> It just takes a temporary file, created behind my back. And
> why not monitor that file for changes and push these backto
> the IO-Slave where it came from?

Because when OpenOffice crashes or misbehaves it leaves your /tmp directory with Gigs of orphaned temporary files.

It's a pain to make OpenOffice and other non-KDE applications aware of IO slaves, and it's outright impossible to do so in closed-source apps. With FUSE, they don't have to be recompiled or modified at all - they see remote files as a normal local files. So it's great for backward compatibility.

[ Reply To This | View ]

Re: KIO-FUSE accesses KIO slaves in non-KDE apps
by superstoned on Thursday 12/Apr/2007, @03:18

this already works in KIO, it CAN create a temporary file, monitors it for changes, and uploads the changed file back to the original location. I agree FUSE is cool, but not the cross-platform solution we need.

[ Reply To This | View ]

Re: KIO-FUSE accesses KIO slaves in non-KDE apps
by ben on Thursday 12/Apr/2007, @09:13

Using FUSE to create a temporary mountpoint is a lot cleaner than creating temporary files and transmitting the changes back. Especially if you're working on a very big file.

But FUSE isn't on all of KDE's platforms. I think the best solution would be to have FUSE where you can, and temporary files when its not an option.

[ Reply To This | View ]

Re: KIO-FUSE accesses KIO slaves in non-KDE apps
by Bill on Thursday 12/Apr/2007, @11:10

> I think the best solution would be to have FUSE where you can,
> and temporary files when its not an option.

Exactly!!!!

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"I switch between vi and xemacs quite a lot. I'm happy with both." -- Simon Hausmann
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.