Re: [SailfishDevel] Qt5SystemInfo status

[jollailija]

Riku kirjoitti ke tammikuuta 13 03:44:04 2016 GMT+0200:
>  
> Are there good examples of dbus handling from qml apps?
> 

Sorry to hijack your topic, but I'd also like to see some examples of dbus 
usage, especially MPRIS in qml (I'm implementing lockscreen media button 
support)

-- 
Lähetetty Jollastani
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Qt5SystemInfo status

[Riku]

Hi!

Thank you for the hints. I will read taot code to get deeper understanding. 

Are there good examples of dbus handling from qml apps?

Riku

Кожевников Андрей Андреевич kirjoitti ti tammikuuta 12 14:01:34 2016 GMT+0200:
> you can read /etc/sailfish-version and etc.
> 
> 12.01.2016 18:00, Oleksii Serdiuk пишет:
> > Well, just for getting cell info - yes, should be enough to query 
> > ofono(?) through dbus.
> >
> > For my case, Inned more info, like device model, OS version, etc. So 
> > custom-built libQt5SystemInfo.so.5 is a drop-in replacement until Qt 
> > SystemInfo gets whitelisted: I'll only have to remove it from the RPM 
> > without needing to change anything in my app.
> >
> > On 12/01/16 12:53, Кожевников Андрей Андреевич wrote:
> >> In most cases you can fetch information using dbus calls without using
> >> systeminfo lib.
> >>
> >> 12.01.2016 17:51, Oleksii Serdiuk пишет:
> >>> I've had a similar issue: I needed Qt SystemInfo to integrate
> >>> analytics into my app.
> >>>
> >>> The recommended way to solve linking against non-whitelisted
> >>> libraries, is to ship them together with your app. However, just
> >>> taking libQt5SystemInfo.so.5 from Sailfish repos and putting it into
> >>> your RPM won't work: it links against other non-whitelisted libraries
> >>> (namely, SSU, and SSU links further). So my solution was to build a
> >>> custom version of libQt5SystemInfo.so.5, which excludes
> >>> non-whitelisted libs.
> >>>
> >>> The source for Sailfish version of Qt SystemInfo is available here:
> >>> https://git.merproject.org/mer-core/qtsystems
> >>>
> >>> I don't remember the qmake flags exactly (I can check them when I'm
> >>> back home, if you need), but I think they were:
> >>> > qmake CONFIG+=ofono CONFIG+=nox11option
> >>>
> >>> This will produce Harbour-compatible version of libQt5SystemInfo.so.5
> >>> which you can link against and include into you RPM.
> >>>
> >>> Or, you can reuse my version of it. It's available here:
> >>> https://olse.me/taot
> >>>
> >>> libQt5SystemInfo.so.5 is in rpm/lib/ folder. You can take a look
> >>> at taot.pro (lines 263-264, 278, and 284), rpm/harbour-taot.yaml (line
> >>> 44), and rpm/harbour-taot.spec to see how I include the lib into RPM.
> >>>
> >>> On 11/01/16 03:29, Riku Lahtinen wrote:
>  Hi!
> 
>  I developed an app At Work, which records the time you stay at work by
>  using GPS. Because of the poor GPS functionality in buildings and
>  response of the app users I added a feature to utilize a cell
>  information also. For that I needed to import QtSystemInfo 5.0. I got
>  that to work by inserting two lines to spec file and everything 
>  seems to
>  be working. Though the app doesn't pass the Jolla Harbour rpm check,
>  because QtSysteminfo is not accepted in the test.
> 
>  Does anybody know when QtSystemInfo is accepted to be used or are 
>  there
>  other paths to proceed? I know OpenRepos is one way but I like the 
>  work
>  they do in Jolla Harbour very much to increase the reliability of our
>  software.
> 
>  Best Regards
> 
>  Riku
> >
> 
> ___
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.or

-- 
Lähetetty Jollastani
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Transient notification categories

[Andrew Branson]

Hello,

