Hi,
Styling is obviously important, but at long as it's only skin-deep (ie
the full range
and feel of components is not there), it's going to lead to frustration
on the long
run. The downside of drawing/making your components (whether by the Qt team
or 3rd party devs) is that you're reimplementing all the work the
platform and UI
teams of Google, Apple, Microsoft etc are doing, with the fraction of
resources.
That's why it's always a catch-up and a "kindasorta" native look and
feel (which
is the same problem all the native-mimicking web frameworks are having).
Attila
On 12/11/2014 5:24 AM, Jason H' wrote:
+1 this. I want info on the new flat style as well.
--
Sent from my Android phone with GMX Mail. Please excuse my brevity.
"Daniel França" <[email protected]> wrote:
The just launched Qt5.4 come with a "flat light" style for Qt
Quick Controls :D
It seems it'll help to achieve what I want, but I can't find any
documentation about those pre-defined styles.
Every time I search for something related I end up here:
http://doc.qt.io/qt-5/qtquick-controls-styles-qmlmodule.html
What seems a much more manual way of set your styles, how can I
easy give my controls this new "flat light" style? Or any other
pre-defined style?
Em Fri Dec 05 2014 at 11:41:50 PM, Attila Csipa <[email protected]
<mailto:[email protected]>> escreveu:
Food for thought - if you're not adhering to native
look'n'feel, your only
(melting) advantage to the various cross-platform
Web-frameworks is
performance. The classic benefit of cross-platform frameworks was
minimizing development efforts, and the web is (warning:
biased opinion
ahead) actually doing a better job at this than oldschool
native-language
frameworks. Without the desire to get into a web-vs-native
flamewar, the
strongest argument for a non-web cross-platform framework is
not that
it gets "close" to native app feel, but that you can't
distinguish native apps
from those written with the framework, and this includes look
and feel, too.
Best regards,
Attila
On 12/5/2014 2:00 PM, Nuno Santos wrote:
Hi,
In my opinion, the real power of QML is precisely the fact
that you don’t need to stick to the native iOS/Android
look and keep the exact same look and feel on both
platforms (obviously you will have some limitations but
depending on the kind of application you are developing,
they will be easily overpassed).
Regarding the components, with listview, repeaters, rows,
columns, grid, etc you will definitely be able to do
almost everything you need.
For more desktop like controls you have QtQuickControls
subset (some of them might also be useful for general
application development ex: StackView). For elastic
layouts you should investigate QtQuickLayouts
http://qt-project.org/doc/qt-5/qtquickcontrols-index.html
http://qt-project.org/doc/qt-5/qtquicklayouts-index.html
Creating custom components in QML is also a breeze.
I think that most important to retain is the paradigm
shift. Taking advantage of states, bindings, etc instead
of making changes in response to events “by hand”.
The most important steps is to do something. After a
couple of small applications you will be up and running in
not time.
QML Book is definitely a nice resource for learning. Qt
documentation as well!
Take this info into account as well:
http://qt-project.org/doc/qt-5/qtquick-performance.html
Regards,
Nuno Santos
On 05 Dec 2014, at 11:51, Daniel França
<[email protected]
<mailto:[email protected]>> wrote:
Hi all,
I started learning QML and would like to ask for some
directions.
My purpose is for mobile development, I've already
done a few projects using Qt/C++ for desktop, but I
didn't code anything for mobile.
The first thing I was trying to find is if there's
already some standard mobile components for qml, like
side menu, button bars, grids, etc.
Something that would make easier to have a mockup on
Fluid or something similar, and then implement it on QML.
Would be great to have components that'll look native
at IOS and Android, or at least something like a
"Bootstrap" for QML.
or if I should do implement this components myself.
I tried to search for a set of components like that
but couldn't find anything.
I'm reading this book btw: http://qmlbook.org/
Thanks for any help.
Regards,
Daniel França
_______________________________________________
Interest mailing list
[email protected] <mailto:[email protected]>
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing [email protected]
<mailto:[email protected]>http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
[email protected] <mailto:[email protected]>
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________ Interest mailing
list
[email protected]http://lists.qt-project.org/mailman/listinfo/interest
<http://lists.qt-project.org/mailman/listinfo/interest>
_______________________________________________
Interest mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/interest
