Re: [SailfishDevel] Starting point for a Swype-like keyboard
Hi, How about using QML and MultiPointTouchArea as a starting point to get the touch data? Probably you are more interested in Qt... Seppo 2014-04-16 9:58 GMT+03:00 Vivia Nikolaidou : > Hi all, and thanks a lot for your replies! > > We did investigate the patents before deciding to start the project > and they do indeed seem to be US-only. So, as long as Jolla isn't even > available in the US, everything should be fine. > > On the other hand, just to be on the safe side, we thought about > leaving it in "beta-proof-of-concept" stage, or at least labelling it > as such, and not promoting it (word of mouth should be enough to make > it reach the devices of those who really want it). After all, patents > only apply for things like sales and exporting, not for "academic > purposes". If someone with access to a patent lawyer would like to > investigate things and help it turn into a real project, this help > would be more than welcome, but unfortunately we don't have such > resources. > > As for github/gitorious, we'll gladly share it when there's something > worthwhile, but without being able to get actual raw data from a > finger drawing a curve, there's not much coding that can be done. So > we'd really appreciate it if someone could give us a hint. :) > > Thanks again, > > Vivia > > On 15 April 2014 22:38, wrote: > > But how does it work for the other swype like keyboards available for > android? > > > > I can't see any differences to the original one. > > > > Am Tue Apr 15 2014 20:49:46 GMT+0200 (CEST) schrieb Michael Doube: > >> On 15/04/14 19:39, Martin Kolman wrote: > >> >> A quick look at the bottom of the Wikipedia entry for Swype confirms > >> >> my suspicion... (2 US patents). :-( > >> > Well, they look like to be US patents - so considering the Jolla is > not > >> > even sold in the USA & it would be an external application anyway, I > >> > don't really see any issue. > >> > >> Well, I wouldn't want the Jolla team to find themselves in hot water for > >> distributing unlicensed functionality on the Harbour site. Nor the > >> external application developer for implementing and publishing it, maybe > >> even for a fee. Since Swype made a US patent, and their product is > >> distributed worldwide, I would expect to find some European patents too > >> (not being listed on Wikipedia is not authoritative evidence of > >> non-existence). Anyway, this is non-expert handwaving. If there is a > >> legal way to get something Swype-like on the Jolla, it would be great. > >> > >> Michael > >> > >> ___ > >> SailfishOS.org Devel mailing list > >> > > > > -- > > Gesendet von meinem Jolla > > ___ > > SailfishOS.org Devel mailing list > ___ > SailfishOS.org Devel mailing list > ___ SailfishOS.org Devel mailing list
[SailfishDevel] Indian characters
Hi, I hear Jolla will be available in India soon. When will the Devanaagarii character set (Hindi/Sanskrit) be available in the OS. As far as I can tell, such 'code page' does not exist in the latest SailfishOS update, or does it? Regards, Seppo ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] SymPy and SailfishOS Unicode fonts - link fixed
Any news about the availability Devanagari characters (for Hindi and Sanskrit in India)? Seppo 2014-05-05 5:18 GMT+03:00 Roberto Colistete Jr. : > Obs.: fixed the link. > >Hi, > > As we can see in the screenshot of FingerTerm running IPython (0.13.2) > with SymPy 0.7.5, mathematical symbols are not show correctly. A workaround > is to disable Unicode. > > So I repeat my suggestion below, to have "DejaVu Sans Mono" font > available in Sailfish OS. And FingerTerm able to change the font. > > About SymPy 0.7.5 for Sailfish : > https://openrepos.net/content/rcolistete/sympy-sailfishos > > Best regards, > > Roberto > > Mensagem original Assunto: Re: [SailfishDevel] > SailfishOS code pages not completed yet? Data: Fri, 27 Sep 2013 21:04:13 > -0300 De: Roberto Colistete Jr. > CC: devel@lists.sailfishos.org > > > Hi, > > Another suggestion : add "DejaVu Sans Mono" font so we can better show > mathematical symbols in Sailfish OS. > > Regards, Roberto > > Em 06-09-2013 02:34, Seppo Tiainen escreveu: > > Hi, > > > > Still hoping to have a more complete implementation of the character > > sets on SailfishOS: > > > > 1) It seems that unicodes u2190... u2193 (arrow key arrow signs) have > > been implemented in SailfishOS but the codes for arrow symbols do not > > extend as far as in Harmattan because some important signs are still > > missing like the Shift sign (broad arrow up, u21e7) and Caps lock sign > > (cut broad arrow up). > > > > 2) Devanagari symbols (essential in India) are missing completely even > > if they were there on Harmattan. > > > > 3) In addition, it would be nice to be able to output technical > > symbols like upsilon (ϒ, u03d2), theta (ϑ) and phi (ϕ, u03d5) even if > > these do not work on Harmattan. > > > > Cheers, > > Seppo > > > > > > > > ___ > SailfishOS.org Devel mailing list > ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
[SailfishDevel] QML support of Multitouch
What I have been missing most in QML is multitouch support. Only Qt 5.0 has QML MultiPointTouchArea but Sailfish is using Qt 4.8. In Harmattan, I was able to read multiple touch points by Lauri Jääskeläinen's QmlMultiTouch code ( http://www.developer.nokia.com/Community/Blogs/blog/lauri-jaaskelas-forum-nokia-blog/2011/02/03/raw-multitouch-pointer-events-in-qml) where a new class (TouchApplicationViewer) is inherited from QmlApplicationViewer, and viewportEvent(QEvent*) method is reimplemented. The code also implements a class MultiTouch which exposes a list of touch points to QML. Now that I'm planning to port my app from Harmattan to Sailfish I'm having problems dealing with view and installing multitouch in main.cpp of Sailfish/Silica. Any ideas how to do that? Or, would it be possible to have a TouchArea library or plugin for Sailfish QtCreator (next update)? I think being able to easily deal with multiple touch points in QML is one of the key features needed while developing interesting Qt apps for modern smartphones. A sample code for main.cpp or Sailfish QtCreator lib upgrade/plugin would be great! - tiptyper ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] QML support of Multitouch
Hi Lucien and Jonni, Thanks for your help guys. I appreciate very much having your advice and a working framework which I can use as a starting point while porting my app to Sailfish OS. Seppo 2013/3/19 Jonni Rainisto > Hi Seppo, > > Lauri's example should work pretty much unmodified, and I did a very quick > hack Sailfish example code in gitorious: > > https://gitorious.org/sailfishtouchexample/sailfishtouchexample > > That seems to work at least on those armhf Sailfish devices that I have > access to. For SDK that example does not work, since currently SDK does not > report any QTouchEvents, ie. SDK only reports mouse events. But if at some > point there is armhf rootfs released, then it might be useful to you. And I > only tested portrait mode, one might or might not need to do some x y > tweaking for mapping raw events other QML orientations. > > re, Jonni > > From: devel-boun...@lists.sailfishos.org [ > devel-boun...@lists.sailfishos.org] on behalf of Lucien XU [ > sfietkonstan...@free.fr] > Sent: Wednesday, March 13, 2013 10:18 PM > To: devel@lists.sailfishos.org > Subject: Re: [SailfishDevel] QML support of Multitouch > > Hello Seppo, > > Instead of subclassing QmlApplicationViewer, did you ever tried to just > subclass a QDeclarativeView, and add the given code from your link to that > subclass ? It should work. > > Cheers, > Lucien > > Le mercredi 6 mars 2013 10:48:15 Seppo Tiainen a écrit : > > What I have been missing most in QML is multitouch support. Only Qt 5.0 > has > > QML MultiPointTouchArea but Sailfish is using Qt 4.8. In Harmattan, I was > > able to read multiple touch points by Lauri Jääskeläinen's QmlMultiTouch > > code ( > > > http://www.developer.nokia.com/Community/Blogs/blog/lauri-jaaskelas-forum-no > > kia-blog/2011/02/03/raw-multitouch-pointer-events-in-qml) where a new > class > > (TouchApplicationViewer) is inherited from > > QmlApplicationViewer, and viewportEvent(QEvent*) method is reimplemented. > > The code also implements a class MultiTouch which exposes a list of touch > > points to QML. > > > > Now that I'm planning to port my app from Harmattan to Sailfish I'm > having > > problems dealing with view and installing multitouch in main.cpp of > > Sailfish/Silica. Any ideas how to do that? Or, would it be possible to > have > > a TouchArea library or plugin for Sailfish QtCreator (next update)? I > think > > being able to easily deal with multiple touch points in QML is one of the > > key features needed while developing interesting Qt apps for modern > > smartphones. A sample code for main.cpp or Sailfish QtCreator lib > > upgrade/plugin would be great! > > > > - tiptyper > ___ > SailfishOS.org Devel mailing list > ___ > SailfishOS.org Devel mailing list > ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] QML support of Multitouch
Still, being able generate touch events in the next update of QtCreator's Sailfish OS Emulator would surely be welcomed by many... Seppo 2013/3/20 Seppo Tiainen > Hi Lucien and Jonni, > > Thanks for your help guys. I appreciate very much having your advice and a > working framework which I can use as a starting point while porting my app > to Sailfish OS. > > Seppo > > > 2013/3/19 Jonni Rainisto > >> Hi Seppo, >> >> Lauri's example should work pretty much unmodified, and I did a very >> quick hack Sailfish example code in gitorious: >> >> https://gitorious.org/sailfishtouchexample/sailfishtouchexample >> >> That seems to work at least on those armhf Sailfish devices that I have >> access to. For SDK that example does not work, since currently SDK does not >> report any QTouchEvents, ie. SDK only reports mouse events. But if at some >> point there is armhf rootfs released, then it might be useful to you. And I >> only tested portrait mode, one might or might not need to do some x y >> tweaking for mapping raw events other QML orientations. >> >> re, Jonni >> >> From: devel-boun...@lists.sailfishos.org [ >> devel-boun...@lists.sailfishos.org] on behalf of Lucien XU [ >> sfietkonstan...@free.fr] >> Sent: Wednesday, March 13, 2013 10:18 PM >> To: devel@lists.sailfishos.org >> Subject: Re: [SailfishDevel] QML support of Multitouch >> >> Hello Seppo, >> >> Instead of subclassing QmlApplicationViewer, did you ever tried to just >> subclass a QDeclarativeView, and add the given code from your link to that >> subclass ? It should work. >> >> Cheers, >> Lucien >> >> Le mercredi 6 mars 2013 10:48:15 Seppo Tiainen a écrit : >> > What I have been missing most in QML is multitouch support. Only Qt 5.0 >> has >> > QML MultiPointTouchArea but Sailfish is using Qt 4.8. In Harmattan, I >> was >> > able to read multiple touch points by Lauri Jääskeläinen's QmlMultiTouch >> > code ( >> > >> http://www.developer.nokia.com/Community/Blogs/blog/lauri-jaaskelas-forum-no >> > kia-blog/2011/02/03/raw-multitouch-pointer-events-in-qml) where a new >> class >> > (TouchApplicationViewer) is inherited from >> > QmlApplicationViewer, and viewportEvent(QEvent*) method is >> reimplemented. >> > The code also implements a class MultiTouch which exposes a list of >> touch >> > points to QML. >> > >> > Now that I'm planning to port my app from Harmattan to Sailfish I'm >> having >> > problems dealing with view and installing multitouch in main.cpp of >> > Sailfish/Silica. Any ideas how to do that? Or, would it be possible to >> have >> > a TouchArea library or plugin for Sailfish QtCreator (next update)? I >> think >> > being able to easily deal with multiple touch points in QML is one of >> the >> > key features needed while developing interesting Qt apps for modern >> > smartphones. A sample code for main.cpp or Sailfish QtCreator lib >> > upgrade/plugin would be great! >> > >> > - tiptyper >> ___ >> SailfishOS.org Devel mailing list >> ___ >> SailfishOS.org Devel mailing list >> > > ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] QML support of Multitouch
In addtition to generating touch events (multi or single), it seems it is not possible to change the device orientation in the SDK's Sailfish OS Emulator either. Is this true or is there a way to test switching between portrait and landscape orientations? 2013/3/24 Seppo Tiainen > Still, being able generate touch events in the next update of QtCreator's > Sailfish OS Emulator would surely be welcomed by many... > > Seppo > > > 2013/3/20 Seppo Tiainen > >> Hi Lucien and Jonni, >> >> Thanks for your help guys. I appreciate very much having your advice and >> a working framework which I can use as a starting point while porting my >> app to Sailfish OS. >> >> Seppo >> >> >> 2013/3/19 Jonni Rainisto >> >>> Hi Seppo, >>> >>> Lauri's example should work pretty much unmodified, and I did a very >>> quick hack Sailfish example code in gitorious: >>> >>> https://gitorious.org/sailfishtouchexample/sailfishtouchexample >>> >>> That seems to work at least on those armhf Sailfish devices that I have >>> access to. For SDK that example does not work, since currently SDK does not >>> report any QTouchEvents, ie. SDK only reports mouse events. But if at some >>> point there is armhf rootfs released, then it might be useful to you. And I >>> only tested portrait mode, one might or might not need to do some x y >>> tweaking for mapping raw events other QML orientations. >>> >>> re, Jonni >>> >>> From: devel-boun...@lists.sailfishos.org [ >>> devel-boun...@lists.sailfishos.org] on behalf of Lucien XU [ >>> sfietkonstan...@free.fr] >>> Sent: Wednesday, March 13, 2013 10:18 PM >>> To: devel@lists.sailfishos.org >>> Subject: Re: [SailfishDevel] QML support of Multitouch >>> >>> Hello Seppo, >>> >>> Instead of subclassing QmlApplicationViewer, did you ever tried to just >>> subclass a QDeclarativeView, and add the given code from your link to >>> that >>> subclass ? It should work. >>> >>> Cheers, >>> Lucien >>> >>> Le mercredi 6 mars 2013 10:48:15 Seppo Tiainen a écrit : >>> > What I have been missing most in QML is multitouch support. Only Qt >>> 5.0 has >>> > QML MultiPointTouchArea but Sailfish is using Qt 4.8. In Harmattan, I >>> was >>> > able to read multiple touch points by Lauri Jääskeläinen's >>> QmlMultiTouch >>> > code ( >>> > >>> http://www.developer.nokia.com/Community/Blogs/blog/lauri-jaaskelas-forum-no >>> > kia-blog/2011/02/03/raw-multitouch-pointer-events-in-qml) where a new >>> class >>> > (TouchApplicationViewer) is inherited from >>> > QmlApplicationViewer, and viewportEvent(QEvent*) method is >>> reimplemented. >>> > The code also implements a class MultiTouch which exposes a list of >>> touch >>> > points to QML. >>> > >>> > Now that I'm planning to port my app from Harmattan to Sailfish I'm >>> having >>> > problems dealing with view and installing multitouch in main.cpp of >>> > Sailfish/Silica. Any ideas how to do that? Or, would it be possible to >>> have >>> > a TouchArea library or plugin for Sailfish QtCreator (next update)? I >>> think >>> > being able to easily deal with multiple touch points in QML is one of >>> the >>> > key features needed while developing interesting Qt apps for modern >>> > smartphones. A sample code for main.cpp or Sailfish QtCreator lib >>> > upgrade/plugin would be great! >>> > >>> > - tiptyper >>> ___ >>> SailfishOS.org Devel mailing list >>> ___ >>> SailfishOS.org Devel mailing list >>> >> >> > ___ SailfishOS.org Devel mailing list
[SailfishDevel] SailfishOS code pages not completed yet?
Hi, Still hoping to have a more complete implementation of the character sets on SailfishOS: 1) It seems that unicodes u2190... u2193 (arrow key arrow signs) have been implemented in SailfishOS but the codes for arrow symbols do not extend as far as in Harmattan because some important signs are still missing like the Shift sign (broad arrow up, u21e7) and Caps lock sign (cut broad arrow up). 2) Devanagari symbols (essential in India) are missing completely even if they were there on Harmattan. 3) In addition, it would be nice to be able to output technical symbols like upsilon (ϒ, u03d2), theta (ϑ) and phi (ϕ, u03d5) even if these do not work on Harmattan. Cheers, Seppo ___ SailfishOS.org Devel mailing list
[SailfishDevel] Managing screen resolution
The SailfishOS SDK (Qt5 Alpha) assumes a screen resolution of 854 × 480 which is the same as on N9. It seems, however, the first Jolla device will have a 960 × 540 pixel display. How should one prepare for that? I have understood that the current advice is to use 16:9 aspect ratio and no hard-coding in number of pixels. But if you are porting an app that has been hard-coded for N9 screen size, what is the best approach? 1) Will there be a global parameter to fix the 'magnification'? (would be great!) 2) Is there any other way to fix the resolution easily? 3) Should the whole app UI be redesigned? (would be a lot of work...) Seppo ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Managing screen resolution
Ok. I made all dimensions of the objects (many!) on the screen dependent on the resolution. So the last thing to do will be getting the device-dependent resolution value to QML which should be no problem in the next version of the SDK, I guess. Seppo 2013/10/11 Jarko Vihriala > Hello, > This resolution is updated to match real device and this change is > delivered in next SDK update. This SDK update is already undergoing tests > so we should be able to release it soon. > > In general apps should not use fixed values of device screen but use > relative bindings. > > thanks, Jarko > > From: devel-boun...@lists.sailfishos.org [ > devel-boun...@lists.sailfishos.org] on behalf of Seppo Tiainen [ > seppo.tiai...@gmail.com] > Sent: Friday, October 11, 2013 7:29 AM > To: devel@lists.sailfishos.org > Subject: [SailfishDevel] Managing screen resolution > > The SailfishOS SDK (Qt5 Alpha) assumes a screen resolution of 854 × 480 > which is the same as on N9. It seems, however, the first Jolla device will > have a 960 × 540 pixel display. How should one prepare for that? I have > understood that the current advice is to use 16:9 aspect ratio and no > hard-coding in number of pixels. > > But if you are porting an app that has been hard-coded for N9 screen size, > what is the best approach? > > 1) Will there be a global parameter to fix the 'magnification'? (would be > great!) > 2) Is there any other way to fix the resolution easily? > 3) Should the whole app UI be redesigned? (would be a lot of work...) > > Seppo > ___ SailfishOS.org Devel mailing list
[SailfishDevel] Status of Sailfish SMS?
Hi, Does anybody know about a possible module and its status in Sailfish/Qt-5 that corresponds to Harmattan Qt Mobility Messaging so that it would be possible to send and receive SMSs (which is essential in my app) through Qt/QML on the Jolla phone? Thanks, Seppo ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Status of Sailfish SMS?
Yes, that's the way to go. In Harmattan QML, there were:
Qt.openUrlExternally("tel:012345x") for calls, and
Qt.openUrlExternally("sms:01234567444" + "?body=" + "bodytext") for SMSs.
The latter did not work for me so I had to use Harmattan c++ Qt Messaging:
QMessage sms;
sms.setType(QMessage::Sms);
sms.setBody(message);
iMessageService.compose(sms);
All these would open the default phone call or text messaging application
for the user to do the final decision.
I'm just wondering if these or similar tools will be made available on
SailfishOS. I haven't seen any yet.
Any observations? Will SMS messaging tools, along the lines above, be
available for Sailfish app development?
Cheers,
Seppo
2013/11/13 Jonni Rainisto
> Afaik, if you try to send sms, it opens default messaging application
> where you can enter the sms. And same for outgoing phonecalls, opens phone
> application where you can make a call.
>
> Reasoning behind it is that as those call create a phone bill to end user,
> then applications are not allowed to secretly bypass default applications.
> But dont take my word on it, its just AFAIK on store QA process.
>
> But ofcourse if you enable developer mode you can do what ever you want.
> I'm not familiar with that side of middleware, so someone else can comment
> more.
>
> re, Jonni
>
> --
> *From:* devel-boun...@lists.sailfishos.org [
> devel-boun...@lists.sailfishos.org] on behalf of Seppo Tiainen [
> seppo.tiai...@gmail.com]
> *Sent:* Wednesday, November 13, 2013 8:19 PM
> *To:* devel@lists.sailfishos.org
> *Subject:* [SailfishDevel] Status of Sailfish SMS?
>
> Hi,
>
> Does anybody know about a possible module and its status in Sailfish/Qt-5
> that corresponds to Harmattan Qt Mobility Messaging so that it would be
> possible to send and receive SMSs (which is essential in my app) through
> Qt/QML on the Jolla phone?
>
> Thanks,
> Seppo
>
> ___
> SailfishOS.org Devel mailing list
>
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] Status of Sailfish SMS?
Thank you! That clarified things.
Seppo
2013/11/14 Robin Burchell
> Hi,
>
> On Wed, Nov 13, 2013 at 11:08 PM, Seppo Tiainen
> wrote:
> > Yes, that's the way to go. In Harmattan QML, there were:
> >
> > Qt.openUrlExternally("tel:012345x") for calls, and
> > Qt.openUrlExternally("sms:01234567444" + "?body=" + "bodytext") for
> SMSs.
>
> tel: is already supported. sms: is not yet supported, and may not be
> supported in the initial software release, but is the planned initial
> public "API" for messaging and should not be complicated to support.
> I've made sure we try to prioritize it for an early update. We do not
> intend to expose the capability to directly send SMS to store-using
> applications for the reasons Jonni mentioned earlier. However: this
> does not restrict people from hacking around with the functionality on
> their own devices.
>
> The Messaging API from Qt Mobility never made the transition to the Qt
> 5 world, and we have no intentions of working on this at this time.
>
> BR,
>
> Robin
> ___
> SailfishOS.org Devel mailing list
>
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] Status of Sailfish SMS?
I just want to point out what exactly I meant by SMS: Short Message Service of a mobile network (GSM/2G/3G/LTE) provided by the network operators. To me, Telepathy protocol is something else (chat using SIP etc.). Regards, Seppo 2013/11/15 > Hi Jonni > > Could you please confirm whether or not it will be possible to send SMSes > direct from an app? (from your reply below it seems this will not be > possible). > > My app Landed on Harmattan could send SMS directly - indeed it is the > raison-d'etre for the app, and it is obvious to the user that he is sending > an SMS (so no problems of secret bypassing...). > > My understanding was that it should be possible to send SMS from an app on > Sailfish using Telepathy. > > I would be thankful for clarification on this issue. > > Chris > > Zitat von "Jonni Rainisto" : > > > Afaik, if you try to send sms, it opens default messaging application >> where you can enter the sms. And same for outgoing phonecalls, opens phone >> application where you can make a call. >> >> Reasoning behind it is that as those call create a phone bill to end >> user, then applications are not allowed to secretly bypass default >> applications. But dont take my word on it, its just AFAIK on store QA >> process. >> >> But ofcourse if you enable developer mode you can do what ever you want. >> I'm not familiar with that side of middleware, so someone else can comment >> more. >> >> re, Jonni >> >> >> From: devel-boun...@lists.sailfishos.org [devel-bounces@lists. >> sailfishos.org] on behalf of Seppo Tiainen [seppo.tiai...@gmail.com] >> Sent: Wednesday, November 13, 2013 8:19 PM >> To: devel@lists.sailfishos.org >> Subject: [SailfishDevel] Status of Sailfish SMS? >> >> Hi, >> >> Does anybody know about a possible module and its status in Sailfish/Qt-5 >> that corresponds to Harmattan Qt Mobility Messaging so that it would be >> possible to send and receive SMSs (which is essential in my app) through >> Qt/QML on the Jolla phone? >> >> Thanks, >> Seppo >> >> > > > ___ > SailfishOS.org Devel mailing list > ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Status of Sailfish SMS?
OK, my mistake. So you can use Telepathy service to control the 'real' SMS. Need to study more. Thanks. 2013/11/15 Andrey Kozhevnikov > Telepathy is not protocol. Its service controlling all system-wide > accounts including ring, sms, mms services. > > > On 15.11.2013 22:22, Seppo Tiainen wrote: > > I just want to point out what exactly I meant by SMS: Short Message > Service of a mobile network (GSM/2G/3G/LTE) provided by the network > operators. To me, Telepathy protocol is something else (chat using SIP > etc.). > > Regards, > Seppo > > > 2013/11/15 > >> Hi Jonni >> >> Could you please confirm whether or not it will be possible to send SMSes >> direct from an app? (from your reply below it seems this will not be >> possible). >> >> My app Landed on Harmattan could send SMS directly - indeed it is the >> raison-d'etre for the app, and it is obvious to the user that he is sending >> an SMS (so no problems of secret bypassing...). >> >> My understanding was that it should be possible to send SMS from an app >> on Sailfish using Telepathy. >> >> I would be thankful for clarification on this issue. >> >> Chris >> >> Zitat von "Jonni Rainisto" : >> >> >> Afaik, if you try to send sms, it opens default messaging application >>> where you can enter the sms. And same for outgoing phonecalls, opens phone >>> application where you can make a call. >>> >>> Reasoning behind it is that as those call create a phone bill to end >>> user, then applications are not allowed to secretly bypass default >>> applications. But dont take my word on it, its just AFAIK on store QA >>> process. >>> >>> But ofcourse if you enable developer mode you can do what ever you want. >>> I'm not familiar with that side of middleware, so someone else can comment >>> more. >>> >>> re, Jonni >>> >>> >>> From: devel-boun...@lists.sailfishos.org [ >>> devel-boun...@lists.sailfishos.org] on behalf of Seppo Tiainen [ >>> seppo.tiai...@gmail.com] >>> Sent: Wednesday, November 13, 2013 8:19 PM >>> To: devel@lists.sailfishos.org >>> Subject: [SailfishDevel] Status of Sailfish SMS? >>> >>> Hi, >>> >>> Does anybody know about a possible module and its status in >>> Sailfish/Qt-5 that corresponds to Harmattan Qt Mobility Messaging so that >>> it would be possible to send and receive SMSs (which is essential in my >>> app) through Qt/QML on the Jolla phone? >>> >>> Thanks, >>> Seppo >>> >>> >> >> >> ___ >> SailfishOS.org Devel mailing list >> > > > > ___ > SailfishOS.org Devel mailing list > > > > ___ > SailfishOS.org Devel mailing list > ___ SailfishOS.org Devel mailing list
[SailfishDevel] Connecting Jolla device to SDK
First, is the current Alpha2 QtCreator/SDK capable of connecting to the new Jolla phone through USB for testing apps under development? If yes, there are many parameters (Device type, Username/Password...) that need to be correctly set. Short instructions would be very welcome. I did not succeed yet. Anybody tried? Seppo ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] [Update] Changelog for SailfishOS update 1 (1.0.1.10)
Today, on 11th December, I choose on my Jolla v.1.0.0.5: Settings > [i] Device info > pull-down menu / Check for updates => Updates: checking... then Updates: Up to date The device has not been hacked in any way, just Dev mode is active as normal. Did I do something wrong or is there a delay with the update? rgds, Seppo 2013/12/9 Bernd Wachter > > Hi all, > > SailfishOS gets its very first update today, version 1.0.1.10 > (Laadunjärvi). It is mainly a bug fix release aimed at improving the > stability and usability of the OS. Here are the highlights of the > improvements this release brings to your Jolla phone: > > Connectivity > * WLAN password input improvements > * WLAN connection possible to change directly from one hotspot to > an other > * Notification banner visible when checking updates without internet > connection > * USB MAC address does not change anymore between connections in > developer mode > * Mobile data switch status (toggle on/off) is shown on the Settings > cover > > Store > * Items in Store feed view now have visual busy indication while > installing > * Chinese comments are no longer presented as "?" characters > * Improved notifications when app download fails > * App grid now shows busy indicators or current status when leaving and > reopening page > * Application downloads are now more resilient to failures > > Bluetooth > * File receive dialog displays the name of the paired device correctly > * Improvements in BT pairing > * BT settings now responds to bluetooth daemon restart properly > > Phone & Messages > * Phone now displays number labels (i.e. work/home/mobile) during > selection > * DTMF tones are not skipped when user rapidly presses keys > * Fixed a case when incoming call is silenced and there is still sound > played after call ends > * Improved contact matching in call logs when contacts imported from SIM > * Active cover shows contact names > * Visual improvements in call forwarding UI and supplementary services > * Support for sms: URL in Messages > > People > * No more duplicated data in SIM contact import > * Improved handling of contact card details including avatars > * Added address does not disappear any more from contact viewer screen > after adding website information > * Stability improvements in People app during contact linking operation > * Performance improvements in Birthday plugin for contacts > > Accounts/services > * Removing a service account now removes related content from People app > * Account emits a signal when enabled / status changes > * Option to share to Facebook does not disappear anymore after adding an > email account > * Facebook notification will not appear repeatedly anymore > * Disabling Facebook account removes Facebook from Events view > * IM accounts now connect without needing to reboot device, after > adding them > * IM presence state persists now over reboot or changing connectivity > * Improved Exchange account setup flow > * Improved interoperability with servers preferring unsupported EAS > protocol 14.x > > Browser > * Audio and video are now in sync while playing youtube videos > * Browser does not crash when playing multiple videos > > Calendar > * New dedicated calendar alarm UI introduced which will show up with > alarms added after the update. > > Homescreen & notifications > * Events view wallpaper stays aligned with homescreen wallpaper > * Lock screen pulley menu shortcuts are not broken when device > lock is on > * In Events view, Share what's on your mind account grid shows > service icons > * Improvements to notification item layouts > * Sound feedback on battery empty shutdown > * Window titles for apps set > > Platform > * Content picker only has the search field when there is content > available > * Context menu is correctly updated with dynamic items > * The press effects in button and list items are unified > * Text linking matches numbers inside word boundaries > * QWindow::setTitle() is sent over Wayland > * DSME initial battery value is correct in bootup, or for shutdown > * Time and date changes persist over reboot > * DSME wakes from suspend to read HW temperatur and battery status > * USB mode notification does not offer Developer mode when developer > mode is not enabled > * Device lock is not anymore set when you use "Clear device lock code" > function > * The device lock code is not asked when the value is the same than > earlier > * Password field does not flash last character in clear text > * Date picker correctly highlights selected date and shows proper week > numbers in January > > > ___ > SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] [Update] Changelog for SailfishOS update 1 (1.0.1.10)
...just adding that the version keeps showing Salfish 1.0.0.5 (Kajaanlampi) and the checking does not take long. Working on WLAN. 2013/12/11 Seppo Tiainen > > Today, on 11th December, I choose on my Jolla v.1.0.0.5: > > Settings > [i] Device info > pull-down menu / Check for updates > > => > > Updates: checking... > then > Updates: Up to date > > The device has not been hacked in any way, just Dev mode is active as > normal. > > Did I do something wrong or is there a delay with the update? > > rgds, > Seppo > > > 2013/12/9 Bernd Wachter > >> >> Hi all, >> >> SailfishOS gets its very first update today, version 1.0.1.10 >> (Laadunjärvi). It is mainly a bug fix release aimed at improving the >> stability and usability of the OS. Here are the highlights of the >> improvements this release brings to your Jolla phone: >> >> Connectivity >> * WLAN password input improvements >> * WLAN connection possible to change directly from one hotspot to >> an other >> * Notification banner visible when checking updates without internet >> connection >> * USB MAC address does not change anymore between connections in >> developer mode >> * Mobile data switch status (toggle on/off) is shown on the Settings >> cover >> >> Store >> * Items in Store feed view now have visual busy indication while >> installing >> * Chinese comments are no longer presented as "?" characters >> * Improved notifications when app download fails >> * App grid now shows busy indicators or current status when leaving and >> reopening page >> * Application downloads are now more resilient to failures >> >> Bluetooth >> * File receive dialog displays the name of the paired device correctly >> * Improvements in BT pairing >> * BT settings now responds to bluetooth daemon restart properly >> >> Phone & Messages >> * Phone now displays number labels (i.e. work/home/mobile) during >> selection >> * DTMF tones are not skipped when user rapidly presses keys >> * Fixed a case when incoming call is silenced and there is still sound >> played after call ends >> * Improved contact matching in call logs when contacts imported from SIM >> * Active cover shows contact names >> * Visual improvements in call forwarding UI and supplementary services >> * Support for sms: URL in Messages >> >> People >> * No more duplicated data in SIM contact import >> * Improved handling of contact card details including avatars >> * Added address does not disappear any more from contact viewer screen >> after adding website information >> * Stability improvements in People app during contact linking operation >> * Performance improvements in Birthday plugin for contacts >> >> Accounts/services >> * Removing a service account now removes related content from People app >> * Account emits a signal when enabled / status changes >> * Option to share to Facebook does not disappear anymore after adding an >> email account >> * Facebook notification will not appear repeatedly anymore >> * Disabling Facebook account removes Facebook from Events view >> * IM accounts now connect without needing to reboot device, after >> adding them >> * IM presence state persists now over reboot or changing connectivity >> * Improved Exchange account setup flow >> * Improved interoperability with servers preferring unsupported EAS >> protocol 14.x >> >> Browser >> * Audio and video are now in sync while playing youtube videos >> * Browser does not crash when playing multiple videos >> >> Calendar >> * New dedicated calendar alarm UI introduced which will show up with >> alarms added after the update. >> >> Homescreen & notifications >> * Events view wallpaper stays aligned with homescreen wallpaper >> * Lock screen pulley menu shortcuts are not broken when device >> lock is on >> * In Events view, Share what's on your mind account grid shows >> service icons >> * Improvements to notification item layouts >> * Sound feedback on battery empty shutdown >> * Window titles for apps set >> >> Platform >> * Content picker only has the search field when there is content >> available >> * Context menu is correctly updated with dynamic items >> * The press effects in button and list items are unified >> * Text linking matches numbers inside word boundaries >> * QWindow::setTit
Re: [SailfishDevel] [Update] Changelog for SailfishOS update 1 (1.0.1.10)
OK, on terminal I get: ssu domain => Device domain is currently: jolla ssu domain sales => changing domain from jolla to sales Then I reboot and check for updates again: Updates: Checking... (getting stuck here for quite while) And finally I get: Updates: Available Thanks! Seppo 2013/12/11 Juha Kallioinen > Hi Seppo, > > if you have developer mode activated, then you probably also have > Fingerterm. Could you please start it and check that you haven't > accidentally changed the ssu settings? > > You can check this by opening fingerterm and entering: ssu domain > > If it says the domain is something else than "sales", then enter: ssu > domain sales > > If this was the case for you, rebooting the device at this point should > fix the situation. > > For more real-time assitance you could join #sailfishos channel in ircNET > and ask for help there. It's also ok to ask questions on this mailing list. > > Best regards, > Juha > > > On 11.12.2013 14:12, Seppo Tiainen wrote: > > ...just adding that the version keeps showing Salfish 1.0.0.5 > (Kajaanlampi) and the checking does not take long. Working on WLAN. > > > 2013/12/11 Seppo Tiainen > >> >> Today, on 11th December, I choose on my Jolla v.1.0.0.5: >> >> Settings > [i] Device info > pull-down menu / Check for updates >> >> => >> >> Updates: checking... >> then >> Updates: Up to date >> >> The device has not been hacked in any way, just Dev mode is active as >> normal. >> >> Did I do something wrong or is there a delay with the update? >> >> rgds, >> Seppo >> >> >> 2013/12/9 Bernd Wachter >> >>> >>> Hi all, >>> >>> SailfishOS gets its very first update today, version 1.0.1.10 >>> (Laadunjärvi). It is mainly a bug fix release aimed at improving the >>> stability and usability of the OS. Here are the highlights of the >>> improvements this release brings to your Jolla phone: >>> >>> Connectivity >>> * WLAN password input improvements >>> * WLAN connection possible to change directly from one hotspot to >>> an other >>> * Notification banner visible when checking updates without internet >>> connection >>> * USB MAC address does not change anymore between connections in >>> developer mode >>> * Mobile data switch status (toggle on/off) is shown on the Settings >>> cover >>> >>> Store >>> * Items in Store feed view now have visual busy indication while >>> installing >>> * Chinese comments are no longer presented as "?" characters >>> * Improved notifications when app download fails >>> * App grid now shows busy indicators or current status when leaving and >>> reopening page >>> * Application downloads are now more resilient to failures >>> >>> Bluetooth >>> * File receive dialog displays the name of the paired device correctly >>> * Improvements in BT pairing >>> * BT settings now responds to bluetooth daemon restart properly >>> >>> Phone & Messages >>> * Phone now displays number labels (i.e. work/home/mobile) during >>> selection >>> * DTMF tones are not skipped when user rapidly presses keys >>> * Fixed a case when incoming call is silenced and there is still sound >>> played after call ends >>> * Improved contact matching in call logs when contacts imported from SIM >>> * Active cover shows contact names >>> * Visual improvements in call forwarding UI and supplementary services >>> * Support for sms: URL in Messages >>> >>> People >>> * No more duplicated data in SIM contact import >>> * Improved handling of contact card details including avatars >>> * Added address does not disappear any more from contact viewer screen >>> after adding website information >>> * Stability improvements in People app during contact linking operation >>> * Performance improvements in Birthday plugin for contacts >>> >>> Accounts/services >>> * Removing a service account now removes related content from People app >>> * Account emits a signal when enabled / status changes >>> * Option to share to Facebook does not disappear anymore after adding an >>> email account >>> * Facebook notification will not appear repeatedly anymore >>> * Disabling Facebook account removes Facebook from Events view >>> * IM accounts now connect without needing to reb
Re: [SailfishDevel] [Update] Changelog for SailfishOS update 1 (1.0.1.10)
..so that solved it. Now I have the latest Sailfish OS version on my orange poppy. 2013/12/11 Seppo Tiainen > OK, on terminal I get: > > ssu domain => Device domain is currently: jolla > ssu domain sales => changing domain from jolla to sales > > Then I reboot and check for updates again: > > Updates: Checking... (getting stuck here for quite while) > > And finally I get: > > Updates: Available > > Thanks! > Seppo > > > 2013/12/11 Juha Kallioinen > >> Hi Seppo, >> >> if you have developer mode activated, then you probably also have >> Fingerterm. Could you please start it and check that you haven't >> accidentally changed the ssu settings? >> >> You can check this by opening fingerterm and entering: ssu domain >> >> If it says the domain is something else than "sales", then enter: ssu >> domain sales >> >> If this was the case for you, rebooting the device at this point should >> fix the situation. >> >> For more real-time assitance you could join #sailfishos channel in ircNET >> and ask for help there. It's also ok to ask questions on this mailing list. >> >> Best regards, >> Juha >> >> >> On 11.12.2013 14:12, Seppo Tiainen wrote: >> >> ...just adding that the version keeps showing Salfish 1.0.0.5 >> (Kajaanlampi) and the checking does not take long. Working on WLAN. >> >> >> 2013/12/11 Seppo Tiainen >> >>> >>> Today, on 11th December, I choose on my Jolla v.1.0.0.5: >>> >>> Settings > [i] Device info > pull-down menu / Check for updates >>> >>> => >>> >>> Updates: checking... >>> then >>> Updates: Up to date >>> >>> The device has not been hacked in any way, just Dev mode is active as >>> normal. >>> >>> Did I do something wrong or is there a delay with the update? >>> >>> rgds, >>> Seppo >>> >>> >>> 2013/12/9 Bernd Wachter >>> >>>> >>>> Hi all, >>>> >>>> SailfishOS gets its very first update today, version 1.0.1.10 >>>> (Laadunjärvi). It is mainly a bug fix release aimed at improving the >>>> stability and usability of the OS. Here are the highlights of the >>>> improvements this release brings to your Jolla phone: >>>> >>>> Connectivity >>>> * WLAN password input improvements >>>> * WLAN connection possible to change directly from one hotspot to >>>> an other >>>> * Notification banner visible when checking updates without internet >>>> connection >>>> * USB MAC address does not change anymore between connections in >>>> developer mode >>>> * Mobile data switch status (toggle on/off) is shown on the Settings >>>> cover >>>> >>>> Store >>>> * Items in Store feed view now have visual busy indication while >>>> installing >>>> * Chinese comments are no longer presented as "?" characters >>>> * Improved notifications when app download fails >>>> * App grid now shows busy indicators or current status when leaving and >>>> reopening page >>>> * Application downloads are now more resilient to failures >>>> >>>> Bluetooth >>>> * File receive dialog displays the name of the paired device correctly >>>> * Improvements in BT pairing >>>> * BT settings now responds to bluetooth daemon restart properly >>>> >>>> Phone & Messages >>>> * Phone now displays number labels (i.e. work/home/mobile) during >>>> selection >>>> * DTMF tones are not skipped when user rapidly presses keys >>>> * Fixed a case when incoming call is silenced and there is still sound >>>> played after call ends >>>> * Improved contact matching in call logs when contacts imported from SIM >>>> * Active cover shows contact names >>>> * Visual improvements in call forwarding UI and supplementary services >>>> * Support for sms: URL in Messages >>>> >>>> People >>>> * No more duplicated data in SIM contact import >>>> * Improved handling of contact card details including avatars >>>> * Added address does not disappear any more from contact viewer screen >>>> after adding website information >>>> * Stability improvements in People app during contact
Re: [SailfishDevel] How to deploy app to Jolla device?
Please check thread 'Connecting Jolla device to SDK', 5th December below. It is not too simple yet. 2013/12/14 Kalle Lammenoja > There is propably a quide somewhere, i just havent found it. So how do i > deploy an app on sailfish IDE directly to Jolla device connected with usb > on dev mode? On windows and linux? > > ___ > SailfishOS.org Devel mailing list > ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Fwd: Re: Re: How to get contacts and sms through Qt(C++)
Hi,
I just tested SMS transmission by QML by using method
Qt.openUrlExternally("sms:01234567444" + "?body=" + "bodytext") on my Jolla
device with OS version 1.0.1.12, sending to my N9.
It seems to work fine but there is a danger with it too: You cannot see to
whom the message is going. The is no indication of the contact or the
recipient tel.number visible. So, when you press enter to finally send the
SMS, you just have to trust that the application is not going to send this
message e.g. to an expensive money collecting number now and then.
I would propose to add a clear contact indication on the SMS message thread
display for the next OS update.
seppo
2013/12/24 Bernd Wachter
> writes:
>
> Hi,
>
> > Thanks, I mentioned that at earlier in this thread.
> >
> > However I think that the harbour rule is too strict. I think there is
> > a legitimate case for apps that clearly state that their purpose is to
> > send SMSes, and have their own send button --> i.e. SMSes are only
> > sent with explicit permission of the user at time of sending.
>
> the upcoming update introduces sms: as supported URL scheme for
> xdg-open, so in the future your application may send SMS by using
> xdg-open to call an URL like sms:12345?body=foo+bar+baz, which will open
> the messages application with number and body prefilled, and just
> requires the user to press 'send'.
>
> Bernd
>
> ___
> SailfishOS.org Devel mailing list
>
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] Disabling navigation gestures
Hi,
You can check if these easy QML tools are enough for you app:
- gesture.grab command within a MultiPointTouchArea ( onGestureStarted:
{gesture.grab();} )
- or, page by page you can use backNavigation: false and/or
forwardNavigation: false.
Seppo
2014/1/15 Alexander Ladygin
> Hi there
> Just a thought: may be you could do it like it's done in Gallery app,
> where tapping one time brings down menu, where you could navigate back and
> forward.
>
> Best regards,
> Alexander.
>
> On Tue, Jan 14, 2014 at 1:45 PM, Antoine Reversat wrote:
>
>> Yeah that's what I was going to do as a last resort :(
>>
>>
>> On Tue, Jan 14, 2014 at 2:49 AM, Bob Jelica wrote:
>>
>>> Hey,
>>>
>>> I’m fighting with the same problem. Only way, at least that I’ve found
>>> thus far, is to use backNavigation/forwardNavigation properties and then
>>> ”faking” the navigation buttons in top-left corner with a switch and a
>>> label :)
>>>
>>> //bob
>>>
>>> On 14 Jan 2014, at 03:42, Antoine Reversat wrote:
>>>
>>> > Hi,
>>> >
>>> > I would like to know if it is possible to disable navigation gestures
>>> . I'm using a Map element and navigation gestures override the panning
>>> gesture. I don't want to disable the navigation buttons at the top left
>>> corner so backNavigation and forwardNavigation properties don't work for me.
>>> >
>>> > Antoine
>>> > ___
>>> > SailfishOS.org Devel mailing list
>>>
>>> ___
>>> SailfishOS.org Devel mailing list
>>>
>>
>>
>> ___
>> SailfishOS.org Devel mailing list
>>
>
>
> ___
> SailfishOS.org Devel mailing list
>
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] No inbox? -> SMS
Hi,
I would like to add two items to the list:
5) If you use Qt.openUrlExternally("sms:" + smsNumber + "?body=" +
smsText); in your app you will not be returned back to the app but you will
have to close the sms sending UI (at least when cancelling) and this may
result in some kind of stack error (?) in some cases (black screen,
reboot). I think a fix is needed. - The same method for tel: works great!
6) Regarding item 5), there is no display of the recipient (number/contact)
of the SMS when you are supposed to finally send the text. Risky?
regards,
Seppo
2014/1/10
> Hi All
>
> As I have had the flu for the past few days, I have been working from
> home, and thus receiving and sending quiet a few SMSes with work
> colleagues. On the whole I found the SMS app useable, even if it could
> benefit from some tweaking.
>
> I found the "prod to reply" fairly obvious, IMHO no need for a reply
> button there; but I completely missed the "swipe to the left to reply by
> phone call". Perhaps the moral here is that some of the UX interactions
> are at first not natural, as they are different to other platforms - even
> the N9. I am in 2 minds as to wether such interactions will become more
> natural with time, or if I will remain permanently "locked out" of some
> functionality because I never chance on the magic touch that reveals it.
>
> Some things I think do need improvement are:
> 1) text is readable with glasses on, but not without, or in difficult
> conditions. Pinch to zoom would be ace and natural.
> 2) When you reply to an SMS, the new SMS is hidden at the very bottom of
> screen, and requires a second prod to show the keyboard. I think it would
> be better if the new SMS opened with the keyboard deployed.
> 3) No cursors (or at least any that I have found) to move around in the
> text of the SMS to make corrections.
> 4) Location of the send button is unfortunate. I also find it a bit small
> and subtle - I would prefer a larger more obvious button.
>
> mfg
>
> Chris
>
> Zitat von "Kalle Vahlman" :
>
> 2014/1/10 Chris Walker :
>>
>>> On the way home from the meeting, I wanted to send a text to my wife.
>>> If I thought email was difficult, that was a walk in the park compared
>>> to trying to send an SMS. Seriously people, have you tried this thing
>>> in the real world? Where's the Reply button? Jeez. You sure are making
>>> life tough.
>>>
>>
>> This intrigues me. What exactly did you find difficult in sending an SMS?
>>
>> From what I see on the device, it should be quite obvious how to do
>> that both through the people app or the messaging app, and
>> not-so-obvious but guessable (long press) from the call app.
>>
>> --
>> Kalle Vahlman, Movial Creative Technologies Inc.
>> Porkkalankatu 20, FI-00180 Helsinki
>> Tel +358 9 8567 6400
>> Fax +358 9 8567 6401
>> www.movial.com
>> ___
>> SailfishOS.org Devel mailing list
>>
>>
>
>
> ___
> SailfishOS.org Devel mailing list
>
___
SailfishOS.org Devel mailing list
[SailfishDevel] SMS issues/wishes
Hi,
I would like to add two more items to the SMS wish list:
1) If you use Qt.openUrlExternally("sms:" + smsNumber + "?body=" +
smsText); in your app you will not be returned back to the app but you will
have to close the sms sending UI (at least when cancelling) and this may
result in some kind of stack error (?) in some cases (black screen,
reboot). I think a fix is needed. - The same method for tel: works great!
Please don't change that.
2) Regarding item 1), there is no display of the recipient (number/contact)
of the SMS when you are supposed to finally send the text. Risky if not
swiping to see more info?
regards,
Seppo
___
SailfishOS.org Devel mailing list
[SailfishDevel] SMS wishlist & a possible issue
Hi,
I would like to add two more items to the SMS wish list:
1) If you use Qt.openUrlExternally("sms:" + smsNumber + "?body=" +
smsText); in your app you will not be returned back to the app after
sending but instead you will have to close the sms sending UI and and
'maximize' the app. In some cases this may result in some kind of error
(stack? - black screen, reboot). I think a fix is needed. - The same method
for 'tel:' works great! Please don't change that. Something similar for the
'sms:' would be really cool.
2) Regarding item 1), there is no display of the recipient (number/contact)
of the SMS when you are supposed to finally send the text, unless you
realize you can swipe to see that and then come back. Risky?
regards,
Seppo
___
SailfishOS.org Devel mailing list
[SailfishDevel] Received SMS?
Hi, What might be the Harbour policy for an app accessing received SMSs? However, I have not yet found any QML tool to enable that. On N9, I did that with Harmattan's Mobility and ListView + MessageModel. Does anyone know how to do that in Sailfish? Regards, Seppo ___ SailfishOS.org Devel mailing list
