Re: [SailfishDevel] SailfishOS SDK April update available tomorrow.

[Andrey Kozhevnikov]

Why you using Qt creator then? use mb/mb2 in mer sdk.

17.04.2014 12:47, Iosif Hamlatzis ?:

Good morning to all

Just updated my SDK with big disaster. Now it doesn't build or clean 
my project which used custom build/clean steps.


In my game I don't need nor want to use Qt so I used the sample from 
https://github.com/sailfish-sdk/sdk-sdl-project-example


Now I get a general message: "*Error while parsing file 
C:/SailfishOS-workspace/harbour-farwest/harbour-farwest.pro 
. Giving up.*"





On 16 April 2014 14:21, Jarko Vihriala > wrote:


Hello all,

We just discovered a serious issue related to using SDK with KDE
based Linux distros such as Fedora or KUbuntu. Therefore we have
removed the Linux installers from the SailfishOS website. Please
do not try to download Linux installers or update your SailfishOS
SDK if you are using KDE Linux distro.

We are now working to get the KDE issue solved, please stay tuned.
We will inform when SDK updates are again available.

thanks, Jarko




*From:* Jarko Vihriala
*Sent:* Tuesday, April 15, 2014 9:36 PM
*To:* Sailfish OS Developers
*Subject:* SailfishOS SDK April update available tomorrow.

Hello again,

Tomorrow (16 April) at 10:00 UTC we will publish new installers,
and package repositories for our Sailfish OS SDK version
Alpha-1404-Qt5. Please note that links in this email are updated
at that time as well.

We apologise for the long delay between the SDK updates. We had to
completely recreate our SDK production environment before being
able to release an update. This took longer than expected and is
the main reason for the delay.

If you already have an existing Alpha-Qt5 SDK installed you should
see the Updates Available icon in Qt Creator. If you don't have a
previous SDK installation you can get the latest installer from
http://www.sailfishos.org. It is recommended to uninstall the old
SDK and download a new installer.

SDK content has been updated to match Jolla Release 1.0.5.16.
Please see below for detailed information of the changed items.

A couple of things you should be aware of:
- Like before, in this update the build engine, emulator and
targets are re-installed so you will lose all changes you may have
made in those - however, if your application packaging is done
correctly, rebuilding your projects should reinstall the packages
you have been using.
- All customization done to SDK (adding new package repositories,
adding custom targets, additional source paths) will be removed
during the installation process so make your own backup of those
before starting the update.
- If you import existing projects made with a previous version of
the Sailfish OS SDK, make sure you select the correct kit in the
project configuration step. Both ARM and i486 kits are available.
- Windows users need to install VC10 runtime from
http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328
or the Installer will ask for admin rights during installation.
- Package repository contents have been updated and consequently
using a previous SDK version with these package repositories is
not supported.
- For more information, please see the SDK Alpha-Qt5 known issues
list at: https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.
- Oldest Mac OS X supported is now 10.8.5 (Mountain Lion). Other
supported platforms can be found from:
https://sailfishos.org/alpha_qt5_sdk_release_notes.html

Here is a summary of changes:

SDK IDE (Qt Creator)
 - Crash fixes on OS X
 - Yaml editor removed from Qt Creator and yaml files are
presented as plain text
 - Alternate projects folder can be changed from Mer settings page
 - Better path handling for shared directories in Windows
 - Updated Sailfish template project
 - Handle errors in project build/deploy phase more gracefully
 - Debugging with GDB from Qt Creator works with the Emulator and
the Device
 - Tooltips are displayed for Virtual Machine statuses
 - Add changelog to your RPM with a .changes file

SDK Control Center:
 - Improved Targets management page
 - Clean build targets are available for download via the Targets
page (pre-configured targets)
 - Easily install/remove multiple packages from a specific target
 - Updates page has a "Check for updates now" button
 - Added Harbour tools page with RPM validator tool

Installer:
 - Better VirtualBox version checking. Lowest version supported is
v4.0
 - Install virtual machines using correct VirtualBox version
specific parameters
 - Handle empty alternate projects folder setting
 - Install Sailfish template project as a pack

Re: [SailfishDevel] SailfishOS SDK April update available tomorrow.

[Iosif Hamlatzis]

Good morning to all

Just updated my SDK with big disaster. Now it doesn't build or clean my
project which used custom build/clean steps.

In my game I don't need nor want to use Qt so I used the sample from
https://github.com/sailfish-sdk/sdk-sdl-project-example

Now I get a general message: "*Error while parsing file
C:/SailfishOS-workspace/harbour-farwest/harbour-farwest.pro
. Giving up.*"




On 16 April 2014 14:21, Jarko Vihriala  wrote:

>  Hello all,
>
> We just discovered a serious issue related to using SDK with KDE based
> Linux distros such as Fedora or KUbuntu. Therefore we have removed the
> Linux installers from the SailfishOS website. Please do not try to download
> Linux installers or update your SailfishOS SDK if you are using KDE Linux
> distro.
>
> We are now working to get the KDE issue solved, please stay tuned. We will
> inform when SDK updates are again available.
>
> thanks, Jarko
>
>
>
>  --
> *From:* Jarko Vihriala
> *Sent:* Tuesday, April 15, 2014 9:36 PM
> *To:* Sailfish OS Developers
> *Subject:* SailfishOS SDK April update available tomorrow.
>
>   Hello again,
>
> Tomorrow (16 April) at 10:00 UTC we will publish new installers, and
> package repositories for our Sailfish OS SDK version Alpha-1404-Qt5. Please
> note that links in this email are updated at that time as well.
>
> We apologise for the long delay between the SDK updates. We had to
> completely recreate our SDK production environment before being able to
> release an update. This took longer than expected and is the main reason
> for the delay.
>
> If you already have an existing Alpha-Qt5 SDK installed you should see the
> Updates Available icon in Qt Creator. If you don't have a previous SDK
> installation you can get the latest installer from
> http://www.sailfishos.org. It is recommended to uninstall the old SDK and
> download a new installer.
>
> SDK content has been updated to match Jolla Release 1.0.5.16. Please see
> below for detailed information of the changed items.
>
> A couple of things you should be aware of:
> - Like before, in this update the build engine, emulator and targets are
> re-installed so you will lose all changes you may have made in those -
> however, if your application packaging is done correctly, rebuilding your
> projects should reinstall the packages you have been using.
> - All customization done to SDK (adding new package repositories, adding
> custom targets, additional source paths) will be removed during the
> installation process so make your own backup of those before starting the
> update.
> - If you import existing projects made with a previous version of the
> Sailfish OS SDK, make sure you select the correct kit in the project
> configuration step. Both ARM and i486 kits are available.
> - Windows users need to install VC10 runtime from
> http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328 or the
> Installer will ask for admin rights during installation.
> - Package repository contents have been updated and consequently using a
> previous SDK version with these package repositories is not supported.
> - For more information, please see the SDK Alpha-Qt5 known issues list at:
> https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.
> - Oldest Mac OS X supported is now 10.8.5 (Mountain Lion). Other supported
> platforms can be found from:
> https://sailfishos.org/alpha_qt5_sdk_release_notes.html
>
> Here is a summary of changes:
>
> SDK IDE (Qt Creator)
>  - Crash fixes on OS X
>  - Yaml editor removed from Qt Creator and yaml files are presented as
> plain text
>  - Alternate projects folder can be changed from Mer settings page
>  - Better path handling for shared directories in Windows
>  - Updated Sailfish template project
>  - Handle errors in project build/deploy phase more gracefully
>  - Debugging with GDB from Qt Creator works with the Emulator and the
> Device
>  - Tooltips are displayed for Virtual Machine statuses
>  - Add changelog to your RPM with a .changes file
>
> SDK Control Center:
>  - Improved Targets management page
>  - Clean build targets are available for download via the Targets page
> (pre-configured targets)
>  - Easily install/remove multiple packages from a specific target
>  - Updates page has a "Check for updates now" button
>  - Added Harbour tools page with RPM validator tool
>
> Installer:
>  - Better VirtualBox version checking. Lowest version supported is v4.0
>  - Install virtual machines using correct VirtualBox version specific
> parameters
>  - Handle empty alternate projects folder setting
>  - Install Sailfish template project as a package making it easier to
> update
>  - Display Sailfish logo on Mac installer
>  - MerSDK no longer directly uses User's home directory, but mounts it as
> /home/mersdk/share/ inside the virtual machine
>  - User's home directory is no longer polluted with a .scratchbox2 folder
>  - Shared mounts are mounted with correct access rig

Re: [SailfishDevel] Two prolblems: #1 Telepathy qt5 and #2 OpenSSL

[christopher . lamb]

Hi UV

Many moons ago I wrote a blog on installing additional packages

http://flyingsheeponsailfish.blogspot.ch/2013/11/deploying-additional-packages-to.html

My project also uses Telepathy on Sailfish, so this may also help.  
Here is a link to the yaml file which included Telepathy stuff.


https://github.com/sailfishapps/landed/blob/master/landed26_QT5/rpm/landed26_QT5.yaml

HtH

Chris

Zitat von "Yuvraaj Kelkar" :


Hello all.
I'm trying to port my application from Maemo/Harmattan to Sailfish.

Problem 1:
One of the dependencies is telepathy-qt.
In Maemo/Harmattan this used to be installable/searchable as
"telepathy-qt4-devel"

From what I understand, in Sailfish, I'm supposed to use telepathy-qt5.
I ssh'd into the mersdk VM and did a "sudo zypper install telepathy-qt5"
As I had assumed, this doesn't install it into the sb2 environment of course.

I added a "PKGCONFIG += TelepathyQt5" to my pro file (found out from Google).
However that didn't work either.

I then entered the sb2 environment and tried to install telepathy-qt5.
This too didn't work: No root privileges.

What do I have to do to be able to use libtelepathy-qt5 ?

Problem 2:
Based on more Googling, I figured out that Sailfish does NOT provide
its own openssl library and expects users to use the statically
compiled version on their own.

I have since then gotten the non-heartbleed openssl, compiled it in
sailfish sb2 for static compilation and managed to link it against my
app.

The question is is this really the correct way to use the openssl library?
It seems unfriendly.

I really hope the answer to #1 isn't "compile it yourself and use it".
I can do that, but then I'm not sure thats the right way of doing
things...

Thanks,
Uv
___
SailfishOS.org Devel mailing list





___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Two prolblems: #1 Telepathy qt5 and #2 OpenSSL

[Kalle Vahlman]

2014-04-17 8:28 GMT+03:00 Yuvraaj Kelkar :
> That is so much better than what I was doing!
> Thanks so much!
>
> I got confused by looking at this thread:
> https://lists.sailfishos.org/pipermail/devel/2013-December/001677.html

Ah yes, that's about the Harbour rules rather than what's actually
available for use.

To submit something to Harbour, it will need to only use the approved
list of things externally and include the rest internally (ie. link
statically).



-- 
Kalle Vahlman, Movial Creative Technologies Inc.
Porkkalankatu 20, FI-00180 Helsinki
Tel +358 9 8567 6400
Fax +358 9 8567 6401
www.movial.com
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Two prolblems: #1 Telepathy qt5 and #2 OpenSSL

[Yuvraaj Kelkar]

That is so much better than what I was doing!
Thanks so much!

I got confused by looking at this thread:
https://lists.sailfishos.org/pipermail/devel/2013-December/001677.html

