Qt 5 Blueprints

I've been working with C/C++ for a few years now, and with Qt for 1-2 years...mainly with Qt4 in embedded systems. I have a couple of the (very thorough) Qt4-based books that are available here on Amazon, and they are very good. In fact, they are almost TOO good from the standpoint that they nearly overwhelm you with information. But as reference material, they are extremely valuable. That being said however, when I saw that this book was dealing with Qt5 I wanted to go ahead and read it.I read both of the reviews posted previous to mine, before buying the book. Then I purchased the Kindle version of this book and worked through the first couple of chapters. I can definitely see the criticism(s) noted in Keith Peter's review. It's pretty apparent that this book did not have a good Technical Editor to go through it, because there are a number of simple errors that should NOT have made it through. For example in chapter 2, here's one such example:"...In other cases, we have to explicitly set the parent for a QObject child so that the parent can take over its ownership and manage the release of its memory. Hence, we pass the QObject parent, which is this, a MainWindow class to the constructor of QTimer."It's unfortunate that the author doesn't point out that the "this" pointer is a pointer to the instance of a class that is currently being referenced. In other words, "this" isn't a class...it's a pointer to an instance of a class.There are a number of similar such errors in the first two chapters, but overall the intent of the author is very good I think. But as I stated above, the book is in dire need of a good Technical Editor to go through and point this out to the author. I have served as a Technical Editor for a book on embedded systems, and it's not an easy task. It take many hours of work to go through a book such as this, but the result is well worth the effort.So overall I'll want to come back and revisit this review after finishing the book, but for now I would have to give it a 4-stars due to poor editing. I would have to agree with Keith on this point. I would also add that you really do need to have some C++ experience before working through this book, as that is assumed--and it would also be most helpful to know something about Qt (and Qt Creator) before reading this book. While it's not absolutely imperative that you have used Qt before, there are many times that the author chooses not to go into elaborate detail on a take he asks you to perform. If you are at least somewhat experienced with Qt Creator you will have little problem getting things accomplished--but you might struggle a little but if you've never used the IDE before. On the other hand it will make you dig more for the answer(s), so I suppose that's not all bad.

This book is useful and I'm enjoying going through it and learning from it. My only criticism is the poor English used in the writing. This book was obviously not written by a native speaker. I'm not picking on the author. But I'm shocked that any editor would let so much through without any correction. There are points in the book where I just sit back and say, "What is he talking about???" Not because it's a difficult technical point, but because I can't parse the words in the sentence. But again, the overall content of the book is great. With better editing, it would be 5+ stars.

good information.

On time. No problems.

This book describes how you can build a Qt5 application step by step. This approach is good for very beginners of Qt framework, but it misses information delivery for the future reference because it does not give any further information on the Qt framework general.

The book has too many mistakes. The grammar problems make the reading difficult. The organization of the material is haphazard. The clarity of the writing is questionable. Beyond all that, the accuracy of what is written is poor. In technical writing your one task is to get the facts correct above all else. The reason for this is that the assumption is the reader is attempting to learn the material without already knowing it. So regardless of the reason for the technical errors, being wrong makes the material worse than having no material at all because you now have information that will lead you in the wrong direction from your destination.I’m on page 23 and so far every page has serious mistakes. For example, I gave up when I read the following:“You may notice that I used the old-style syntax of the connect statement. This is because QML is dynamic and the C++ compiler can’t detect the existence of the signal in the QML file. Since things in QML are checked at runtime, it doesn’t make sense to use the old syntax here.”If you attempt to read this you’ll notice it is self-contradictory. If this was a one off mistake, fine, but this non-sense is everywhere. The problem is if you don’t know the material it is difficult to detect. In this case you can clearly see it even without knowing Qt. This makes the rest of the material highly suspect and possibly damaging to read if your goal is to learn something.The author should be paying you to proofread this material. It is truly some of the worst I have ever read.