Going to add Digest Authentication to the Rest Client.

@edvin It's working 😉 thanks again, this is much cleaner then my approach 😉

@nimakro I knew that thing would come in handy :))

@edvin Just realized that a

item

in the

listmenu

dost't have an

action

like the other

controls

, so I have to use the

activeProperty

to dock a new Views? Would this be the preferred way of doing it? Or would it make sense to add an action callback which will be called every time the item is active?

@nimakro

whenSelected {}

@edvin 🙈Wonder why I didn't see that one 😉

hehe

@nimakro I was wondering if we should make a companion node for the listmenu that would automatically take care of docking based on the Tag in the ListMenuItem.

@nimakro Hehe.. It's actually not an extension function like all the rest, since this is a TornadoFX "native" component. Maybe that's why it was harder to spot.

This looks crazy, but hopefully i does what I want it to:

@User uploaded a file: Parse Digest Auth WWW-Authenticate header

@edvin Well I was checking the code but I guess not carer full enough 😉

@edvin Regarding the companion node, not sure if I am fully understanding it right? So do you mean we could then set a View or Fragment in the

item

like

item("someitem") { onDock = SomeView::class }

which would be automatically docked when selected?

I'm thinking that the ListMenu can be told that whenever a ListMenuItem that represents a View is activated, it will be docked in that other component.

You would then just do

add(MyFirstView::class)

etc inside of the ListMenu, and that would be it.

Oh, and do

listmenu.dockTarget = someOtherNode

perhaps.

@edvin So instead of adding

items

you could just add

Views

which represent the

items

?

@edvin This is how I am doing it now 😉

@nimakro Yes, same way you can do for Tab now.

I'm getting this on a form. I thought i already had a bi-directional binding

The addValidator extension on TextInputControl can only be used on inputs that are already bound bidirectionally to a property in a Viewmodel

form { fieldset { field("URL") { textfield(vm.urlProperty()).required() }

Here's the fieldset

and here's the viewmodel property

class ConnectViewModel(url : String? = null, user : String? = null, password : String? = null, connected : Boolean = false) : ViewModel() { var url by property(url) fun urlProperty() = getProperty(ConnectViewModel::url)

@nimakro That's perfect, just docking on select. I didn't think about that you were in a Workspace. Of course you don't need the companion thing I was talking about 🙂

@carlw Validators are only available for properties bound in a ViewModel. This might be an unintuitive constraint, maybe I can change that. Will check if it's possible soon.

what would a bound property look like in the viewmodel?

Initially, I didn't intend for the ViewModel to be used without being a proxy for an actual underlying domain object.