On Wed, Apr 16, 2014 at 10:15 PM, Kalle Vahlman
 wrote:
> 2014-04-17 2:15 GMT+03:00 Yuvraaj Kelkar :
>> Hello all.
>> I'm trying to port my application from Maemo/Harmattan to Sailfish.
>>
>> Problem 1:
>> One of the dependencies is telepathy-qt.
>> In Maemo/Harmattan this used to be installable/searchable as
>> "telepathy-qt4-devel"
>>
>> From what I understand, in Sailfish, I'm supposed to use telepathy-qt5.
>> I ssh'd into the mersdk VM and did a "sudo zypper install telepathy-qt5"
>> As I had assumed, this doesn't install it into the sb2 environment of course.
>
> It does install it to the sdk, however...
>
>> I added a "PKGCONFIG += TelepathyQt5" to my pro file (found out from Google).
>> However that didn't work either.
>
> ...if you want to use it for compilation you need the
> telepathy-qt5-devel package. And no need to ssh in the vm, just go to
> the SailfishOS -> Targets tab, click on manage for the desired
> target(s), search for telepathy and install the telepathy-qt5-devel
> package (and whatever else you need).
>
>> I then entered the sb2 environment and tried to install telepathy-qt5.
>> This too didn't work: No root privileges.
>
> If you really want to do this, add -R to sb2 command line. It will
> *appear* to give you root privileges. But as said, you don't need sb2
> for this task.
>
>> Problem 2:
>> Based on more Googling, I figured out that Sailfish does NOT provide
>> its own openssl library and expects users to use the statically
>> compiled version on their own.
>
> It certainly does *include* openssl library as the heartbleed bug was
> a part of the recent release :)
>
> Which google hit might have suggested otherwise?
>
> --
> Kalle Vahlman, Movial Creative Technologies Inc.
> Porkkalankatu 20, FI-00180 Helsinki
> Tel +358 9 8567 6400
> Fax +358 9 8567 6401
> www.movial.com
> ___
> SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Two prolblems: #1 Telepathy qt5 and #2 OpenSSL

[Kalle Vahlman]

2014-04-17 2:15 GMT+03:00 Yuvraaj Kelkar :
> Hello all.
> I'm trying to port my application from Maemo/Harmattan to Sailfish.
>
> Problem 1:
> One of the dependencies is telepathy-qt.
> In Maemo/Harmattan this used to be installable/searchable as
> "telepathy-qt4-devel"
>
> From what I understand, in Sailfish, I'm supposed to use telepathy-qt5.
> I ssh'd into the mersdk VM and did a "sudo zypper install telepathy-qt5"
> As I had assumed, this doesn't install it into the sb2 environment of course.

It does install it to the sdk, however...

> I added a "PKGCONFIG += TelepathyQt5" to my pro file (found out from Google).
> However that didn't work either.

...if you want to use it for compilation you need the
telepathy-qt5-devel package. And no need to ssh in the vm, just go to
the SailfishOS -> Targets tab, click on manage for the desired
target(s), search for telepathy and install the telepathy-qt5-devel
package (and whatever else you need).

> I then entered the sb2 environment and tried to install telepathy-qt5.
> This too didn't work: No root privileges.

If you really want to do this, add -R to sb2 command line. It will
*appear* to give you root privileges. But as said, you don't need sb2
for this task.

> Problem 2:
> Based on more Googling, I figured out that Sailfish does NOT provide
> its own openssl library and expects users to use the statically
> compiled version on their own.

It certainly does *include* openssl library as the heartbleed bug was
a part of the recent release :)

Which google hit might have suggested otherwise?

-- 
Kalle Vahlman, Movial Creative Technologies Inc.
Porkkalankatu 20, FI-00180 Helsinki
Tel +358 9 8567 6400
Fax +358 9 8567 6401
www.movial.com
___
SailfishOS.org Devel mailing list

[SailfishDevel] Two prolblems: #1 Telepathy qt5 and #2 OpenSSL

[Yuvraaj Kelkar]

Hello all.
I'm trying to port my application from Maemo/Harmattan to Sailfish.

Problem 1:
One of the dependencies is telepathy-qt.
In Maemo/Harmattan this used to be installable/searchable as
"telepathy-qt4-devel"

>From what I understand, in Sailfish, I'm supposed to use telepathy-qt5.
I ssh'd into the mersdk VM and did a "sudo zypper install telepathy-qt5"
As I had assumed, this doesn't install it into the sb2 environment of course.

I added a "PKGCONFIG += TelepathyQt5" to my pro file (found out from Google).
However that didn't work either.

I then entered the sb2 environment and tried to install telepathy-qt5.
This too didn't work: No root privileges.

What do I have to do to be able to use libtelepathy-qt5 ?

Problem 2:
Based on more Googling, I figured out that Sailfish does NOT provide
its own openssl library and expects users to use the statically
compiled version on their own.

I have since then gotten the non-heartbleed openssl, compiled it in
sailfish sb2 for static compilation and managed to link it against my
app.

The question is is this really the correct way to use the openssl library?
It seems unfriendly.

I really hope the answer to #1 isn't "compile it yourself and use it".
I can do that, but then I'm not sure thats the right way of doing
things...

Thanks,
Uv
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

[khertan]

I got the exactly same surprise. Rights of file was readable only by root.

My projects is placed on a foldr that is synced between many devices, os, and 
fs, (btsync on windows/fat32, linux ext4, ext3 on rasp, n9) ...  and look like 
file attrb are badly set :)

Regards

À Wed Apr 16 2014 14:55:37 GMT+0200 (CEST), christopher.l...@thurweb.ch a écrit 
:
> Hi Andrey
> 
> Thanks for the fast answer
> 
> Given that we are talking about cross-platform development -  
> developing on one and deploying to another I am not sure that is  
> always possible. What if my development host was Windows?
> 
> And as a developer I want to worry about writing code, not all the  
> arcane rights that all the files need to work when deployed
> 
> In fact my main development host is OSX which has unix like  
> permissions, the same as Sailfish. Having a look at the files on my  
> host, it looks like the files are now deployed with the original  
> (strange mix of) rights from my host.
> 
> However in previous SDK releases this was not an issue, As far as I  
> can see the SDK took care of permissions.
> 
> In the meantime I will chmod the files on the host and see if that helps...
> 
> Cheers
> 
> Chris
> 
> Zitat von "Andrey Kozhevnikov" :
> 
> > IMHO you should manage file permissions yourself before deploying?
> >
> > 16.04.2014 18:39, christopher.l...@thurweb.ch пишет:
> >> Hi All
> >>
> >> I have just installed the April SDK update, and have opened an  
> >> existing app, and am trying to deploy to my Jolla.
> >>
> >> The app worked with the previous SDK release, and is already  
> >> installed on the phone.
> >>
> >> If I deploy as "Deploy by copying Binaries" then thinks work as  
> >> expected, and the app successfully deploys and starts on the phone.
> >>
> >> If I deploy as "Deploy as RPM Package", then I get the error below  
> >> in QtCreator, and a "white screen of death" on the phone.
> >>
> >>
> >> [W] unknown:72 -  
> >> file:///usr/share/landed26_QT5/qml/landed26_QT5.qml:72:5: Type  
> >> MainPage unavailable
> >> MainPage {
> >> ^
> >> [W] unknown:9 -  
> >> file:///usr/share/landed26_QT5/qml/gui/MainPage.qml:9:1: Script  
> >> file:///usr/share/landed26_QT5/qml/javascript/landed.js unavailable
> >> import "../javascript/landed.js" as LJS
> >> ^
> >> [W] unknown:-1 -  
> >> file:///usr/share/landed26_QT5/qml/javascript/landed.js: File not  
> >> found
> >>
> >> I also get the white screen when trying to open the app.
> >>
> >> Via SSH on the jolla device I can find the file is present:
> >> [nemo@Jolla javascript]$ pwd
> >> /usr/share/landed26_QT5/qml/javascript
> >> [nemo@Jolla javascript]$ ls -ahl
> >> total 48K
> >> drwxr-xr-x 1 root root 152 2014-04-16 14:31 .
> >> drwxr-xr-x 1 root root 110 2014-04-16 14:31 ..
> >> -rw-r--r-- 1 root root 4.2K 2014-04-16 14:31 jsonpath.js
> >> -rw--- 1 root root 349 2014-04-16 14:31 landed.js
> >> -rw--- 1 root root 1.2K 2014-04-16 14:31 message.js
> >> -rwxr-xr-x 1 root root 9.4K 2014-04-16 14:31 readDataModel.js
> >> -rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
> >> -rw-r--r-- 1 root root 5.2K 2014-04-16 14:31 writeDataModel.js
> >>
> >> However the access permissions look very strange. I suspect that  
> >> all the js files should have rights like -rwxr-xr-x
> >>
> >> Chris
> >>
> >>
> >>
> >> ___
> >> SailfishOS.org Devel mailing list
> >
> > ___
> > SailfishOS.org Devel mailing list
> 
> 
> 
> ___
> SailfishOS.org Devel mailing lis

-- 
Benoît HERVIER - http://khertan.net
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Starting point for a Swype-like keyboard

[Peter 'p2' De Schrijver]

On 2014-04-16 09:35:31 (+0200), Ruediger Gad  wrote:
> Hi,
> 
> I am no real expert here but I used to look into Maliit some time ago:
> 
> Some pointers:
> http://quickgit.kde.org/?p=plasma-active-maliit.git
> Specifically look at, e.g.,
> active-keyboard/org/kde/active/keyboard/LandscapeVKB.qml
> 
> On the Jolla device itself: /usr/lib/maliit/plugins/jolla-keyboard.qml
> (But they seem to do some "magic" for implementing a configurable keyboard.)
> 
> https://wiki.maliit.org/Plugin_Development_Quickstart
> 
> 
> 
> In the end, it seems that a keyboard plug-in, in a nutshell, is "just" a
> QML Item (In the Maliit examples there seems to be even C++ sample
> plugin code.).
> So, all means for getting signals/events in QML should apply as well.
> Furthermore, adding custom C++/QML types should be possible too.
> Thus, you should be also able to use the "common" Qt functionality for
> getting data about the input (e.g., as offered by a MouseArea etc.).
> 

Ok! Thanks for the links!

Cheers,

Peter.
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SailfishOS SDK April update available tomorrow. [update:all installers and repositories are online]

[Mikael Hermansson]

I don't know if this is related to just kubuntu or just a VMissue since the 
sailfishemulator does not work. I just get the kernel message but sailfishUI 
does not start. More exactly lipstick does not start. I can login via ssh and 
try start lipstick but only get:

[C] unknown:0 - Failed to create display (Connection refused)

also Vbox eating cpu since fan goes wild.



On Wednesday, April 16, 2014 15:45:34 Jarko Vihriala wrote:
> Did you run fresh installation or updated ?
> If you did fresh install can you check the MD5SUM of that installer file?
> Current MD5 sums are online at:
> https://sailfishos.org/wiki/FileInformation_SDK_1404
> 
> thanks, Jarko
> 
> 
> 
> From: devel-boun...@lists.sailfishos.org
> [devel-boun...@lists.sailfishos.org] on behalf of blood9ra...@gmail.com
> [blood9ra...@gmail.com] Sent: Wednesday, April 16, 2014 6:37 PM
> To: devel@lists.sailfishos.org
> Subject: Re: [SailfishDevel] SailfishOS SDK April update available tomorrow.
> [update:all installers and repositories are online]
> 
> I installed it on KDE Archlinux and i did not found any issues?
> Should i reinstall?
> 
> On Wed Apr 16 2014 17:03:48 GMT+0200 (CEST), Jarko Vihriala wrote:
> > Update: We fixed the issue and after testing also KDE based Linux distros
> > show green light. Go ahead and head to https://www.sailfishos.org/ and
> > update or install SailfishOS SDK 1404.
> > 
> > For Linux users who managed to install/update their setup, it's
> > recommended to reinstall the 1404 SDK to make sure everything is working
> > ok.
> > 
> > We apologize this inconvenience and thank you for your understanding,
> > the Jolla SDK Team
> > 
> > 
> > From: devel-boun...@lists.sailfishos.org
> > [devel-boun...@lists.sailfishos.org] on behalf of Jarko Vihriala
> > [jarko.vihri...@jolla.com] Sent: Wednesday, April 16, 2014 2:21 PM
> > To: Sailfish OS Developers
> > Subject: Re: [SailfishDevel] SailfishOS SDK April update available
> > tomorrow.
> > 
> > Hello all,
> > 
> > We just discovered a serious issue related to using SDK with KDE based
> > Linux distros such as Fedora or KUbuntu. Therefore we have removed the
> > Linux installers from the SailfishOS website. Please do not try to
> > download Linux installers or update your SailfishOS SDK if you are using
> > KDE Linux distro.
> > 
> > We are now working to get the KDE issue solved, please stay tuned. We will
> > inform when SDK updates are again available.
> > 
> > thanks, Jarko
> > 
> > 
> > 
> > 
> > From: Jarko Vihriala
> > Sent: Tuesday, April 15, 2014 9:36 PM
> > To: Sailfish OS Developers
> > Subject: SailfishOS SDK April update available tomorrow.
> > 
> > Hello again,
> > 
> > Tomorrow (16 April) at 10:00 UTC we will publish new installers, and
> > package repositories for our Sailfish OS SDK version Alpha-1404-Qt5.
> > Please note that links in this email are updated at that time as well.
> > 
> > We apologise for the long delay between the SDK updates. We had to
> > completely recreate our SDK production environment before being able to
> > release an update. This took longer than expected and is the main reason
> > for the delay.
> > 
> > If you already have an existing Alpha-Qt5 SDK installed you should see the
> > Updates Available icon in Qt Creator. If you don't have a previous SDK
> > installation you can get the latest installer from
> > http://www.sailfishos.org. It is recommended to uninstall the old SDK and
> > download a new installer.
> > 
> > SDK content has been updated to match Jolla Release 1.0.5.16. Please see
> > below for detailed information of the changed items.
> > 
> > A couple of things you should be aware of:
> > - Like before, in this update the build engine, emulator and targets are
> > re-installed so you will lose all changes you may have made in those -
> > however, if your application packaging is done correctly, rebuilding your
> > projects should reinstall the packages you have been using. - All
> > customization done to SDK (adding new package repositories, adding 
custom
> > targets, additional source paths) will be removed during the installation
> > process so make your own backup of those before starting the update. - If
> > you import existing projects made with a previous version of the Sailfish
> > OS SDK, make sure you select the correct kit in the project configuration
> > step. Both ARM and i486 kits are available. - Windows users need to
> > install VC10 runtime from
> > http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328 or 
the
> > Installer will ask for admin rights during installation. - Package
> > repository contents have been updated and consequently using a previous
> > SDK version with these package repositories is not supported. - For more
> > information, please see the SDK Alpha-Qt5 known issues list at:
> > https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues. - Oldest Mac OS X
> > support

Re: [SailfishDevel] maces sdk issue

[Mikael Hermansson]

Same for me running kubuntu nor solution so far I tried add the VM manually 
afterward since they exist in

intslldir/ 

emulator/sailfishemu,vdk and mersdk/mersdk.vdk

But that seems not work or I have to tweak alot so I will probadly reinstall 
from scratch tomorrow... :/


On Wednesday, April 16, 2014 18:52:19 Nicola De Filippo wrote:
> Hi,
> updating the sdk on MacOS i have 2 issue:
> 
> 1) when the maintenance tool execute /usr/bin/VBoxManage createvm --
name
> MerSDK --register --basefolder /Users/nicola/SailfishOS/mersdk and i
> resolved removing MerSDK.vbox and pressing retry in the dialog
> 
> 2)  when the maintenance tool execute /usr/bin/VBoxManage createvm --
name
> SailfishOS Emulator --register --basefolder
> /Users/nicola/SailfishOS/emulator and i resolved removing Emulator.vbox and
> pressing retry in the dialog
> 


