Re: [SailfishDevel] best way to work with covers?

If you declare all your pages in ApplicationWindow like: ApplicationWindow { id: appWindow cover: Qt.resolvedUrl("CoverPage.qml") MainPage { id: mainPage } SecondPage { id: secondPage } } then you can use pages global properties and functions from CoverPage: CoverBackgroun

Re: [SailfishDevel] best way to work with covers?

Hi Artem, thanks for the fast response. Your solution is a good idea, and could work for some values (main page and first cover) - thanks for that! :), but not all. Because I can pass them only in the moment I instantiate them. So I have to instantiate all of them in the ApplicationWindow. This

Re: [SailfishDevel] best way to work with covers?

Hi Gabriel There are several ways of passing data between Cover and rest of app (or any components). You can try using app global object ids or javascript files with .pragma library and gloval [to them] variables or inject global objects from C++ via setContextProperty(). The way I like doing it

[SailfishDevel] best way to work with covers?

Hi Sailfish sailors, I want to ask, what is recommended/best practice to handle different covers/covers with dynamic information. My case: On the main page (MainPage.qml) you can select some options and search depending on the selected options. My main cover shows the selected options if minimi

Re: [SailfishDevel] Saving state/config

On Friday 15 November 2013 14:27 Jonni Rainisto wrote: > Yes your .spec file should have following line if you want to use the > plugin: > > Requires: nemo-qml-plugin-configuration-qt5 I went with the QSettings wrapper as proposed by Andrey, but this is certainly good to know for further devel

Re: [SailfishDevel] Saving state/config

Thanks a lot, Jonni! Discussion went further already, but I am just fascinated you guys have got such a plugin ready! I used to implement GConf modification on my own or create a Settings wrapper for the LocalStorage and now there's a ready made plugin for GConf - great! Best regards, Artem. O

Re: [SailfishDevel] Saving state/config

Ah OK. I had missed that. It would also have been almost too easy ;) Thanks a lot for your thorough help On Friday 15 November 2013 23:39 Andrey Kozhevnikov wrote: > unfortunately you cant use QSettings class this way. It have no public > slots to be used from QML side. You need to write some Qml

Re: [SailfishDevel] Saving state/config

unfortunately you cant use QSettings class this way. It have no public slots to be used from QML side. You need to write some QmlSettings class wrapper for QSettings: class QmlSettings: publicQObject ... public slots: QVariant value(const QString &key); void setValue(const QString &key, con

Re: [SailfishDevel] Saving state/config

On Friday 15 November 2013 20:50 Andrey Kozhevnikov wrote: > both are easy. check Qt Assistant. examples and api reference are inside > your Qt Creator ;) Forgive me for non-SailfishOS questions, but I must be doing something wrong, even if it's easy ;) My main is now: int main(int argc, char *

Re: [SailfishDevel] Status of Sailfish SMS?

Hi, On Nov 15, 2013, at 8:01 AM, christopher.l...@thurweb.ch wrote: > 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). As Robin said, the only API we’re supporting initial

Re: [SailfishDevel] Status of Sailfish SMS?

Hi Seppo My definition of SMS is exactly the same as yours. You will find some older questions from me on the subject of Telepathy and SMSes in the archive of this mailing list. Chris Zitat von "Seppo Tiainen" : OK, my mistake. So you can use Telepathy service to control the 'real' SMS. N

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 wrot

Re: [SailfishDevel] Status of Sailfish SMS?

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 opera

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

Re: [SailfishDevel] Saving state/config

I'm also just learning to use Qt Creator. Used to a simple text editor ;) On Friday 15 November 2013 20:50 Andrey Kozhevnikov wrote: > both are easy. check Qt Assistant. examples and api reference are inside > your Qt Creator ;) > > On 15.11.2013 20:48, Thomas Tanghus wrote: > > On Friday 15 Nove

[SailfishDevel] Persecute - indie WhatsApp client for SailfishOS

