Committed.

@edvin what did you think about the indirection i used for the ViewModel / Command -> Model modifications? I have the ViewModel listening entirely for Model events. I'm not updating the ViewModel en route to the Model.

i noticed in the larger app that I'm working on that there is a maintenance problem when the initiator gets a special status. For example, let's say you update the VM, setting a bound property, then issuing an optimistic call to the model. That works, but you also have to code the case where the VM listens to a model event that someone else generates

if you handle all Model -> VM updates through the event bus, your VM responds identically regardless of where the update came from

@User uploaded a file: Possible problem with IDEA plugin? and commented: Discover something new every day -- slack code snippet , who knew?

Anyway... that code doesn't compile. Kotlin wants a regular reference to item.bar.

SimpleBooleanProperty(item.bar)

@carlw I will take a look when I'm back home, at Jiu Jitsu practice with Alyssa.

@kastork

if (item == null) SimpleBooleanProperty() else SimpleBooleanProperty(item!!.bar)

Alternatively

SimpleBooleanProperty(item?.bar ?: false)

@kastork I fixed the faulty code generation in the plugin yesterday, will release a new version soon.

Consider this command binding:

@User uploaded a file: Untitled

I would like to make a function so you can set the command and the property at once, for example:

@User uploaded a file: Untitled

What would be a good name for

command

in the above example?

I don't want to reuse command, since there is a function called

command

that is globally available. It would cause confusion.

Some possible verbs would be

bind

or

assign

perhaps. Or change the syntax, so you'd do:

@User uploaded a file: Untitled

Doesn't feel right.

@Ruckus Any suggestions?

@edvin what about this? button("Say Hello") { command = helloCommand commandParameter = myvar }

button("Say Hello") {
   command = helloCommand {
     param=myvar
  }
}

?

@edvin Too bad Kotlin doesn't support multiple receivers, or you could do something like

button("Say Hello") { ctrl.helloCommand with nameProperty }

As it is,

bind

is used elsewhere for properties, but in a different way that could be confusing. You could go more specific with something like

assignCommand(ctrl.helloCommand, nameProperty)

, but that's longer to type.

I'm not a fan of the alternative syntax (the

this

inside looks weird to me)

@carlw That syntax is exactly what we support now.

@kastork @Ruckus Thanks guys, this gave me some ideas.

So I'm thinking:

@User uploaded a file: Untitled

I just need to create a little subclass of Command called CommandReferenceWithParameter or something to make that happen 🙂

I think that would be pretty intuitive.