We have moved to a new Sailfish OS Forum. Please start new discussions there.
31

App interoperability the Sailfish way. What is the way to share between apps (UI and API wise)?

asked 2014-01-23 12:52:30 +0300

Artem gravatar image

updated 2014-05-12 16:25:20 +0300

Simplest use case: You are using Tweetian or Friends and want to save a link to some read-it-later service, or share to a not built-in social network (Russian VKontakte or Chinese Weibo) or even to a built-in app such as Messaging or Email. Or you implement a whatsapp client and want to send photos from both local hardrive and dropbox/box/picasa/whatever-the-user-has.

To my understanding right now all of these use cases are simply not possible (except for starting email/sms with a given text via openUrlExternally).

What are the Sailfish longer term plans regarding it?
- Android-like intents to provide whichever service to whichever clients + few standard intents?
- iOS-like hard coded intents to the known applications that support it?
- Something Linux standard?

edit retag flag offensive close delete

Comments

1

+1 Such a function (similar to Android rather than iOS) is needed.

andreibechet ( 2014-05-12 18:36:39 +0300 )edit

2 Answers

Sort by » oldest newest most voted
2

answered 2014-05-12 22:58:20 +0300

tortoisedoc gravatar image

sharing via plugins is probably the closest match which I can recall.see transfer ui et co.

edit flag offensive delete publish link more
1

answered 2014-05-12 16:58:19 +0300

dsilveira gravatar image

Why do you think dbus does not fulfill your requirements?

edit flag offensive delete publish link more

Comments

3

Certainly that would work, but it requires you to know each and every service's dbus interface you need to connect to in advance. A more standardized (at an OS level) way to do it would be much better IMHO: if an app provides some sort of "share" functionality it register itself as a provider; on the other hand, if an app wants to share something, it can request a list of known providers and simply let the user choose which one to use.

donaggio ( 2014-05-12 17:54:00 +0300 )edit
2

D-Bus is missing a "find all objects implementing this interface" function. Never understood why it was left from the initial design.

javispedro ( 2014-05-13 03:07:26 +0300 )edit
1

I think first and foremost we should push for a dbus improvement in this regard.

Then, while we wait for it to be implemented, we build a workaround that registers every apps dbus interface on install, by introspection.

Then this register will itself publish an dbus interface, which can be used to query about available dbus services, etc.

Jolla could publish an standard expected interface, if required.

I just think, that we shouldn't reinvent the wheel, specially now that dbus is going zero-copy efficiency with kernel integration!

dsilveira ( 2014-05-14 17:43:55 +0300 )edit
Login/Signup to Answer

Question tools

Follow
4 followers

Stats

Asked: 2014-01-23 12:52:30 +0300

Seen: 444 times

Last updated: May 12 '14