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

[nf2]

On Sun, Nov 1, 2009 at 6:33 PM, Dario Freddi <drf54321 at gmail.com> wrote:
> On Sunday 01 November 2009 17:50:56 nf2 wrote:
>> 1) Putting a different label on an already existing system, like I
>> would suggest: "This ist the standard system for the major
>> file-management protocols, thanks, problem solved". Technically easy,
>> but won't work because there are understandably different opinions on
>> which one to pick.
>
> Renaming is technically easy. What about porting? What about kio_http and
> protocols not supported by GIO?

HTTP is an important protocol, but not so much for basic
file-management. You will hardly run across it in Dolphin or in
file-choosers. And where it is, it's probably just downloading a file
via HTTP GET, which is provided by both systems already. The extra
features kio_http provides, are tailored for certain KDE apps using
them. So there is no reason to change the status-quo here (But it's
relationship with webdav might be a challenge).

Regarding the protocols not supported by GVFS: That's an interesting
issue. Which of them do you think are related to "general
file-management"? I can see two: nfs: and fish:  (At least from
looking at kdelibs and kdebase).


>
> Sorry, but I keep seeing my solution as the only feasible way, from every
> point of view, and you still did not put any relevant point to confutate this.
>
> Every solution you proposed had the word "replace", except from mine, which is
> already quite an indicator of the technical difficulty. Do you think it is
> really so hard to write an API and 2 wrappers, especially compared to rename a
> framework and port every existing linux application to it? With my proposal
> you would have to touch ~0 lines of code in applications relying on KIO or GIO
> and just use the new API on 3rd party apps (and eventually write bridges for
> better integration)
>

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?

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).

Regards,
Norbert