yeah that could work

You can still inject that viewmodel into each of the two views.

I am now wondering why you reacted with weird, the use case (add or update) is not that strange

Using the same form.. that's weird to me 🙂 Also, in real world applications, the input to create is often a subset of or at least different than the properties you can edit on an existing object. Granted, in some cases they are the same. I still think it would be better to either pop up a new window for add, or.. if you want the quick-add always visible, go to a new page or a popup to edit existing items. You could still use the same editor if you want to, just use a different scope for example.

That would also let you always set the correct item into the viewmodel - an existing if editing or a blank/new if creating a new item.

@ron I just thought of a cop out for your situation. If you want to bind both selection and form to the same model, your add/clear button could just add a new item to the list at once and then select that 🙂

and then press the clear button 3 times?

One time to add a new entry?

I have to think about this

@ron I will play a little with it tomorrow as well, might try to make this the basis of a screencast to talk more about properties and viewmodels

Important reminder that you should never instantiate UIComponents manually: https://github.com/edvin/tornadofx/issues/584

@edvin the only way to dock 2 views in a workspace is to make an hbox or vbox?

@ron Not sure I understand what you mean. Plenty of layout containers can be used to dock 2 views.

@ron uploaded a file: Untitled

I know there are several layout containers, so I need to use one if I want to have 2 views next to eachother, answer enough

@ron A better way to do that would be to override WorkspaceApp instead and supply EntryForm as a parameter, btw.

@ron You can also dock stuff in the left, right or bottom area of the workspace. Depends on your use case 🙂

I want this view

@ron uploaded a file:

(yes the measurements are dangerously high I know)

If this inside a workspace it would make the most sense to dock a view that adds those two views to an hbox or splitpane, yes 🙂

that is what I though

the workspaceapp is basically the the App and workspace rolled in one?

Yes, just a convenience 🙂

you have disableRefresh, but not hideRefresh etc?

also disableNavigate does not seem to be callable from a view

@ron You can do

refreshButton.hide()

I think

@ron You can do

workspace.disableNavigation()

?

you have to do the

workspace.refreshbutton

when using the WorkspaceApp class

@ron Yes, you should do it in

init

of your custom workspace for example.