I respectively disagree. While the book you describe is indeed useful, the book I want when learning JavaFX shows me how to use JavaFX. The book you describe is a big picture book and many portions have nothing to do with JavaFX in particular, but have to do with software engineering and architecture. These, of course, are important but belong in a different book.
For example, in designing an online store you must decide on your persistence strategy. Will you use Hibernate, jdbc/database, ejb? Any /all of these strategies can be used with JavaFX, your front end.
If you include "learning JavaFX" with these topics, your book will be 1,000 pages. (I personally don't like 1,000-page books.)
I don't know about you, but when I'm learning a new language, I appreciate the work the author has done to build the examples and explain the language features used. A previous poster said, "I can learn everything about the language using Google and scouring the internet." Maybe. But it will take you 3-4 times as long.
For example. Let's say you want to write a game in JavaFX. You will need animation. Looking up the APIs you see that JavaFX implements animation with the Timeline class. Oh, and there's also Transitions: TranslateTransition, ScaleTransition, RotateTransition, FadeTransition, PathTransition, PauseTransition. There's compound transitions too: ParallelTransition and SequentialTransition. Okay, time to study these APIs.
In our chapter on Animation, we talk about all of this. And it turns out that you use Timeline for periodic updates, the kind you would use in a game situation (have I collided with something yet?).
When writing a book, the Table of Contents is a collaborative effort with the acquisitions editor, the authors, other technical parties, perhaps engineers involved with the topic. Our goal was targeting programmers who want to learn JavaFX. We don't assume Java or Swing experience. (Indeed I have found that people without extensive Java knowledge accept the JavaFX programming paradigm more rapidly. Some Java programmers find the scene graph metaphor
One final point. Not every piece of software is an elaborate system. Some are "just widgets." One of our examples shows a flickr-based slideshow (an animated carousel). It uses JavaFX support for web services and pull parsers (to parse either XML or JSON). This is not a large example (thanks to JavaFX) but it is hugely useful (and fun). You can embed it in a web page and show your own (or others') flickr photographs.
In summary, the book you describe is very useful. But, that's not the book I would want to learn JavaFX. Just my opinion.