Re: [SailfishDevel] Developing with SailfishOS - a short introduction
Hi all, just a little update. A downloadable pdf version can now be found at http://hardcodes.de/SailfishOS/Developing-with-SailfishOS.pdf. It is still far from complete but grows :-) I went from thinking about moving to another markup language to I will move. But I am still thinking about which one?. If you ask for a gut reaction, I would answer MultiMarkDown. Still not sure... Have a nice weekend! BR. Sven ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Sharing version number (and other constants?) between .yaml/spec, .pro and .cpp/.qml
Hi, I've used something like VERSION = 0.1.0 HC_GITHASH = $$system(git show HEAD|grep ^commit|cut -c 8-) # c style DEFINEs to access the git hash and program version DEFINES += HC_PROGRAMVERSION=\\\$$VERSION\\\ DEFINES += HC_GITHASH=\\\$$HC_GITHASH\\\ in the .PRO file. This provides access in the .PRO file itself and in any .h or .cpp file. From there should be a way to .qml (via Q_PROPERTY). Not sure about the .yaml file. BR. Sven On 07.12.2013, at 00:26, Artem Marchenko artem.marche...@gmail.com wrote: P.S. Oh well, super ideal version would pull tag from git into both .pro and .yaml, but I guess that is impossible without the custom scripts. On Sat, Dec 7, 2013 at 1:25 AM, Artem Marchenko artem.marche...@gmail.com wrote: Just what I was looking for. Thanks, Robin! Cheers, Artem. On Sat, Dec 7, 2013 at 12:50 AM, Robin Burchell robin.burch...@jolla.com wrote: https://github.com/nemomobile/mlite/blob/master/rpm/mlite-qt5.yaml#L20 gives you https://github.com/nemomobile/mlite/blob/master/rpm/mlite-qt5.spec#L60 if you want to go all out gung-ho with automation, you can also do something like https://github.com/nemomobile/mlite/blob/master/src/src.pro#L3 in your project file for local builds. On 06 Dec 2013, at 23:45, Artem Marchenko artem.marche...@gmail.com wrote: Hi All Does anybody know a way to share constants between .yaml and any other project file (preferably .pro, but any other way would do as well)? I sort of got tired to duplicate version numbers in .yaml and app's about dialog :) Writing app description in one place only would've been good too. Best regards, Artem. -- Artem Marchenko http://agilesoftwaredevelopment.com http://twitter.com/AgileArtem ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list -- Artem Marchenko http://agilesoftwaredevelopment.com http://twitter.com/AgileArtem -- Artem Marchenko http://agilesoftwaredevelopment.com http://twitter.com/AgileArtem ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Developing with SailfishOS - a short introduction
W dniu 07.12.2013 11:13, Putze Sven pisze: Hi all, just a little update. A downloadable pdf version can now be found at http://hardcodes.de/SailfishOS/Developing-with-SailfishOS.pdf. It is still far from complete but grows :-) I went from thinking about moving to another markup language to I will move. But I am still thinking about which one?. If you ask for a gut reaction, I would answer MultiMarkDown. Still not sure... Have a nice weekend! How did I miss your first post in this thread? Great idea of creating such document - things like that are really needed to attract new developers. Regards, Filip PS. Thanks for mentioning SmartDevCon ;) ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Serious request: please let us use C++!
Thanks for elaborating! :)
Btw. will this payback always in QML (so let's assume Fremantle Qt 4.7.4)
or only on Sailfish?
--
Marcin
2013/12/7 Thomas Perl th.p...@gmail.com
On 06 Dec 2013, at 17:46, Marcin M. marmistrz...@gmail.com wrote:
2013/12/6 Wim de Vries wsvr...@xs4all.nl
On 12/05/2013 06:41 PM, Marcin M. wrote:
A style for plain Qt which would display with the native look feel
(compare the unsupported and buggy meegotouch-qt-style) would be great too!
Do you mean QML or QWidgets lookfeel?
I mean: use plain Qt, get Silica lookfeel. Just like on Fremantle: you
use Qt, but get the gtk theme look feel.
(walls of text here again; tl;dr: try QML, you’ll like it, it is better
[easier to write + faster to render] than QWidgets for implementing UIs)
No, that won’t be possible, and even if someone were to try and replicate
it (with much time and dedication, one can “fake” enough of it to look
almost like Sailfish Silica, I’m sure), you wouldn’t achieve the same
visual quality (note how the pattern of e.g. buttons and switches is not
tied to the button and switch, but rather “lights up” the background when
you scroll? cannot see that in screenshots, but only when you try it in the
emulator / on the device) and performance (QML2 with the Qt Scene Graph can
utilize the GPU quite well, and from what I’ve seen with Qt 5.2, this is
only getting better).
QML is actually quite nice for defining how the UI looks. See it as (in
QWidgets terms) “more powerful versions of .ui files”. And don’t see it as
“now I have to code my app in JavaScript”, that’s not the case - you can
use as much or as little JavaScript as you want, and do the important stuff
in C++.
Granted, most of the time you actually have to use JavaScript expressions
to set some property values, but the expressions look syntactically not
much different from their C++ counterparts, and you get the property
binding (automatic recalculation + update when a value the expression
depends on) for free. And that’s also the reason why (short from moc-style
pre-processing and custom language extensions on the C++ side) there is an
actual need for dynamic languages like JavaScript in QML - you can’t do
property bindings in “pure” C++ code, as the AST of the expression is lost
after compile time.
Yes, it requires you to learn something new, and yes, it’s hard in the
beginning (it was for me) until you start realizing that you’re not
modifying the UI tree from your C++ code anymore, but rather, you access
the C++ code/state from your UI. The C++ code only needs to expose the
state / content / database in a nice way (Qt models, invokables,
properties, signals and slots, etc..) and then you can access these from
the UI whenever you want.
And if you get the properties on your C++ objects right, with
notifications and all, you never have to worry when (for example) to set
your button to enabled / disabled manually (mybutton.setEnabled(true),
etc..), because you only define e.g. on the C++ side a property that tells
you if you’re currently processing something or not (say a boolean property
“processing”) and then on the QML side, you can easily say “Button {
enabled: !myobject.processing }” and the button enabled state will always
be right, and will be recalculated accordingly when the processing
property’s value changes. This provides a nice way to split your backend
from the UI and not worry about keeping your UI state in sync. You can even
use that property in multiple places in the UI or not at all - the C++ side
doesn’t change, which is nice (so you can e.g. have the same C++ backend
for different QML UIs - one for phone, one for tablet, one for desktop,
etc..)
If that little JavaScript running there every time something changes
sounds like too much overhead for you, think of it this way: The amount of
CPU “wasted” by running JS in the QML case is saved (and paid back multiple
times) by offloading big parts (not all) of the rendering from the CPU to
the GPU.
HTH :)
Thomas
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] Developing with SailfishOS - a short introduction
Great work! A troubleshooting section with known issues could be great to have as well! Best, tortoisedoc On Sun, Dec 1, 2013 at 10:27 PM, christopher.l...@thurweb.ch wrote: Hi Sven Have now downloaded. Lots of good content, but I need to read through it a few more times to comment in detail. One thing that immediately occurs to me is: 2.3 Linux While it is not supported, an instalation of Sailfish within a Linux VM hosted on OSX works quite happily. It is some months since I did it (first sDK version), but I was able to install Lubuntu on VMWare Fusion hosted by OSX, and then install VirtualBox and the Sailfish SDK into that. The only problems I had could be replicated on a bare-metal install of Lubuntu. mfg Chris Zitat von Sven Putze sailfish...@hardcodes.de: Hi there, first of all: this is far from complete and basically just a skeleton yet. Nevertheless I have started to write down a howto for SailfishOS development. Criticism, suggestions, bugfixes, contribution wanted! https://github.com/hardcodes/developwithsailfishos BR. Sven ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
[SailfishDevel] Harbour should allow libcrypt/openssl
I think harbour store should allow libcrypt/openssl because AFAIK that API will not change very often and is probadly already used in sailfishos? I guess there is some apps that want to use AES/MD5/SHA256 and so on. Passwordwallet apps and similar Regards Mikael ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Harbour should allow libcrypt/openssl
That's a good point, just today I was wondering if it's possible for apps to use this library. Il 07/dic/2013 20:38 Mikael Hermansson m...@7b4.se ha scritto: I think harbour store should allow libcrypt/openssl because AFAIK that API will not change very often and is probadly already used in sailfishos? I guess there is some apps that want to use AES/MD5/SHA256 and so on. Passwordwallet apps and similar Regards Mikael ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Developing with SailfishOS - a short introduction
Thanks! There is already a troubleshooting section but of course only with those problems that occurred to me so far. I guess some quirks will certainly follow. If you know something worth mentioning, I will be happy to integrate any clean text delivery if you don't want to latex around ;-) Nevertheless it's still very much work in progress. BR. Sven Great work! A troubleshooting section with known issues could be great to have as well! Best, tortoisedoc ___ SailfishOS.org Devel mailing list