-- 
I am Software engineer and Open Source geek:

Professional experience in Qt/QML, C++, C, Python, GIT, Linux on embedded.

Twitter: http://www.twitter.com/mikecomputing
Linkedin: http://www.linkedin.com/pub/mikael-hermansson/30/95b/204
Diaspora: https://diasp.eu/u/mike7b4
Phone: +46732546542

___
SailfishOS.org Devel mailing list

[SailfishDevel] maces sdk issue

[Nicola De Filippo]

Hi,
updating the sdk on MacOS i have 2 issue:

1) when the maintenance tool execute /usr/bin/VBoxManage createvm --name MerSDK 
--register --basefolder /Users/nicola/SailfishOS/mersdk and i resolved removing 
MerSDK.vbox and pressing retry in the dialog 

2)  when the maintenance tool execute /usr/bin/VBoxManage createvm --name 
SailfishOS Emulator --register --basefolder /Users/nicola/SailfishOS/emulator 
and i resolved removing Emulator.vbox and pressing retry in the dialog

   BR
   Nicola


___
SailfishOS.org Devel mailing list

[SailfishDevel] SDL2 versions (was: RE: SailfishOS SDK April update available tomorrow.)

[Jarko Vihriala]

The SDK2* stuff in this release are following what was released with the Jolla 
Phone update5.
Just checked and SDL2 is marked as version 2.0.1-1.2.1 and SDK2_mixer is 
2.0.0-1.1.2.

You can browse through the repositories with a web client on: 
http://releases.sailfishos.org/sdk/latest/

thanks, Jarko


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Iosif Hamlatzis [i.hamlat...@gmail.com]
Sent: Wednesday, April 16, 2014 11:33 AM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] SailfishOS SDK April update available tomorrow.

What about fixes on SDL2 and SDL2_mixer libraries? Are they included with this 
update?


On 16 April 2014 11:32, Luca Donaggio 
mailto:donag...@gmail.com>> wrote:
What about localization?
I've seen some work in that area in libsailfishapp git repo, does it make the 
cut and is included in present update?
Can you give some hints on how we should use it?


On Tue, Apr 15, 2014 at 8:36 PM, Jarko Vihriala 
mailto:jarko.vihri...@jolla.com>> wrote:
Hello again,

Tomorrow (16 April) at 10:00 UTC we will publish new installers, and package 
repositories for our Sailfish OS SDK version Alpha-1404-Qt5. Please note that 
links in this email are updated at that time as well.

We apologise for the long delay between the SDK updates. We had to completely 
recreate our SDK production environment before being able to release an update. 
This took longer than expected and is the main reason for the delay.

If you already have an existing Alpha-Qt5 SDK installed you should see the 
Updates Available icon in Qt Creator. If you don't have a previous SDK 
installation you can get the latest installer from http://www.sailfishos.org. 
It is recommended to uninstall the old SDK and download a new installer.

SDK content has been updated to match Jolla Release 1.0.5.16. Please see below 
for detailed information of the changed items.

A couple of things you should be aware of:
- Like before, in this update the build engine, emulator and targets are 
re-installed so you will lose all changes you may have made in those - however, 
if your application packaging is done correctly, rebuilding your projects 
should reinstall the packages you have been using.
- All customization done to SDK (adding new package repositories, adding custom 
targets, additional source paths) will be removed during the installation 
process so make your own backup of those before starting the update.
- If you import existing projects made with a previous version of the Sailfish 
OS SDK, make sure you select the correct kit in the project configuration step. 
Both ARM and i486 kits are available.
- Windows users need to install VC10 runtime from 
http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328 or the 
Installer will ask for admin rights during installation.
- Package repository contents have been updated and consequently using a 
previous SDK version with these package repositories is not supported.
- For more information, please see the SDK Alpha-Qt5 known issues list at: 
https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.
- Oldest Mac OS X supported is now 10.8.5 (Mountain Lion). Other supported 
platforms can be found from: 
https://sailfishos.org/alpha_qt5_sdk_release_notes.html

Here is a summary of changes:

SDK IDE (Qt Creator)
 - Crash fixes on OS X
 - Yaml editor removed from Qt Creator and yaml files are presented as plain 
text
 - Alternate projects folder can be changed from Mer settings page
 - Better path handling for shared directories in Windows
 - Updated Sailfish template project
 - Handle errors in project build/deploy phase more gracefully
 - Debugging with GDB from Qt Creator works with the Emulator and the Device
 - Tooltips are displayed for Virtual Machine statuses
 - Add changelog to your RPM with a .changes file

SDK Control Center:
 - Improved Targets management page
 - Clean build targets are available for download via the Targets page 
(pre-configured targets)
 - Easily install/remove multiple packages from a specific target
 - Updates page has a "Check for updates now" button
 - Added Harbour tools page with RPM validator tool

Installer:
 - Better VirtualBox version checking. Lowest version supported is v4.0
 - Install virtual machines using correct VirtualBox version specific parameters
 - Handle empty alternate projects folder setting
 - Install Sailfish template project as a package making it easier to update
 - Display Sailfish logo on Mac installer
 - MerSDK no longer directly uses User's home directory, but mounts it as 
/home/mersdk/share/ inside the virtual machine
 - User's home directory is no longer polluted with a .scratchbox2 folder
 - Shared mounts are mounted with correct access rights
 - Default i486 target renamed to SailfishOS-i486
 - Rework documentation packaging

Emulator:
 - Applications can be removed from the Emulator's home screen by long-clicking 
on the application icon, jus

Re: [SailfishDevel] SailfishOS SDK April update available tomorrow. [update:all installers and repositories are online]

[Jarko Vihriala]

Did you run fresh installation or updated ?
If you did fresh install can you check the MD5SUM of that installer file? 
Current MD5 sums are online at:
https://sailfishos.org/wiki/FileInformation_SDK_1404

thanks, Jarko



From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of blood9ra...@gmail.com [blood9ra...@gmail.com]
Sent: Wednesday, April 16, 2014 6:37 PM
To: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] SailfishOS SDK April update available tomorrow. 
[update:all installers and repositories are online]

I installed it on KDE Archlinux and i did not found any issues?
Should i reinstall?

