The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
If your actions inspire others to dream more, learn more, do more and become more, you are a leader.-John Q. Adams You must accept one of two basic premises: Either we are alone in the universe, or we are not alone in the universe. And either way, the implications are staggering.-Wernher von Braun Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.-Albert Einstein
No, "The Pond" is always specifically the Atlantic Ocean.
The other side of our small but great island is either "The Channel" which is the English Channel between civilisation and the rest of Europe (mostly France in this case) and is called "THE channel as it is the only one that counts, all other "channels" have their own names and are referred to by them. Above The Channel is the North Sea which is referred to as bloody cold!
There are other bits of water here and there but we don't worry about naming them properly in normal conversations.
: I just noticed you put:
across the pong
...so you must have been referring to Belgium?
- I would love to change the world, but they won’t give me the source code.
It's a common phrase here, and reflects the fact that most government contracts are awarded to the lowest bidder, often by law. Anyone who has done source selection work knows that a RFP will result three price groups.
The providers who price at the high end have plenty of work, don't need the job, but if you're willing to pay extra, they'll take it.
The lowest priced group either didn't bother to read the specs and have no idea what the job really entails, read it and have no idea what all those long words mean, or understood it and intend to do the bare minimum required with no attention to quality and make up their profits from change orders that cost more than the original product.
The middle group read and understand exactly what is required, and will probably do an excellent job at a fair price. But they rarely get the job.
As a result, products built for the government are usually of shoddy quality, or grossly overpriced after the changes made to make them work as required are paid for. Hence, "good enough for government work."
If you have a Mac where you want to install your Development Environment, you have to watch a few things[^]
(Linux and Windows installers from the download page work out of the box).
Apart from that, be warned that tutorials for earlier versions may not reflect what is recommended to be done when using the latest 5.2.1 release.
Signals and Slots are a PITA at first, but after a while you get a pretty good hang on it. Always watch the console output of the debugger, if you made a typo while connecting them it will not be shown before runtime.
So, and if you got any more questions you can either ask me or someone at the Qt forums[^] - They're usually pretty quick with answering questions.
(Good reply Marco. And good luck with the book I think we need a good new book on Qt. )
If I may add my few cents to that:
C++ programmers know there are many ways and styles to use C++. Try to find out the Qt way of doing things. Its a good way, and it saves you a lot of time.
Make sure you understand the implicitly shared data types, and the smart pointers. They save you a lot of effort.
QML is definitely the way to go, IMO, not just for cross-platform.
For databinding to the UI (QML), I like QProperties, but there's a lot of ceremonial code required for them. You need to find a good snippet, macro, code-completion thingy in your IDE to take care of all the typing you have to do for them.
An alternative to QProperties, if you have dumb objects consider using QDeclartivePropertyMaps. They're a quick way of making simple objects that automatically bind to your QML.
I have some other tips in this blog post/[^].
It's a nice book, no doubt. But Qt is already at version 5.2.1, and I'm not sure if this book covers 'hot' topics as QML (for example) accurately.
Don't get me wrong, it's good for a starter but as soon as you want to support Android|iOS|WinRT that book won't probably help much. Qt is a cross-platform framework, and a GUI written with Qt technologies shall support all available platforms (IMHO, at least).
I will never again mention that Dalek Dave was the poster of the One Millionth Lounge Post, nor that it was complete drivel.