Bug 202053 - KDE protocols should be transparent to non-kde applications
Summary: KDE protocols should be transparent to non-kde applications
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-31 05:13 UTC by Parameshwara Bhat
Modified: 2024-09-14 16:18 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Parameshwara Bhat 2009-07-31 05:13:19 UTC
Version:           1.3 (using 4.2.98 (KDE 4.2.98 (KDE 4.3 RC3)) "release 150", KDE:KDE4:Factory:Desktop / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (i686) release 2.6.27.25-0.1-default

I open up an smb share in Dolphin.Now if I click on an OpenOffice file,it does not open in Openoffice as it does not know how to handle smb: protocol.This happens with any non-kde application,even Firefox.

KDEs protocol system could be flexible and nice for KDE,but not good for inter-operability at all.If I send a similar file from Nautilus to Koffice ,no such issue,as Gnome mounts network shares(any protocol results)to a File system location.Target application can find it.

The present scenario with OpenOffice can be addressed with OO specific patch,may be.But other non-kde applications will have problem.

KDE should address this exporting of internal protocols to non-kde applications in a manner transparent to any target non-kde application.May be this can get included in LSB.
Comment 1 Christoph Cullmann 2024-09-14 16:18:46 UTC
Hi,

kdelibs (version 4 and earlier) is no longer maintained since a few years.

KDE Frameworks 5 or 6 might already have implemented this wish.

If not, please re-open against the matching framework if feasible or against the application that shows the issue.

We then can still dispatch it to the right Bugzilla product or component.

Greetings
Christoph Cullmann