Re: [SailfishDevel] Is support for commercial apps a TABOO subject?
Another cool thing could be possibility to have beta testing on end users (as for example steam does for games). Von meinem iPad gesendet Am 29.5.2014 um 2.32 schrieb Artem Marchenko artem.marche...@gmail.com: Hi there In the mean time, you have time to get your apps ready, tested and polished. Also, let us know what additional APIs you need for your Harbour app so that by the time payments are available, your app is ready to sail. As for harbour-related APIs and functions, subscription-based and try-before-you-buy would have been very nice [for me at least] as IMHO they motivate developers for continuous app improvement. I'd love to have platform support for something like WhatsApp is doing: have free usage for a substantially long time (a month at least, maybe a year), and then something like $1 or even $0.1 per half a year. That would motivate for paying only for the actually useful apps (you tried app for a long time and still use it) and for continuing development (if app doesn't improve, user uninstalls and goes for another app). Sure, how to implement it technically without touching user privacy too much is a separate story (who will check whether user still has the app installed/running?). One option could be to encourage implementing this via in-app purchase of subscriptions (a'la iOS?) that could be verified completely on device without contacting the home base except for the act of purchase. Cheers, Artem. On Fri, Apr 25, 2014 at 3:42 PM, Karl Granström karl.granst...@jolla.com wrote: Ahoy!!! We see the payment support in store as a really important part of our developer offering. We are currently working to support payments in our Jolla Store and Harbour but there are a lot of things for us to do. Our current target is to provide you the monetizing possibility durign the 2nd half of 2014. In the mean time, you have time to get your apps ready, tested and polished. Also, let us know what additional APIs you need for your Harbour app so that by the time payments are available, your app is ready to sail. Br, Jolla Store team On 24 Apr 2014, at 14:34, Mohammed Hassan mohammed.has...@jollamobile.com wrote: On Thu, Apr 24, 2014 at 09:33:22AM +0200, tw_bolek wrote: [...] So my question is: is this some kind of taboo subject, or something of as little importance that for over 4 months now no Jollan has said A WORD about it despite numerous requests? A couple of my friends already gave up after waiting so long for even just any information, and I must say that I'm slowly losing hope, too. We all understand and are aware of the enormous job Jolla has been doing, so we're asking for just INFORMATION about the progress, even just if AT ALL there are any plans to do it in a foreseeable future, and if so then knowing even just as little as if it will take a month or half a year would be all we need... There will be support for commercial apps and those will have copy protection. This was mentioned bt Rainisto long ago already. I cannot give more info nor can I give an ETA for that though :/ Cheers, ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list -- Artem Marchenko http://agilesoftwaredevelopment.com http://twitter.com/AgileArtem ___ 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] DatePickerDialog and locale
Hello, You can try devel-su -p aplication + parameters. This other behavior is due launcher runs application as nemo:privaliged, but from ssh you run it as nemo:nemo. BR, Vladislav -- Původní zpráva -- Od: Kimmo Lindholm kimmo.lindh...@eke.fi Komu: devel@lists.sailfishos.org devel@lists.sailfishos.org Datum: 24. 5. 2014 19:45:25 Předmět: [SailfishDevel] DatePickerDialog and locale (No actual question here but my observations) Just noticed that depending how i start my application on the phone, DatePickerDialog returns different values. If started from ssh session, dateText returns “24 May 2014” If started from launcher icon (as normally user would do) or from fingerterm, dateText returns “24.5.2014” (later caused my app to fail) Also the complete datepicker is in English when started from ssh. Setting LANG=fi_FI.utf8 env from putty gets app started in ‘my’ language. Maybe i’ll use this to test application in different languages. -kimmo ___ 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] QThread priority
On Wednesday 28 May 2014 22:07:20 Andrey Kozhevnikov wrote:
need to look into your parseReadyData
28.05.2014 22:03, Krisztian Olah ?:
Hi Andrey,
Thanks for the answer, your snippet looks very similar to what I
have. Perhaps if I posted my code segment would be of help in helping
me figuring out where I'm wrong.
During parsing CPU usage reaches 97-100% which causes my GUI to
hang(I have about 500 000 opening and closing tags and half of the
enclosed items I need to process: save, in some cases insert spaces,
etc), especially awkward when I start parsing whilst still fetching
the data from network(sometimes hangs during pageStack.push() ), but
it's bad for up to 2-5 seconds nevertheless. I wouldn't mind if
parsing took 10 seconds if GUI was responsive. This is what I'm doing:
void SomeClass::someMethod() {
MyContainer* container = new MyContainer();
//reader has a handle to container, through which it
populates the container
MyXmlStreamReader* parser = new
MyXmlStreamReader(container);
QThread* parserThread = new QThread();
parser-moveToThread(parserThread);
connect(parser, SIGNAL(finished()), this, SLOT(onParsingFinished)
);
connect(parser, SIGNAL(finished()), parserThread, SLOT(quit()) );
connect(parser, SIGNAL(finished()), parser, SLOT(deleteLater())
);
connect(parserThread, SIGNAL(finished()), parserThread,
SLOT(deleteLater()) ); parserThread-start();
reply = networkMngr-get(QNetworkRequest(someUrl)); //both
pointers are class members connect(reply, SIGNAL(finished()),
this, SLOT(onAllDataRecieved()) ); //this starts the parser with
the data available at the time,
// when parser reaches the end of xml document it emits
itsfinished() signal
connect(reply, SIGNAL(readyRead()), this, SLOT(parseReadyData())
);
}
To run parser in parallel just to get results in the main thread it is better
to use QtConcurrent::run() + QFutureWatcher.
- denis
Thanks again
Kris
On 28 May 2014 06:16, Andrey Kozhevnikov coderusin...@gmail.com
mailto:coderusin...@gmail.com wrote:
it can't doesn't help much. you initializing thread wrong.
simple threading way is:
MyXmlParser *parser = new MyXmlParser(xmlDocument);
QThread *thread = new QThread(parser);
parser-moveToThread(thread);
QObject::connect(thread, SIGNAL(started()), parser, SLOT(parse()));
QObject::connect(parser, SIGNAL(parseComplete(QVariantMap)), this,
SLOT(onParseComplete(QVariantMap)));
thread-start();
28.05.2014 03:24, Krisztian Olah ?:
Hi list,
I have a rather large xml file to parse and it causes the UI to
freeze, I assingned the parser to a different thread, but it
doesn't help much. According to the Qt documentation
QThread::setPriority() doesn't work on Linux, is there some kind
of workaround that could be used?
Thanks
Kris
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail
todevel-unsubscr...@lists.sailfishos.org
mailto:devel-unsubscr...@lists.sailfishos.org
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to
devel-unsubscr...@lists.sailfishos.org
mailto: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] QThread priority
Thanks Denis, I'll look into QtConcurrent + QFutureWatcher tonight when I'll have time. I will also consult pthread's documentation after comparing the two approaches. Thanks again Kris On 29 May 2014 11:01, Denis Zalevskiy denis.zalevs...@jollamobile.com wrote: On Thursday 29 May 2014 13:55:40 Denis Zalevskiy wrote: To run parser in parallel just to get results in the main thread it is better to use QtConcurrent::run() + QFutureWatcher. Also, to set priority I guess you can use posix pthread functions, smth. like ::pthread_setschedprio(::pthread_self(), SCHED_IDLE); - denis - denis Thanks again Kris On 28 May 2014 06:16, Andrey Kozhevnikov coderusin...@gmail.com mailto:coderusin...@gmail.com wrote: it can't doesn't help much. you initializing thread wrong. simple threading way is: MyXmlParser *parser = new MyXmlParser(xmlDocument); QThread *thread = new QThread(parser); parser-moveToThread(thread); QObject::connect(thread, SIGNAL(started()), parser, SLOT(parse())); QObject::connect(parser, SIGNAL(parseComplete(QVariantMap)), this, SLOT(onParseComplete(QVariantMap))); thread-start(); 28.05.2014 03:24, Krisztian Olah ?: Hi list, I have a rather large xml file to parse and it causes the UI to freeze, I assingned the parser to a different thread, but it doesn't help much. According to the Qt documentation QThread::setPriority() doesn't work on Linux, is there some kind of workaround that could be used? Thanks Kris ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail todevel-unsubscr...@lists.sailfishos.org mailto:devel-unsubscr...@lists.sailfishos.org ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org mailto: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 ___ 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] sporadic bouts of Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server.
Hi All
I am still suffering from this issue, and getting more and more frustrated!
Right now it is refusing to deploy as RPM to the Emulator.
Is anything I can do to better debug / understand this issue?
The timeout settings previously suggested are probably red-herrings, as
they apply to the device (phone / Emulator), whereas the error is a
timeout to the SDK.
All help greatly appreciated.
Grüsse
Chris
On 28.04.14 08:01, christopher.l...@thurweb.ch wrote:
Hi
Thanks.
I found a well hidden {1} timeout setting in the preferences / devices
and increased this from the default 2 secs to 10 secs. This does seem
to help, but as always with sporadic problems only time will tell if
this is a fix, or if the problem is just dormant for a while.
What I don't understand is, given the error says Could not connect to
MerSDK Virtual Machine why should a timeout for connecting to a
Jolla device play any role?
Is the error misleading? is the problem actually in connecting FROM
the MerSDK to the Jolla?
Chris
{1} when the preferences pane opens, at least on my OSX host the
timeout setting is offscreen in an embedded pane with scroll bars in
the middle of the preferences pane. Only if you scroll down in the
embedded pane are further settings including the timeout revealed.
Truly a wonderful bit of UI design 8-)
Zitat von fasza2mob...@gmail.com:
I believe the timeout setting can be adjusted in QtCreator where you
set up your mer device(ssh password, etc). By increasing this value
you can probably prevent the timeout issue altogether. I don't have
the SDK in front of me to give you the exact menu you need to open,
but it isn't too hard to find once you know what you're looking for.
On Sat Apr 26 2014 13:41:20 GMT+0100 (BST),
christopher.l...@thurweb.ch wrote:
Hi All
I am suffering from sporadic bouts of the error: Could not connect to
MerSDK Virtual Machine. Timeout waiting for reply from server
One moment I can be happily hacking and deploying code to my Jolla
without error. Then I make a small change to the code, try to deploy,
and bing! the error rears its ugly head once again like a scandinavian
troll from under a bridge.
Project ERROR: Could not connect to MerSDK Virtual Machine. Timeout
waiting for reply from server.
14:02:28: The process
/Users/christopherlamb/.config/SailfishAlpha4/mer-sdk-tools/MerSDK/SailfishOS-armv7hl/deploy
exited with code
1.
Error while building/deploying project landed26_QT5 (kit:
MerSDK-SailfishOS-armv7hl)
When executing step 'Rpm'
14:02:28: Elapsed time: 00:27.
When the error occurs, there seem to be at least 2 variants:
1) It will successfully deploy As binaries without error, but will
give the error on deploy as RPM.
2) Any kind of deploy gives the error.
The strange thing is, that despite the error, it does seem to
(sometimes) deploy (or possibly partially deploy) code.
Right now I am getting the error in constellation 1), so according to
the error a deploy as RPM should fail. Yet the test below indicates
that it is at least partially deploying code.
[root@Jolla javascript]# pwd
/usr/share/landed26_QT5/qml/javascript
[root@Jolla javascript]#
[root@Jolla javascript]# ls -ahl
total 52K
drwxr-xr-x 1 root root 180 2014-04-26 13:56 .
drwxr-xr-x 1 root root 110 2014-04-26 13:56 ..
-rw-r--r-- 1 root root 4.2K 2014-04-26 13:55 jsonpath.js
-rw-r--r-- 1 root root 1.3K 2014-04-26 13:55 jsonSupport.js
-rw-r--r-- 1 root root 349 2014-04-26 13:55 landed.js
-rw-r--r-- 1 root root 1.2K 2014-04-26 13:55 message.js
-rw-r--r-- 1 root root 8.4K 2014-04-26 13:55 readDataModel.js
-rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
-rw-r--r-- 1 root root 5.2K 2014-04-26 13:55 writeDataModel.js
//create new file testDeploy.js in QtCreator, then attempt deploy as
RPM. Error is generated. Repeat attempt to deploy as RPM. Error is
generated again.
//but testDeploy.js is now on the Jolla!
[root@Jolla javascript]# ls -ahl
total 56K
drwxr-xr-x 1 root root 206 2014-04-26 14:01 .
drwxr-xr-x 1 root root 110 2014-04-26 14:01 ..
-rw-r--r-- 1 root root 4.2K 2014-04-26 14:00 jsonpath.js
-rw-r--r-- 1 root root 1.3K 2014-04-26 14:00 jsonSupport.js
-rw-r--r-- 1 root root 349 2014-04-26 14:00 landed.js
-rw-r--r-- 1 root root 1.2K 2014-04-26 14:00 message.js
-rw-r--r-- 1 root root 8.4K 2014-04-26 14:00 readDataModel.js
-rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
-rw-r--r-- 1 root root 38 2014-04-26 14:00 testDeploy.js
-rw-r--r-- 1 root root 5.2K 2014-04-26 14:00 writeDataModel.js
So it looks like that after a second failed deploy, the file is
actually deployed!
During bouts of the error, QtCreator seems to get out of sync the true
status of the SDK VM (indicated by the VirtualBox GUI). So QtCreator
may show the green Start SDK status, even though the SDK is already
running. Or QtCreator shows the same button grey.
So far I have not found any lasting solution to prevent the error in
the first place. Sometimes it goes away on its own
Re: [SailfishDevel] QThread priority
Andrey, you are right if I'm not using the signals/slots, but calling it directly causes it to run in current thread. It works just fine now, thanks. Denis, I did check out QtConcurrent::run(), but since I return void from the function and I have to call the function multiple times possibly in the same thread so that I can append to QXmlStreamReader's data, I think it is easier to just use QThread in this case. However thank you for your input, I'm sure I will make use of QtConcurrent in the QFuture. (pun intended) ;) On 29 May 2014 12:23, Krisztian Olah fasza2mob...@gmail.com wrote: Thanks Denis, I'll look into QtConcurrent + QFutureWatcher tonight when I'll have time. I will also consult pthread's documentation after comparing the two approaches. Thanks again Kris On 29 May 2014 11:01, Denis Zalevskiy denis.zalevs...@jollamobile.com wrote: On Thursday 29 May 2014 13:55:40 Denis Zalevskiy wrote: To run parser in parallel just to get results in the main thread it is better to use QtConcurrent::run() + QFutureWatcher. Also, to set priority I guess you can use posix pthread functions, smth. like ::pthread_setschedprio(::pthread_self(), SCHED_IDLE); - denis - denis Thanks again Kris On 28 May 2014 06:16, Andrey Kozhevnikov coderusin...@gmail.com mailto:coderusin...@gmail.com wrote: it can't doesn't help much. you initializing thread wrong. simple threading way is: MyXmlParser *parser = new MyXmlParser(xmlDocument); QThread *thread = new QThread(parser); parser-moveToThread(thread); QObject::connect(thread, SIGNAL(started()), parser, SLOT(parse())); QObject::connect(parser, SIGNAL(parseComplete(QVariantMap)), this, SLOT(onParseComplete(QVariantMap))); thread-start(); 28.05.2014 03:24, Krisztian Olah ?: Hi list, I have a rather large xml file to parse and it causes the UI to freeze, I assingned the parser to a different thread, but it doesn't help much. According to the Qt documentation QThread::setPriority() doesn't work on Linux, is there some kind of workaround that could be used? Thanks Kris ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail todevel-unsubscr...@lists.sailfishos.org mailto:devel-unsubscr...@lists.sailfishos.org ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org mailto: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 ___ 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