On Wed Apr 16 2014 17:03:48 GMT+0200 (CEST), Jarko Vihriala wrote:
> Update: We fixed the issue and after testing also KDE based Linux distros 
> show green light. Go ahead and head to https://www.sailfishos.org/ and update 
> or install SailfishOS SDK 1404.
>
> For Linux users who managed to install/update their setup, it's recommended 
> to reinstall the 1404 SDK to make sure everything is working ok.
>
> We apologize this inconvenience and thank you for your understanding,
> the Jolla SDK Team
>
> 
> From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
> on behalf of Jarko Vihriala [jarko.vihri...@jolla.com]
> Sent: Wednesday, April 16, 2014 2:21 PM
> To: Sailfish OS Developers
> Subject: Re: [SailfishDevel] SailfishOS SDK April update available tomorrow.
>
> Hello all,
>
> We just discovered a serious issue related to using SDK with KDE based Linux 
> distros such as Fedora or KUbuntu. Therefore we have removed the Linux 
> installers from the SailfishOS website. Please do not try to download Linux 
> installers or update your SailfishOS SDK if you are using KDE Linux distro.
>
> We are now working to get the KDE issue solved, please stay tuned. We will 
> inform when SDK updates are again available.
>
> thanks, Jarko
>
>
>
> 
> From: Jarko Vihriala
> Sent: Tuesday, April 15, 2014 9:36 PM
> To: Sailfish OS Developers
> Subject: SailfishOS SDK April update available tomorrow.
>
> Hello again,
>
> Tomorrow (16 April) at 10:00 UTC we will publish new installers, and package 
> repositories for our Sailfish OS SDK version Alpha-1404-Qt5. Please note that 
> links in this email are updated at that time as well.
>
> We apologise for the long delay between the SDK updates. We had to completely 
> recreate our SDK production environment before being able to release an 
> update. This took longer than expected and is the main reason for the delay.
>
> If you already have an existing Alpha-Qt5 SDK installed you should see the 
> Updates Available icon in Qt Creator. If you don't have a previous SDK 
> installation you can get the latest installer from http://www.sailfishos.org. 
> It is recommended to uninstall the old SDK and download a new installer.
>
> SDK content has been updated to match Jolla Release 1.0.5.16. Please see 
> below for detailed information of the changed items.
>
> A couple of things you should be aware of:
> - Like before, in this update the build engine, emulator and targets are 
> re-installed so you will lose all changes you may have made in those - 
> however, if your application packaging is done correctly, rebuilding your 
> projects should reinstall the packages you have been using.
> - All customization done to SDK (adding new package repositories, adding 
> custom targets, additional source paths) will be removed during the 
> installation process so make your own backup of those before starting the 
> update.
> - If you import existing projects made with a previous version of the 
> Sailfish OS SDK, make sure you select the correct kit in the project 
> configuration step. Both ARM and i486 kits are available.
> - Windows users need to install VC10 runtime from 
> http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328 or the 
> Installer will ask for admin rights during installation.
> - Package repository contents have been updated and consequently using a 
> previous SDK version with these package repositories is not supported.
> - For more information, please see the SDK Alpha-Qt5 known issues list at: 
> https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.
> - Oldest Mac OS X supported is now 10.8.5 (Mountain Lion). Other supported 
> platforms can be found from: 
> https://sailfishos.org/alpha_qt5_sdk_release_notes.html
>
> Here is a summary of changes:
>
> SDK IDE (Qt Creator)
>  - Crash fixes on OS X
>  - Yaml editor removed from Qt Creator and yaml files are presented as plain 
> text
>  - Alternate projects folder can be changed from Mer settings page
>  - Better path handling for shared directories in Windows
>  - Updated Sailfish template project
>  - Handle errors in project build/deploy phase more gracefully
>  - Debugging with GDB from Qt Creator works with the Emulator and the Device
>  - 

Re: [SailfishDevel] SailfishOS SDK April update available tomorrow. [update:all installers and repositories are online]

[blood9raven]

I installed it on KDE Archlinux and i did not found any issues?
Should i reinstall?

On Wed Apr 16 2014 17:03:48 GMT+0200 (CEST), Jarko Vihriala wrote:
> Update: We fixed the issue and after testing also KDE based Linux distros 
> show green light. Go ahead and head to https://www.sailfishos.org/ and update 
> or install SailfishOS SDK 1404.
> 
> For Linux users who managed to install/update their setup, it's recommended 
> to reinstall the 1404 SDK to make sure everything is working ok.
> 
> We apologize this inconvenience and thank you for your understanding,
> the Jolla SDK Team
> 
> 
> From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
> on behalf of Jarko Vihriala [jarko.vihri...@jolla.com]
> Sent: Wednesday, April 16, 2014 2:21 PM
> To: Sailfish OS Developers
> Subject: Re: [SailfishDevel] SailfishOS SDK April update available tomorrow.
> 
> Hello all,
> 
> We just discovered a serious issue related to using SDK with KDE based Linux 
> distros such as Fedora or KUbuntu. Therefore we have removed the Linux 
> installers from the SailfishOS website. Please do not try to download Linux 
> installers or update your SailfishOS SDK if you are using KDE Linux distro.
> 
> We are now working to get the KDE issue solved, please stay tuned. We will 
> inform when SDK updates are again available.
> 
> thanks, Jarko
> 
> 
> 
> 
> From: Jarko Vihriala
> Sent: Tuesday, April 15, 2014 9:36 PM
> To: Sailfish OS Developers
> Subject: SailfishOS SDK April update available tomorrow.
> 
> Hello again,
> 
> Tomorrow (16 April) at 10:00 UTC we will publish new installers, and package 
> repositories for our Sailfish OS SDK version Alpha-1404-Qt5. Please note that 
> links in this email are updated at that time as well.
> 
> We apologise for the long delay between the SDK updates. We had to completely 
> recreate our SDK production environment before being able to release an 
> update. This took longer than expected and is the main reason for the delay.
> 
> If you already have an existing Alpha-Qt5 SDK installed you should see the 
> Updates Available icon in Qt Creator. If you don't have a previous SDK 
> installation you can get the latest installer from http://www.sailfishos.org. 
> It is recommended to uninstall the old SDK and download a new installer.
> 
> SDK content has been updated to match Jolla Release 1.0.5.16. Please see 
> below for detailed information of the changed items.
> 
> A couple of things you should be aware of:
> - Like before, in this update the build engine, emulator and targets are 
> re-installed so you will lose all changes you may have made in those - 
> however, if your application packaging is done correctly, rebuilding your 
> projects should reinstall the packages you have been using.
> - All customization done to SDK (adding new package repositories, adding 
> custom targets, additional source paths) will be removed during the 
> installation process so make your own backup of those before starting the 
> update.
> - If you import existing projects made with a previous version of the 
> Sailfish OS SDK, make sure you select the correct kit in the project 
> configuration step. Both ARM and i486 kits are available.
> - Windows users need to install VC10 runtime from 
> http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328 or the 
> Installer will ask for admin rights during installation.
> - Package repository contents have been updated and consequently using a 
> previous SDK version with these package repositories is not supported.
> - For more information, please see the SDK Alpha-Qt5 known issues list at: 
> https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.
> - Oldest Mac OS X supported is now 10.8.5 (Mountain Lion). Other supported 
> platforms can be found from: 
> https://sailfishos.org/alpha_qt5_sdk_release_notes.html
> 
> Here is a summary of changes:
> 
> SDK IDE (Qt Creator)
>  - Crash fixes on OS X
>  - Yaml editor removed from Qt Creator and yaml files are presented as plain 
> text
>  - Alternate projects folder can be changed from Mer settings page
>  - Better path handling for shared directories in Windows
>  - Updated Sailfish template project
>  - Handle errors in project build/deploy phase more gracefully
>  - Debugging with GDB from Qt Creator works with the Emulator and the Device
>  - Tooltips are displayed for Virtual Machine statuses
>  - Add changelog to your RPM with a .changes file
> 
> SDK Control Center:
>  - Improved Targets management page
>  - Clean build targets are available for download via the Targets page 
> (pre-configured targets)
>  - Easily install/remove multiple packages from a specific target
>  - Updates page has a "Check for updates now" button
>  - Added Harbour tools page with RPM validator tool
> 
> Installer:
>  - Better VirtualBox version checking. Lowest version supported is v4.0
>  - Install virtual machines using correct Virtu

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

[Mohammed Hassan]

On Wed, 16 Apr 2014 16:17:07 +0200
 wrote:

> Hi Mohammed
> 
> thanks
> 
> The varied permission on the qml / js files on my host probably  
> reflect that the project originated in pre-sailfish days, and thus
> the files have come from various sources / versions of Qt Creator /
> edited with different text editors etc. since then.
> 
> I have now set all qml and js files in the project on my development  
> host to chmod 644
> e.g
> -rw-r--r--   1 christopherlamb  staff   7,7K 24 Feb 17:20  
> InitialCharacterPicker.qml
> 
> Are these the correct permissions? It is how a new demo project sets  
> the permissions.

I guess for RPM generation it'd be better to use %attr and %defattr as
Juha pointed out.

In general I use %defattr(-,root,root-) and that works fine for me.

What you need is +r set for everybody and +rx set on the directories.

Cheers,

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SailfishOS SDK April update available tomorrow. [update:all installers and repositories are online]

[Jarko Vihriala]

Update: We fixed the issue and after testing also KDE based Linux distros show 
green light. Go ahead and head to https://www.sailfishos.org/ and update or 
install SailfishOS SDK 1404.

For Linux users who managed to install/update their setup, it's recommended to 
reinstall the 1404 SDK to make sure everything is working ok.

We apologize this inconvenience and thank you for your understanding,
the Jolla SDK Team


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Jarko Vihriala [jarko.vihri...@jolla.com]
Sent: Wednesday, April 16, 2014 2:21 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] SailfishOS SDK April update available tomorrow.

Hello all,

We just discovered a serious issue related to using SDK with KDE based Linux 
distros such as Fedora or KUbuntu. Therefore we have removed the Linux 
installers from the SailfishOS website. Please do not try to download Linux 
installers or update your SailfishOS SDK if you are using KDE Linux distro.

We are now working to get the KDE issue solved, please stay tuned. We will 
inform when SDK updates are again available.

thanks, Jarko




From: Jarko Vihriala
Sent: Tuesday, April 15, 2014 9:36 PM
To: Sailfish OS Developers
Subject: SailfishOS SDK April update available tomorrow.

Hello again,

Tomorrow (16 April) at 10:00 UTC we will publish new installers, and package 
repositories for our Sailfish OS SDK version Alpha-1404-Qt5. Please note that 
links in this email are updated at that time as well.

We apologise for the long delay between the SDK updates. We had to completely 
recreate our SDK production environment before being able to release an update. 
This took longer than expected and is the main reason for the delay.

If you already have an existing Alpha-Qt5 SDK installed you should see the 
Updates Available icon in Qt Creator. If you don't have a previous SDK 
installation you can get the latest installer from http://www.sailfishos.org. 
It is recommended to uninstall the old SDK and download a new installer.

SDK content has been updated to match Jolla Release 1.0.5.16. Please see below 
for detailed information of the changed items.

A couple of things you should be aware of:
- Like before, in this update the build engine, emulator and targets are 
re-installed so you will lose all changes you may have made in those - however, 
if your application packaging is done correctly, rebuilding your projects 
should reinstall the packages you have been using.
- All customization done to SDK (adding new package repositories, adding custom 
targets, additional source paths) will be removed during the installation 
process so make your own backup of those before starting the update.
- If you import existing projects made with a previous version of the Sailfish 
OS SDK, make sure you select the correct kit in the project configuration step. 
Both ARM and i486 kits are available.
- Windows users need to install VC10 runtime from 
http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328 or the 
Installer will ask for admin rights during installation.
- Package repository contents have been updated and consequently using a 
previous SDK version with these package repositories is not supported.
- For more information, please see the SDK Alpha-Qt5 known issues list at: 
https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.
- Oldest Mac OS X supported is now 10.8.5 (Mountain Lion). Other supported 
platforms can be found from: 
https://sailfishos.org/alpha_qt5_sdk_release_notes.html

