oh.. actually, this could be my opportunity to try out klaxon

@amanda.hinchman-dominguez No, you don't need to. If you have an array, that's totally fine. As I told you, you can turn that into an observable list of your domain objects with a single

toModel()

, provided that your domain objects support JsonModel and that you have overridden

updateModel

. Involving klaxon is just extra weight and no benefit, infact you won't be able to leverage the rest support in TornadoFX if you do that. I feel like you don't have a full grasp of how the JSON support in TornadoFX is working, but if you want to go the klaxon route first I can show you how to convert that to the built in support later if you want.

@edvin I definitely don't. I read through the documentation but most of it was just an example on constructing the model. If I can just do that, I'll try that first. If it doesn't work out I'll try Klaxon

😕

@poohbar We didn't reinvent the wheel, we depend upon javax.json

that's an API, not an implementation..

@poohbar That's the only thing needed, it uses that API and expects an implementation to be on the classpath. There happens to be one by default though, the reference implementation 🙂

anyone know how I can get an instance of my view

I need to pass it to soemthing else in the system

the normal find() call should work since the View is a singleton if you're not using scopes. you'll get that instance back

Also how do I launch the fx application and not block main thread

Because if I launch it in a side thread it never shows up

@edvin I ended up using your

.toModel

method - no need for klaxon. It freaks me out how lightweight TornadoFX can be

in a good way, of course

@amanda.hinchman-dominguez haha 🙂 Sweet!

excited! Now I have it in models, I have to refactor the codes and classes. Once I get those json models to generate the grids, I'll make a change on the open-source version as well

And can observable values be chained like that in the first place?

Ah, should be fitWidthProperty.

@hestad to answer your questions, can you briefly describe what it is that you're trying to do from an end user's perspective?

are you trying to resize them as you change the size of the primarystage/view?

Anyone know how to make the wizard display stuff depending on the option on the first page?

@jkbbwr You can inject a model object that you can bind to and observe in different wizard pages

@amanda.hinchman-dominguez From a users perspective, the primarystage should support different sized screens and resizing as you mention. The images (with the drawings) should resize together with the primarystage/view, yes.

@hestad Are you using

replaceWith()

to switch between the views? You can override

onDock()

in those views and do

currentStage?.sizeToScene()

.

@edvin that sounds complicated

@jkbbwr It's not, it's actually incredibly simple. You have a viewmodel that describe your state, inject that into the wizard pages and show/hide components based on that state. It can't get much simpler than that.

(I don't do ui usually)

@edvin I only have one view.

@jkbbwr I have to agree with edvin, replaceWith is really easy and simple to sue

@hestad so the issue you're having is that your

imageview

does not resize? or resize programmatically?