Re: [SailfishDevel] Harbour rules and faq
Hello, I also have to agree with Gabriel on this one, the polcies for Harbour need to be made much more clearer. At the moment it is not inspiring working of Sailfish development due to the store issues. I would expect that Jolla would indeed need as many developers as only possible onboard, and to aid that, the Harbour rules needs to be made clearer / substantially more relaxed. More native applications are indeed needed as the Android integration currently seems to be everything else than optimal. Regards, Andreas Enbacka Ohh nice, I planed to use DBUS for few features, good that I have not implemented a lot so far. Why will DBUS also be restricted? There are just a small amount to nearly no, save to use APIs. There are nearly no offical APIs, just some Nemo middle ware stuff that works - maybe, but is not allowed at harbour. What about device feedback, what about notifications, what about sharing options, what about deamons, now also DBUS will be restricted. DBUS was an option to work around missing notifications. :-/ I'm sure it's difficult and hard for a small team, but hey come on you wanted it. And if you can't solve/realise things atm, be open and different - talk to use, tell your plans, show what can be expected when. Talk to your devs, maybe let's discuss ideas, make plans together. But don't be shy and say nothing and came in the next moment with any - positive or negative suprise. Gabriel. -- Von meinem Nokia N9 gesendet Basil Semuonov schrieb am 13.01.14 19:38: Hi there, habour supporters and moderators. Please, please, really PLEASE do update your https://harbour.jolla.com/faq AND MAKE CLEAN RULES what is restricted and what is not. This is not the game where we should guess your imaginary rules. This is just ridiculous to submit apps, wait for 4 days and then get response that app is rejected with new , since "This application uses a DBus API which should not be used by 3rd party applications, and will be restricted soon.". How the hell I should know what will be restricted and will not? If you not sure about anything at harbour in the future, create white list of what is allowed, like qml imports and link libraries. Do you understand, that it is impossible to create any usefull and complex application, which is not "a one-page + one-button + haha-look-at-my-cover-it-is-awesome" when you does not share your plans for future and does not supply strict rules? All your ecosystem depends on this. Regards, Basil. -- Semuonov Basil --- Line of cut --- Linux everywhere... ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Harbour QA process...
Thanks for the support :) I will develop QSpot for SailfishOS, timetable however depends on when certain libs will be whitelisted / allowed. I could also consider publishing an alpha for testing somewhere else. I hope that the QA process will be improved and eased, and possible more automation added. Having submitted apps to several app stores, e.g., WP Store and Google Play, I would stay Google Play is a good example how it should work. //Andreas 2014/1/10 Andreas Enbacka : I would like to agree with Franck on this. I have also partly held off developing for SailfishOS due to e.g., the Harbour process, as well as due to APIs my apps need to are not allowed. This seems backwards; if no cool apps exist for SailfishOS that use certain API's, what's the incentive for Jolla to allow them in Harbour? Please please do develop for SailfishOS and *make* Jolla beg and promise anything to get your superb app submitted to Harbour! ;) Kalle ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Harbour QA process...
I would like to agree with Franck on this. I have also partly held off developing for SailfishOS due to e.g., the Harbour process, as well as due to APIs my apps need to are not allowed. I think that in case Jolla wants developers to focus on developing native apps for SailfishOS, many improvments are needed in this area. Regards, Andreas Enbacka On 10.1.2014 9:57, Franck Routier (perso) wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, currently, the Harbour QA process is quite frustrating, as problems are reported one after the other, with a delay of several days inbetween... reminds me of the old time cobol compilators! It would be cool if the efforts made by the developper to provide free native application were a bit more considered. Ok, I'm talking out of frustration, but I had my app rejected first because of naming conventions of the app itself (I didn't properly read the FAQ, but it is not stated either in the app submission page of Harbour), delay of 7 days, then because of rmp file naming convention (which I did not find clearly stated except in the rejection notification - 5 more days). Now I am waiting for next step (2 days for now...) I understand this is a lot of work, but what I suggest is : - - more controls and more information in the app submission page (testing the naming conventions of at least the files seems trivial) - - when doing QA, report all problems at once, not just the first one - - maybe provide a QA tool so that developpers could do this job and let jolla teams concentrate on real QA (power consumption, security checks, ...) Hope this does not sound too demanding... Best regards, Franck -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSz6f+AAoJEGEvoAir78RoEOsH/3jBwaf6MTpi0tRqVQXZDvsU nTUoc/H2zFWOFVDoSJqc6FQCQcPue5Fvu/tuGe8zEF8HPeW5Et08dmpGP7wdXurP VJhaG8LOHCMj9AhgPLPkFKJKMCqKR8H0PmbvOaEhj+zua6AdpzlOz4MOPaxeQltz FUbXwnrGNZQ/KRoM1NPJM8g9SkUmkg+1cBBS1ThhJuVP+jANBit9BFJuYnvh8HzO y6ODX+jpn1348p89PWrt1/dDzRqLw62kccf5G6nyaBumjKNdzodfU7/+i2C6wHNG tTfS46ytuebzm/5SMG9yJN77jg1bsFZlHPjiKUp+vLaU99RBWVlFaybJPJf1QAY= =uJPj -END PGP SIGNATURE- ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
[SailfishDevel] QAudioOutput and raw/pcm audio output
Hello, What codes are supported currently on SailfishOS using QAudioOutput? In my QSpot application I am writing raw PCM audio directly (using push) to QAudioOutput, however I get absolutely no sound output (tested on the emulator, and also on SailfishOS port running on N950). Is this the expected behaviour, and in such case, are any solutions available? Regards, Andreas Enbacka ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Problem finding main qml file
Thanks, that worked great!
//Andreas
i'm using
view->setSource(SailfishApp::pathTo("qml/main.qml"));
On 12.11.2013 18:45, Andreas Enbacka wrote:
Hello,
I am using view->setSource(QUrl::fromLocalFile("qml/projectName.qml))
to set the initial qml view for my app, however it is not found using
run-time (it tries to access it from /home/nemo/qml/..). What is the
correct way to specify the relative path in SailfishOS?
BR,
Andreas Enbacka
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
[SailfishDevel] Problem finding main qml file
Hello,
I am using view->setSource(QUrl::fromLocalFile("qml/projectName.qml)) to
set the initial qml view for my app, however it is not found using
run-time (it tries to access it from /home/nemo/qml/..). What is the
correct way to specify the relative path in SailfishOS?
BR,
Andreas Enbacka
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] Sailfish app - testing on real device
Hello, Thanks for the info, I will at some point prepare a version for testing and post a link to the rpm. //Andreas if you drop by in efnet irc #sailfishos channel, there are people with real devices, and we have been testing rpm packages that people have pointer url's at. Or we are also happy to test packages that you give urls in this mailing list. re, Jonni From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] on behalf of Andreas Enbacka [aenba...@gmail.com] Sent: Tuesday, November 12, 2013 12:01 PM To: Sailfish OS Developers Subject: [SailfishDevel] Sailfish app - testing on real device Hello, I am working on porting QSpot Spotify client to SailfishOS, and wondered how reliable testing should be performed. Currently I can test the application on the Emulator; however I have issues with no sound and random application startup issues (not present on current N9/N900 version of QSpot based on the same code / library). Should I assume that these could be issues with the emulator, and it might work correctly on the real Jolla device? And is the only current possibility to get real device test feedback to submit a rpm package to the Jolla Harbour? Regards, Andreas Enbacka ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
[SailfishDevel] Sailfish app - testing on real device
Hello, I am working on porting QSpot Spotify client to SailfishOS, and wondered how reliable testing should be performed. Currently I can test the application on the Emulator; however I have issues with no sound and random application startup issues (not present on current N9/N900 version of QSpot based on the same code / library). Should I assume that these could be issues with the emulator, and it might work correctly on the real Jolla device? And is the only current possibility to get real device test feedback to submit a rpm package to the Jolla Harbour? Regards, Andreas Enbacka ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Jolla Harbour and Jolla Store
Hello, Some questions concerning Android application submission to Jolla Harbour: 1) What Android API levels are supported? 2) Are Android applications that utilize Play Services compatible with SailfishOS (e.g., use Android notifications etc.) Thanks, Andreas Enbacka Ahoy all, Today we're launching Jolla Harbour , the portal for submitting applications to the Jolla Store. You can submit and manage your applications. Consumers will be able to install them directly from their Jolla phones. Here are some details about Jolla Harbour: Joining and logging into Jolla Harbour: Joining is free! You can create a Jolla account from the Jolla Harbour landing page (harbour.jolla.com) or if you have pre-ordered your Jolla phone, you have everything you need to get started. To manage your account details, please visit account.jolla.com. Support for Sailfish and Android™ applications: You can submit both Sailfish and Android™ applications to Jolla Harbour. The submission process is the same. Start with free applications: At launch, the Jolla Harbour and Jolla Store will support only free applications. We are working hard to enable payment solutions and we will keep you posted about these capabilities as they develop. Binary package naming: You will receive naming guidelines when you upload the binary package to Jolla Harbour. You can also find guidelines on versioning at http://semver.org. Preparing your metadata: Jolla Harbour needs to know a few things about your app: - An app icon for the Store (86x86px, png) (Current SDK supports 90x90px images; more details to follow soon) - 1-3 screenshots (540x960px, png or jpg) - An optional Cover image for your Store page (516x252px, png or jpg) Submission process: To submit your application to Jolla Harbour, fill in the metadata for it and upload the binary and required images. After you have submitted your app, Jolla will start Quality Assurance testing. Quality Assurance testing: Jolla will perform QA testing on your applications on real Jolla devices. We will get back to you with feedback on your app within a few days. You will be notified on the QA results via the email address you have registered to your Jolla account. If you encounter any issues, please contact us by email, developer-c...@jolla.com, or report them to the Sailfish developers mailing list at devel at lists.sailfishos.org. Happy hacking! The Jolla Store Team ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
[SailfishDevel] No audio codecs on SailfishOS emulator
Hello everyone, I am currently working on porting the QSpot Spotify client to SailfishOS using the latest SDK based on Qt5 and QtQuick2. However, I have problems using QAudioOutput class on the emulator; when using push-mode and calling write method with the pcm audio data, it returns 0. Also, QAudioDeviceInfo::supportedCodecs returns an empty list. Is it so that audio playback using QAudioOutput is not currently supported on the SailfishOS emulator? Any info would be greatly appreciated. Regards, Andreas Enbacka ___ SailfishOS.org Devel mailing list
