Yes. That is one case.
From: Marcin Mielniczuk [mailto:marmistrz...@gmail.com]
Sent: 19. helmikuuta 2018 9:55
To: Sailfish OS Developers; Kimmo Lindholm
Subject: Re: [SailfishDevel] Keep an application running without keeping the
window open
Do I understand correctly that the dbus daemons run
lmikuuta 2018 21.29
> *Vastaanottaja:* Adam Pigg ; Sailfish OS Developers
>
> *Aihe:* Re: [SailfishDevel] Keep an application running without
> keeping the window open
>
>
>
> Is there any minimal example I could take a look at? I've never done
> anything mor
] Puolesta Marcin
Mielniczuk
Lähetetty: sunnuntai 18. helmikuuta 2018 21.29
Vastaanottaja: Adam Pigg ; Sailfish OS Developers
Aihe: Re: [SailfishDevel] Keep an application running without keeping the
window open
Is there any minimal example I could take a look at? I've never done anything
more
Is there any minimal example I could take a look at? I've never done
anything more with dbus than dbus-send.
On 17.02.2018 22:06, Adam Pigg wrote:
> Hi
>
> You could create a dbus service for the application to talk to. The
> gui application can launch the dbus service if it isnt running, and
> c
Hi
You could create a dbus service for the application to talk to. The gui
application can launch the dbus service if it isnt running, and connect
next time it is opened, leaving it running in the background.
Adam
On Sat, 17 Feb 2018 at 20:58 rinigus wrote:
> Hi,
>
> from the point of view of
Hi,
from the point of view of portability, having a split GUI and backend
should be nicely portable. Even focusing on systemd would cover large
portion of Linux distributions, but you don't have to include any systemd
dependencies as such. On desktop, it would allow you to move the backend
into de
I'm not sure if that's a good choice when trying to achieve portability.
Usually on desktop you'd rather have a monolithic application with just
minimize to tray.
Any other options?
On 05.02.2018 10:33, rinigus wrote:
> Hi,
>
> the obvious solution is to run service that is 24/7 on and separate
Hi,
the obvious solution is to run service that is 24/7 on and separate client
for GUI. That's what stock messaging is doing. I would recommend it and use
some simple messaging API for communicating between them. There are
probably many APIs to choose that will allow you to set it up simply.
If y
Hi,
When creating SFOS applications which should run 24/7 (e.g. IMs) we
would like to achieve similar behavior as the stock applications, e.g.
the stock e-mail client: the sync (*) runs in the background, even
though the application is closed. A window staying open just to make
sure the sync goes
