<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
everything possible, but widgets is the worst what can happen for
sailfish. get time to learn qml, its easy.<br>
<br>
<div class="moz-cite-prefix">On 27.01.2014 00:15, Gabriel Böhme
wrote:<br>
</div>
<blockquote cite="mid:-6147840355795446478@unknownmsgid" type="cite">
<div id="fenix-user-content">
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span
style="font-family:'NokiaPureTextLight'"> Hi Dietmar,</span></p>
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px;font-family:'NokiaPureTextLight'"><br>
</p>
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span
style="font-family:'NokiaPureTextLight'">I've started to
learn coding with Python/PyQt on N900 just before the N9 and
all the QML stuff started. That was a bit hard.</span></p>
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px;font-family:'NokiaPureTextLight'"><br>
</p>
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span
style="font-family:'NokiaPureTextLight'">I started to learn
also QML and fell in love - kind of. On one side it's so
easy and fast to creat stunning UI's and the other point -
it makes sense to split UI ane logic clearly. And if you are
doing so, it's easy to publish/port your application on
another platform. You just have to rewrite, your UI in QML -
and because it's so easy, it takes in the most cases just
some hours, or in difficult cases some days.</span></p>
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px;font-family:'NokiaPureTextLight'"><br>
</p>
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span
style="font-family:'NokiaPureTextLight'">But than you offer
the best UI experience everywhere, because it's writen
especially for the platform (for example Desktop, Tablet,
Smartphone)</span></p>
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px;font-family:'NokiaPureTextLight'"><br>
</p>
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span
style="font-family:'NokiaPureTextLight'">It's a bit a hard
situation to do the first step, but after all I think it's
worth it.</span></p>
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px;font-family:'NokiaPureTextLight'"><br>
</p>
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span
style="font-family:'NokiaPureTextLight'">But yes, it takes
time to learn QML and yes it takes time to write a
new/modify your application and no, it's not really possible
to offer with less to no changes a native look and feel. But
I could be wrong, I remember Thomas Perl was working on
something like that, to make it easier - don't know the
details.</span></p>
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px;font-family:'NokiaPureTextLight'"><br>
</p>
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span
style="font-family:'NokiaPureTextLight'">Cheers, Gabriel.</span></p>
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span
style="font-family:'NokiaPureTextLight'"> </span></p>
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span
style="font-family:'NokiaPureTextLight'">--</span></p>
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span
style="font-family:'NokiaPureTextLight'"> </span></p>
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span
style="font-family:'NokiaPureTextLight'">Von meinem Nokia N9
gesendet</span></p>
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span
style="font-family:'NokiaPureTextLight'"> </span></p>
</div>
<br>
<div id="fenix-reply-header">
<p>Marcin M. schrieb am 26.01.14 18:34:<br>
</p>
</div>
<div id="fenix-quoted-body">
<div dir="ltr">Just a thought - maybe using some legacy (i.e.
Fremantle) theme could be a fix. But I have no idea whether it
can be done and with how much effort.<br>
</div>
<div class="gmail_extra">
<br clear="all">
<div>
<div>
--</div>
Marcin<br>
</div>
<br>
<br>
<div class="gmail_quote">2014-01-26 <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:christopher.lamb@thurweb.ch"
target="_blank">christopher.lamb@thurweb.ch</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Dietmar<br>
<br>
Zitat von "Dietmar Schwertberger" <<a
moz-do-not-send="true"
href="mailto:maillist@schwertberger.de" target="_blank">maillist@schwertberger.de</a>>:
<div><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Switching to QML/Qt Quick seems a major effort and
especially, it is very un-pythonic to use this mixture
of two languages.<br>
</blockquote>
<br>
</div>
There is only one language here, QML, which is an
extension of javascript.<br>
Qt Quick is a set of components used by QML. This
component set is further extended by the Sailfish Silica
component set.<br>
<br>
I did not find QML itself that hard to learn, and there
are lots of examples and tutorials on the interweb.<br>
<br>
The mix of 2 languages comes when need to do some
heavy-lifting and have to fall back to C++. Having said
that C++ and QML are well integrated.<br>
<br>
Zitat von "Dietmar Schwertberger" <<a
moz-do-not-send="true"
href="mailto:maillist@schwertberger.de" target="_blank">maillist@schwertberger.de</a>>:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
...there's quite some effort to stay compatible over<br>
multiple platforms ....<br>
</blockquote>
<br>
You have hit the nail on the head. Multiplatform coding is
not easy, especially if you want to keep native
interaction, and look and feel. We know that Sailfish is
quite a bit different from any other platform.
Multi-platform is not impossible, but it does involve
compromises.<br>
<br>
I have been working for some while to port a Harmattan app
to Sailfish. For the most part I have got it working, but
not without some obstacles. Off the top of my head (and
without going into detail), here is a list of differences
I found between these 2 platforms<br>
<br>
1) Qt Version 4.7.4 --> 5.x<br>
<br>
2) QtQuick version 1.0 --> 2.0<br>
<br>
3) Mobility 1.2 --> Qt 5.0 equivalents<br>
<br>
4) Project Template Files C++ main function, Pro file<br>
<br>
5) Project structure<br>
<br>
6) Sailfish look and feel, user interaction<br>
<br>
7) Sailfish Specials: e.g Cover<br>
<br>
8) Missing QML Components / Extra Components,<br>
<br>
9) Component Property differences<br>
<br>
10) Library differences inc. Bugs<br>
<br>
11) Niggly Technical Stuff<br>
<br>
11.1) How a javascript file imports a second javascript
file<br>
<br>
11.2) Location of LocalStorage DB<br>
<br>
12) Harbour rules (somethings are technically possible,
but not allowed to be harbour compliant)<br>
<br>
13) etc ....<br>
<br>
Grüsse<br>
<br>
Chris
<div>
<div><br>
<br>
_______________________________________________<br>
SailfishOS.org Devel mailing list<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
_______________________________________________<br>
SailfishOS.org Devel mailing list<br>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SailfishOS.org Devel mailing list</pre>
</blockquote>
<br>
</body>
</html>