That way you can manipulate the data and not need to keep references to the fragments

you mean pass a property and bind to a property in with the params object?

For example

Ideally something like find<Address>(mailingStreetProperty)

Untitled.kt

What about find<Address>(viewModel.mailingStreetProperty)

guice has something like this with Assisted Inject

I don't think we have a nice way of detecting what parameter this should bind to in Kotlin

But you could add a nice companion function in AddressFragment though

this generates factories for dependencies

with your snippet, no binding is involved at all right?

Or something lazy:"

-.kt

I used to love magic stuff like that Guice thing, but now I find it too vague and also just too much boiler plate to set up

But the magic might allow you to do something like this textfield(viewModel.name) textfield(viewModel.phone) find<AddressFragment>(viewModel.street1, viewModel.city, viewModel.state) ...

Could find() be smart enough to take an AddressFragment with a constructor?

It actually could, but I think it would confuse people into thinking they can just instantiate fragments by themselves. The find method could make sure the lifecycle bits happen, but that wouldn't happen if you instantiate manually, so I think it's a bad idea. It's quite easy to add a companion object to your editor though, or just a lazy builder like I made above.

take a look at #769, there's that confusion today with no-arg constructors

it looks like you're making the factory functions i wrote about with guice on line 14

Maybe we could make it even easier to make these functions then 🙂

@edvin What do you think of this Fragment usage for the users?

not really an issue for Views since they're singleton and can bind to specific known model elements

and some fragments can be specific too like "MenuFragment", "ContentFragment", and "StatusFragment"

^ those can bind to specific elements too although they would best be singleton so that no double binding occurs

i have task that must update my data every 5 seconds. My current implementation

runAsync {
         while (true) {
             TimeUnit.SECONDS.sleep(2)
             homeController.updateDeviceStatus(printers, notificationEnabled)
             homeController.updatePrintingServiceStatus(printers)
             homeController.runPrinterService(printers)
        }
}

but when i closed app it task still work

@Roman Use

runAsync(daemon = true) { .. }

and also make sure that your calls to

homeController

are either wrapped in

runLater

so they run on the UI thread, or make sure the functions themselves make sure they run on the correct thread

@edvin i'm running runAsync in my view. In your tutorial it was written that runAsync for a long background process🙂

@Roman Yes, and that's fine, but your background process is not just long running, it's forever running 🙂

As long as the non daemon async task is running it prevents the app from exiting