maemo.org - Talk - Sailfish SDK version 1608 (2.0.2) Qt5 released

maemo.org - Talk (https://talk.maemo.org/index.php)

- SailfishOS (https://talk.maemo.org/forumdisplay.php?f=52)

- - Sailfish SDK version 1608 (2.0.2) Qt5 released (https://talk.maemo.org/showthread.php?t=89294)

Re: Sailfish SDK Alpha released

am at uni, am at my programming class. may as well learn this :D

also a nexus 4 running sailfish, would that not be pretty awesome?

Re: Sailfish SDK Alpha released

Quote:

Originally Posted by cuongle (Post 1325320)

I think the main point is We can be mixed QtQuick and Silica components :D

Even if this works today, don't assume it will always be the case, and don't assume that it will work, and work without setting your device on fire.

There's code in both sets of components that conflicts (either theoretically or for sure).

Consider it an aid for transitioning code if you need to by all means, but _don't_ rely on it.

EDIT: I was assuming this meant "we can mix MeeGo and Silica components", which is probably somewhat possible, but don't do that. Mixing plain QML is encouraged and indeed how it's supposed to work :)

Re: Sailfish SDK Alpha released

Quote:

Originally Posted by javispedro (Post 1325206)

timed (straight from Harmattan, even including references to Aegis :D )

Not quite straight from Harmattan. A lot of work has gone into timed since then: https://github.com/nemomobile/timed/commits/master

As for Aegis... Pull requests to remove it probably welcome. :)

Re: Sailfish SDK Alpha released

Quote:

Originally Posted by jflatt (Post 1325089)

Still based on Qt 4

It is good to have Qt 4.8 :
- Qt 5.0 has no Python-PySide yet;
- Mer/Sailfish OS also has Python 2.7.3 and Python-PySide, enabling GUI softwares made with Python/Qt/QML;
- so lot of Maemo 5 / MeeGo Harmattan softwares developed in Python/Qt/QML can be ported very easily.

By the way, Mer/Sailfish OS already has Qt 5.0 ! Using the Sailfish OS emulator, it shows more than 160 Qt5 packages :

Code:

[root@SailfishEmul ~]# zypper se qt5 | wc

    166    1513   20447

Re: Sailfish SDK Alpha released

Quote:

Originally Posted by Hariainm (Post 1325223)

wondering what phone will be your next, any hint?

Probably this, as so far seems to be basically what was "promised".
It looks much more sane than Ubuntu Touch (aka Ubuntu Chroot for Android) or Firefox OS (aka Boot To Gecko From Android).

Re: Sailfish SDK Alpha released

How did you guys install pyside?
I somehow can't get internet connection in the emulator, eventough I can connect via ssh...

Re: Sailfish SDK Alpha released

Quote:

Originally Posted by Hurrian (Post 1325328)

Assuming the SDK's built like the Harmattan and Maemo ones, will we be getting an ARM target SDK? Y'know, for testing.

I see no Sailfish OS ARM rootstrap in Salfish SDK. The Mer-SDK and Sailfish Emulator images are i486. We can add "Mer-SB2-armv7hl" as Mer-SDK target, but it is not a Sailfish OS ARM rootstrap.

Re: Sailfish SDK Alpha released

It seems like Qt Creator can't see SailfishOS emulator running...
Somebody having a similar problem when trying to run a project? :confused:
http://dl.dropbox.com/u/23939497/sailfishsdk.png

Re: Sailfish SDK Alpha released

Quote:

Originally Posted by brunelli (Post 1325368)

It seems like Qt Creator can't see SailfishOS emulator running...
Somebody having a similar problem when trying to run a project? :confused:

Try ssh by hand:

Code:

ssh root@localhost -p 2223 -v -i ~/.ssh/mer-qt-creator-rsa

Re: Sailfish SDK Alpha released

Quote:

Originally Posted by murrayy (Post 1325370)

Try ssh by hand:

Code:

ssh root@localhost -p 2223 -v -i ~/.ssh/mer-qt-creator-rsa

Permission denied :(

Code:

ssh root@localhost -p 2223 -v -i ~/.ssh/mer-qt-creator-rsa

OpenSSH_6.1p1, OpenSSL 1.0.1c-fips 10 May 2012

debug1: Reading configuration data /etc/ssh/ssh_config

debug1: /etc/ssh/ssh_config line 50: Applying options for *

debug1: Connecting to localhost [127.0.0.1] port 2223.

debug1: Connection established.

debug1: identity file /home/ian/.ssh/mer-qt-creator-rsa type 1

debug1: identity file /home/ian/.ssh/mer-qt-creator-rsa-cert type -1

debug1: Remote protocol version 2.0, remote software version OpenSSH_5.6

debug1: match: OpenSSH_5.6 pat OpenSSH_5*

debug1: Enabling compatibility mode for protocol 2.0

debug1: Local version string SSH-2.0-OpenSSH_6.1

debug1: SSH2_MSG_KEXINIT sent

debug1: SSH2_MSG_KEXINIT received

debug1: kex: server->client aes128-ctr hmac-md5 none

debug1: kex: client->server aes128-ctr hmac-md5 none

debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent

debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP

debug1: SSH2_MSG_KEX_DH_GEX_INIT sent

debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY

debug1: Server host key: RSA 4a:96:c8:bb:75:f6:68:64:b6:0c:c1:8a:49:e5:d0:b4

debug1: checking without port identifier

The authenticity of host '[localhost]:2223 ([127.0.0.1]:2223)' can't be established.

RSA key fingerprint is 4a:96:c8:bb:75:f6:68:64:b6:0c:c1:8a:49:e5:d0:b4.

Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added '[localhost]:2223' (RSA) to the list of known hosts.

debug1: ssh_rsa_verify: signature correct

debug1: SSH2_MSG_NEWKEYS sent

debug1: expecting SSH2_MSG_NEWKEYS

debug1: SSH2_MSG_NEWKEYS received

debug1: Roaming not allowed by server

debug1: SSH2_MSG_SERVICE_REQUEST sent

debug1: SSH2_MSG_SERVICE_ACCEPT received

debug1: Authentications that can continue: publickey

debug1: Next authentication method: publickey

debug1: Offering RSA public key: /home/ian/.ssh/mer-qt-creator-rsa

debug1: Authentications that can continue: publickey

debug1: No more authentication methods to try.

Permission denied (publickey).