Android Controls are pretty far behind Silica when it comes to OS
integrated appearance for obvious reasons right now but a look at
staging on qt-project's jira will show you that most of those issues
should be resolved by the next minor release.
On 5/26/2014 11:08 PM, mikete...@gmail.com wrote:
Thanks to all for the inputs! :)
On Mon, 26 May 2014 14:17:40 +0200
Martin Windolph <mar...@yoktobit.de> wrote:
Hi,
my way was the opposite. I had an app for Windows and then went for Android. As
Sailfish OS came out, I ported it to Sailfish OS. The porting afford to
Sailfish OS was a lot higher than for Android. So you are fine when using basic
QtQuick 2.0 there without any Silica (I use separate pro files for
Windows/Android and Sailfish OS).
BR
Martin
Date: Mon, 26 May 2014 14:07:34 +0200
From: mikete...@gmail.com
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] porting QML app to non sailfishos archs
Hi in short time I'm going to 'port' my pure QML application to android and ios.
Currently I import QtQuick 2.0 and QtQuick.LocalStorage 2.0
(and Sailfish.Silica 1.0)
I use LocalStorage and XMLHttpRequest, I try to keep it simple, I'm using only
Rectangle, Row, Text, TextInput, MouseArea, few anchors.
In short, nothing specific to Silica.
Do you think that I'll be fine with this ?
Do you have some experience to share ?
Is QML on android and ios stable ?
Thanks for your attention,
wish you a great week,
Mike
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