Here is a summary of changes:

SDK IDE (Qt Creator)
 - Crash fixes on OS X
 - Yaml editor removed from Qt Creator and yaml files are presented as plain 
text
 - Alternate projects folder can be changed from Mer settings page
 - Better path handling for shared directories in Windows
 - Updated Sailfish template project
 - Handle errors in project build/deploy phase more gracefully
 - Debugging with GDB from Qt Creator works with the Emulator and the Device
 - Tooltips are displayed for Virtual Machine statuses
 - Add changelog to your RPM with a .changes file

SDK Control Center:
 - Improved Targets management page
 - Clean build targets are available for download via the Targets page 
(pre-configured targets)
 - Easily install/remove multiple packages from a specific target
 - Updates page has a "Check for updates now" button
 - Added Harbour tools page with RPM validator tool

Installer:
 - Better VirtualBox version checking. Lowest version supported is v4.0
 - Install virtual machines using correct VirtualBox version specific parameters
 - Handle empty alternate projects folder setting
 - Install Sailfish template project as a package making it easier to update
 - Display Sailfish logo on Mac installer
 - MerSDK no longer directly uses User's home directory, but mounts it as 
/home/mersdk/share/ inside the virtual machine
 - User's home directory is no lon

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

[Juha Kallioinen]

On 16.04.2014 16:19, christopher.l...@thurweb.ch wrote:

Zitat von "Juha Kallioinen" :

Hi Juha


On my host the access permissions were

apple-pip:javascript christopherlamb$ cd 
/Users/christopherlamb/QTProjects/landed/landed26_QT5/landed26_QT5/qml/javascript

apple-pip:javascript christopherlamb$ ls -ahl
total 72
drwxr-xr-x  7 christopherlamb  staff   238B 22 Feb 22:01 .
drwxr-xr-x  9 christopherlamb  staff   306B  8 Feb 19:57 ..
-rw-r--r--  1 christopherlamb  staff   4,1K 22 Feb 22:01 jsonpath.js
-rw---  1 christopherlamb  staff   349B  8 Nov 15:56 landed.js
-rw---  1 christopherlamb  staff   1,1K 11 Feb 19:33 message.js
-rwxrwxrwx  1 christopherlamb  staff   9,4K 22 Feb 19:47 readDataModel.js
-rw-r--r--  1 christopherlamb  staff   5,2K  8 Feb 17:29 
writeDataModel.js



I am not sure why the files on my host have such wildly different 
permissions. This probably reflects the different ages / sources of 
the files. Until now the permissions set on the host was not an issue 
I had to think about.


I have now done a chmod 777 *.js


That got me a little further, it next complained about missing qml 
files, so we have a similar issue with the permissions of .qml files.


Having gone through all my qml file in the project on my host with 
chmod 755 *.qml the project now deploys successfully to the device.


So it looks like, that (at least on OSX) the permissions of files on 
the host are important and need to be set correctly as expected on the 
end device. Something for the known issues page?


Ok glad it was this issue. You can do permission management for RPM 
packages in the yaml/spec file %files section using the %attr and 
%defattr directives. Here's more information about those directives:


http://www.rpm.org/max-rpm-snapshot/s1-rpm-inside-files-list-directives.html

Best regards,
 Juha



___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

[christopher . lamb]

Hi Mohammed

thanks

The varied permission on the qml / js files on my host probably  
reflect that the project originated in pre-sailfish days, and thus the  
files have come from various sources / versions of Qt Creator / edited  
with different text editors etc. since then.


I have now set all qml and js files in the project on my development  
host to chmod 644

e.g
-rw-r--r--   1 christopherlamb  staff   7,7K 24 Feb 17:20  
InitialCharacterPicker.qml


Are these the correct permissions? It is how a new demo project sets  
the permissions.


Chris

Zitat von "Mohammed Hassan" :

You don't need executable permission (x) for js files. Read bit is  
enough so the SDK is correct here.


I noticed that the missing scripts do not have read permission set  
which is the problem.


I have no idea how it happened though.

Cheers,

--
Sent from my Nokia N9On 16.4.2014 15:39 christopher.l...@thurweb.ch wrote:
Hi All

I have just installed the April SDK update, and have opened an
existing app, and am trying to deploy to my Jolla.

The app worked with the previous SDK release, and is already installed
on the phone.

If I deploy as "Deploy by copying Binaries" then thinks work as
expected, and the app successfully deploys and starts on the phone.

If I deploy as "Deploy as RPM Package", then I get the error below in
QtCreator, and a "white screen of death" on the phone.


[W] unknown:72 -
file:///usr/share/landed26_QT5/qml/landed26_QT5.qml:72:5: Type
MainPage unavailable
  MainPage {
  ^
[W] unknown:9 -
file:///usr/share/landed26_QT5/qml/gui/MainPage.qml:9:1: Script
file:///usr/share/landed26_QT5/qml/javascript/landed.js unavailable
  import "../javascript/landed.js" as LJS
  ^
[W] unknown:-1 -
file:///usr/share/landed26_QT5/qml/javascript/landed.js: File not found

I also get the white screen when trying to open the app.

Via SSH on the jolla device I can find the file is present:
[nemo@Jolla javascript]$ pwd
/usr/share/landed26_QT5/qml/javascript
[nemo@Jolla javascript]$ ls -ahl
total 48K
drwxr-xr-x 1 root root  152 2014-04-16 14:31 .
drwxr-xr-x 1 root root  110 2014-04-16 14:31 ..
-rw-r--r-- 1 root root 4.2K 2014-04-16 14:31 jsonpath.js
-rw--- 1 root root  349 2014-04-16 14:31 landed.js
-rw--- 1 root root 1.2K 2014-04-16 14:31 message.js
-rwxr-xr-x 1 root root 9.4K 2014-04-16 14:31 readDataModel.js
-rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
-rw-r--r-- 1 root root 5.2K 2014-04-16 14:31 writeDataModel.js

However the access permissions look very strange. I suspect that all
the js files should have rights like -rwxr-xr-x

Chris



___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list





___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] where to find any statistics about apps published in Jolla Harbour?

[Luca Donaggio]

AFAIK, you can't (yet)!

These features are planned but not yet implemented in Horbour web interface
(harbour.jolla.com).


On Wed, Apr 16, 2014 at 3:37 PM, Zoltán Lutor wrote:

> Hi,
>
> Any source where developers can track their apps (downloads, reviews,
> comments, whatnot) for Jolla Harbour?
>
> Thx,
>
>  Zoltan
>
> ___
> SailfishOS.org Devel mailing list
>



-- 
Luca Donaggio
___
SailfishOS.org Devel mailing list

[SailfishDevel] where to find any statistics about apps published in Jolla Harbour?

[Zoltán Lutor]

Hi,

Any source where developers can track their apps (downloads, reviews,
comments, whatnot) for Jolla Harbour?

Thx,

 Zoltan
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

[Mohammed Hassan]

You don't need executable permission (x) for js files. Read bit is enough so 
the SDK is correct here.

I noticed that the missing scripts do not have read permission set which is the 
problem.

I have no idea how it happened though.

Cheers,

--
Sent from my Nokia N9On 16.4.2014 15:39 christopher.l...@thurweb.ch wrote:
Hi All

I have just installed the April SDK update, and have opened an  
existing app, and am trying to deploy to my Jolla.

The app worked with the previous SDK release, and is already installed  
on the phone.

If I deploy as "Deploy by copying Binaries" then thinks work as  
expected, and the app successfully deploys and starts on the phone.

If I deploy as "Deploy as RPM Package", then I get the error below in  
QtCreator, and a "white screen of death" on the phone.


[W] unknown:72 -  
file:///usr/share/landed26_QT5/qml/landed26_QT5.qml:72:5: Type  
MainPage unavailable
  MainPage {
  ^
[W] unknown:9 -  
file:///usr/share/landed26_QT5/qml/gui/MainPage.qml:9:1: Script  
file:///usr/share/landed26_QT5/qml/javascript/landed.js unavailable
  import "../javascript/landed.js" as LJS
  ^
[W] unknown:-1 -  
file:///usr/share/landed26_QT5/qml/javascript/landed.js: File not found

I also get the white screen when trying to open the app.

Via SSH on the jolla device I can find the file is present:
[nemo@Jolla javascript]$ pwd
/usr/share/landed26_QT5/qml/javascript
[nemo@Jolla javascript]$ ls -ahl
total 48K
drwxr-xr-x 1 root root  152 2014-04-16 14:31 .
drwxr-xr-x 1 root root  110 2014-04-16 14:31 ..
-rw-r--r-- 1 root root 4.2K 2014-04-16 14:31 jsonpath.js
-rw--- 1 root root  349 2014-04-16 14:31 landed.js
-rw--- 1 root root 1.2K 2014-04-16 14:31 message.js
-rwxr-xr-x 1 root root 9.4K 2014-04-16 14:31 readDataModel.js
-rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
-rw-r--r-- 1 root root 5.2K 2014-04-16 14:31 writeDataModel.js

However the access permissions look very strange. I suspect that all  
the js files should have rights like -rwxr-xr-x

Chris



___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

[christopher . lamb]

Zitat von "Juha Kallioinen" :

Hi Juha


On my host the access permissions were

apple-pip:javascript christopherlamb$ cd  
/Users/christopherlamb/QTProjects/landed/landed26_QT5/landed26_QT5/qml/javascript

apple-pip:javascript christopherlamb$ ls -ahl
total 72
drwxr-xr-x  7 christopherlamb  staff   238B 22 Feb 22:01 .
drwxr-xr-x  9 christopherlamb  staff   306B  8 Feb 19:57 ..
-rw-r--r--  1 christopherlamb  staff   4,1K 22 Feb 22:01 jsonpath.js
-rw---  1 christopherlamb  staff   349B  8 Nov 15:56 landed.js
-rw---  1 christopherlamb  staff   1,1K 11 Feb 19:33 message.js
-rwxrwxrwx  1 christopherlamb  staff   9,4K 22 Feb 19:47 readDataModel.js
-rw-r--r--  1 christopherlamb  staff   5,2K  8 Feb 17:29 writeDataModel.js


I am not sure why the files on my host have such wildly different  
permissions. This probably reflects the different ages / sources of  
the files. Until now the permissions set on the host was not an issue  
I had to think about.


I have now done a chmod 777 *.js


That got me a little further, it next complained about missing qml  
files, so we have a similar issue with the permissions of .qml files.


Having gone through all my qml file in the project on my host with  
chmod 755 *.qml the project now deploys successfully to the device.


So it looks like, that (at least on OSX) the permissions of files on  
the host are important and need to be set correctly as expected on the  
end device. Something for the known issues page?



Grüsse

Chris



Hi Chris,

I've changed the way the shared directories are mounted to the  
virtual machine. This might be caused by that. Previously the shared  
folders were mounted with 777 rights and all files were shown as  
read/write/exec for all inside the virtual  machine. I've changed it  
so that the rights are as they are on your host filesystem.


But there's really no reason for those two files to have only root  
access and the others have more access unless there's some root  
cause with your source files.


There's no code anywhere in the SDK that checks if a file is named  
'landed.js' and modifies its access rights :-)


