KDE is not an OS platform... (And neither is Gnome)

[nf2]

On Sun, Nov 1, 2009 at 8:32 PM, Martin Sandsmark <sandsmark at samfundet.no> wrote:
> On Sun, Nov 01, 2009 at 08:12:34PM +0100, nf2 wrote:
>> And how do you want to solve the problem for KDE apps on Gnome and GTK
>> apps on KDE? How do you want to get this extra layer into KIO and GIO?
>
> Why can't they just hand over the RFC-compliant URLs to eachother? It's the
> easiest, but with some downsides (having to type in the password again, for
> example. Though this could be worked around by having a common auth storage). :-)

Read my "solution" number 2 above.

>
>> And if you really want to be able to switch the entire VFS
>> implementation, there might as well be an "easier" way to do that: The
>> reverse bridge. Just write a KIO plugin for GIO. As GIO loads the VFS
>> implementation as a module, this doesn't look like a completely
>> impossible thing (but not a walk in the park, i'm afraid).
>

Actually it might be a 100 times easier if you implement it as
GVfsBackend. You can use the KIO-jobs there. On the client side you
would just need an GVfsUriMapper which delegates all protocols to this
single backend.

So if the solution is running Kio-GioBridge on Gnome and
GVfs-KioBridge on KDE, why not. :-)

Of course that means you don't get the benefits of GVFS on KDE (like
things appearing as mounts, connection pooling,...), but at least both
VFS APIs would be running on the same implementation in a desktop
session. That's the most important thing. :-)

> If one is already taking on such a huge tasks, why not try to design a common
> interface?
>

It's gonna take years, i'm afraid.

Norbert