@User uploaded a file:

Reading up on

Chapter 11 - ViewModel and Validation

. Perhaps we should present the

ItemViewModel

first and may even move

ViewModel

to the appendix?

Let me study it a bit longer. It might help explain how the underlying stuff works.

Okay, this might actually be good as is. Good job with this, I'm going to try and push these to be used at work a bit more.

@thomasnield I thought about that actually. You don't really need to know what's going on under the hood, and we might loose a few readers along the way there, but I think this way it shows the natural progression into the Item`ViewModel`. It might be good to add some hints in there so the reader understands that we will introduce something sexier later in the chapter.

Agreed, I'll read through it again but I think the structure is not really going to change. It somehow feels necessary the way it is.

Some concepts are more tricky to introduce I guess. I will read through it one more time when I'm done with the scopes and see if I can perhaps shave off some of it.

@edvin just don't leave out anything that might be of value. I wouldn't fret too much about it. Worry about the scopes for now. That's critical.

@thomasnield Good advice. OK, I won't touch it for now 🙂

discussion going on over at reddit... https://www.reddit.com/r/java/comments/5hcunn/is_javafx_not_really_dead

@jchildress nice to see TornadoFX got brought up in the discussion!

The fact people talk about JavaFX still...

That's got to mean something.

@thomasnield I know... I hate to "argue" with people about it.. but for some applications I just wouldn't want to use a web app everyday... 🙂

@jchildress Me as well. I remember hearing the number of JavaFX users is not known, but by the download numbers for Gluon's SceneBuilder it sounds pretty high. It's used behind corporate firewalls hence why it's adoption is not exactly clear.

Personally, I would never use JavaScript for the projects I'm doing right now. That would be hell.

Yes.. I'm not allowed to show our stuff... That we have built.... nothing ground breaking, but very functional and fast for our needs..

I think Java in general and JavaFX in particular is used a lot in enterprise software that is never mentioned publicly, and mostly used internally in an organization. There are a lot less script kiddies making "software" in large companies. Enterprise developers aren't always hip bloggers or even allowed to talk about their projects, as @jchildress mentioned. I don't worry about the perceived popularity of JavaFX anymore - as long as it's the best tool for the job I'll use it every time. I had to laugh when a guy in that forum thread said that the tooling and software around JavaScript can't be beat.. He probably never tried Java/Kotlin in IDEA and probably never refactored any code in his life apart from copy/paste 😜

@edvin @jchildress haha I definitely fall into that category. Airlines do not like to share what they do internally because of the competitive nature of the industry.

@edvin I've learned over the past 6 years or so it is important to explore and be aware of what technologies are out there, even ones you think you don't like.

Speaking of, we are almost done moving our entire pricing software suite into tornadofx, rxjava, and kotlin. The difference from our Java code base is significant. I have to say it @edvin you have become just as much of a team member to us at work. We would never have achieved this kind of success without you, and we've just gotten started.

@thomasnield Thank you for saying that. It means a lot to me. One of the best things about writing this framework has been helping people with real problems, in fact, a majority of the features we've added have come as a direct requirement or a question from someone in this channel or on GitHub. I think this has helped to keep TornadoFX lean as well. Even though development has slowed a little, I feel that's a good thing - we have a stable framework that doesn't need a constant flow of new features anymore. Of course there is a lot more we can do, and I can't wait to push TornadoFX further together with you guys!

Working through an issue with the Rest client... not sure if it's something I have done wrong... Just posting this while I double check my code. When I do a post the content type is set as "text/plain"... i'm looking for it to send over "application/json"

@jchildress Are you using the default client (based on HttpURLConnection) or the Apache HttpClient version? Also, are you posting the content as a

JsonModel

or a

JsonObject

?

apache... i think that is the problem

just changed

on sec

I think you might be right, it seems the

HttpClientEngine

doesn't add the header by default.

JsonModel

got it