What are the source files' permissions in your Mac's filesystem when  
you list them?


Best regards,
 Juha



___
SailfishOS.org Devel mailing list





___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

[Juha Kallioinen]

On 16.04.2014 15:39, christopher.l...@thurweb.ch wrote:

Hi All


...

I also get the white screen when trying to open the app.

Via SSH on the jolla device I can find the file is present:
[nemo@Jolla javascript]$ pwd
/usr/share/landed26_QT5/qml/javascript
[nemo@Jolla javascript]$ ls -ahl
total 48K
drwxr-xr-x 1 root root  152 2014-04-16 14:31 .
drwxr-xr-x 1 root root  110 2014-04-16 14:31 ..
-rw-r--r-- 1 root root 4.2K 2014-04-16 14:31 jsonpath.js
-rw--- 1 root root  349 2014-04-16 14:31 landed.js
-rw--- 1 root root 1.2K 2014-04-16 14:31 message.js
-rwxr-xr-x 1 root root 9.4K 2014-04-16 14:31 readDataModel.js
-rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
-rw-r--r-- 1 root root 5.2K 2014-04-16 14:31 writeDataModel.js

However the access permissions look very strange. I suspect that all 
the js files should have rights like -rwxr-xr-x


Hi Chris,

I've changed the way the shared directories are mounted to the virtual 
machine. This might be caused by that. Previously the shared folders 
were mounted with 777 rights and all files were shown as read/write/exec 
for all inside the virtual  machine. I've changed it so that the rights 
are as they are on your host filesystem.


But there's really no reason for those two files to have only root 
access and the others have more access unless there's some root cause 
with your source files.


There's no code anywhere in the SDK that checks if a file is named 
'landed.js' and modifies its access rights :-)


What are the source files' permissions in your Mac's filesystem when you 
list them?


Best regards,
 Juha



___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

[Luca Donaggio]

This reminds me of SDK RPM-validator tool complaining about files with
executable permission (it issued a warning about possible deprecation of
executable files in RPM according to Harbour rules).

If any sort of permission-scheme has to be enforced, shouldn't the SDK's
RPM generator take care of it by itself?


On Wed, Apr 16, 2014 at 2:41 PM, Andrey Kozhevnikov
wrote:

> IMHO you should manage file permissions yourself before deploying?
>
> 16.04.2014 18:39, christopher.l...@thurweb.ch пишет:
>
>  Hi All
>>
>> I have just installed the April SDK update, and have opened an existing
>> app, and am trying to deploy to my Jolla.
>>
>> The app worked with the previous SDK release, and is already installed on
>> the phone.
>>
>> If I deploy as "Deploy by copying Binaries" then thinks work as expected,
>> and the app successfully deploys and starts on the phone.
>>
>> If I deploy as "Deploy as RPM Package", then I get the error below in
>> QtCreator, and a "white screen of death" on the phone.
>>
>>
>> [W] unknown:72 - file:///usr/share/landed26_QT5/qml/landed26_QT5.qml:72:5:
>> Type MainPage unavailable
>> MainPage {
>> ^
>> [W] unknown:9 - file:///usr/share/landed26_QT5/qml/gui/MainPage.qml:9:1:
>> Script file:///usr/share/landed26_QT5/qml/javascript/landed.js
>> unavailable
>> import "../javascript/landed.js" as LJS
>> ^
>> [W] unknown:-1 - file:///usr/share/landed26_QT5/qml/javascript/landed.js:
>> File not found
>>
>> I also get the white screen when trying to open the app.
>>
>> Via SSH on the jolla device I can find the file is present:
>> [nemo@Jolla javascript]$ pwd
>> /usr/share/landed26_QT5/qml/javascript
>> [nemo@Jolla javascript]$ ls -ahl
>> total 48K
>> drwxr-xr-x 1 root root 152 2014-04-16 14:31 .
>> drwxr-xr-x 1 root root 110 2014-04-16 14:31 ..
>> -rw-r--r-- 1 root root 4.2K 2014-04-16 14:31 jsonpath.js
>> -rw--- 1 root root 349 2014-04-16 14:31 landed.js
>> -rw--- 1 root root 1.2K 2014-04-16 14:31 message.js
>> -rwxr-xr-x 1 root root 9.4K 2014-04-16 14:31 readDataModel.js
>> -rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
>> -rw-r--r-- 1 root root 5.2K 2014-04-16 14:31 writeDataModel.js
>>
>> However the access permissions look very strange. I suspect that all the
>> js files should have rights like -rwxr-xr-x
>>
>> Chris
>>
>>
>>
>> ___
>> SailfishOS.org Devel mailing list
>>
>
> ___
> SailfishOS.org Devel mailing list
>



-- 
Luca Donaggio
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

[christopher . lamb]

Hi Andrey

Thanks for the fast answer

Given that we are talking about cross-platform development -  
developing on one and deploying to another I am not sure that is  
always possible. What if my development host was Windows?


And as a developer I want to worry about writing code, not all the  
arcane rights that all the files need to work when deployed


In fact my main development host is OSX which has unix like  
permissions, the same as Sailfish. Having a look at the files on my  
host, it looks like the files are now deployed with the original  
(strange mix of) rights from my host.


However in previous SDK releases this was not an issue, As far as I  
can see the SDK took care of permissions.


In the meantime I will chmod the files on the host and see if that helps...

Cheers

Chris

Zitat von "Andrey Kozhevnikov" :


IMHO you should manage file permissions yourself before deploying?

16.04.2014 18:39, christopher.l...@thurweb.ch пишет:

Hi All

I have just installed the April SDK update, and have opened an  
existing app, and am trying to deploy to my Jolla.


The app worked with the previous SDK release, and is already  
installed on the phone.


If I deploy as "Deploy by copying Binaries" then thinks work as  
expected, and the app successfully deploys and starts on the phone.


If I deploy as "Deploy as RPM Package", then I get the error below  
in QtCreator, and a "white screen of death" on the phone.



[W] unknown:72 -  
file:///usr/share/landed26_QT5/qml/landed26_QT5.qml:72:5: Type  
MainPage unavailable

MainPage {
^
[W] unknown:9 -  
file:///usr/share/landed26_QT5/qml/gui/MainPage.qml:9:1: Script  
file:///usr/share/landed26_QT5/qml/javascript/landed.js unavailable

import "../javascript/landed.js" as LJS
^
[W] unknown:-1 -  
file:///usr/share/landed26_QT5/qml/javascript/landed.js: File not  
found


I also get the white screen when trying to open the app.

Via SSH on the jolla device I can find the file is present:
[nemo@Jolla javascript]$ pwd
/usr/share/landed26_QT5/qml/javascript
[nemo@Jolla javascript]$ ls -ahl
total 48K
drwxr-xr-x 1 root root 152 2014-04-16 14:31 .
drwxr-xr-x 1 root root 110 2014-04-16 14:31 ..
-rw-r--r-- 1 root root 4.2K 2014-04-16 14:31 jsonpath.js
-rw--- 1 root root 349 2014-04-16 14:31 landed.js
-rw--- 1 root root 1.2K 2014-04-16 14:31 message.js
-rwxr-xr-x 1 root root 9.4K 2014-04-16 14:31 readDataModel.js
-rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
-rw-r--r-- 1 root root 5.2K 2014-04-16 14:31 writeDataModel.js

However the access permissions look very strange. I suspect that  
all the js files should have rights like -rwxr-xr-x


Chris



___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list




___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] What happens on Harbour between approved and published?

[Reto Zingg]

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] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

[Andrey Kozhevnikov]

IMHO you should manage file permissions yourself before deploying?

16.04.2014 18:39, christopher.l...@thurweb.ch пишет:

Hi All

I have just installed the April SDK update, and have opened an 
existing app, and am trying to deploy to my Jolla.


The app worked with the previous SDK release, and is already installed 
on the phone.


If I deploy as "Deploy by copying Binaries" then thinks work as 
expected, and the app successfully deploys and starts on the phone.


If I deploy as "Deploy as RPM Package", then I get the error below in 
QtCreator, and a "white screen of death" on the phone.



[W] unknown:72 - 
file:///usr/share/landed26_QT5/qml/landed26_QT5.qml:72:5: Type 
MainPage unavailable

