Re: [SailfishDevel] installing extra files via rpm
create sailfish project, or dont use yaml, use spec. On 21.11.2013 16:01, Wim de Vries wrote: Hi Artem, Thanks for the reply. Best way would then to change .yaml, I guess. But somehow there is no .yaml in the rpm dir. Tried to add an empty one hoping that qmake or rebuild would fill it, but remains emty. Any idea how to get the yaml created? Thanks. On 11/20/2013 09:45 PM, Artem Marchenko wrote: You need to mention these files in .yaml (or user editable part of .spec that's generated from .yaml). Basically here's what happens: 1. Your project files are mounted to the virtual build machine 2. make install copies data to the appropriate final folders on the build machine (not visible from your PC) 3. RPM generation happens on build machine. RPM packager puts installed file to one or more (just one for a simple case) RPM packages according to .yaml/.spec and then it figures that some installed files are not going into any .rpm, so it gives you an error: Installed (but unpackaged) file(s) found: Cheers, Artem. On Wed, Nov 20, 2013 at 9:45 PM, Wim de Vries wsvr...@xs4all.nl mailto:wsvr...@xs4all.nl wrote: Hi, I am able to deploy via RPM. Or better, QtCreator is able to do it ;-) Still, I need to install some data files as well. pro file: data.files = checklistsdata/* OTHER_FILES += \ checklistsdata/skyArrow-walkaround \ checklistsdata/skyArrowEMERGENCY \ . In the .pri: data.path = /home/nemo/checklistsdata INSTALLS += target qml desktop data As far as I understand this should be sufficient. Still deployment fails. Any hints? Thanks. Output when deploying: nstall -m 755 -p checklists /home/deploy/installroot/usr/bin/checklists install -m 755 -p /home/mersdk/qt/checklists/main.qml /home/deploy/installroot/usr/share/checklists/ cp -f -R /home/mersdk/qt/checklists/pages /home/deploy/installroot/usr/share/checklists/ cp -f -R /home/mersdk/qt/checklists/cover /home/deploy/installroot/usr/share/checklists/ cp -f -R /home/mersdk/qt/checklists/controls /home/deploy/installroot/usr/share/checklists/ install -m 755 -p /home/mersdk/qt/checklists/main.qml /home/deploy/installroot/usr/share/checklists/ install -m 755 -p /home/mersdk/qt/checklists/checklists.desktop /home/deploy/installroot/usr/share/applications/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/eurofox /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/eurofoxEMERGENCY /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO1 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO2 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO3 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO4 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO5 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO6 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO7 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO8 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO9 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/skyArrow /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/skyArrow-walkaround /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/skyArrowEMERGENCY /home/deploy/installroot/home/nemo/checklistsdata/ + /usr/lib/rpm/find-debuginfo.sh --strict-build-id /home/mersdk/qt/checklists/ . Processing files: checklists-0.1-1.i586 Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(FileDigests) = 4.6.0-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 Requires: libGLESv2.so.2 libQt5Core.so.5 libQt5Gui.so.5 libQt5Network.so.5 libQt5Qml.so.5 libQt5Quick.so.5 libc.so.6 libc.so.6(GLIBC_2.0) libgcc_s.so.1 libgcc_s.so.1(GCC_3.0) libm.so.6 libpthread.so.0 libstdc++.so.6 libstdc++.so.6(CXXABI_1.3) libstdc++.so.6(GLIBCXX_3.4) rtld(GNU_HASH) Processing files: checklists-debugsource-0.1-1.i586 Processing files: checklists-debuginfo-0.1-1.i586 Provides: debuginfo(build-id) =
[SailfishDevel] SDK and Harbour news
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
Re: [SailfishDevel] installing extra files via rpm
Thanks. Removing and adding kits seems to generate new .yaml file based on .pro and .pri. On 11/21/2013 11:11 AM, Andrey Kozhevnikov wrote: create sailfish project, or dont use yaml, use spec. On 21.11.2013 16:01, Wim de Vries wrote: Hi Artem, Thanks for the reply. Best way would then to change .yaml, I guess. But somehow there is no .yaml in the rpm dir. Tried to add an empty one hoping that qmake or rebuild would fill it, but remains emty. Any idea how to get the yaml created? Thanks. On 11/20/2013 09:45 PM, Artem Marchenko wrote: You need to mention these files in .yaml (or user editable part of .spec that's generated from .yaml). Basically here's what happens: 1. Your project files are mounted to the virtual build machine 2. make install copies data to the appropriate final folders on the build machine (not visible from your PC) 3. RPM generation happens on build machine. RPM packager puts installed file to one or more (just one for a simple case) RPM packages according to .yaml/.spec and then it figures that some installed files are not going into any .rpm, so it gives you an error: Installed (but unpackaged) file(s) found: Cheers, Artem. On Wed, Nov 20, 2013 at 9:45 PM, Wim de Vries wsvr...@xs4all.nl mailto:wsvr...@xs4all.nl wrote: Hi, I am able to deploy via RPM. Or better, QtCreator is able to do it ;-) Still, I need to install some data files as well. pro file: data.files = checklistsdata/* OTHER_FILES += \ checklistsdata/skyArrow-walkaround \ checklistsdata/skyArrowEMERGENCY \ . In the .pri: data.path = /home/nemo/checklistsdata INSTALLS += target qml desktop data As far as I understand this should be sufficient. Still deployment fails. Any hints? Thanks. Output when deploying: nstall -m 755 -p checklists /home/deploy/installroot/usr/bin/checklists install -m 755 -p /home/mersdk/qt/checklists/main.qml /home/deploy/installroot/usr/share/checklists/ cp -f -R /home/mersdk/qt/checklists/pages /home/deploy/installroot/usr/share/checklists/ cp -f -R /home/mersdk/qt/checklists/cover /home/deploy/installroot/usr/share/checklists/ cp -f -R /home/mersdk/qt/checklists/controls /home/deploy/installroot/usr/share/checklists/ install -m 755 -p /home/mersdk/qt/checklists/main.qml /home/deploy/installroot/usr/share/checklists/ install -m 755 -p /home/mersdk/qt/checklists/checklists.desktop /home/deploy/installroot/usr/share/applications/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/eurofox /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/eurofoxEMERGENCY /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO1 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO2 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO3 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO4 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO5 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO6 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO7 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO8 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO9 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/skyArrow /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/skyArrow-walkaround /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/skyArrowEMERGENCY /home/deploy/installroot/home/nemo/checklistsdata/ + /usr/lib/rpm/find-debuginfo.sh --strict-build-id /home/mersdk/qt/checklists/ . Processing files: checklists-0.1-1.i586 Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(FileDigests) = 4.6.0-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 Requires: libGLESv2.so.2 libQt5Core.so.5 libQt5Gui.so.5 libQt5Network.so.5 libQt5Qml.so.5 libQt5Quick.so.5 libc.so.6 libc.so.6(GLIBC_2.0) libgcc_s.so.1 libgcc_s.so.1(GCC_3.0) libm.so.6 libpthread.so.0 libstdc++.so.6 libstdc++.so.6(CXXABI_1.3) libstdc++.so.6(GLIBCXX_3.4) rtld(GNU_HASH) Processing files:
Re: [SailfishDevel] installing extra files via rpm
i have src/client and src/server and everything is built correctly automatically. On 21.11.2013 21:05, Artem Marchenko wrote: Yes, Qt Creator plugin trying to modify .yaml is a big annoyance to anybody with non standard .yaml (I have src/test subprojects and plugin is apparently able to work with one package only). How I solved it, I just keep resetting .yaml to version from version control whenever QtCreator wants to be clever and touch .yaml himself. Sure, sometimes I miss it, but most of the time everything's fine. Maybe same will work for you. Or maybe somebody will now post how to kill this .yaml modification plugin completely :) Cheers, Artem. On Thu, Nov 21, 2013 at 3:25 PM, Wim de Vries wsvr...@xs4all.nl mailto:wsvr...@xs4all.nl wrote: Thanks. Removing and adding kits seems to generate new .yaml file based on .pro and .pri. On 11/21/2013 11:11 AM, Andrey Kozhevnikov wrote: create sailfish project, or dont use yaml, use spec. On 21.11.2013 16:01, Wim de Vries wrote: Hi Artem, Thanks for the reply. Best way would then to change .yaml, I guess. But somehow there is no .yaml in the rpm dir. Tried to add an empty one hoping that qmake or rebuild would fill it, but remains emty. Any idea how to get the yaml created? Thanks. On 11/20/2013 09:45 PM, Artem Marchenko wrote: You need to mention these files in .yaml (or user editable part of .spec that's generated from .yaml). Basically here's what happens: 1. Your project files are mounted to the virtual build machine 2. make install copies data to the appropriate final folders on the build machine (not visible from your PC) 3. RPM generation happens on build machine. RPM packager puts installed file to one or more (just one for a simple case) RPM packages according to .yaml/.spec and then it figures that some installed files are not going into any .rpm, so it gives you an error: Installed (but unpackaged) file(s) found: Cheers, Artem. On Wed, Nov 20, 2013 at 9:45 PM, Wim de Vries wsvr...@xs4all.nl mailto:wsvr...@xs4all.nl wrote: Hi, I am able to deploy via RPM. Or better, QtCreator is able to do it ;-) Still, I need to install some data files as well. pro file: data.files = checklistsdata/* OTHER_FILES += \ checklistsdata/skyArrow-walkaround \ checklistsdata/skyArrowEMERGENCY \ . In the .pri: data.path = /home/nemo/checklistsdata INSTALLS += target qml desktop data As far as I understand this should be sufficient. Still deployment fails. Any hints? Thanks. Output when deploying: nstall -m 755 -p checklists /home/deploy/installroot/usr/bin/checklists install -m 755 -p /home/mersdk/qt/checklists/main.qml /home/deploy/installroot/usr/share/checklists/ cp -f -R /home/mersdk/qt/checklists/pages /home/deploy/installroot/usr/share/checklists/ cp -f -R /home/mersdk/qt/checklists/cover /home/deploy/installroot/usr/share/checklists/ cp -f -R /home/mersdk/qt/checklists/controls /home/deploy/installroot/usr/share/checklists/ install -m 755 -p /home/mersdk/qt/checklists/main.qml /home/deploy/installroot/usr/share/checklists/ install -m 755 -p /home/mersdk/qt/checklists/checklists.desktop /home/deploy/installroot/usr/share/applications/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/eurofox /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/eurofoxEMERGENCY /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO1 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO2 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO3 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO4 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO5 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO6 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO7 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO8
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] Feedback / Haptics on Jolla Device
Ciao Mariaon Have you tried: import QtFeedback 5.0 https://qt.gitorious.org/qt/qtfeedback/source/dea0da72655f1defccaea643dbe37373f6692243:doc/src/snippets/declarative/declarative-feedback.qml Obviously your emulator won't vibrate ...8-) Chris Zitat von Mariano Boragno marianobora...@gmail.com: Hi there, I'm porting a little game I wrote for Harmattan in QML which uses HapticsEffect from the Qt Mobility 1.2 Feedback API. I've found that as per https://sailfishos.org/wiki/Porting/Harmattan, Qt5 QtFeedback Add-on could be used in Sailfish, but I haven't found much documentation about it. Is there any QML plugin (something like a wrapper) to use the add-on or should I interface the QML view with C++? Any suggestion, ideas? Thanks a lot in advance. Regards... ...Mariano Boragno... ___ 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] Connection to Emulator not working if PC offline
Hello all, We tested the offline situation as well when preparing the images so we did obviously something differently. We'll visit this issue for sure before we launch next release of SDK. Right now we are working hard to make the emulator content and it's APIs to match 1:1 the stuff that real device uses. There were many changes even on the repository layouts so things just take time. But ; next SDK is coming up pretty soon. thanks, Jarko From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] on behalf of Luciano Montanaro [mikel...@gmail.com] Sent: Wednesday, November 20, 2013 1:49 PM To: Sailfish OS Developers Subject: Re: [SailfishDevel] Connection to Emulator not working if PC offline Hi Andrey, this happens to me too. I am using Linux, Kubuntu 13.10. The workaround I have found is to ifconfig 192.168.0.1 (or something like that) to give an address to the network. This usually lets me use the emulator. Luciano On Wed, Nov 20, 2013 at 9:28 AM, Andrey Kozhevnikov coderusin...@gmail.com wrote: I'm not connected via wlan or lan. just not connected. want to code when i'm on long road to home without any internet connection :) On 20.11.2013 14:26, Jarko Vihriala wrote: party, but the name acrynym is not that obivious, it is (P)rogram(R)esponsiveness(I)dle(S)ystem(M)anagement :) Joke's aside. It's interesting to see that happen with your PC as we tried both offline and online with the 1310 SDK package. Obiviously we did not test some combination. Are you on WLAN or LAN? thanks, Jarko From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] on behalf of Andrey Kozhevnikov [coderusin...@gmail.com] Sent: Wednesday, November 20, 2013 10:05 AM To: Sailfish OS Developers Subject: [SailfishDevel] Connection to Emulator not working if PC offline Just found weird problem. If my laptop not connected to internet, Sailfish Emulator not responding and i can't work with it. Anyone else have same problem? ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list -- Luciano Montanaro Anyone who is capable of getting themselves made President should on no account be allowed to do the job. -- Douglas Adams ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] (QtLocation 5.0) Coordinate is not a type
Hi, On Thu, 21 Nov 2013 08:43:11 tw_bolek wrote: BTW. Do you perhaps now the URL of the site where one can register to get the API key to use Nokia Maps plugin? If I try to use it without any key it says to go to https://api.developer.nokia.com but that URL just redirects to the main Nokia Developer page. I can't find the right place to register... Try developer.here.com. Sign in or create an account. The click on the Get Started link at the top of the page. Cheers, -- Aaron McCarthy ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Emoji in SailfishOS
On Nov 21, 2013, at 11:01 AM, Andrey Kozhevnikov coderusin...@gmail.com wrote: the other question is: does it support color fonts? or just common glyphs? Do any linux systems support them? At least, putting the Apple Color Emoji font on device does not work. Using a glyph-based emoji font like Android Emoji [1] does work. If your interest is in having a full-color emoji set for an application, it’s probably better to stick with real images. If you have one you’re interested in testing, the emulator will work the same way as the device. Put fonts in /usr/share/fonts/ and run fc-cache. [1] https://github.com/android/platform_frameworks_base/blob/master/data/fonts/AndroidEmoji.ttf — John Brooks Jolla On 21.11.2013 23:29, Andrea Bernabei wrote: Andrey Kozhevnikov coderusinbox@... writes: Back to my old question: will jolla device with sailfishos have emoji fonts to display hi-color unicode emoji correctly or i should prepare my own input method component for emoji selection? ___ SailfishOS.org Devel mailing list I have two news for you, one bad and one good :) The bad news is that SailfishOS default font doesn't have color emoji so they will be shown as boxes The good news is that there is a fallback system (and it's working) that will get the missing bits from other eventually installed fonts :) ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
[SailfishDevel] Emoji in SailfishOS
Back to my old question: will jolla device with sailfishos have emoji fonts to display hi-color unicode emoji correctly or i should prepare my own input method component for emoji selection? ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Emoji in SailfishOS
Andrey Kozhevnikov coderusinbox@... writes: Back to my old question: will jolla device with sailfishos have emoji fonts to display hi-color unicode emoji correctly or i should prepare my own input method component for emoji selection? ___ SailfishOS.org Devel mailing list I have two news for you, one bad and one good :) The bad news is that SailfishOS default font doesn't have color emoji so they will be shown as boxes The good news is that there is a fallback system (and it's working) that will get the missing bits from other eventually installed fonts :) ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] installing extra files via rpm
check __ARMEL__ or __ARM_ARCH_7__ On 21.11.2013 21:37, Luciano Montanaro wrote: For the record, I also have problems,. whenever I switch between ARM/486 builds or between sailfish and harmattan. A slightly different topic... Is there a way to detect the kit in use from the qmake file? Currently, I add CONFIG+=sailfish on the build options when I want to build for sailfish... But this setting also gets lost often. If there were a method to detect the toolchain automatically from the qmake file that would be great. Alternatively, is it possible to add the CONFIG+=sailfish option to the .yaml file? Am I the only one that is trying to keep their applicaion buildable for sailfish as well as other targets? How are you dealing with this? Because my application.pro file is getting hard to maintain. On Thu, Nov 21, 2013 at 4:19 PM, Andrey Kozhevnikov coderusin...@gmail.com wrote: i have src/client and src/server and everything is built correctly automatically. On 21.11.2013 21:05, Artem Marchenko wrote: Yes, Qt Creator plugin trying to modify .yaml is a big annoyance to anybody with non standard .yaml (I have src/test subprojects and plugin is apparently able to work with one package only). How I solved it, I just keep resetting .yaml to version from version control whenever QtCreator wants to be clever and touch .yaml himself. Sure, sometimes I miss it, but most of the time everything's fine. Maybe same will work for you. Or maybe somebody will now post how to kill this .yaml modification plugin completely :) Cheers, Artem. On Thu, Nov 21, 2013 at 3:25 PM, Wim de Vries wsvr...@xs4all.nl wrote: Thanks. Removing and adding kits seems to generate new .yaml file based on .pro and .pri. On 11/21/2013 11:11 AM, Andrey Kozhevnikov wrote: create sailfish project, or dont use yaml, use spec. On 21.11.2013 16:01, Wim de Vries wrote: Hi Artem, Thanks for the reply. Best way would then to change .yaml, I guess. But somehow there is no .yaml in the rpm dir. Tried to add an empty one hoping that qmake or rebuild would fill it, but remains emty. Any idea how to get the yaml created? Thanks. On 11/20/2013 09:45 PM, Artem Marchenko wrote: You need to mention these files in .yaml (or user editable part of .spec that's generated from .yaml). Basically here's what happens: 1. Your project files are mounted to the virtual build machine 2. make install copies data to the appropriate final folders on the build machine (not visible from your PC) 3. RPM generation happens on build machine. RPM packager puts installed file to one or more (just one for a simple case) RPM packages according to .yaml/.spec and then it figures that some installed files are not going into any .rpm, so it gives you an error: Installed (but unpackaged) file(s) found: Cheers, Artem. On Wed, Nov 20, 2013 at 9:45 PM, Wim de Vries wsvr...@xs4all.nl wrote: Hi, I am able to deploy via RPM. Or better, QtCreator is able to do it ;-) Still, I need to install some data files as well. pro file: data.files = checklistsdata/* OTHER_FILES += \ checklistsdata/skyArrow-walkaround \ checklistsdata/skyArrowEMERGENCY \ . In the .pri: data.path = /home/nemo/checklistsdata INSTALLS += target qml desktop data As far as I understand this should be sufficient. Still deployment fails. Any hints? Thanks. Output when deploying: nstall -m 755 -p checklists /home/deploy/installroot/usr/bin/checklists install -m 755 -p /home/mersdk/qt/checklists/main.qml /home/deploy/installroot/usr/share/checklists/ cp -f -R /home/mersdk/qt/checklists/pages /home/deploy/installroot/usr/share/checklists/ cp -f -R /home/mersdk/qt/checklists/cover /home/deploy/installroot/usr/share/checklists/ cp -f -R /home/mersdk/qt/checklists/controls /home/deploy/installroot/usr/share/checklists/ install -m 755 -p /home/mersdk/qt/checklists/main.qml /home/deploy/installroot/usr/share/checklists/ install -m 755 -p /home/mersdk/qt/checklists/checklists.desktop /home/deploy/installroot/usr/share/applications/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/eurofox /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/eurofoxEMERGENCY /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO1 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO2 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO3 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO4 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO5 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO6 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p
Re: [SailfishDevel] installing extra files via rpm
Is it possible to install files directly via .yaml/.spec (without using the qmake installs)? -- Marcin 2013/11/21 Andrey Kozhevnikov coderusin...@gmail.com check __ARMEL__ or __ARM_ARCH_7__ On 21.11.2013 21:37, Luciano Montanaro wrote: For the record, I also have problems,. whenever I switch between ARM/486 builds or between sailfish and harmattan. A slightly different topic... Is there a way to detect the kit in use from the qmake file? Currently, I add CONFIG+=sailfish on the build options when I want to build for sailfish... But this setting also gets lost often. If there were a method to detect the toolchain automatically from the qmake file that would be great. Alternatively, is it possible to add the CONFIG+=sailfish option to the .yaml file? Am I the only one that is trying to keep their applicaion buildable for sailfish as well as other targets? How are you dealing with this? Because my application.pro file is getting hard to maintain. On Thu, Nov 21, 2013 at 4:19 PM, Andrey Kozhevnikov coderusin...@gmail.com wrote: i have src/client and src/server and everything is built correctly automatically. On 21.11.2013 21:05, Artem Marchenko wrote: Yes, Qt Creator plugin trying to modify .yaml is a big annoyance to anybody with non standard .yaml (I have src/test subprojects and plugin is apparently able to work with one package only). How I solved it, I just keep resetting .yaml to version from version control whenever QtCreator wants to be clever and touch .yaml himself. Sure, sometimes I miss it, but most of the time everything's fine. Maybe same will work for you. Or maybe somebody will now post how to kill this .yaml modification plugin completely :) Cheers, Artem. On Thu, Nov 21, 2013 at 3:25 PM, Wim de Vries wsvr...@xs4all.nl wrote: Thanks. Removing and adding kits seems to generate new .yaml file based on .pro and .pri. On 11/21/2013 11:11 AM, Andrey Kozhevnikov wrote: create sailfish project, or dont use yaml, use spec. On 21.11.2013 16:01, Wim de Vries wrote: Hi Artem, Thanks for the reply. Best way would then to change .yaml, I guess. But somehow there is no .yaml in the rpm dir. Tried to add an empty one hoping that qmake or rebuild would fill it, but remains emty. Any idea how to get the yaml created? Thanks. On 11/20/2013 09:45 PM, Artem Marchenko wrote: You need to mention these files in .yaml (or user editable part of .spec that's generated from .yaml). Basically here's what happens: 1. Your project files are mounted to the virtual build machine 2. make install copies data to the appropriate final folders on the build machine (not visible from your PC) 3. RPM generation happens on build machine. RPM packager puts installed file to one or more (just one for a simple case) RPM packages according to .yaml/.spec and then it figures that some installed files are not going into any .rpm, so it gives you an error: Installed (but unpackaged) file(s) found: Cheers, Artem. On Wed, Nov 20, 2013 at 9:45 PM, Wim de Vries wsvr...@xs4all.nl wrote: Hi, I am able to deploy via RPM. Or better, QtCreator is able to do it ;-) Still, I need to install some data files as well. pro file: data.files = checklistsdata/* OTHER_FILES += \ checklistsdata/skyArrow-walkaround \ checklistsdata/skyArrowEMERGENCY \ . In the .pri: data.path = /home/nemo/checklistsdata INSTALLS += target qml desktop data As far as I understand this should be sufficient. Still deployment fails. Any hints? Thanks. Output when deploying: nstall -m 755 -p checklists /home/deploy/installroot/usr/bin/checklists install -m 755 -p /home/mersdk/qt/checklists/main.qml /home/deploy/installroot/usr/share/checklists/ cp -f -R /home/mersdk/qt/checklists/pages /home/deploy/installroot/usr/share/checklists/ cp -f -R /home/mersdk/qt/checklists/cover /home/deploy/installroot/usr/share/checklists/ cp -f -R /home/mersdk/qt/checklists/controls /home/deploy/installroot/usr/share/checklists/ install -m 755 -p /home/mersdk/qt/checklists/main.qml /home/deploy/installroot/usr/share/checklists/ install -m 755 -p /home/mersdk/qt/checklists/checklists.desktop /home/deploy/installroot/usr/share/applications/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/eurofox /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/eurofoxEMERGENCY /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO1 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO2 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO3 /home/deploy/installroot/home/nemo/checklistsdata/ install -m 755 -p /home/mersdk/qt/checklists/checklistsdata/GEO4
Re: [SailfishDevel] Emoji in SailfishOS
the other question is: does it support color fonts? or just common glyphs? On 21.11.2013 23:29, Andrea Bernabei wrote: Andrey Kozhevnikov coderusinbox@... writes: Back to my old question: will jolla device with sailfishos have emoji fonts to display hi-color unicode emoji correctly or i should prepare my own input method component for emoji selection? ___ SailfishOS.org Devel mailing list I have two news for you, one bad and one good :) The bad news is that SailfishOS default font doesn't have color emoji so they will be shown as boxes The good news is that there is a fallback system (and it's working) that will get the missing bits from other eventually installed fonts :) ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] SDK and Harbour news
i have two binaries in application, how to? 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
Re: [SailfishDevel] connect gridview on delegates click signal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for your tips, and sorry for the lte reply.
Le 18/10/2013 12:50, Matt Austin a écrit :
I think you should be able to get what you're after with the
following - assuming you have a reference to your 'detail page'
(lets call it 'detailPage'):
That's the point. How do I get a reference to my detail page in my
grid page ?
I guess I should instanciate it in some way... maybe using a Loader ?
Here is what I tried:
GridView {
id: gridView
anchors.fill: parent
cellHeight: 150
cellWidth:110
model: ListModel {
ListElement {
ico: qrc:///card1.png
val: 1
}
ListElement {
ico: qrc:///card2.png
val: 2
}
}
Loader { id: pageLoader }
header: PageHeader {
title: Choose your card !
}
delegate: Card {
source: ico
value: val
onClicked: {
pageLoader.source = CardPage.qml
pageLoader.item.currentCard = this
pageStack.push(pageLoader.item)
}
}
}
with CardPage defined like this:
Page {
id: page
property variant currentCard
Column {
width: page.width
spacing: Theme.paddingLarge
PageHeader {
title: Your card !
}
Card {
source: currentCard.source
value: currentCard.value
}
}
}
I get the CardPage to be displayed, but then references to currentCard
are undefined. Maybe I shouldn't be using 'this' keyword ?
Or is there a better way to have a shared object to let my page
communicate ?
Thanks in advance,
Franck
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSjgemAAoJEGEvoAir78RosRsH/1geVAWzTlaajeWyMapZUU+o
GeDYg0uE91a7WM4iaFFHtmLOeIvTIXYZN3VuWqhDxJKNy5vgg0Oj87VjLLGxQIMl
54k0S3gF9rJx2nb0YW5sip7FXM+voM/bKeswuuvEyJaJ5CaArhei4gr2Khy24ZRh
DSLj9TmB6+YL3S8HFE8igPo6U+I6ND7VkWgxuenwMWZF9GKqou6NLLvn8fpAyESn
jdMgETXWLJ/gQeQNw/WPabn28b1SGZj4rRZWLU4tEKDk30hf/Y6TN3rJ2Def8usL
stouaLWmwHFT36Ek9889Qgee7Zpq1uG0/DMQPPr2sGGLqev+JcCT6EJtjhPkYp8=
=8yHw
-END PGP SIGNATURE-
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] SDK and Harbour news
- 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 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. Best. Sven ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Problem with installing package in SDK Control Center
dont press enter in input field. its bug. search for available packages will be automatically. On 22.11.2013 00:23, Sven Putze wrote: Hi there, on one computer I've got problems with installing a packages via SDK Control Center, here are the steps: SDK Control Center, Tab Target click on manage (SailfishOS-i486-x86) enter boost-devel, click install finished: installing package boost-devel - exited with status 0 (WARNING) rpm[6896/1862375168]Executing statically linked native binary /srv/mer/targets/SailfishOS-i486-x86/sbin/ldconfig (WARNING) rpm[6929/1862960896]Executing statically linked native binary /srv/mer/targets/SailfishOS-i486-x86/sbin/ldconfig (WARNING) rpm[6935/1862911744]Executing statically linked native binary /srv/mer/targets/SailfishOS-i486-x86/sbin/ldconfig (WARNING) rpm[6937/1862608640]Executing statically linked native binary /srv/mer/targets/SailfishOS-i486-x86/sbin/ldconfig (WARNING) rpm[6939/1862158080]Executing statically linked native binary /srv/mer/targets/SailfishOS-i486-x86/sbin/ldconfig (WARNING) rpm[6941/1862596352]Executing statically linked native binary /srv/mer/targets/SailfishOS-i486-x86/sbin/ldconfig (WARNING) rpm[6943/1862625024]Executing statically linked native binary /srv/mer/targets/SailfishOS-i486-x86/sbin/ldconfig # exit 0 (0) Sync completed SDK Control Center, Tab Target click on manage (SailfishOS-armv7hl) enter name, names appear, dark red error message: Toolchain '' is not available in any repository. That target cannot be installed. Tab Updates Engine Up-to-date SailfishOS-armv7hl Up-to-date SailfishOS-i486-x86 Up-to-date Most recent version of the SDK Most recent version of Virtual Box Platform: OSX Works on one computer, one with error message What should I do? Best. Sven ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] SDK and Harbour news
Thanks for the update, Lekku Questions there are :) **Submitted apps (and to be submitted ones)** First of all what do we do with the apps already approved, under QA or scheduled for submission tomorrow? You know, launch date is a very special date, I wouldn't like to change anything unless absolutely necessary. Will the apps violating these rules, but currently approved or submitted and under QA still work fine for the launch? And will users get proper update notifications when you change package name from e.g. flashlight to com.iamcool.flashlight and update icon to 86x86? What about the apps that are to be submitted today-tomorrow? Do you know when this will be a FAQ will happen and since when shall it be enforced (rather than just recommended)? **QML API and Shared libraries** What about standard Qt5 modules such as qt5-qtdeclarative-systeminfo and qt5-qtgraphicaleffects Can I still Require them in .yaml/.spec to guarantee that device will install them or shall we bundle them in manually somehow? Cheers, Artem. On Thu, Nov 21, 2013 at 2:20 PM, Iekku Pylkka iekku.pyl...@jolla.comwrote: 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 -- Artem Marchenko http://agilesoftwaredevelopment.com http://twitter.com/AgileArtem ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] SDK and Harbour news
On 21/11/13 10:50 PM, Robin Burchell wrote: Hi Artem, On Thu, Nov 21, 2013 at 1:41 PM, Artem Marchenko artem.marche...@gmail.com wrote: Thanks for the update, Lekku I, not L :-) Will the apps violating these rules, but currently approved or submitted and under QA still work fine for the launch? And will users get proper update notifications when you change package name from e.g. flashlight to com.iamcool.flashlight and update icon to 86x86? Any update will trigger an update notification in store as far as I know. What about the apps that are to be submitted today-tomorrow? Do you know when this will be a FAQ will happen and since when shall it be enforced (rather than just recommended)? First draft was written yesterday, it might take a little longer while we nail out a few final things. Not too long I'd hope. *QML API and Shared libraries* What about standard Qt5 modules such as qt5-qtdeclarative-systeminfo and qt5-qtgraphicaleffects Can I still Require them in .yaml/.spec to guarantee that device will install them or shall we bundle them in manually somehow? You will still need to specify your requirements. Note: not everything with a Qt in the name is necessarily supported. I'll make sure a full list will come around the same time as the FAQ/with the FAQ. In particular, as I understand it, QtSystemInfo is not yet API/ABI stable upstream (Lorn, please correct me if I'm wrong...), so we are unable to offer support for it at this time. QtSystemInfo is not yet officially released from upstream, not stable and is currently undergoing a change in API. :) Cheers, Artem. BR, Robin ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Feedback / Haptics on Jolla Device
Hi Chris, Well, that was sss simple! I wasn't able to find any documentation, next time I will try to calm myself down and dig some more, lol! Thanks a lot for the support, guys! I hope to submit my game soon to the harbour... :-) ...Mariano Boragno... On Thu, Nov 21, 2013 at 7:52 PM, christopher.l...@thurweb.ch wrote: Ciao Mariaon Have you tried: import QtFeedback 5.0 https://qt.gitorious.org/qt/qtfeedback/source/ dea0da72655f1defccaea643dbe37373f6692243:doc/src/snippets/ declarative/declarative-feedback.qml Obviously your emulator won't vibrate ...8-) Chris Zitat von Mariano Boragno marianobora...@gmail.com: Hi there, I'm porting a little game I wrote for Harmattan in QML which uses HapticsEffect from the Qt Mobility 1.2 Feedback API. I've found that as per https://sailfishos.org/wiki/Porting/Harmattan, Qt5 QtFeedback Add-on could be used in Sailfish, but I haven't found much documentation about it. Is there any QML plugin (something like a wrapper) to use the add-on or should I interface the QML view with C++? Any suggestion, ideas? Thanks a lot in advance. Regards... ...Mariano Boragno... ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] SDK and Harbour news
Ahoi Sailors; I do believe this info will be available in the wiki as well, correct? Best, tortoisedoc On Thu, Nov 21, 2013 at 2:20 PM, Iekku Pylkka iekku.pyl...@jolla.comwrote: 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
Re: [SailfishDevel] Feedback / Haptics on Jolla Device
Hi, Just a quick note on that: not many theme effects are currently supported, and file effects are not supported. For best results, use a custom haptic effect, with manually tuned intensity and envelope values. You NEED to test on a real device, as haptics are something which feel completely different on different devices even with the same intensity etc values, just depending on the type of vibra motor which is in the device, and any specifics of it (eg, the mass of the ERM, etc). The backend is https://github.com/nemomobile/qt-mobility-haptics-ffmemless just fyi. Cheers, Chris. From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] on behalf of Mariano Boragno [marianobora...@gmail.com] Sent: Friday, November 22, 2013 3:17 PM To: Christopher Lamb Cc: Sailfish OS Developers Subject: Re: [SailfishDevel] Feedback / Haptics on Jolla Device Hi Chris, Well, that was sss simple! I wasn't able to find any documentation, next time I will try to calm myself down and dig some more, lol! Thanks a lot for the support, guys! I hope to submit my game soon to the harbour... :-) ...Mariano Boragno... On Thu, Nov 21, 2013 at 7:52 PM, christopher.l...@thurweb.chmailto:christopher.l...@thurweb.ch wrote: Ciao Mariaon Have you tried: import QtFeedback 5.0 https://qt.gitorious.org/qt/qtfeedback/source/dea0da72655f1defccaea643dbe37373f6692243:doc/src/snippets/declarative/declarative-feedback.qml Obviously your emulator won't vibrate ...8-) Chris Zitat von Mariano Boragno marianobora...@gmail.commailto:marianobora...@gmail.com: Hi there, I'm porting a little game I wrote for Harmattan in QML which uses HapticsEffect from the Qt Mobility 1.2 Feedback API. I've found that as per https://sailfishos.org/wiki/Porting/Harmattan, Qt5 QtFeedback Add-on could be used in Sailfish, but I haven't found much documentation about it. Is there any QML plugin (something like a wrapper) to use the add-on or should I interface the QML view with C++? Any suggestion, ideas? Thanks a lot in advance. Regards... ...Mariano Boragno... ___ SailfishOS.org Devel mailing list
