Interface for Snappy Apps that understand Unity8 Application Lifecycle
Michał Sawicz
michal.sawicz at canonical.com
Mon May 30 12:23:13 UTC 2016
W dniu 27.05.2016 o 19:48, Ted Gould pisze:
> In a nutshell, it is listening to a set commands that are sent via the
> Mir connection from QtMir/Unity8 which correspond with the different
> states that an application is put in. As an example, it is told when it
> is about to be suspended so that the application can save data in memory
> to disk. For QML/Qt apps this is implemented in the QPA plugin.
> Applications that do not speak this protocol could lose user data if
> they were killed by Unity8 and didn't realize they needed to use their
> chance to save.
I just wonder if this is anything really unity8-specific. We've not
created special APIs (at least not compared to Qt ones), we're not
actively killing apps for no reason, it's just that we're more resource
constrained and OOM killer kicks in quicker. When closing apps, we do
tell apps, after waking them, when the user closes them, so they know
they need to save data (we're not giving them a chance to prevent
closing, at least not yet).
Well-behaved apps (LibreOffice, Firefox) do this already by periodically
saving restore information, would you consider those as "supporting the
unity8 lifecycle"?
--
Michał Sawicz <michal.sawicz at canonical.com>
Canonical Ltd.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/snapcraft/attachments/20160530/12d1ce0d/attachment.sig>
More information about the Snapcraft
mailing list