MainPage {
^
[W] unknown:9 - 
file:///usr/share/landed26_QT5/qml/gui/MainPage.qml:9:1: Script 
file:///usr/share/landed26_QT5/qml/javascript/landed.js unavailable

import "../javascript/landed.js" as LJS
^
[W] unknown:-1 - 
file:///usr/share/landed26_QT5/qml/javascript/landed.js: File not found


I also get the white screen when trying to open the app.

Via SSH on the jolla device I can find the file is present:
[nemo@Jolla javascript]$ pwd
/usr/share/landed26_QT5/qml/javascript
[nemo@Jolla javascript]$ ls -ahl
total 48K
drwxr-xr-x 1 root root 152 2014-04-16 14:31 .
drwxr-xr-x 1 root root 110 2014-04-16 14:31 ..
-rw-r--r-- 1 root root 4.2K 2014-04-16 14:31 jsonpath.js
-rw--- 1 root root 349 2014-04-16 14:31 landed.js
-rw--- 1 root root 1.2K 2014-04-16 14:31 message.js
-rwxr-xr-x 1 root root 9.4K 2014-04-16 14:31 readDataModel.js
-rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
-rw-r--r-- 1 root root 5.2K 2014-04-16 14:31 writeDataModel.js

However the access permissions look very strange. I suspect that all 
the js files should have rights like -rwxr-xr-x


Chris



___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

[SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

[christopher . lamb]

Hi All

I have just installed the April SDK update, and have opened an  
existing app, and am trying to deploy to my Jolla.


The app worked with the previous SDK release, and is already installed  
on the phone.


If I deploy as "Deploy by copying Binaries" then thinks work as  
expected, and the app successfully deploys and starts on the phone.


If I deploy as "Deploy as RPM Package", then I get the error below in  
QtCreator, and a "white screen of death" on the phone.



[W] unknown:72 -  
file:///usr/share/landed26_QT5/qml/landed26_QT5.qml:72:5: Type  
MainPage unavailable

 MainPage {
 ^
[W] unknown:9 -  
file:///usr/share/landed26_QT5/qml/gui/MainPage.qml:9:1: Script  
file:///usr/share/landed26_QT5/qml/javascript/landed.js unavailable

 import "../javascript/landed.js" as LJS
 ^
[W] unknown:-1 -  
file:///usr/share/landed26_QT5/qml/javascript/landed.js: File not found


I also get the white screen when trying to open the app.

Via SSH on the jolla device I can find the file is present:
[nemo@Jolla javascript]$ pwd
/usr/share/landed26_QT5/qml/javascript
[nemo@Jolla javascript]$ ls -ahl
total 48K
drwxr-xr-x 1 root root  152 2014-04-16 14:31 .
drwxr-xr-x 1 root root  110 2014-04-16 14:31 ..
-rw-r--r-- 1 root root 4.2K 2014-04-16 14:31 jsonpath.js
-rw--- 1 root root  349 2014-04-16 14:31 landed.js
-rw--- 1 root root 1.2K 2014-04-16 14:31 message.js
-rwxr-xr-x 1 root root 9.4K 2014-04-16 14:31 readDataModel.js
-rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
-rw-r--r-- 1 root root 5.2K 2014-04-16 14:31 writeDataModel.js

However the access permissions look very strange. I suspect that all  
the js files should have rights like -rwxr-xr-x


Chris



___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SailfishOS SDK April update available tomorrow.

[Jarko Vihriala]

Hello all,

We just discovered a serious issue related to using SDK with KDE based Linux 
distros such as Fedora or KUbuntu. Therefore we have removed the Linux 
installers from the SailfishOS website. Please do not try to download Linux 
installers or update your SailfishOS SDK if you are using KDE Linux distro.

We are now working to get the KDE issue solved, please stay tuned. We will 
inform when SDK updates are again available.

thanks, Jarko




From: Jarko Vihriala
Sent: Tuesday, April 15, 2014 9:36 PM
To: Sailfish OS Developers
Subject: SailfishOS SDK April update available tomorrow.

Hello again,

Tomorrow (16 April) at 10:00 UTC we will publish new installers, and package 
repositories for our Sailfish OS SDK version Alpha-1404-Qt5. Please note that 
links in this email are updated at that time as well.

We apologise for the long delay between the SDK updates. We had to completely 
recreate our SDK production environment before being able to release an update. 
This took longer than expected and is the main reason for the delay.

If you already have an existing Alpha-Qt5 SDK installed you should see the 
Updates Available icon in Qt Creator. If you don't have a previous SDK 
installation you can get the latest installer from http://www.sailfishos.org. 
It is recommended to uninstall the old SDK and download a new installer.

SDK content has been updated to match Jolla Release 1.0.5.16. Please see below 
for detailed information of the changed items.

A couple of things you should be aware of:
- Like before, in this update the build engine, emulator and targets are 
re-installed so you will lose all changes you may have made in those - however, 
if your application packaging is done correctly, rebuilding your projects 
should reinstall the packages you have been using.
- All customization done to SDK (adding new package repositories, adding custom 
targets, additional source paths) will be removed during the installation 
process so make your own backup of those before starting the update.
- If you import existing projects made with a previous version of the Sailfish 
OS SDK, make sure you select the correct kit in the project configuration step. 
Both ARM and i486 kits are available.
- Windows users need to install VC10 runtime from 
http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328 or the 
Installer will ask for admin rights during installation.
- Package repository contents have been updated and consequently using a 
previous SDK version with these package repositories is not supported.
- For more information, please see the SDK Alpha-Qt5 known issues list at: 
https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.
- Oldest Mac OS X supported is now 10.8.5 (Mountain Lion). Other supported 
platforms can be found from: 
https://sailfishos.org/alpha_qt5_sdk_release_notes.html

Here is a summary of changes:

SDK IDE (Qt Creator)
 - Crash fixes on OS X
 - Yaml editor removed from Qt Creator and yaml files are presented as plain 
text
 - Alternate projects folder can be changed from Mer settings page
 - Better path handling for shared directories in Windows
 - Updated Sailfish template project
 - Handle errors in project build/deploy phase more gracefully
 - Debugging with GDB from Qt Creator works with the Emulator and the Device
 - Tooltips are displayed for Virtual Machine statuses
 - Add changelog to your RPM with a .changes file

SDK Control Center:
 - Improved Targets management page
 - Clean build targets are available for download via the Targets page 
(pre-configured targets)
 - Easily install/remove multiple packages from a specific target
 - Updates page has a "Check for updates now" button
 - Added Harbour tools page with RPM validator tool

Installer:
 - Better VirtualBox version checking. Lowest version supported is v4.0
 - Install virtual machines using correct VirtualBox version specific parameters
 - Handle empty alternate projects folder setting
 - Install Sailfish template project as a package making it easier to update
 - Display Sailfish logo on Mac installer
 - MerSDK no longer directly uses User's home directory, but mounts it as 
/home/mersdk/share/ inside the virtual machine
 - User's home directory is no longer polluted with a .scratchbox2 folder
 - Shared mounts are mounted with correct access rights
 - Default i486 target renamed to SailfishOS-i486
 - Rework documentation packaging

Emulator:
 - Applications can be removed from the Emulator's home screen by long-clicking 
on the application icon, just like it is done on the phone.

If you have any questions, you can either send email to this mailing list: 
devel@lists.sailfishos.org or write it up in http://together.jolla.com and tag 
your issue with 'sdk'.

Happy hacking,
Jolla SDK Team.

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SDL_mixer: different behaviour between emulator and actual device

[Thomas Perl]

On 2014-04-15 18:40, Iosif Hamlatzis wrote:
Just verified it the sample from 
https://github.com/thp/sdl2-opengles-test regarding the mixer only 
works on the emulator.


On the emulator every time you touch the screen a sound (.ogg file 
format) is played, but on the actual device no sound comes out.


Did something go wrong when SDL2_mixer was ported to SailfishOS?


No, but there did change something in the middleware that requires you 
to acquire the audio resources. I'll eventually update the example code 
to use libaudioresource. See below for a link to a SDL2 project that 
already uses libaudioresource.


See: https://github.com/thp/sdl2-opengles-test/issues/1

The example needs to be updated to use libaudioresource (which is a 
thin, API-stable wrapper around the real libresource):

https://github.com/nemomobile/libaudioresource/

Some example code that already uses libaudioresource:
https://github.com/thp/brainparty/blob/sailfish/main.cpp


HTH :)
Thomas
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SailfishOS SDK April update available tomorrow.

[Iosif Hamlatzis]

What about fixes on SDL2 and SDL2_mixer libraries? Are they included with
this update?


On 16 April 2014 11:32, Luca Donaggio  wrote:

> What about localization?
> I've seen some work in that area in libsailfishapp git repo, does it make
> the cut and is included in present update?
> Can you give some hints on how we should use it?
>
>
> On Tue, Apr 15, 2014 at 8:36 PM, Jarko Vihriala 
> wrote:
>
>>  Hello again,
>>
>> Tomorrow (16 April) at 10:00 UTC we will publish new installers, and
>> package repositories for our Sailfish OS SDK version Alpha-1404-Qt5. Please
>> note that links in this email are updated at that time as well.
>>
>> We apologise for the long delay between the SDK updates. We had to
>> completely recreate our SDK production environment before being able to
>> release an update. This took longer than expected and is the main reason
>> for the delay.
>>
>> If you already have an existing Alpha-Qt5 SDK installed you should see
>> the Updates Available icon in Qt Creator. If you don't have a previous SDK
>> installation you can get the latest installer from
>> http://www.sailfishos.org. It is recommended to uninstall the old SDK
>> and download a new installer.
>>
>> SDK content has been updated to match Jolla Release 1.0.5.16. Please see
>> below for detailed information of the changed items.
>>
>> A couple of things you should be aware of:
>> - Like before, in this update the build engine, emulator and targets are
>> re-installed so you will lose all changes you may have made in those -
>> however, if your application packaging is done correctly, rebuilding your
>> projects should reinstall the packages you have been using.
>> - All customization done to SDK (adding new package repositories, adding
>> custom targets, additional source paths) will be removed during the
>> installation process so make your own backup of those before starting the
>> update.
>> - If you import existing projects made with a previous version of the
>> Sailfish OS SDK, make sure you select the correct kit in the project
>> configuration step. Both ARM and i486 kits are available.
>> - Windows users need to install VC10 runtime from
>> http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328 or the
>> Installer will ask for admin rights during installation.
>> - Package repository contents have been updated and consequently using a
>> previous SDK version with these package repositories is not supported.
>> - For more information, please see the SDK Alpha-Qt5 known issues list
>> at: https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.
>> - Oldest Mac OS X supported is now 10.8.5 (Mountain Lion). Other
>> supported platforms can be found from:
>> https://sailfishos.org/alpha_qt5_sdk_release_notes.html
>>
>> Here is a summary of changes:
>>
>> SDK IDE (Qt Creator)
>>  - Crash fixes on OS X
>>  - Yaml editor removed from Qt Creator and yaml files are presented as
>> plain text
>>  - Alternate projects folder can be changed from Mer settings page
>>  - Better path handling for shared directories in Windows
>>  - Updated Sailfish template project
>>  - Handle errors in project build/deploy phase more gracefully
>>  - Debugging with GDB from Qt Creator works with the Emulator and the
>> Device
>>  - Tooltips are displayed for Virtual Machine statuses
>>  - Add changelog to your RPM with a .changes file
>>
>> SDK Control Center:
>>  - Improved Targets management page
>>  - Clean build targets are available for download via the Targets page
>> (pre-configured targets)
>>  - Easily install/remove multiple packages from a specific target
>>  - Updates page has a "Check for updates now" button
>>  - Added Harbour tools page with RPM validator tool
>>
>> Installer:
>>  - Better VirtualBox version checking. Lowest version supported is v4.0
>>  - Install virtual machines using correct VirtualBox version specific
>> parameters
>>  - Handle empty alternate projects folder setting
>>  - Install Sailfish template project as a package making it easier to
>> update
>>  - Display Sailfish logo on Mac installer
>>  - MerSDK no longer directly uses User's home directory, but mounts it as
>> /home/mersdk/share/ inside the virtual machine
>>  - User's home directory is no longer polluted with a .scratchbox2 folder
>>  - Shared mounts are mounted with correct access rights
>>  - Default i486 target renamed to SailfishOS-i486
>>  - Rework documentation packaging
>>
>> Emulator:
>>  - Applications can be removed from the Emulator's home screen by
>> long-clicking on the application icon, just like it is done on the phone.
>>
>> If you have any questions, you can either send email to this mailing
>> list: devel@lists.sailfishos.org or write it up in
>> http://together.jolla.com and tag your issue with 'sdk'.
>>
>> Happy hacking,
>> Jolla SDK Team.
>>
>>
>> ___
>> SailfishOS.org Devel mailing list
>>
>
>
>
> --
> Luca Donaggio
>
> ___
> Sailfi

Re: [SailfishDevel] SailfishOS SDK April update available tomorrow.

[Luca Donaggio]

What about localization?
I've seen some work in that area in libsailfishapp git repo, does it make
the cut and is included in present update?
Can you give some hints on how we should use it?


On Tue, Apr 15, 2014 at 8:36 PM, Jarko Vihriala wrote:

>  Hello again,
>
> Tomorrow (16 April) at 10:00 UTC we will publish new installers, and
> package repositories for our Sailfish OS SDK version Alpha-1404-Qt5. Please
> note that links in this email are updated at that time as well.
>
> We apologise for the long delay between the SDK updates. We had to
> completely recreate our SDK production environment before being able to
> release an update. This took longer than expected and is the main reason
> for the delay.
>
> If you already have an existing Alpha-Qt5 SDK installed you should see the
> Updates Available icon in Qt Creator. If you don't have a previous SDK
> installation you can get the latest installer from
> http://www.sailfishos.org. It is recommended to uninstall the old SDK and
> download a new installer.
>
> SDK content has been updated to match Jolla Release 1.0.5.16. Please see
> below for detailed information of the changed items.
>
> A couple of things you should be aware of:
> - Like before, in this update the build engine, emulator and targets are
> re-installed so you will lose all changes you may have made in those -
> however, if your application packaging is done correctly, rebuilding your
> projects should reinstall the packages you have been using.
> - All customization done to SDK (adding new package repositories, adding
> custom targets, additional source paths) will be removed during the
> installation process so make your own backup of those before starting the
> update.
> - If you import existing projects made with a previous version of the
> Sailfish OS SDK, make sure you select the correct kit in the project
> configuration step. Both ARM and i486 kits are available.
> - Windows users need to install VC10 runtime from
> http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328 or the
> Installer will ask for admin rights during installation.
> - Package repository contents have been updated and consequently using a
> previous SDK version with these package repositories is not supported.
> - For more information, please see the SDK Alpha-Qt5 known issues list at:
> https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.
> - Oldest Mac OS X supported is now 10.8.5 (Mountain Lion). Other supported
> platforms can be found from:
> https://sailfishos.org/alpha_qt5_sdk_release_notes.html
>
> Here is a summary of changes:
>
> SDK IDE (Qt Creator)
>  - Crash fixes on OS X
>  - Yaml editor removed from Qt Creator and yaml files are presented as
> plain text
>  - Alternate projects folder can be changed from Mer settings page
>  - Better path handling for shared directories in Windows
>  - Updated Sailfish template project
>  - Handle errors in project build/deploy phase more gracefully
>  - Debugging with GDB from Qt Creator works with the Emulator and the
> Device
>  - Tooltips are displayed for Virtual Machine statuses
>  - Add changelog to your RPM with a .changes file
>
> SDK Control Center:
>  - Improved Targets management page
>  - Clean build targets are available for download via the Targets page
> (pre-configured targets)
>  - Easily install/remove multiple packages from a specific target
>  - Updates page has a "Check for updates now" button
>  - Added Harbour tools page with RPM validator tool
>
> Installer:
>  - Better VirtualBox version checking. Lowest version supported is v4.0
>  - Install virtual machines using correct VirtualBox version specific
> parameters
>  - Handle empty alternate projects folder setting
>  - Install Sailfish template project as a package making it easier to
> update
>  - Display Sailfish logo on Mac installer
>  - MerSDK no longer directly uses User's home directory, but mounts it as
> /home/mersdk/share/ inside the virtual machine
>  - User's home directory is no longer polluted with a .scratchbox2 folder
>  - Shared mounts are mounted with correct access rights
>  - Default i486 target renamed to SailfishOS-i486
>  - Rework documentation packaging
>
> Emulator:
>  - Applications can be removed from the Emulator's home screen by
> long-clicking on the application icon, just like it is done on the phone.
>
> If you have any questions, you can either send email to this mailing list:
> devel@lists.sailfishos.org or write it up in http://together.jolla.comand tag 
> your issue with 'sdk'.
>
> Happy hacking,
> Jolla SDK Team.
>
>
> ___
> SailfishOS.org Devel mailing list
>



-- 
Luca Donaggio
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] [Minutes][FollowUp] A kickoff meeting about SailfishOS, open source, collaboration, way forward @ 15 April, 15:00 UTC

[Filip Kłębczyk]

W dniu 15.04.2014 18:40, "Thomas B. Rücker" pisze:

Hi,

thanks to everyone for the great discussion. It was a pleasure to chair it.
Without further ado, here are the meeting minutes:

Minutes:
http://merproject.org/meetings/mer-meeting/2014/mer-meeting.2014-04-15-15.00.html
Minutes (text):
http://merproject.org/meetings/mer-meeting/2014/mer-meeting.2014-04-15-15.00.txt
Log:
http://merproject.org/meetings/mer-meeting/2014/mer-meeting.2014-04-15-15.00.log.html

For follow up discussion just answer to this email/thread.

The next meeting will be at2014-04-22T15:00 UTC.
Invitation and topics will be posted separately.

Thanks again


Thank you all for making this meeting to happen - I think it was 
fruitful discussion.


Though, I have one serious, technical/organizational point. I don't 
understand why time from topic 3.3 was taken - it was supposed to last 
16:26 UTC, but ended 16:12 despite there were still discussants. For 
example what I was expressing was cut by tbr announcing 3.4 and it 
landed partly in 3.4. For me personally topic 3.3 was very, very 
important, as much as 3.2 for example. Also I didn't like the fact, that 
not related topics were brought in 3.3. It's all clearly seen in the logs:

http://merproject.org/meetings/mer-meeting/2014/mer-meeting.2014-04-15-15.00.log.html

I know there might be less or more comfortable topics for someone or 
topic might be not important, but cutting discussion in the middle is 
not ok and not fair.


SOLUTION:
Therefore I propose not cutting time of topic if there is still at least 
one person that wants to say something and continue discussion or 
discussion is still happening.


Also another remark - if there are large chunks of text like:
https://together.jolla.com/question/39552/what-is-the-participation-and-contribution-policy-for-jollas-open-source-contributors-in-open-source-projects/

there should be e-mail on mailing list, before meeting, that such thing 
appeared, so all discussants have time to read it. How that looks, when 
link to such document is pasted on the beginning of 3.3 and that part of 
discussion gets time cut I think everyone can judge by himself.


Personally I wouldn't even spot it if Morpog_PC didn't paste it on the 
IRC channel some time before the meeting, that such document appeared.


Regards,
Filip
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Starting point for a Swype-like keyboard

[Seppo Tiainen]

Hi,

How about using QML and MultiPointTouchArea as a starting point to get the
touch data? Probably you are more interested in Qt...

Seppo


2014-04-16 9:58 GMT+03:00 Vivia Nikolaidou :

> Hi all, and thanks a lot for your replies!
>
> We did investigate the patents before deciding to start the project
> and they do indeed seem to be US-only. So, as long as Jolla isn't even
> available in the US, everything should be fine.
>
> On the other hand, just to be on the safe side, we thought about
> leaving it in "beta-proof-of-concept" stage, or at least labelling it
> as such, and not promoting it (word of mouth should be enough to make
> it reach the devices of those who really want it). After all, patents
> only apply for things like sales and exporting, not for "academic
> purposes". If someone with access to a patent lawyer would like to
> investigate things and help it turn into a real project, this help
> would be more than welcome, but unfortunately we don't have such
> resources.
>
> As for github/gitorious, we'll gladly share it when there's something
> worthwhile, but without being able to get actual raw data from a
> finger drawing a curve, there's not much coding that can be done. So
> we'd really appreciate it if someone could give us a hint. :)
>
> Thanks again,
>
> Vivia
>
> On 15 April 2014 22:38,   wrote:
> > But how does it  work for the other swype like keyboards available for
> android?
> >
> > I can't see any differences to the original one.
> >
> > Am Tue Apr 15 2014 20:49:46 GMT+0200 (CEST) schrieb Michael Doube:
> >> On 15/04/14 19:39, Martin Kolman wrote:
> >> >> A quick look at the bottom of the Wikipedia entry for Swype confirms
> >> >> my suspicion... (2 US patents). :-(
> >> > Well, they look like to be US patents - so considering the Jolla is
> not
> >> > even sold in the USA & it would be an external application anyway, I
> >> > don't really see any issue.
> >>
> >> Well, I wouldn't want the Jolla team to find themselves in hot water for
> >> distributing unlicensed functionality on the Harbour site. Nor the
> >> external application developer for implementing and publishing it, maybe
> >> even for a fee. Since Swype made a US patent, and their product is
> >> distributed worldwide, I would expect to find some European patents too
> >> (not being listed on Wikipedia is not authoritative evidence of
> >> non-existence). Anyway, this is non-expert handwaving. If there is a
> >> legal way to get something Swype-like on the Jolla, it would be great.
> >>
> >> Michael
> >>
> >> ___
> >> SailfishOS.org Devel mailing list
> >>
> >
> > --
> > Gesendet von meinem Jolla
> > ___
> > SailfishOS.org Devel mailing list
> ___
> SailfishOS.org Devel mailing list
>
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Starting point for a Swype-like keyboard

[Ruediger Gad]

Hi,

I am no real expert here but I used to look into Maliit some time ago:

Some pointers:
http://quickgit.kde.org/?p=plasma-active-maliit.git
Specifically look at, e.g.,
active-keyboard/org/kde/active/keyboard/LandscapeVKB.qml

On the Jolla device itself: /usr/lib/maliit/plugins/jolla-keyboard.qml
(But they seem to do some "magic" for implementing a configurable keyboard.)

https://wiki.maliit.org/Plugin_Development_Quickstart



In the end, it seems that a keyboard plug-in, in a nutshell, is "just" a
QML Item (In the Maliit examples there seems to be even C++ sample
plugin code.).
So, all means for getting signals/events in QML should apply as well.
Furthermore, adding custom C++/QML types should be possible too.
Thus, you should be also able to use the "common" Qt functionality for
getting data about the input (e.g., as offered by a MouseArea etc.).



hth,

Ruediger




On 04/16/2014 08:58 AM, Vivia Nikolaidou wrote:
> Hi all, and thanks a lot for your replies!
> 
> We did investigate the patents before deciding to start the project
> and they do indeed seem to be US-only. So, as long as Jolla isn't even
> available in the US, everything should be fine.
> 
> On the other hand, just to be on the safe side, we thought about
> leaving it in "beta-proof-of-concept" stage, or at least labelling it
> as such, and not promoting it (word of mouth should be enough to make
> it reach the devices of those who really want it). After all, patents
> only apply for things like sales and exporting, not for "academic
> purposes". If someone with access to a patent lawyer would like to
> investigate things and help it turn into a real project, this help
> would be more than welcome, but unfortunately we don't have such
> resources.
> 
> As for github/gitorious, we'll gladly share it when there's something
> worthwhile, but without being able to get actual raw data from a
> finger drawing a curve, there's not much coding that can be done. So
> we'd really appreciate it if someone could give us a hint. :)
> 
> Thanks again,
> 
> Vivia
> 
> On 15 April 2014 22:38,   wrote:
>> But how does it  work for the other swype like keyboards available for 
>> android?
>>
>> I can't see any differences to the original one.
>>
>> Am Tue Apr 15 2014 20:49:46 GMT+0200 (CEST) schrieb Michael Doube:
>>> On 15/04/14 19:39, Martin Kolman wrote:
> A quick look at the bottom of the Wikipedia entry for Swype confirms
> my suspicion... (2 US patents). :-(
 Well, they look like to be US patents - so considering the Jolla is not
 even sold in the USA & it would be an external application anyway, I
 don't really see any issue.
>>>
>>> Well, I wouldn't want the Jolla team to find themselves in hot water for
>>> distributing unlicensed functionality on the Harbour site. Nor the
>>> external application developer for implementing and publishing it, maybe
>>> even for a fee. Since Swype made a US patent, and their product is
>>> distributed worldwide, I would expect to find some European patents too
>>> (not being listed on Wikipedia is not authoritative evidence of
>>> non-existence). Anyway, this is non-expert handwaving. If there is a
>>> legal way to get something Swype-like on the Jolla, it would be great.
>>>
>>> Michael
>>>
>>> ___
>>> SailfishOS.org Devel mailing list
>>>
>>
>> --
>> Gesendet von meinem Jolla
>> ___
>> SailfishOS.org Devel mailing list
> ___
> SailfishOS.org Devel mailing list
> 


-- 
http://ruedigergad.com
___
SailfishOS.org Devel mailing list