Yes I did, but that's more geared towards an application that publishes its own notifications, 
rather than eavesdropping on them like pebbled is. I found the most relevant info in QtCreator 
help under Lipstick>Related Pages>Notifications, which said "If a notification is 
intended to have no presence in the events view, it should set the 'transient' hint to true. 
This will cause it to be closed immediately after it has been displayed to the user.".

Thanks,

Andrew


On 12/01/2016 12:26 pm, Alexander Ladygin wrote:

Hei Andrew,

did you check 
https://sailfishos.org/develop/docs/nemo-qml-plugin-notifications/ ?

On Mon, Jan 11, 2016 at 11:09 PM, Andrew Branson mailto:andrew.bran...@cern.ch>> wrote:

Hi,

I'm trying to improve the filtering of notifications in the pebble daemon 
for Sailfish, and I stumbled upon the category property 'transient' in the 
QtCreator docs which it said indicated that a notification would only be 
flashed at the top of the screen and not left in the Events view. I thought 
that would be a good indicator of whether the notification should be forwarded 
to the watch, so I did that, but after that no messaging notifications were 
coming through at  all. I checked the category files, and all of the messaging 
preview categories have the transient property set, even though they are 
persistent on the Events view. Can anyone tell me what's going on here? How 
does the system decide which notifications end up on the events view?

Is there additional documentation about the notification system anywhere 
that I don't know about? Someone mentioned that a new notification model in 
SF2.0 would let us sidestep the '2 new messages' notification and get the real 
preview text, so I'd like to find out about that too.


Thanks very much,

Andrew
___
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


___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Qt5SystemInfo status

[Кожевников Андрей Андреевич]

you can read /etc/sailfish-version and etc.

12.01.2016 18:00, Oleksii Serdiuk пишет:
Well, just for getting cell info - yes, should be enough to query 
ofono(?) through dbus.


For my case, Inned more info, like device model, OS version, etc. So 
custom-built libQt5SystemInfo.so.5 is a drop-in replacement until Qt 
SystemInfo gets whitelisted: I'll only have to remove it from the RPM 
without needing to change anything in my app.


On 12/01/16 12:53, Кожевников Андрей Андреевич wrote:

In most cases you can fetch information using dbus calls without using
systeminfo lib.

12.01.2016 17:51, Oleksii Serdiuk пишет:

I've had a similar issue: I needed Qt SystemInfo to integrate
analytics into my app.

The recommended way to solve linking against non-whitelisted
libraries, is to ship them together with your app. However, just
taking libQt5SystemInfo.so.5 from Sailfish repos and putting it into
your RPM won't work: it links against other non-whitelisted libraries
(namely, SSU, and SSU links further). So my solution was to build a
custom version of libQt5SystemInfo.so.5, which excludes
non-whitelisted libs.

The source for Sailfish version of Qt SystemInfo is available here:
https://git.merproject.org/mer-core/qtsystems

I don't remember the qmake flags exactly (I can check them when I'm
back home, if you need), but I think they were:
> qmake CONFIG+=ofono CONFIG+=nox11option

This will produce Harbour-compatible version of libQt5SystemInfo.so.5
which you can link against and include into you RPM.

Or, you can reuse my version of it. It's available here:
https://olse.me/taot

libQt5SystemInfo.so.5 is in rpm/lib/ folder. You can take a look
at taot.pro (lines 263-264, 278, and 284), rpm/harbour-taot.yaml (line
44), and rpm/harbour-taot.spec to see how I include the lib into RPM.

On 11/01/16 03:29, Riku Lahtinen wrote:

Hi!

I developed an app At Work, which records the time you stay at work by
using GPS. Because of the poor GPS functionality in buildings and
response of the app users I added a feature to utilize a cell
information also. For that I needed to import QtSystemInfo 5.0. I got
that to work by inserting two lines to spec file and everything 
seems to

be working. Though the app doesn't pass the Jolla Harbour rpm check,
because QtSysteminfo is not accepted in the test.

