Re: [SailfishDevel] Introducing the Jolla Tablet Developer Device loan program (Pilot)
Hi, On 29.05.2015 11:14, Michele Tameni wrote: As many other of us I backed the tablet, and now I'm curious if the early access to the SDK will be limited to the developer in the program or will be opened up to every one? Seems this needs a little bit of explanation. Plan was to ship an 'early SDK' (for the developer program) just with a build target, without any 'tablet emulator' (we are not sure, that we get that working till then). So our thinking was that it does not make a lot of sense if you can build the software for the tablet, but don't have any target to try it out. So this led to a wording in the announcement text, which might give the impression that this SDK is exclusive just for the participants of the developer program. It's more that we don't think it's very useful for others. It's very likely that already this 'early SDK' already can be downloaded by anybody. And the plan is, as soon we have an SDK which also contains a 'tablet emulator' and works, we will make it public available for all, so you can start porting your apps. This might be already fall together with the start of the developer program, or be a little later. Sorry for any confusion and I hope this explains it. thanks and best regards Reto I will like to have the ability to check and port my apps to the new devices before it will be in the hand of the many backers, and as the delivery should be in July having the SDK in June seems good even if we have to wait the tablet outside the developer program. Thankyou Michele 2015-05-29 9:57 GMT+02:00 Tone Kastlunger users.giulie...@gmail.com: It's an interesting question! I back it up! On Fri, May 29, 2015 at 10:56 AM, Andrey Kozhevnikov coderusin...@gmail.com wrote: Thank you, cool news. What about developers, who backed tablet on indiegogo? 29.05.2015 12:52, Iekku Pylkka пишет: Ahoy, Here’s text version from today’s blog post about Tablet Develor Device Loan Program Pilot, you can check full version from: https://blog.jolla.com/jolla-tablet-developer-device-loan-program-starting-soon/ Jolla Tablet Developer Device loan program starting soon From the launch of Jolla smartphpone, to the opening of Jolla Harbour [0] (accepting apps to Jolla Store), to the recent introduction of the Jolla tablet [1], our community members have asked for a Developer Program they can participate in. This demand for a Developer Program certainly did not go unnoticed! Already about a year ago, we introduced the community beta (cbeta) group as an endeavor to collect feedback from our community. We take this opportunity to thank our cbeta members for making this a success by giving us honest feedback on how each release candidate is perceived! In addition we’ve been paving the road for a smoother developer experience every step of the way. Some of our efforts have included: accepting more APIs for Harbour, regular Sailfish OS and open source collaboration meetings, renewing Sailfish OS portal at sailfishos.org [2], and also bringing the missing Silica documentation [3] back. Introducing the Jolla Tablet Developer Device loan program We are now ready to take the next step in our Developer Program, and pilot a developer program for the Jolla Tablet! We have decided to make the pilot phase invite-only, to keep the program focused and manageable as we start it off. We aim for an Unlike Developer Program, fitting the unique needs of our community. The developers who will be getting their personal invitations within the next few weeks are hand-picked based on their technical contributions to Sailfish OS. These are active community members (including current cbeta members), and we trust that they will provide appropriate feedback during the pilot to serve the program expansion in the future. What we are piloting now is the Jolla Tablet Developer Device loan program. Within the program we will ship a number of loan devices to selected developers by the end of June, along with early access SDK and tablet Software Release(s). As the SDK and tablet software releases aren’t public yet, the devices and software will be given out for selected developers under a common Product Loan Agreement (PLA). In return, we expect feedback in the form of failure reports and suggestions for better process. We are taking this step by step, so please be patient. We will see how it goes and evaluate what else we can provide or what is needed from the developer community. If you do not receive an invitation for the program pilot, please do not worry and bear with us for a little longer. We will share info about future opportunities to join the Developer Program as it grows. [0] https://harbour.jolla.com/https://harbour.jolla.com/ [1] https://jolla.com/tablethttps://jolla.com/tablet [2] http://sailfishos.org/http://sailfishos.org/ [3] https://sailfishos.org/develop/docs/silica/ https://sailfishos.org/develop/docs/silica/
Re: [SailfishDevel] QtFeedback 5.0 not allowed? Really?
On 30.04.2015 01:49, Martin Kolman wrote:
Wed, 29 Apr 2015 12:56:20 + Kimmo Lindholm kimmo.lindh...@eke.fi:
Any news about whitelisting QtFeedback?
-kimmo
Also what about QtPositioning ? I know that the pull request for RPM
validator has already been merged a while ago,
but when I recently tried to submit an application using QtPositioning
to Harbour, I got a reply that is actually still not yet allowed...
as always, the new APIs get allowed once the matching SDK is out. As
communicated earlier QtPosition will be allowed with 1.1.4.x, but that
is not even out yet for all (just early access).
So please be patient a little more, thanks.
Regarding QtFeedback, it still needs somebody to step up and take over
maintainership, ideally upstream.
Once it's stabilized then, we can allow it in Harbour.
best regards
Reto
Martin
-Original Message-
From: devel-boun...@lists.sailfishos.org [mailto:devel-
boun...@lists.sailfishos.org] On Behalf Of Reto Zingg
Sent: 2. joulukuuta 2014 11:00
To: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] QtFeedback 5.0 not allowed? Really?
Hi,
On 01.12.2014 23:34, sailfishmail wrote:
Another observation:
You're allowed to require qt5-qtfeedback in your RPM-packaging
according to the faq:
https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/blob/1.18/all
owed_requires.conf
It's a mistake that qt5-qtfeedback made it into the
allowed_requires.conf file.
It's out for update 10:
https://github.com/sailfish-sdk/sdk-harbour-
rpmvalidator/blob/1.21/allowed_requires.conf
As soon as this libQt0Feedback.so.0 naming mess (note the 0 between
Qt and
Feedback!) is clean up, we will allow QtFeedback in Harbour (will
probably not
make it to the next update, but in a later one).
br
Reto
which installs
/usr/lib/libQt0Feedback.so.0
/usr/lib/libQt0Feedback.so.0.0
/usr/lib/libQt0Feedback.so.0.0.0
/usr/lib/qt5/qml
/usr/lib/qt5/qml/QtFeedback
/usr/lib/qt5/qml/QtFeedback/libdeclarative_feedback.so
/usr/lib/qt5/qml/QtFeedback/plugins.qmltypes
/usr/lib/qt5/qml/QtFeedback/qmldir
However, according to
https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/blob/1.18/all
owed_libraries.conf
and
https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/blob/1.18/all
owed_qmlimports.conf you're not allowed to use what you required to be
installed.
Maybe some misunderstanding when making the harbour validation scripts?
-Asser
Mon, 01 Dec 2014 22:08:34 +0100
Peter Pykäläinen peter.pykalai...@gmail.com kirjoitti:
Thanks Kimmo!
That was new.
And it fails:
Libraries
=
ERROR [/usr/bin/harbour-sailraid] Cannot link to shared library:
libQt0Feedback.so.0
INFO [/usr/bin/harbour-sailraid] Please see our FAQ here:
https://harbour.jolla.com/faq#Shared_Libraries
FAILED
Requires
ERROR [libQt0Feedback.so.0] Cannot require shared library:
'libQt0Feedback.so.0'
INFO [harbour-sailraid] Please see our FAQ here:
https://harbour.jolla.com/faq#2.6.0 how to use
'__provides_exclude_from' and '__requires_exclude' .spec file to
avoid that FAILED
And it fails totally.
Not fun.
So no vibration then, how can this basic stuff not be accepted?
// Peter Pykäläinen
On 1 December 2014 at 22:57, Kimmo Lindholm kimmo.lindh...@eke.fi
wrote:
Run the pre-validation tool from SDK, if you get green there, it’s
much closer to approval…
(I prefer accessing it through browser,
http://127.0.0.1:8080/C/harbour_tools/ )
-kimmo
*From:* devel-boun...@lists.sailfishos.org [mailto:
devel-boun...@lists.sailfishos.org] *On Behalf Of *Peter Pykäläinen
*Sent:* Monday, December 01, 2014 10:34 PM
*To:* Sailfish OS Developers
*Subject:* Re: [SailfishDevel] QtFeedback 5.0 not allowed? Really?
Hi,
yes I did, thank you all for your help.
Especially Andrey, you are the man!
Let's see now if this passes harbour QA or not :)
// Peter Pykäläinen
On 1 December 2014 at 22:30, Gabriel Böhme
m.gabrielboe...@googlemail.com wrote:
Have you tried cleaning the project? Helps sometimes.
Am Mon Dec 01 2014 21:18:17 GMT+0100 (CET) schrieb Peter Pykäläinen:
I give up!
Once I figured out how to add the stupid haptics stuff into the
.pro
file I
then get errors on my main when I try to compile:
error: undefined reference to `SailfishApp::application(int,
char**)' error: undefined reference to `SailfishApp::createView()'
error: undefined reference to `SailfishApp::pathTo(QString const)'
I have used this kind of code succesfully in my other app and no
issue there.
Any help would be much appreciated.
My main looks like this:
#ifdef QT_QML_DEBUG
#include QtQuick
#endif
#include sailfishapp.h
#include rumbler.h
#include QQuickView
#include QQmlContext
#include QGuiApplication
int main(int argc, char *argv[])
{
// SailfishApp::main() will display qml/template.qml, if you
need
more
// control over initialization, you can use:
//
// - SailfishApp::application(int, char *[]) to get the
QGuiApplication
Re: [SailfishDevel] Harbour: Allow more libraries to link against
Hi, On 28.12.2013 18:56, Ruediger Gad wrote: Hi, thanks for the reply. It's good to know that this is the right channel and that you are listening. :) Unfortunately, I discovered two more libs some other apps I may try to port would rely on: - libsndfile libsndfile, is now allowed in Harbour. Rpmvalidator allowing it is part of SDK 1502: https://lists.sailfishos.org/pipermail/devel/2015-March/005771.html br Reto - qt5-qtconnectivity-qtbluetooth Those are the package names and not the actual library names but I hope that's sufficient. Both seem also to be available already for SailfishOS. libsndfile is even already installed on my Jolla by default. I don't want to sound demanding but I am really motivated to push apps to Harbour and those are the libs I would need to link against. Best regards, Ruediger PS: In some cases statically linking or shipping a lib with an app might solve the issue. However, it feels kind of wrong to do this when a lib is available anyhow. And there may be other cases in which you end up in a long dependency chain such that these workarounds are not practical. Furthermore, to me as a developer, adding such workarounds is an additional overhead and takes time I'd prefer to invest somewhere else, like actually improving an app or writing/porting a new one. Please do not mistake me, I don't want to sound rude but just want to explain my situation. PPS: As people start to develop more apps now (hopefully ;)), I assume that even more people will come up with requests for libs to link against. Would it make sense to have a more centralized place to discuss this or to collect requests? I mean to have a place for devs as well as for you to quickly see which libs had already been requested and to possible vote for libs. E.g., would it make sense to use together.jolla.com for this and maybe add a tag like #harbour-lib-request or something? On 12/27/2013 06:04 PM, Reto Zingg wrote: Hi, On 27.12.2013 18:48, Ruediger Gad wrote: I hope this is the right channel to address this request to. If not, please redirect me in the appropriate direction. for once a nice request and not just ranting :-) this is the right channel. We heard you and will look into it, but I can't promise any time frame when will finally decide whenever we will allow it or not. br Reto ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Ignoring source control directory in the final rpm
Hi, On 27.01.2015 14:55, Andrey Kozhevnikov wrote: but initially, why having git tree in qml folder and not in the root project folder? see below: 27.01.2015 09:10, Juho Rutila пишет: Hi Reto, snip The reason for this is that I have a git submodule in the feedlib directory. What should I add and where to ignore the .git directory in there? I think it should be in .pro-file in the OTHER_FILES or something. snap it's a 'git submodule'. br Reto ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Harbour libssl and libcrypto
Hi Jakub, On 19.01.2015 17:35, Reto Zingg wrote: Hi, On 19.01.2015 17:34, Jakub Skokan wrote: On 01/19/2015 04:30 PM, Reto Zingg wrote: On 19.01.2015 17:29, Andrey Kozhevnikov wrote: Also i can't find usage of QCA in your project code. And haveclip-core submodule is set to some private repository. Forgot to mention that, it's here: https://github.com/aither64/haveclip-core Only submodule points to my private repo. yeah that's why I was asking for the resulting RPM :) https://secure.havefun.cz/~aither/harbour-haveclip-0.14.0-1.armv7hl.rpm ok thx, I'll check it out. Can you please try again to upload the RPM, it should now work. Sorry for any inconveniences, we forgot to add the new allowed libraries with update 10 too all relevant bits and pieces. So Harbour back-end didn't know about it. Our admins now updated it, so it should work. thanks for your patient and best regards Reto br Reto ___ 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] Harbour libssl and libcrypto
On 19.01.2015 17:29, Andrey Kozhevnikov wrote: Also i can't find usage of QCA in your project code. And haveclip-core submodule is set to some private repository. yeah that's why I was asking for the resulting RPM :) 19.01.2015 20:20, Jakub Skokan пишет: Hello, has anyone succeeded in publishing an app requiring libssl in Harbour? Even though the RPM validator tool in Qt Creator says my package is ok, when I try to upload it to Harbour, it fails: No OS version and packages satisfy package requirements: Requirement libcrypto.so.10 not available Requirement libcrypto.so.10(libcrypto.so.10) not available Requirement libssl.so.10 not available Requirement libssl.so.10(libssl.so.10) not available Those are the exact libraries that are supposed to be whitelisted, so I'm at a loss... When installed on the phone running latest OS version using Qt Creator (deploy by RPM), it works as expected. For reference, the source code of the app and resulting RPM is here: https://github.com/aither64/haveclip-mobile I'm shipping a private library (QCA), which requires libssl, don't know if that may be the problem or why. Thanks for any hints. Jakub ___ 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] Harbour libssl and libcrypto
Hi, On 19.01.2015 17:34, Jakub Skokan wrote: On 01/19/2015 04:30 PM, Reto Zingg wrote: On 19.01.2015 17:29, Andrey Kozhevnikov wrote: Also i can't find usage of QCA in your project code. And haveclip-core submodule is set to some private repository. Forgot to mention that, it's here: https://github.com/aither64/haveclip-core Only submodule points to my private repo. yeah that's why I was asking for the resulting RPM :) https://secure.havefun.cz/~aither/harbour-haveclip-0.14.0-1.armv7hl.rpm ok thx, I'll check it out. br Reto ___ 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] Harbour libssl and libcrypto
Hi, On 19.01.2015 17:20, Jakub Skokan wrote: Hello, has anyone succeeded in publishing an app requiring libssl in Harbour? Even though the RPM validator tool in Qt Creator says my package is ok, when I try to upload it to Harbour, it fails: No OS version and packages satisfy package requirements: Requirement libcrypto.so.10 not available Requirement libcrypto.so.10(libcrypto.so.10) not available Requirement libssl.so.10 not available Requirement libssl.so.10(libssl.so.10) not available yeah sounds about right. Those are the exact libraries that are supposed to be whitelisted, so I'm at a loss... When installed on the phone running latest OS version using Qt Creator (deploy by RPM), it works as expected. For reference, the source code of the app and resulting RPM is here: https://github.com/aither64/haveclip-mobile can you maybe share the resulting RPM somewhere? So we can download it and examine? thx and br Reto I'm shipping a private library (QCA), which requires libssl, don't know if that may be the problem or why. Thanks for any hints. Jakub ___ 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] Harbour news
Hi, On 18.12.2013 10:32, dcali...@free.fr wrote: Hello, Selon Iekku Pylkka iekku.pyl...@jolla.com: 5) New APIs are approved as we go along - we'll inform you when you're allowed to use new APIs in Harbour apps on the mailing list. If you think you need an API (library or QML import) for your Harbour app that is not yet approved, let us know on sailfish-devel. The current list of approved APIs can be found While I'm requesting for low-level libs, may I suggest two others : - libxml2. As far as I know, their API is quite stable now even if it was not the case in the past (I remember having some trouble with it in 2003, but it's history now !). as mentioned in several places before. Harbour QA started on 07. Jan 2015 to accept submissions which depend on: libxml2.so.2 - gconf. I allows to access gconf keys. It was the prefered way to store application preferences in the Maemo days, so many codes are using it. As for the Glib stuff, it has a stable API and is available already in Mer. GConf is deprecated upstream and got replaced with DConf in Update 7. See Saapunki 1.0.7.16 release notes[0]. Note: The GConf functions in mlite5 still work, and they transparently use DConf as backend now. [0] https://together.jolla.com/question/45064/release-notes-software-version-10716-saapunki/ br Reto What's your point of view on these two ? Damien. ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Questions about not yet allowed APIs
Hi, On 12.01.2014 06:43, Timur Kristóf wrote: Hi, I'd like to ask about status ETA about the following QML imports, ie. what's their current status (stability, maturity, etc) and when are we going to be able to use them in the harbour. import Qt.labs.settings 1.0 anything starting with Qt.labs is kinda red flag, no ETA on that yet. Has overlapping functionality with other org.nemomobile modules. import QtGraphicalEffects 1.0 On 07. Jan 2015 Harbour QA started to accept submissions which use QtGraphicalEffects 1.0. import QtFeedback 5.0 Is lacking an upstream maintainer and promised API stability. Once in place we can allow it in Harbour. import QtDocGallery 5.0 Is under review. No ETA. import org.nemomobile.ngf 1.0 import org.nemomobile.notifications 1.0 all org.nemomobile imports need a maintainer, API stability and documentation. Once that is in place we will allow them in Harbour. br Reto It seems to me that there's a LOT of functionality which is not available without these APIs and this is a serious impairment to harbour apps. That's why I'm interested. Thanks in advance for your answer! Cheers, Timur ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Harbour should allow libcrypt/openssl
Hi, On 07.12.2013 21:37, Mikael Hermansson wrote: I think harbour store should allow libcrypt/openssl because AFAIK that API will not change very often and is probadly already used in sailfishos? as mentioned in several places before. Harbour QA started on 07. Jan 2015 to accept submissions which depend on: libssl.so.10 libcrypto.so.10 best regards Reto I guess there is some apps that want to use AES/MD5/SHA256 and so on. Passwordwallet apps and similar Regards Mikael ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Harbour: Allow more libraries to link against
Hi, On 27.12.2013 18:48, Ruediger Gad wrote: Hi, two of my apps (MeePasswords and Q To-Do) are being rejected because they are linked against libraries that are not allowed. I read the according FAQ at https://harbour.jolla.com/faq and understand your motivation for being so restrictive. However, I'd love to add these apps to Harbour and I think that the libs as well as their API are pretty much stable and should be suited for addition to the whitelist of allowed libs. The relevant libraries are: - libqmfclient5.so.1 - libssl.so.10 - libcrypto.so.10 as mentioned in several places before. Harbour QA started on 07. Jan 2015 to accept submissions which depend on: libssl.so.10 libcrypto.so.10 Unfortunately libqmfclient5.so.1 is not yet among the allowed libraries. There are API changes coming up and the library is not widely requested, so it does not have high priority to be allowed in Harbour soon. best regards Reto It would be great if these could be added to the allowed libraries to link against. Some explanation what I use these libs for: libqmfclient5.so.1: Both of my apps offer a synchronization feature that uses IMAP for synchronising files between different devices. For this, I use the IMAP/e-mail API as provided by QMF. libssl.so.10 libcrypto.so.10 MeePasswords uses cryptography to encrypt data. For this it uses qca-qt5 which links against said libs. I know that there is qca-qt5 already in nemo:devel:mw (I actually filed the PR to enable packaging of the qt5 version) but it is not supported for Harbour apps yet. I also requested the addition of qca-qt5 to the allowed libs some time ago. As work-around I ship qca-qt5 with my app and thus need to link against said libs in the meantime. I hope this is the right channel to address this request to. If not, please redirect me in the appropriate direction. Thanks and best regards, Ruediger ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Jolla release plan for high-level features - update 9
Hi, On 14.12.2014 15:06, Pekka Koivunen wrote: Hello! I must ask, because i am waiting the next update Jolla Uitukka, and yuo are promised, that it is ready end of september 2014, but now is 14 december and , when this update is ready for all Jolla users? It was very nice, because you answer to me. Have you missed our latest announcement regarding the releases on together.jolla.com? please check out: https://together.jolla.com/question/68125/official-announcement-current-status-of-update10/ br Reto BR / Pekka Koivunen from Finland. Hello everyone, We are back from a refreshing summer break and have some good things lined up. First and foremost, we are now quite positive about upgrading to Qt5.2 with the next OS update. Major changes: * We have made changes to the forward and backward indicator glow on the PageStack silica component, primarily to communicate to the user when there is more content to the left/right of the screen. * Accounts framework has undergone a fair amount of unification, making the account setup process more user friendly. * App dialogs have been redesigned for easier access of cancel and accept actions and to clearly separate dialogs visually from normal app pages. The old design was seen confusing by the new users. This moves the accept and cancel buttons from the page area to a persistent header above the page, which may cause some visual regression in 3rd party applications that assume the dialog page fills the whole display. No changes are needed for most of the dialogs as we have tried to be backwards compatible as much as it was possible with the new design. But, some breakages are to be expected. In addition, we hope to release the following features * Search support in media player https://together.jolla.com/question/17615/searching-in-music-player/ * Copy unsaved numbers from call log https://together.jolla.com/question/41245/possibility-to-copy-number-by-long-press-in-call-history/ * Kazakh keyboard layout * Finer control to enable/disable AGPS assistance for obtaining location fix * Automatically save draft emails on page exit https://together.jolla.com/question/4040/mail-prompt-before-discarding-message-being-composed/ * Fix to a bug which caused camera to overwrite captured media * Simplified startup wizard flow * Improved Homescreen performance and Sailfish application memory use (thanks to the new Qt 5.2 rendering pipeline, and background apps not keeping buffers and opengl context in memory). To recap the implications for app developers, please refer to https://www.mail-archive.com/devel@lists.sailfishos.org/msg04084.html. * Browser engine update to Gecko 31 to improve compatibility with various web sites and improving scrolling performance * Fix to WLAN disconnect issue while roaming due to RSN IE mismatch * Internet interface MTU resized to 1280 bytes for mobile data to overcome issues with some operator infrastructure As usual, this comes with a friendly disclaimer that it is an intent of the release content and not a promise. We also noticed that signing up for a new Facebook account from a Jolla device is no longer possible. The drop-down selection for birthday does not work, hence making it impossible to complete the signing up process. We suspect that it is most likely due to changes from Facebook, nevertheless we'll continue to keep an eye on this issue. Regards, Soumya ___ 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] Changes in Harbour Web UI
Hi, On 12.12.2014 17:56, Andrey Kozhevnikov wrote: 12.12.2014 20:41, Developer Care пишет: - Does Harbour QA test the application on all OS versions? No. Normally QA tests the application only with the latest released OS version. I hope you will test at least with u8 and u9? current praxis is that we test on Update 8, if it does not work there or the developer stressed out it just works on Update 9, then we test it on Update 9. Once Update 10 is public available (not during Opt-In period), we will start testing just on Update 10. br Reto ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] QtFeedback 5.0 not allowed? Really?
Hi,
On 01.12.2014 23:34, sailfishmail wrote:
Another observation:
You're allowed to require qt5-qtfeedback in your RPM-packaging
according to the faq:
https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/blob/1.18/allowed_requires.conf
It's a mistake that qt5-qtfeedback made it into the
allowed_requires.conf file.
It's out for update 10:
https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/blob/1.21/allowed_requires.conf
As soon as this libQt0Feedback.so.0 naming mess (note the 0 between Qt
and Feedback!) is clean up, we will allow QtFeedback in Harbour (will
probably not make it to the next update, but in a later one).
br
Reto
which installs
/usr/lib/libQt0Feedback.so.0
/usr/lib/libQt0Feedback.so.0.0
/usr/lib/libQt0Feedback.so.0.0.0
/usr/lib/qt5/qml
/usr/lib/qt5/qml/QtFeedback
/usr/lib/qt5/qml/QtFeedback/libdeclarative_feedback.so
/usr/lib/qt5/qml/QtFeedback/plugins.qmltypes
/usr/lib/qt5/qml/QtFeedback/qmldir
However, according to
https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/blob/1.18/allowed_libraries.conf
and
https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/blob/1.18/allowed_qmlimports.conf
you're not allowed to use what you required to be installed.
Maybe some misunderstanding when making the harbour validation scripts?
-Asser
Mon, 01 Dec 2014 22:08:34 +0100
Peter Pykäläinen peter.pykalai...@gmail.com kirjoitti:
Thanks Kimmo!
That was new.
And it fails:
Libraries
=
ERROR [/usr/bin/harbour-sailraid] Cannot link to shared library:
libQt0Feedback.so.0
INFO [/usr/bin/harbour-sailraid] Please see our FAQ here:
https://harbour.jolla.com/faq#Shared_Libraries
FAILED
Requires
ERROR [libQt0Feedback.so.0] Cannot require shared library:
'libQt0Feedback.so.0'
INFO [harbour-sailraid] Please see our FAQ here:
https://harbour.jolla.com/faq#2.6.0 how to use
'__provides_exclude_from' and '__requires_exclude' .spec file to
avoid that FAILED
And it fails totally.
Not fun.
So no vibration then, how can this basic stuff not be accepted?
// Peter Pykäläinen
On 1 December 2014 at 22:57, Kimmo Lindholm kimmo.lindh...@eke.fi
wrote:
Run the pre-validation tool from SDK, if you get green there, it’s
much closer to approval…
(I prefer accessing it through browser,
http://127.0.0.1:8080/C/harbour_tools/ )
-kimmo
*From:* devel-boun...@lists.sailfishos.org [mailto:
devel-boun...@lists.sailfishos.org] *On Behalf Of *Peter Pykäläinen
*Sent:* Monday, December 01, 2014 10:34 PM
*To:* Sailfish OS Developers
*Subject:* Re: [SailfishDevel] QtFeedback 5.0 not allowed? Really?
Hi,
yes I did, thank you all for your help.
Especially Andrey, you are the man!
Let's see now if this passes harbour QA or not :)
// Peter Pykäläinen
On 1 December 2014 at 22:30, Gabriel Böhme
m.gabrielboe...@googlemail.com wrote:
Have you tried cleaning the project? Helps sometimes.
Am Mon Dec 01 2014 21:18:17 GMT+0100 (CET) schrieb Peter Pykäläinen:
I give up!
Once I figured out how to add the stupid haptics stuff into
the .pro
file I
then get errors on my main when I try to compile:
error: undefined reference to `SailfishApp::application(int,
char**)' error: undefined reference to `SailfishApp::createView()'
error: undefined reference to `SailfishApp::pathTo(QString
const)'
I have used this kind of code succesfully in my other app and no
issue there.
Any help would be much appreciated.
My main looks like this:
#ifdef QT_QML_DEBUG
#include QtQuick
#endif
#include sailfishapp.h
#include rumbler.h
#include QQuickView
#include QQmlContext
#include QGuiApplication
int main(int argc, char *argv[])
{
// SailfishApp::main() will display qml/template.qml, if
you need
more
// control over initialization, you can use:
//
// - SailfishApp::application(int, char *[]) to get the
QGuiApplication *
// - SailfishApp::createView() to get a new QQuickView *
instance
// - SailfishApp::pathTo(QString) to get a QUrl to a
resource file
//
// To display the view, call show() (will show fullscreen on
device).
//return SailfishApp::main(argc, argv);
QScopedPointerQGuiApplication
app(SailfishApp::application(argc,
argv));
QScopedPointerQQuickView view(SailfishApp::createView());
Rumbler rumbler;
view-rootContext()-setContextProperty(Rumbler, rumbler);
view-setSource(SailfishApp::pathTo(qml/harbour-myapp.qml));
view-show();
view-showFullScreen();
return app-exec();
}
// Peter Pykäläinen
On 1 December 2014 at 15:08, Andrey Kozhevnikov
coderusin...@gmail.com wrote:
I can suggest you to use QtFeedback from Qt side and register
QML
type.
01.12.2014 18:06, Peter Pykäläinen пишет:
Just got my game rejected in Jolla Harbour this morning due
to:
*Import 'QtFeedback 5.0' is not allowed *
Is it really so that vibration is not allowed in Harbour apps?
Is there any alternative?
// Peter Pykäläinen
Re: [SailfishDevel] Locked in QA
Hi, On 08.06.2014 01:48, Krisztian Olah wrote: Hi Sailors, I submited an update to my app London Sail yesterday, today noon I found a blocker bug in one of the features, so I was trying to remove the app going through QA before it goes out, but unfortunately it was already locked (being processed?) in QA. I did remove the binary through the web interface, and it seemed to stopped my app going live. I fixed the bug and uploaded the new binary, but now it shows up as Locked in QA and I cannot (re)submit it. I realize that I am the one at fault and I do appologize if it causes/caused any inconvenience, but could you please unblock my App? I did submit the new binary, but if it is preferable I can manually resubmit it once the lock is removed. Thanks very much and sorry again Kris Sorry for the delay, but during the weekend non of Harbour Sailors was reading the mailing list and saw your request. We unlocked the application now, so you can update it. Sorry for any circumstances and regards Reto ___ 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] What happens on Harbour between approved and published?
Hi, ups somehow I missed that, sorry. On 13.04.2014 14:47, Matthias Fehring wrote: Hello, does anyone know what happens on Harbour between the approved and the published status? One of my apps (Markat) is now appoved in a new version since two days, but keeps in that state instead of getting published. Or is it only because of weekend? ;-) Normally when an app gets approved it's imported to store within the next 30min... But sometimes something goes wrong and the import fails, and in rare cases we miss that something failed... that was the case here. Sorry about that. Version 0.1.3 is now available from store. best regards Reto Best greetings Buschmann ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] RPM validator question
Hi, On 25.03.2014 20:59, Iosif Hamlatzis wrote: The QtCreator IDE under the Harbour Tools provides an RPM validator. I just wanted to test my package but I get the message the file is too large. Is there a maximum file size only for the validator or also for the actual jolla shop? Yes there is a limit in the web frontend 'Harbour Tools', it's ~40MB. The used web server somehow can't handle bigger files and we didn't had yet time to investigate it. You can do the check also on CLI: On Linux, login to the Build-Engine virtual box: $ ssh -p -i ~/SailfishOS/vmshare/ssh/private_keys/engine/mersdk mersdk@localhost then inside the build engine: $ rpmvalidation.sh harbour-myapp-0.1-4.arch.rpm In that case the limit is the /tmp size (unpacked rpm) which is ~249MB in the build engine. br Reto ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] /var/log is not writable. Where do I create my logs then?
Hi, On 14.03.2014 00:58, Artem Marchenko wrote: P.S. Actually harbour FAQ tells to put at least my cache files to $XDG_CACHE_HOME subdir that is /var/log/harbour-myapp . So I guess having /var/log unwritable is a bug then see https://harbour.jolla.com/faq#2.14.0 If $XDG_CACHE_HOME is either not set or empty, a default equal to $HOME/.cache should be used. and XDG_CACHE_HOME is currently not set on device out of the box. br Reto On Fri, Mar 14, 2014 at 12:55 AM, Artem Marchenko artem.marche...@gmail.com mailto:artem.marche...@gmail.com wrote: Hi All /var/log is not writable by user nemo, so what is a good location for my log files then? I log certain events to journalctl, but I also would want app specific log file(s) for longer term analysis. /var/log looked like a good place, because it is standard and cleaned once in a while, so I don't need to care about deleting own old logs. So is /var/log not writable by mistake? Or where shall I create my log files instead? And do I have to clean them myself or can I somehow register them for deletion once a month or so? Cheers, Artem. -- Artem Marchenko http://agilesoftwaredevelopment.com http://twitter.com/AgileArtem -- Artem Marchenko http://agilesoftwaredevelopment.com http://twitter.com/AgileArtem ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] requiring libpulse.so.0
Hi, On 14.03.2014 02:10, Victor Mataré wrote: Ugh sorry, didn't read far enough: https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/blob/master/allowed_libraries.conf Question answered. Have nice day ;-) yes, it was a mistake to not add it to the allowed_requires, sorry. Is now fixed. https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/blob/df3f85f19b45bae3a1f0910821de4963c297ed14/allowed_requires.conf#L25 br Reto On Friday, 14.03.2014 01:03:13 Victor Mataré wrote: Hi all, I'm writing an app that provides a GUI for the PulseAudio network transparency features (i.e. module-tunnel-sink, possibly add RTP support later), but in https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/blob/master/allowe d_requires.conf I see that I can't require libpulse.so.0. Does that mean I just can't put it in the RPM deps, or am I actually prohibited from even linking against libpulse altogether? If so, why is that? Does it mean that no app that uses the full PulseAudio API can ever get into the Harbour? Greetings and thanks for any clarification, Victor ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Sideload Native App To Sailfish
Hi, On 05.02.2014 09:18, christopher.l...@thurweb.ch wrote: No rooting (or jailbreaking) pr verboten-hacks required. Just put the phone into developer mode. In theory any user can do this with a few clicks. Then you can install anything that will run. However this route does imply that the user has some idea of what they are doing, just a a user installing on a Linux desktop will need some idea as well. It might not be a route for a stereotypical grandma. Developer mode is not for everybody, that is clear. And the other suggested methods w/o developer mode will not work out of the box much longer as stressed out already earlier: https://lists.sailfishos.org/pipermail/devel/2014-January/002901.html As stressed out in the same mail, we work on it to make it possible to side load rpm's, if the user sets up the device to allow untrusted sources (or how ever we are gonna call that setting). br Reto Apologies in a advance to all the non-stereotypical-Linux-savvy-Jolla-wielding-grandmas who are part of this mailing list. Grüsse Chris Zitat von Network Nut sillyst...@gmail.com: Hi All, I have what I imagine to be a very common problem: 1. There will be billions of people who own smartphones. 2. I have a 100% native Linux C++ app that I would like a few of those billions of people to use. These are my future customers. 3. I do not necessarily want to use an app store of any kind, if I choose not to use any. 4. I would like for my customers to decide, at their own discretion, whether to side-load my native app onto their smartphone by going to my web site, and not an app store. 5. I would like to avoid having my customers call my tech-support line and listen on the phone for 30 minutes as one of my tech-support representatives tells him/her how to root their phone so that they can side-load my app. In other words, I would like the same situation that exists now under the desktop model, where anyone who owns a desktop computer has full discretion of what they do with their computer, without (significant) restrictions from the OS vendor. I understand that Jolla allows 100% true native C++ apps, but I was unable to determine, with a quick search on the WWW, whether Jolla allows 100% native C++ apps under the acquisition model above. Can anyone clarify? Is it true that the owner of a Jolla smartphone will be able to determine for himself/herself whether to side-load a third-party native application without jumping through hoops to bypass restrictions created by the OS? Regards, -Nut ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] bidirectional channel toward people reviewing apps in Jolla harbour?
Hi, On 29.01.2014 17:07, Zoltán Lutor wrote: Hi, What is the preferred channel for bidirectional communication with people reviewing our apps submitted into Jolla Harbour? use: developer-care at jolla.com br Reto Thx, Zoltan https://www.facebook.com/ForFictionMobile ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] harbour rejects user files in a Documents subfolder?
Hi, On 22.01.2014 11:29, Wim de Vries wrote: Hi, My checklists app got rejected by harbour again because of user data files :-( . My app creates a checklistdata folder under Documents (one default/example data file is copied there after first start up). Harbour doesn't want that: File creation in /home/nemo/Documents/ is not allowed, if these are not user documents. Files should be stored in $XDG_DATA_HOME. $XDG_DATA_HOME is silly for users: my users must be able to copy there PC created checklist files (plain text) via USB to their Jolla device. OK, this use case was not clear to us. To our understanding the app was just storing data, which the user otherwise does not modify. Please use QStandardPaths::DocumentsLocation (if you don't use that already) and resubmit your application. Sorry for the circumstances. best regards Reto $XDG_DATA_HOME is hidden, and even if it wasn't, it is very contra intuitive place for normal user to find. All users know the Documents folder. Any harbour people, having suggestions (a $XDG_ folder would render the app completely useless)? Thanks ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] How to attach a page to initial page?
Hi, On 17.01.2014 17:56, Tobi D. wrote: Hi there, How can I push an attached page to my initial page on the pageStack? I'd like to have a behavior similar to the Jolla Store app. There you can push to the next page to get categories when you are on initial page. I tried several thing to achieve this, but didn't get it work. Doing an pushAttached to pageStack in onComplete of my initial page ends in error message that you can not push a page on stack while another push is running. There is another idea I've not tried yet. Maybe it is possible to use a Timer with a few milliseconds which does the pushAttached to the pageStack and disables itself after that. But this solution sounds quite bad to me. If I understood you right, then pycage has that in his Tidings application, from the entry/main page you can access the settings with a swipe R-L, I don't know which magic he uses, but check out the sources here: https://github.com/pycage/tidings br Reto Thanks for help! Best regards, Tobi ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] SailfishOS SDK January update available today.
Hi, On 17.01.2014 15:50, Thomas Tanghus wrote: On Wednesday 15 January 2014 15:24 Jarko Vihriala wrote: Provide a tool to verify that basic submission criterias are fulfilled with Harbour intake requirements. This is done from the new view called 'Harbour Tools' in Control Center. This is a really helpful addition! I assume it will be kept in sync with Harbours verification tool? Yes we try to keep it in sync, that's why before the script is ran and the option Harbour tool updates are is enabled, a new version of the script is installed automatically. But there might be some unexpected delays in pushing a new version to the repos, and what the Harbour QA guys already use. br Reto ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Harbour: howto to delete a draft application ?
Hi, On 15.01.2014 11:16, Franck Routier (perso) wrote: Hi, when first playing with harbour, I created an Untitled application, before creating the right one. This untitled app is here in the list of my apps, with a draft status, and I can find no way to delete it. How can I do ? please contact developer-care at jolla.com and request it, AFAIK there is no way to do it for you. br Reto BR, Franck ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Random white screen issue, app has passed QA
Hi, On 14.01.2014 10:21, Kaj-Michael Lang wrote: Got my first app into the Harbour, works for me and obvisouly for QA too. But about 1/2 of the comments are people complaining that all they get is a white screen. That most likely is some error in the qml, a import plugin missing, but how can that be if QA passed it ? Any ideas? Oh, and the app in question is Y-Radio. Or better yet, anyone on list that experiences the problem ? Could you start it from the terminal and send me any error messages that might be printed ? seems you use: import QtQuick.XmlListModel 2.0 that is not by default on device. Add a dependency to: qt5-qtdeclarative-import-xmllistmodel that should fix it. We need to investigate how that could get pre installed to the device of the Harbour testers. Sorry for the troubles. br Reto ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Random white screen issue, app has passed QA
Hi, On 14.01.2014 10:34, Reto Zingg wrote: Hi, On 14.01.2014 10:21, Kaj-Michael Lang wrote: Got my first app into the Harbour, works for me and obvisouly for QA too. But about 1/2 of the comments are people complaining that all they get is a white screen. That most likely is some error in the qml, a import plugin missing, but how can that be if QA passed it ? Any ideas? Oh, and the app in question is Y-Radio. Or better yet, anyone on list that experiences the problem ? Could you start it from the terminal and send me any error messages that might be printed ? seems you use: import QtQuick.XmlListModel 2.0 that is not by default on device. Add a dependency to: qt5-qtdeclarative-import-xmllistmodel that should fix it. We need to investigate how that could get pre installed to the device of the Harbour testers. Testers also need finger term to be able to install the rpm. Fingerterm depends on qt5-qtdeclarative-import-xmllistmodel: rpm -q --whatrequires qt5-qtdeclarative-import-xmllistmodel fingerterm-1.1.8-1.7.1.armv7hl That's how the qt5-qtdeclarative-import-xmllistmodel came into the image the testers use. br Reto Sorry for the troubles. br Reto ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Jolla harbour website
Hi, On 14.01.2014 12:49, Franck Routier (perso) wrote: Hi, I suppose this is a known bug, but the stats on harbour are always at 0 (nr of downloads, likes, comments, ...), be on the dashboard, or on a specific app page. I would not call a missing feature a bug :-) This is on the todo list, is't it ? Yes, that's why there are place holders... br Reto BR, Franck ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Howto ship QML plugins for harbour
Hi, On 09.01.2014 12:39, dcali...@free.fr wrote: Hello, I need to ship two system QML plugins with my app for it to validate the harbour recommendations. How can I do this ? Let's take the example of QtPositioning lets take an other example ;-) https://github.com/nemomobile/nemo-qml-plugin-dbus which is not allowed as such in Harbour, so I had to add it: https://github.com/d0b3rm4n/harbour-simpletorch/tree/master/src/dbus I had to make changes in plugin.cpp and qmldir and install it accordingly (see dbus.pro, qmldir installs to /usr/share/$NAME/lib/harbour/simpletorch/dbus, and lib to /usr/share/$NAME/lib/). In https://github.com/d0b3rm4n/harbour-simpletorch/blob/master/src/harbour-simpletorch.cpp I had to set the addImportPath to /usr/share/$NAME/lib/ and then I can import is in .qml files as: import harbour.simpletorch.dbus 1.0 br Reto We have: [nemo@SailfishEmul devel]$ rpm -ql qt5-qtdeclarative-import-positioning /usr/lib/qt5/qml/QtPositioning /usr/lib/qt5/qml/QtPositioning/libdeclarative_positioning.so /usr/lib/qt5/qml/QtPositioning/plugins.qmltypes /usr/lib/qt5/qml/QtPositioning/qmldir So, in the spec file, I can install these three files in /usr/share/$APPNAME/qml. But in the FAQ of the harbour, they say that one should rename the import to harbour.appname.QtPositioning, when I grep QtPositioning in qmldir and plugins.qmltypes, it appears a lot of times. Should I replace all with APPNAME-QtPositioning ? Then, should the directory be renamed also ? And finally, when all is shipped in the RPM, and everything has been renamed properly, how can I expand the QML search dir to include also /usr/share/$APPNAME/qml ? Thanks for the help, have a nice day, Damien. ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Harbour QA process...
Hi, On 10.01.2014 10:36, Ruediger Gad wrote: Hi, I agree as well. Having a quicker way to check at least simple requirements would greatly improve the developer experience as well as the work of the testers at Harbour. I filed a request about this at together.jolla.com: https://together.jolla.com/question/13023/harbour-toolautomatism-for-quickly-checking-simple-compliance-requirements/ That's a duplicate request... see current answer here: https://together.jolla.com/question/1593/integrate-qa-testing-scripts-with-sailfish-sdk/#post-id-8663 br Reto This is not intended as complaint but as a request to improve things. I think, having a quicker way to check compliance would not only benefit us developers but would also ease the work of the testers at Harbour as they would not need to complain about simple standard issues that often. Besides, I just got an app rejected again (after about two days) because I missed one path that was not according to the XDG requirements. Yeah, I know, I should have looked more thoroughly (I actually grepped through all my sources but somehow still managed to miss that one thing.) but in that case a tool that I could run or a pre-check that is run automatically after uploading an *.rpm to Harbour would have been great. Best regards, Ruediger On 01/10/2014 09:01 AM, Andreas Enbacka wrote: 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: 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 ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Harbour QA process...
Hi, On 10.01.2014 11:01, Martin Windolph wrote: Hi, another point for me is a possibility to contact the tester. A prior rejection reason for an update of my game Morzyn was a missing menu button (that was absolutely ok, because it leads to bad usability, so I included one), my last rejection reason was battery consumption when minimizing while the AI players do their move. This is intended behaviour, but my game was rejected because it consumes 3%-10% CPU while the AI players move (round-based) and the game is minimized (measured by top). When the game waits for the players move, I According to my information the app got not rejected because of AI still running, but because the audio blocks the power management to go to suspend mode. And since there is no sound audible it might be that sound output is done in a not supported way. (But don't ask me how to do it correctly :-) But I'm sure here are other Sailors which can help you with that in your particular case). see also about how we test: https://lists.sailfishos.org/pipermail/devel/2014-January/002440.html br Reto don't see it in top. I love to finish my move, switch to my mail folders or read facebook messages while the other 6 AI players make their move. Another point is that in future I want to include network gaming. Therefore I also want it to run in background. The great thing of Sailfish OS is that one can simply close an app like in the good old desktop days, if you don't want it to consume power. So now I have no idea how to react on this and just did nothing, because I also have desktop and Android versions to take care of. But I'm not happy that the few users of Morzyn can't profit from the fixes of the update and have to deal with the version in store. Martin Date: Fri, 10 Jan 2014 08:57:50 +0100 From: a...@mecadu.org To: devel@lists.sailfishos.org Subject: [SailfishDevel] Harbour QA process... -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 ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Harbour QA process...
Hi,
On 10.01.2014 15:56, Martin Windolph wrote:
Hi,
oh, thanks for the information and sorry then for hijacking this thread.
I thought that it was just an assumption that Audio was the reason.
How can I find out if it's audio that is preventing suspend mode
(emulator or device)?
So Audio output seems to be really a problem in Sailfish OS. I'm using
the QML Audio Element of QtMultimedia. Isn't it supported? I use Audio
as Robin wrote in
https://together.jolla.com/question/421/qaudiooutput-isnt-integrated-with-system-volume-and-libresource-like-qmediaplayer/#post-id-6991
this combination is an issue at the moment.
But David found a workaround for that at least for his application,
which passed store QA.
checkout his main.qml from:
https://build.merproject.org/package/files?package=screenshotproject=home%3Albt%3Asailfishos
he does something like:
ffmpeg -ar 48000 -t 0.1 -f s16le -acodec pcm_s16le -ac 2 -i /dev/zero
-acodec copy noSound.wav
ApplicationWindow {
...
Audio {
id: noSound
source: /usr/share/harbour-screenshot/noSound.wav
}
// workaround a bug in QtMultimedia
Component.onCompleted: noSound.play()
}
}
br
Reto
just for a few things:
1. Play title music
2. Play attack sounds of the creatures
I temporary disabled 1. because of a known volume bug
(https://together.jolla.com/question/421/qaudiooutput-isnt-integrated-with-system-volume-and-libresource-like-qmediaplayer/)
by setting the source to null.
2. is still enabled (because I don't change their volume), but I do play
sounds only if the application is active and I don't hear anything if I
run it on my device.
Maybe setting the source of 1. to null is the reason? But in my opinion,
playing a null source should just result in a returning play() method...
the source of the audio element:
https://github.com/yoktobit/morzyn/blob/master/qml/MorzynPage.qml
Thanks
Martin
Date: Fri, 10 Jan 2014 15:29:31 +0200
From: reto.zi...@jolla.com
To: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] Harbour QA process...
Hi,
On 10.01.2014 11:01, Martin Windolph wrote:
Hi,
another point for me is a possibility to contact the tester.
A prior rejection reason for an update of my game Morzyn was a
missing
menu button (that was absolutely ok, because it leads to bad usability,
so I included one), my last rejection reason was battery consumption
when minimizing while the AI players do their move.
This is intended behaviour, but my game was rejected because it
consumes
3%-10% CPU while the AI players move (round-based) and the game is
minimized (measured by top). When the game waits for the players
move, I
According to my information the app got not rejected because of AI still
running, but because the audio blocks the power management to go to
suspend mode.
And since there is no sound audible it might be that sound output is
done in a not supported way. (But don't ask me how to do it correctly
:-) But I'm sure here are other Sailors which can help you with that in
your particular case).
see also about how we test:
https://lists.sailfishos.org/pipermail/devel/2014-January/002440.html
br
Reto
don't see it in top. I love to finish my move, switch to my mail
folders or read facebook messages while the other 6 AI players make
their move.
Another point is that in future I want to include network gaming.
Therefore I also want it to run in background. The great thing of
Sailfish OS is that one can simply close an app like in the good old
desktop days, if you don't want it to consume power.
So now I have no idea how to react on this and just did nothing,
because
I also have desktop and Android versions to take care of. But I'm not
happy that the few users of Morzyn can't profit from the fixes of the
update and have to deal with the version in store.
Martin
Date: Fri, 10 Jan 2014 08:57:50 +0100
From: a...@mecadu.org
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Harbour QA process...
-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
Re: [SailfishDevel] How to install user (controlled) data files for my app avoiding /usr/share
Hi, On 09.01.2014 12:25, Wim de Vries wrote: Thanks. On 01/09/2014 09:36 AM, Luciano Montanaro wrote: Maybe make the application download the map on the first run? mm.. I cannot afford time/money for a server + support. if the data is 'free' (in the sense you don't want to specially protect them) you could place it on e.g. http://sourceforge.net/ for download? Or do they have now a days some limits (size, per/day/month) or so? Or some git hoster, like github, gitorious, code.google.com etc... guess also needs some check that it's not abusive... br Reto Only support for the app. On the long term, users themselves may set up sth to share maps. But you must be able to provide the maps on a server in this case. The additional benefit is that the user can skip downloading the data if he knows it will not use it. Never the case in first use. Only after some time of usage. Luciano On Thu, Jan 9, 2014 at 9:05 AM, Wim de Vries wsvr...@xs4all.nl wrote: Hi, I am converting my aircraft navigation app to Sailfish. It comes (default) with OpenStreet based maps + 3D data files of Western Europe (in RPM). Most users will use this map, but some users may use their home made maps (generated by a PC application). In the latter case, the users will delete this W-Europe map (it takes up quite some disk space). So far so good, but the installation/RPM is a problem: Harbour says that I should install the app data (very much bytes for the W-Eu map) in /usr/share/$NAME and in the first run of the app, copy them to $XDG_CONFIG_HOME/$NAME. But now I am stuck with an enormous amount of (useless) data in /usr/share/$NAME that cannot be removed. Any suggestions? Thanks. ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] No inbox?
Hi, On 09.01.2014 19:03, Markus Svensson wrote: Hi, I've never been able to get email fully working on the Jolla either. I can receive email via IMAP, but can't send via SMTP. I just get the Problem with sync message. Does the mail app log errors somewhere on the device? If you have developer mode enabled, set in /home/nemo/.config/QtProject/Messageserver.conf: [StdStreamLog] Enabled=1 Then run message server in foreground pkill messageserver5; /usr/bin/messageserver5 and reproduce, any errors? Once you are done, change it back to 0 in the .conf file :-) br Reto 9 jan 2014 kl. 16:22 skrev Chris Walker cdw_noki...@the-walker-household.co.uk: On Thu, 09 Jan 2014 17:02:17 +0200 Valerio Valerio valerio.vale...@jollamobile.com wrote: On 09/01/14 16:05, Chris Walker wrote: On Tue, 7 Jan 2014 13:39:49 + Chris Walker cdw_noki...@the-walker-household.co.uk wrote: [mega snip] I have also just replied to AL13N (al...@rmail.be) closing this thread so we'll leave it there. Final comment on this. I created another new email account called jolla@the.. and went through the usual rigmarole of setting it up via the GUI. It failed to send. I then asked for help from the email hosting company who told me that no attempt had been made to log into the SMTP server. They suggested various tweaks to the settings, all to no avail although I did receive different errors on the phone. What are the smtp settings you used for android mail app ? I followed these instructions - http://www.daily.co.uk/support?id=1021 which is what I had already followed when trying to setup email on the native accounts program (daily.co.uk is my hosting company). What I find a little frustrating is that when trying to setup IMAP for cdw_pcmail@the.. the phone would send but not receive - hence no inbox which is where this thread started - but now when I have created jolla@the... it can receive but not send. But I'm using all the same settings with the same server names and so on (for those UK readers, I am reminded of the Morecambe and Wise sketch with Andre Previn!). Even more frustrating is that K9 uses the same settings and just works. So doesn't that imply that something on the phone is broken? But what? ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] xdg folder stuff: howto? more info
Hi, On 08.01.2014 10:55, Wim de Vries wrote: Hi, I am adding some more info to my question. I am using QStandardPaths. Harbour is refusing my app, stating that I should use $XDG_CONFIG_HOME Still, this var is not set. The only ones are: XDG_SESSION_ID value: c5 and XDG_RUNTIME_DIR value: /run/user/10 I need to add data files during installation, and the user should be able to add/remove data files from his PC via USB. Thanks. The spec says: If $XDG_DATA_HOME is either not set or empty, a default equal to $HOME/.local/share should be used. If $XDG_CONFIG_HOME is either not set or empty, a default equal to $HOME/.config should be used. AFAIK does QStandartPath not yet do the right thing, there is a bug. as the Harbour FAQs says about XDG_*_HOME: _Do not_ create the subfolder in the rpm package, create it during _run time_ from the application! I assume you create the folder already in the rpm? Put your files to /usr/share/$NAME and copy it form there to $XDG_DATA_HOME (if set resp. $HOME/.local/share/$NAME if not set) at launch. Or it might also be that you use /home/nemo instead of $HOME? That your app got rejected. br Reto On 01/07/2014 07:29 PM, Wim de Vries wrote: Hi, Can someone please explain how the XDG folders work. These env vars seem not be set when I try to read the values with QProcessEnvironment. So how can I read/write to those folders (C++)? And how to access them from QML? The documention/FAQ only gives a very general spec. I must be missing sth. Thanks. ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Harbour: Allow more libraries to link against
Hi, On 28.12.2013 18:56, Ruediger Gad wrote: PPS: As people start to develop more apps now (hopefully ;)), I assume that even more people will come up with requests for libs to link against. Would it make sense to have a more centralized place to discuss this or to collect requests? I mean to have a place for devs as well as for you to quickly see which libs had already been requested and to possible vote for libs. E.g., would it make sense to use together.jolla.com for this and maybe add a tag like #harbour-lib-request or something? I suggest to use together.jolla.com with the tag harbour-api-request. br Reto ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Harbour: Allow more libraries to link against
Hi, On 27.12.2013 22:16, Alejandro Exojo wrote: El Friday 27 December 2013, Reto Zingg escribió: for once a nice request and not just ranting :-) I can fix that! Y U NO SHIP MA LIBRARY?! ;-) this is the right channel. We heard you and will look into it, but I can't promise any time frame when will finally decide whenever we will allow it or not. In the meantime, correct me if I'm wrong, but I understood that one can ship libraries in the package, as long as you care about setting RPATH (and other packaging issues) yourself. Yes, if you ship the libraries your self (and the libraries it self, just depend on allowed libraries). Then you are fine to submit to Harbour. br Reto Is definitely not the optimal solution that we, Linux enthusiasts like, but is what Windows and Android developers do, and look at their marketshare! A trillion flies can't be wrong! :-) ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Harbour: Allow more libraries to link against
Hi, On 02.01.2014 11:28, Ville Ranki wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-12-27 22:16, Alejandro Exojo wrote: In the meantime, correct me if I'm wrong, but I understood that one can ship libraries in the package, as long as you care about setting RPATH (and other packaging issues) yourself. Can you recommend a tutorial or example on how to do this properly on Sailfish? We didn't had the time yet to write one and I'm not aware if somebody form the community has written something. Another Harbour question: My app is reported to cause too many wakeups per second. The app is completely asynchronous and nothing should be happening when it is idle. How can i debug issues like this? What tool can i use to measure wakeups? use powertop: ssu ar mer-tools pkcon install powertop connect over ssh to device, start your app, let the screen blank, wait an other 10s, then start the powertop command over ssh, w/o any parameters (that's how Harbour QA does it). If wake ups are below 60, the app is accepted (that is the current value and not written into stone and might change any time), if it's over 60 we research deeper if there is a good reason (e.g. Internet Radio app) to still accept it. If not then we reject it. Most likely you have still some timer running? Stop them when your app is not active. br Reto - -- Ville Ranki ville.ra...@iki.fi http://www.iki.fi/~cos PGP public key: http://www.iki.fi/~cos/vranki_pub.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLFMSwACgkQVm11nqR7UVwGowCcDq/6s+tNWzdbW1iLAG7s3F0M osEAn0HAPR3lX8Zk1VA2wm0PFF96oB2Z =oOzQ -END PGP SIGNATURE- ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Harbour: Allow more libraries to link against
Hi, On 27.12.2013 18:48, Ruediger Gad wrote: I hope this is the right channel to address this request to. If not, please redirect me in the appropriate direction. for once a nice request and not just ranting :-) this is the right channel. We heard you and will look into it, but I can't promise any time frame when will finally decide whenever we will allow it or not. br Reto ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Harbour news
Ahoy, short update. On 17.12.2013 17:43, Iekku Pylkka wrote: 4) Heads up: Soon we won't allow any files not needing the execution bit set, to have it set. So .png, .desktop and .qml files (and any other file you package with your rpm, except the binary) are not allowed to have permission 755, just 644! You might now get with your rejection info some warning about that, e.g. WARNING [/usr/share/$NAME/qml/pages/main.qml] File must not be executable This is not yet the reason that your rpm got rejected! Just an info that you might need to change something in future. Details will follow. 5) New APIs are approved as we go along - we'll inform you when you're allowed to use new APIs in Harbour apps on the mailing list. If you think you need an API (library or QML import) for your Harbour app that is not yet approved, let us know on sailfish-devel. The current list of approved APIs can be found on https://harbour.jolla.com/faq We allow now some more libraries, please check out: https://harbour.jolla.com/faq Happy hacking Reto ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Any reach to support related to Jolla harbour QA decision?
Hi, On 22.11.2013 08:49, Zoltán Lutor wrote: Hi, Do you happen to know any contact info who reply on questions related to QA decision of Jolla harbour? can you please contact: developer-care at jolla.com br Reto I've got some really strange reasoning why my apps were rejected but there is no any possibility to reply to those decision. Thanks, Zoltan ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Update on application naming for Harbour applications
Hi, On 22.11.2013 16:39, Andrey Kozhevnikov wrote: really? harbour-org.coderus.application how domain.organization.application naming can clash with device packages? why? QtCreator does not allow it: https://qt.gitorious.org/qt-creator/qt-creator/source/54636d9756966fab7365043d8fd255993675e935:src/libs/utils/projectnamevalidatinglineedit.cpp#L46 br Reto On 22.11.2013 20:32, Robin Burchell wrote: Ahoy, In Iekku’s mail yesterday, we referred to application names needing to use a “dotted” form (e.g. com.example.myapp). It was brought to our attention that this isn’t factually possible at this time due to limitations in Qt Creator/qmake, so we’re unfortunately forced due to time limitations - so as to not inconvenience you developers - to change plans. The new requirement is that application names must start with a prefix of “harbour-“. The reason (if it wasn’t clear) for this requirement is so that applications do not clash with other installed packages on the device. We’re very sorry for the confusion. Thanks for understanding. Should you have any questions on this or anything else, feel free to send an e-mail as always! P.S. We’ll be launching a FAQ explaining this (and other store requirements) in detail early next week, unless anything unforeseen crops up. Happy hacking, The Jolla Crew ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Update on application naming for Harbour applications
Hi, On 22.11.2013 16:47, Andrey Kozhevnikov wrote: ah, just harbour-application instead of domain naming? ok then sorry for misreading. but i compiled package with dots successfully. check my package in Harbour :) yes renaming a existing project by hand works incl. build and compiling, but you can't start a new SailfishOS project, which contains dots :-( And we want to stick to upstream QtCreator. br Reto On 22.11.2013 20:40, Reto Zingg wrote: Hi, On 22.11.2013 16:39, Andrey Kozhevnikov wrote: really? harbour-org.coderus.application how domain.organization.application naming can clash with device packages? why? QtCreator does not allow it: https://qt.gitorious.org/qt-creator/qt-creator/source/54636d9756966fab7365043d8fd255993675e935:src/libs/utils/projectnamevalidatinglineedit.cpp#L46 br Reto On 22.11.2013 20:32, Robin Burchell wrote: Ahoy, In Iekku’s mail yesterday, we referred to application names needing to use a “dotted” form (e.g. com.example.myapp). It was brought to our attention that this isn’t factually possible at this time due to limitations in Qt Creator/qmake, so we’re unfortunately forced due to time limitations - so as to not inconvenience you developers - to change plans. The new requirement is that application names must start with a prefix of “harbour-“. The reason (if it wasn’t clear) for this requirement is so that applications do not clash with other installed packages on the device. We’re very sorry for the confusion. Thanks for understanding. Should you have any questions on this or anything else, feel free to send an e-mail as always! P.S. We’ll be launching a FAQ explaining this (and other store requirements) in detail early next week, unless anything unforeseen crops up. Happy hacking, The Jolla Crew ___ 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] SDK and Harbour news
Hi, On 21.11.2013 15:24, Putze Sven wrote: On 21.11.2013, at 14:06, Reto Zingg reto.zi...@jolla.com wrote: On 21.11.2013 14:53, Putze Sven wrote: - Shared libraries · You can ship your own private copies of shared libraries that you link against in /usr/share/name of your app/, you are not allowed to install shared libraries anywhere else. Hi, do I get it right that for each and every App there will be a directory in the form /usr/share/mydomain.mygreatcompany.nameofmyapp the folder just exists if the rpm creates it. which is private and for App access only? IMHO you could/should create a directory standard which should be followed inside this folder. E.g. like the bundle folders in the Apple universe. No, the folder is not private and any app can access it's content. And no, do not write into the folder at runtime. With 'your own private copies of ...' we mean: your version of a shared library, which we don't want to have installed any where else in the system (which it might interfere with other apps) and shall just be used by this very one app. Sorry, my wording was not precise enough. I meant private in a way that this folder can contain anything that an app needs to run and I want to deliver upon installation. Like, e.g. libraries, images, all kind of resource files, maybe even database templates. I didn't understand it as a runtime work path. I am just picking on this because some mails in this list weren't clear or contradictory. Yes, that is what we mean :-) You can have under '/usr/share/mydomain.mygreatcompany.nameofmyapp' what ever you want/need for your app to run. br Reto Best. Sven ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] SDK and Harbour news
Hi, On 21.11.2013 15:58, Andrey Kozhevnikov wrote: i have two binaries in application, how to? can you elaborate more? Why would you have to apps in one rpm? br Reto On 21.11.2013 19:52, Reto Zingg wrote: Hi, On 21.11.2013 15:48, Andrey Kozhevnikov wrote: binary names rename same or should be renamed in domain-style too? /usr/bin/myapp or /usr/bin/org.coderus.myapp ? yes, also the binary name has to be named after that schema. But do not mix that up with the Title you give your application in Harbour where you upload the application. br Reto On 21.11.2013 18:20, Iekku Pylkka wrote: Ahoy all, As you might have noticed, there has been lot of stuff happening on application development and application releasing. Some of you who have already submitted applications to Harbour (Jolla's app store intake) have faced these challenges already. Thank you very much for your submissions. Here is a list of items we have identified that cause headache and are the reasons why your app might not have gotten store approval yet: - Icon size: ·SDK still uses 90x90 icon size whereas the device uses 86x86. Harbour submission requires 86x86 icons. An update to the SDK will be released soon to sync it up to the new icon size. - Icon path defined in .desktop file: ·Application icon path is not needed anymore (Icon=appname is enough), you will have to remove absolute paths for Harbour submission. The home screen in upcoming SDK release will have a fix for this. - Application name ·There will be a FAQ on Harbour regarding what file names need to match the RPM package name at upload time. Your application name should be in dotted form, e.g. com.example.myapp and we will soon update Harbour to validate this and then all the applications should follow this naming convention. - QML API ·For QML application development we support QtQuick 2.x and Sailfish Silica 1.0. In our repositories there are various other packages but as they are not reviewed by us we cannot guarantee that APIs they provide are available in future, so take caution when using them - your application might be rejected or stop working if you are using unsupported API. - Shared libraries ·You can ship your own private copies of shared libraries that you link against in /usr/share/name of your app/, you are not allowed to install shared libraries anywhere else. - Private QML imports ·If you are using custom QML imports, you have to install them into /usr/share/name of your app/, you are not allowed to install the QML imports anywhere else. Also, the name of your QML import must match the application package name (e.g. an application org.example.coolapp can only have a single private qml import module, and that must be imported as import org.example.coolapp 1.0). - Runtimes ·Application runtimes such as Python are not supported yet, but we are actively working on getting Python support into shape, at which point Python QML APIs will be allowed in Harbour. Stay tuned. - More info ·There will be the mentioned FAQ page on Harbour which addresses the known application submission problems. Hopefully, most of these will make sense and not require clarification but if you need any help at all, just holler. We hope to expand the list of supported APIs, and are interested in feedback from you as to what you would like to see and be able to do in store applications. Should you have any questions or improvement ideas of these, please send replies to this mailing list. Happy hacking, The Jolla Crew ___ 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] SDK and Harbour news
Hi, On 21.11.2013 15:48, Andrey Kozhevnikov wrote: binary names rename same or should be renamed in domain-style too? /usr/bin/myapp or /usr/bin/org.coderus.myapp ? yes, also the binary name has to be named after that schema. But do not mix that up with the Title you give your application in Harbour where you upload the application. br Reto On 21.11.2013 18:20, Iekku Pylkka wrote: Ahoy all, As you might have noticed, there has been lot of stuff happening on application development and application releasing. Some of you who have already submitted applications to Harbour (Jolla's app store intake) have faced these challenges already. Thank you very much for your submissions. Here is a list of items we have identified that cause headache and are the reasons why your app might not have gotten store approval yet: - Icon size: ·SDK still uses 90x90 icon size whereas the device uses 86x86. Harbour submission requires 86x86 icons. An update to the SDK will be released soon to sync it up to the new icon size. - Icon path defined in .desktop file: ·Application icon path is not needed anymore (Icon=appname is enough), you will have to remove absolute paths for Harbour submission. The home screen in upcoming SDK release will have a fix for this. - Application name ·There will be a FAQ on Harbour regarding what file names need to match the RPM package name at upload time. Your application name should be in dotted form, e.g. com.example.myapp and we will soon update Harbour to validate this and then all the applications should follow this naming convention. - QML API ·For QML application development we support QtQuick 2.x and Sailfish Silica 1.0. In our repositories there are various other packages but as they are not reviewed by us we cannot guarantee that APIs they provide are available in future, so take caution when using them - your application might be rejected or stop working if you are using unsupported API. - Shared libraries ·You can ship your own private copies of shared libraries that you link against in /usr/share/name of your app/, you are not allowed to install shared libraries anywhere else. - Private QML imports ·If you are using custom QML imports, you have to install them into /usr/share/name of your app/, you are not allowed to install the QML imports anywhere else. Also, the name of your QML import must match the application package name (e.g. an application org.example.coolapp can only have a single private qml import module, and that must be imported as import org.example.coolapp 1.0). - Runtimes ·Application runtimes such as Python are not supported yet, but we are actively working on getting Python support into shape, at which point Python QML APIs will be allowed in Harbour. Stay tuned. - More info ·There will be the mentioned FAQ page on Harbour which addresses the known application submission problems. Hopefully, most of these will make sense and not require clarification but if you need any help at all, just holler. We hope to expand the list of supported APIs, and are interested in feedback from you as to what you would like to see and be able to do in store applications. Should you have any questions or improvement ideas of these, please send replies to this mailing list. Happy hacking, The Jolla Crew ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Bug in German virtual keyboard
Hi, On 18.09.2013 21:46, Stefan Lahner wrote: Hello, If you activate the German keyboard and you press the 'Z'-key, the big preview shows an 'Y' (but the output is still a 'Z'. Also if you press long enough the 'Z'-key, you get a representation of different 'Y' equal chars (do not know how to call them). The same happens if you press the 'Y'-key (but you do not see the same amount of 'Y' equal chars as for the 'Z'-key. Thx for reporting this, the preview it self got fixed already (big preview). The y/ý (resp. Y/Ý) and ¥ (Yen) are still offered under z/Z. I created a bug to address this. best regards Reto ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] cover stays after app has quitted
Hi,
On 29.08.2013 16:22, Wim de Vries wrote:
Hi all,
After quitting the app, very often, the cover is still there (sometimes
garbled).
It works ok when the shutDown function is called from the pull-down menu.
yes, that is a know bug. We call it the dead cover bug. I think just
this morning it got fixed (verification pending).
So it shold be fixed in one of the future release of the SDK.
br
Reto
(MyesNoDialog is used as a message Dialog).
QML:
Page..
if (saveFailed)
{
var errorDialog = pageStack.push(MyesNoDialog.qml, {text :
FATAL ERROR: CANNOT SAVE.\nSHUTTING DOWN\n})
errorDialog.accepted.connect(
function()
{
myqquickview.shutDown()
})
errorDialog.rejected.connect(
function()
{
myqquickview.shutDown()
})
}
C++ (myqquickview):
void MyQQuickView::shutDown()
{
qWarning() shutting down;
close();
}
Thanks.
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
