i don't know if you've had a lot of nested tasks, but i'm looking forward to a nice clean, left-justified workflow

something like login wait() auditLogin() wait() instead of Task { login succeed

Task { auditLogin{

succeed

.... etc

yeah, I use lambda and task queues for backend work so it makes more sense to me with the channels & actors

do task, put result in queue, queue manager launches another lambda, puts result in queue

mostly for me though it’s processing lots of data, I think it coroutines it’s called “fan-out”

i'd go with the plain iteration because you'll be able to cancel the endpoint checks by looking at the isCancelled flag in between

yeah, but I don’t want to cancel them 😛 I want them to run or fail and update the UI with the result

but yeah, anything that’s async has about 100 ways to do it

hey, while you’re here, do you know how to remove a style if I set one? like backgroundColor += c(“yellow”)

now I want it to go back to normal… backgroundColor.clear() … ?

maybe setup a new style "ClearStyle" and then toggle the class?

or just skip the style and toggle the style off ex, left = region { addClass( MyStyles.style1 ) toggleClass( MyStyles.style1, false )

}

good idea

works even better because the criteria is a boolean -> highlightRow false/true

strangely now I get a yellow border around the object, instead of a yellow highlight

fixed, thanks for the help

np

I have a dynamically generated list of an object

I think I make it something like FXCOllections.observable() and add something like PersonModel s to it

where do I save it?

in the View, Controller or Model?

need to access it in a View and calculate it in a Controller (I think)

@wineluis I would prefer a Model inside a Controller over saving it in the View if I had to choose, but I think an injectable ViewModel might be even better.

It's a matter of preference, really. A

PersonController

with a

persons

list is fine as well IMO.

@wineluis @edvin The difference will depend on your software architecture. If you're doing MVC, then the Controller. That means that there is a View layer, some model components, and everything else is brokered in the Controller. If you're doing MVVM, you'll have a ViewModel, but IMO you'll want to pull in the Event Bus to keep the object relationships unidirectional.

@carlw Good point 🙂