Does anybody know when QtSystemInfo is accepted to be used or are 
there
other paths to proceed? I know OpenRepos is one way but I like the 
work

they do in Jolla Harbour very much to increase the reliability of our
software.

Best Regards

Riku




___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Qt5SystemInfo status

[Oleksii Serdiuk]

Well, just for getting cell info - yes, should be enough to query 
ofono(?) through dbus.


For my case, Inned more info, like device model, OS version, etc. So 
custom-built libQt5SystemInfo.so.5 is a drop-in replacement until Qt 
SystemInfo gets whitelisted: I'll only have to remove it from the RPM 
without needing to change anything in my app.


On 12/01/16 12:53, Кожевников Андрей Андреевич wrote:

In most cases you can fetch information using dbus calls without using
systeminfo lib.

12.01.2016 17:51, Oleksii Serdiuk пишет:

I've had a similar issue: I needed Qt SystemInfo to integrate
analytics into my app.

The recommended way to solve linking against non-whitelisted
libraries, is to ship them together with your app. However, just
taking libQt5SystemInfo.so.5 from Sailfish repos and putting it into
your RPM won't work: it links against other non-whitelisted libraries
(namely, SSU, and SSU links further). So my solution was to build a
custom version of libQt5SystemInfo.so.5, which excludes
non-whitelisted libs.

The source for Sailfish version of Qt SystemInfo is available here:
https://git.merproject.org/mer-core/qtsystems

I don't remember the qmake flags exactly (I can check them when I'm
back home, if you need), but I think they were:
> qmake CONFIG+=ofono CONFIG+=nox11option

This will produce Harbour-compatible version of libQt5SystemInfo.so.5
which you can link against and include into you RPM.

Or, you can reuse my version of it. It's available here:
https://olse.me/taot

libQt5SystemInfo.so.5 is in rpm/lib/ folder. You can take a look
at taot.pro (lines 263-264, 278, and 284), rpm/harbour-taot.yaml (line
44), and rpm/harbour-taot.spec to see how I include the lib into RPM.

On 11/01/16 03:29, Riku Lahtinen wrote:

Hi!

I developed an app At Work, which records the time you stay at work by
using GPS. Because of the poor GPS functionality in buildings and
response of the app users I added a feature to utilize a cell
information also. For that I needed to import QtSystemInfo 5.0. I got
that to work by inserting two lines to spec file and everything seems to
be working. Though the app doesn't pass the Jolla Harbour rpm check,
because QtSysteminfo is not accepted in the test.

Does anybody know when QtSystemInfo is accepted to be used or are there
other paths to proceed? I know OpenRepos is one way but I like the work
they do in Jolla Harbour very much to increase the reliability of our
software.

Best Regards

Riku


--
With best regards,
Oleksii Serdiuk
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Qt5SystemInfo status

[Кожевников Андрей Андреевич]

In most cases you can fetch information using dbus calls without using 
systeminfo lib.


12.01.2016 17:51, Oleksii Serdiuk пишет:
I've had a similar issue: I needed Qt SystemInfo to integrate 
analytics into my app.


The recommended way to solve linking against non-whitelisted 
libraries, is to ship them together with your app. However, just 
taking libQt5SystemInfo.so.5 from Sailfish repos and putting it into 
your RPM won't work: it links against other non-whitelisted libraries 
(namely, SSU, and SSU links further). So my solution was to build a 
custom version of libQt5SystemInfo.so.5, which excludes 
non-whitelisted libs.


The source for Sailfish version of Qt SystemInfo is available here:
https://git.merproject.org/mer-core/qtsystems

I don't remember the qmake flags exactly (I can check them when I'm 
back home, if you need), but I think they were:

> qmake CONFIG+=ofono CONFIG+=nox11option

This will produce Harbour-compatible version of libQt5SystemInfo.so.5 
which you can link against and include into you RPM.


Or, you can reuse my version of it. It's available here:
https://olse.me/taot

libQt5SystemInfo.so.5 is in rpm/lib/ folder. You can take a look 
at taot.pro (lines 263-264, 278, and 284), rpm/harbour-taot.yaml (line 
44), and rpm/harbour-taot.spec to see how I include the lib into RPM.


