faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
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
|
[
Reply To This | View ]
|
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 ]
|
|
Re: KIO-FUSE accesses KIO slaves in non-KDE apps
by Bill on Wednesday 11/Apr/2007, @19:39
|
> FUSE is Linux-only (ok, + some BSDs and a hackish Mac OS X-Part).
> KDE, is not.
Fuse already works in Linux, FreeBSD, DesktopBSD and Solaris. I don't see why the users of these systems should be dragged down by the ineptitude of some of the more obscure OS's.
|
[
Reply To This | View ]
|
Re: KIO-FUSE accesses KIO slaves in non-KDE apps
by superstoned on Thursday 12/Apr/2007, @03:19
|
It doesn't work on Mac OS X and Windows, thus it's still not an option.
|
[
Reply To This | View ]
|
Re: KIO-FUSE accesses KIO slaves in non-KDE apps
by niko on Thursday 12/Apr/2007, @10:58
|
Will KIO slaves will ever run on Windows/OS X?
imho this is not neccessary.
Applications (Amarok, Krita, Quanta, ...) yes - but KIO-slaves?
|
[
Reply To This | View ]
|
Re: KIO-FUSE accesses KIO slaves in non-KDE apps
by Sutoka on Thursday 12/Apr/2007, @12:12
|
Getting the KIO-Slaves to work on the other platforms should be much easier than getting the applications. Especially on OS X where the primary differences between OS X and FreeBSD (or OS X vs Darwin+X) exist only with regards to the GUI.
|
[
Reply To This | View ]
|
Re: KIO-FUSE accesses KIO slaves in non-KDE apps
by Pino Toscano on Monday 16/Apr/2007, @04:06
|
> Will KIO slaves will ever run on Windows/OS X?
> imho this is not neccessary.
> Applications (Amarok, Krita, Quanta, ...) yes - but KIO-slaves?
http is a KIO-Slave too. Do you want Konqueror on MacOSX or Windows?
Getting the KIO-Slaves to work on *all* the platforms KDE support *IS* necessary.
|
[
Reply To This | View ]
|
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|