Hello Sailors! Please test my application - Persecute. Persecute is indie WhatsApp client in Qt/QML. Initially written by me for Harmattan in Qt4/QML and now ported to Qt5/QML for Sailfish. http://sailfish.openrepos.net/coderus/personal/main/p/persecute-0.1-1.armv7hl.rpm http://sailfish.openr

Re: [SailfishDevel] Status of Sailfish SMS?

Hi, Sorry, I'm not familiar with that part of middleware (or Harbour QA rules), so I'm unable to say yes or no. Maybe someone else can comment on this (or you need to wait for few weeks until devices hit the market and see it yourself). re, Jonni From: c

Re: [SailfishDevel] Saving state/config

Sure. but you can make own classes for bth QSettings and GConfItem ;) On 15.11.2013 21:00, Marcin M. wrote: The plugin uses gconf, doesn't it? Can we use it to modify any gconf entry then? -- Marcin 2013/11/15 Andrey Kozhevnikov > both are easy. check Qt A

Re: [SailfishDevel] Saving state/config

The plugin uses gconf, doesn't it? Can we use it to modify any gconf entry then? -- Marcin 2013/11/15 Andrey Kozhevnikov > both are easy. check Qt Assistant. examples and api reference are inside > your Qt Creator ;) > > > On 15.11.2013 20:48, Thomas Tanghus wrote: > >> On Friday 15 November 2

Re: [SailfishDevel] Status of Sailfish SMS?

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

Re: [SailfishDevel] Saving state/config

both are easy. check Qt Assistant. examples and api reference are inside your Qt Creator ;) On 15.11.2013 20:48, Thomas Tanghus wrote: On Friday 15 November 2013 20:26 Andrey Kozhevnikov wrote: use QSettings as Jonni said and register own component to use in qml, if need, or export single clas

Re: [SailfishDevel] Saving state/config

On Friday 15 November 2013 20:26 Andrey Kozhevnikov wrote: > use QSettings as Jonni said and register own component to use in qml, if > need, or export single class instance via setContextProperty The latter sounds like the easiest approach. Thanks both for your good advice. > On 15.11.2013 20:2

Re: [SailfishDevel] Saving state/config

On Friday 15 November 2013 14:21 Jonni Rainisto wrote: > Yes its as simple as assign a new value and it will be automaticly stored. > > your_foo_setting.value = newValue Ah, even more simple - I like that ;) > But having said that, I'm not sure what is the store's current intake QA > rules, it m

Re: [SailfishDevel] Saving state/config

Yes your .spec file should have following line if you want to use the plugin: Requires: nemo-qml-plugin-configuration-qt5 From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] on behalf of Thomas Tanghus [tho...@tanghus.net] Sent

Re: [SailfishDevel] Saving state/config

use QSettings as Jonni said and register own component to use in qml, if need, or export single class instance via setContextProperty On 15.11.2013 20:24, Thomas Tanghus wrote: On Friday 15 November 2013 05:44 Jonni Rainisto wrote: import org.nemomobile.configuration 1.0 My n00bness shows aga

Re: [SailfishDevel] Saving state/config

On Friday 15 November 2013 05:44 Jonni Rainisto wrote: > import org.nemomobile.configuration 1.0 My n00bness shows again :P Will I have to add this module to my project? The SailfishOS-i486-x86 target only comes with org.nemomobile.ngf -- Med venlig hilsen / Best Regards Thomas Tanghus ___

Re: [SailfishDevel] Saving state/config

Hi, Yes its as simple as assign a new value and it will be automaticly stored. your_foo_setting.value = newValue But having said that, I'm not sure what is the store's current intake QA rules, it might be that configuration plugin is not whitelisted yet. So you might need to use QSettings if y

Re: [SailfishDevel] Saving state/config

On Friday 15 November 2013 05:44 Jonni Rainisto wrote: > Hi, > > Normal usage of QSettings which saves under /home/nemo/.config/app would be > just fine for C++. If you just want to save few config values in QML, then > you might want to use GConf by importing nemo-qml-plugin-configuration > modul