Re: [SailfishDevel] Removing libcontextkit-statefs-qt5.so from allowed libraries
On Thursday, 14 May 2020 08.37 Pekka Vuorela wrote:
> On Wed, 2020-05-13 at 20:41 +0300, rinigus wrote:
> > Hi Pekka,
> >
> > with the respect of statefs plans, I would like to ask if it is
> > planned to phase out /run/state/namespaces/ API in future. I am using
> > it in collectd to log battery, bluetooth, cellular, and internet data
> > in the corresponding plugins.
>
> That depends on the statefs packages being installed. Since we're not
> talking about Harbour software, you can still explicitly pull them in.
> They might go away some day, but there's no immediate need for doing
> that.
>
> Alternative is to switch to other methods, e.g. dbus-send or more
> specific command line tools. Mcetool for example can tell the battery
> state among other things.
Just to be sure: The QML ContextProperty will not go away?
I use something like this in my apps:
QtObject {
property bool isOnline: state.value === 'connected'
property ContextProperty state: ContextProperty {
// `cat /run/state/namespaces/Internet/NetworkState`
key: 'Internet.NetworkState'
}
}
--
Med venlig hilsen / Best regards
Thomas Tanghus
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?
signature.asc
Description: This is a digitally signed message part.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Removing libcontextkit-statefs-qt5.so from allowed libraries
On Thu, 2020-05-14 at 09:03 +0200, Thomas Tanghus wrote:
> On Thursday, 14 May 2020 08.37 Pekka Vuorela wrote:
> > Alternative is to switch to other methods, e.g. dbus-send or more
> > specific command line tools. Mcetool for example can tell the
> > battery
> > state among other things.
>
> Just to be sure: The QML ContextProperty will not go away?
>
> I use something like this in my apps:
>
> QtObject {
> property bool isOnline: state.value === 'connected'
> property ContextProperty state: ContextProperty {
> // `cat /run/state/namespaces/Internet/NetworkState`
> key: 'Internet.NetworkState'
> }
> }
Yep, no changes there.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
[SailfishDevel] Sailfish OS, OSS community collab meeting, May 14th 2020 at 08:00 UTC
Hi everyone, Welcome to today's meeting! _*NOTE: the meeting is being held at our new meeting room #sailfishos-meeting*_ Date: 14/05/2020 Time: 08:00 UTC Duration: Approximately 40 minutes Chair: abranson Location: #sailfishos-meeting on freenode IRC http://webchat.freenode.net/ Topics: - Intro (5 min) -More useful python3 modules support (10 min) - General discussion (20 min) - Next meeting time & date (5 min) -- More details on the topics can be found here: https://together.jolla.com/question/54157/sailfishos-open-source-collaboration-meeting-planning/ Please familiarise yourself with them before the meeting, as well as the common Meetbot commandshttps://wiki.debian.org/MeetBot(it's used for meeting management and logging) Best regards, James ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Removing libcontextkit-statefs-qt5.so from allowed libraries
Sorry but I'm going to hijack this thread. If this is acceptable to you then why can't you just add a slew of other libs to harbour (mpris, mediakeys). If what you officially supported was rocksolid stable and no bugs and mpris had issues you might have had a case but I can tell you that gpodder was patched to work with mpris in 2017 the code was not modified since then and it's still working today, seemingly more stable then "officially supported" libs. Some food for thought in the weekend, Eli Op wo 13 mei 2020 om 17:34 schreef Pekka Vuorela : > Hello, > > As you might have noticed, we've been lately migrating away from the > Statefs based ContextKit API implementation. The QML interface already > got rewritten in 3.3.0 as a simpler version that doesn't need a > background daemon [1]. Ideally, and hopefully, applications using that > module should keep working as they used to. > > Alas, it didn't all go without glitches: the Jolla phone, tablet and > SDK are depending on bluez4 packages and a dependency problem related > to that slipped through the cracks [2]. It's fixed now and if we end up > doing a bug fix release for 3.3.0, that should be included there. > > What's been remaining is the c++ library, libcontextkit-statefs-qt5.so, > which is about to be removed from the allowed libraries [3]. Based on > our checks on Store app dependencies, that shouldn't affect too many. > We found only two applications from a single developer and have > contacted him. The usage on those didn't either seem too hard to > migrate to QML or other API. So all in all it hasn't appeared worth it > providing a c++ compatibility library for this little use. > > This as heads up. Please comment if you have any concerns. > > [1] https://git.sailfishos.org/mer-core/nemo-qml-plugin-contextkit > [2] > > https://git.sailfishos.org/mer-core/nemo-qml-plugin-contextkit/merge_requests/4 > [3] https://github.com/sailfishos/sdk-harbour-rpmvalidator/pull/120 > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