On 11/01/16 03:29, Riku Lahtinen wrote:

Hi!

I developed an app At Work, which records the time you stay at work by
using GPS. Because of the poor GPS functionality in buildings and
response of the app users I added a feature to utilize a cell
information also. For that I needed to import QtSystemInfo 5.0. I got
that to work by inserting two lines to spec file and everything seems to
be working. Though the app doesn't pass the Jolla Harbour rpm check,
because QtSysteminfo is not accepted in the test.

Does anybody know when QtSystemInfo is accepted to be used or are there
other paths to proceed? I know OpenRepos is one way but I like the work
they do in Jolla Harbour very much to increase the reliability of our
software.

Best Regards

Riku




___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Qt5SystemInfo status

[Oleksii Serdiuk]

I've had a similar issue: I needed Qt SystemInfo to integrate analytics 
into my app.


The recommended way to solve linking against non-whitelisted libraries, 
is to ship them together with your app. However, just taking 
libQt5SystemInfo.so.5 from Sailfish repos and putting it into your RPM 
won't work: it links against other non-whitelisted libraries (namely, 
SSU, and SSU links further). So my solution was to build a custom 
version of libQt5SystemInfo.so.5, which excludes non-whitelisted libs.


The source for Sailfish version of Qt SystemInfo is available here:
https://git.merproject.org/mer-core/qtsystems

I don't remember the qmake flags exactly (I can check them when I'm back 
home, if you need), but I think they were:

> qmake CONFIG+=ofono CONFIG+=nox11option

This will produce Harbour-compatible version of libQt5SystemInfo.so.5 
which you can link against and include into you RPM.


Or, you can reuse my version of it. It's available here:
https://olse.me/taot

libQt5SystemInfo.so.5 is in rpm/lib/ folder. You can take a look 
at taot.pro (lines 263-264, 278, and 284), rpm/harbour-taot.yaml (line 
44), and rpm/harbour-taot.spec to see how I include the lib into RPM.


On 11/01/16 03:29, Riku Lahtinen wrote:

Hi!

I developed an app At Work, which records the time you stay at work by
using GPS. Because of the poor GPS functionality in buildings and
response of the app users I added a feature to utilize a cell
information also. For that I needed to import QtSystemInfo 5.0. I got
that to work by inserting two lines to spec file and everything seems to
be working. Though the app doesn't pass the Jolla Harbour rpm check,
because QtSysteminfo is not accepted in the test.

Does anybody know when QtSystemInfo is accepted to be used or are there
other paths to proceed? I know OpenRepos is one way but I like the work
they do in Jolla Harbour very much to increase the reliability of our
software.

Best Regards

Riku


--
With best regards,
Oleksii Serdiuk
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Transient notification categories

[Alexander Ladygin]

Hei Andrew,

did you check
https://sailfishos.org/develop/docs/nemo-qml-plugin-notifications/ ?

On Mon, Jan 11, 2016 at 11:09 PM, Andrew Branson 
wrote:

> Hi,
>
> I'm trying to improve the filtering of notifications in the pebble daemon
> for Sailfish, and I stumbled upon the category property 'transient' in the
> QtCreator docs which it said indicated that a notification would only be
> flashed at the top of the screen and not left in the Events view. I thought
> that would be a good indicator of whether the notification should be
> forwarded to the watch, so I did that, but after that no messaging
> notifications were coming through at  all. I checked the category files,
> and all of the messaging preview categories have the transient property
> set, even though they are persistent on the Events view. Can anyone tell me
> what's going on here? How does the system decide which notifications end up
> on the events view?
>
> Is there additional documentation about the notification system anywhere
> that I don't know about? Someone mentioned that a new notification model in
> SF2.0 would let us sidestep the '2 new messages' notification and get the
> real preview text, so I'd like to find out about that too.
>
>
> Thanks very much,
>
> Andrew
> ___
> 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