On 1/7/2019 11:49 AM, Jason H wrote:
Similar to QtQuartely (anyone remember that?)
Ah yes...QtQuarterly.
So that's my idea. I'd expect it implemented as a section before "Detailed Description"
as "Relevant Articles" which is a link of the title to the content (contained in Qt, not
online, because we change domains too often).
Thoughts?
That section needs to include links to the relevant examples (ones which
actually compile and run, not snippets) and tutorials. A REAL example,
not App that ate Manhattan example. When a noob goes to the doc for
worthless QML and wants a Page example, don't point them here:
https://doc.qt.io/qt-5.11/qtquickcontrols2-gallery-example.html
True, what they want to know "may" be in there, but they will never find
it. If they do manage to find it they will never figure out how to use
just it because there is so much else in there.
If you are going to flesh it out completely and attempt to justify the
50,000 pound resource hog which is QML feasting on the battery until it
is gone, the __limited and simple__ examples for C++ class core types
should be progressive.
1) Console app manipulating them and dumping out with both stdout and
qDebug.
2) Single item C++ GUI app with just the object itself going back and forth.
3) Another Single item C++ GUI app back and forth along with any
associated validators.
4) A C++ backend sending that object via signal to a QML front end . . .
possibly bundling bi-directional signalling of the same C++ object.
5) A C++ backend using properties for the object values and QML
manipulating them.
By core stuff I'm thinking of QString, QDateTime, etc. Objects used to
store and manipulate fundamental values.
The Widget based stuff should, of course, have a slightly shorter list
of very simple examples.
1) Single item C++ GUI app showing how to display the widget, populate
the widget and retrieve the widget value.
2) QML application mirroring the C++ GUI application with a back end
populating and retrieving the value.
There I'm thinking along the lines of a QTextArea with scroll bars and
the other more basic widgets. Admittedly it gets harder with the more
complex widgets and physically impossible when QML doesn't have an
equivalence or vice versa, but that level of information is currently
missing from the doc. It may be somewhere, but it is not on the class
doc page. The end result of this is you have people starting out with
QML because it is touted as new and trendy. Then they hack in some
javascript. Finally, they hit a wall where what they wish to do cannot
readily be done in QML or javascript and they create a train wreck where
just a little bit of logic is in a C++ backend and the rest is scattered
in various QML source files.
In an effort to reduce the number of examples the example programs have
ballooned in size to the point of being expert friendly. Just to learn
how to use one thing you sometimes have to search through dozens of files.
--
Roland Hughes, President
Logikal Solutions
(630)-205-1593 (cell)
http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.johnsmith-book.com
_______________________________________________
Interest mailing list
[email protected]
https://lists.qt-project.org/listinfo/interest
