In Android, those are APIs, Instances, Intents, and Services - going through this book actually has me comparing a lot to TornadoFX concepts and making me understand them a little better

@amanda.hinchman-dominguez Lifecycle is relevant too. You'll see some similarities in the "Best practices" section of this link to what's recommended on this channel for the desktop https://developer.android.com/topic/libraries/architecture/lifecycle

This is awesome! Let me read and process it a bit and I'll get back on my thoughts

Lifecycle of an application, right? I've confused it with SDLC

objects

not requirements/development/testing/delivery

If I'm getting it right, Android is kinda coherent system, so such formalization is vital there, on desktops we have more freedom. How to achieve such modularization, perhaps, with dynamic loading of components on desktop? AFAIK all `import`s will be loaded to the app, when it starts. So all the fragments and controllers will be loaded. I see most practical reason in structurizing a project -- is code maintenance, not performance (as in Android's case)

the android lifecycle system is mostly a UI latency hack, that comes at huge cost and isn't really necessary

it's one of the worse parts of the android API imo. there's no need to copy it on desktops

^ which is better than the full complement of empty methods you used to have to implement

Hello again 🙂 I still can't get my Wizard working. I use a wizard in my application in a tab. On complete I would like to only close the tab but the whole application window is closing. Is there a trick to not close everything?

This is a little reproducer:

import tornadofx.*

class Test : App(TestView::class)

class TestView : View() {
    override val root = pane {
        tabpane {
            tab(TestWizard::class)
        }
    }
}

class TestWizard : Wizard() {
    init {
        add(TestWizard1::class)
    }
}

class TestWizard1 : View("Test") {
    override val root = pane {}
}

My goal ist to close the tab on complete and not the full App.

@Nico Smeenk In your

Wizard

subclass, override

onSave

, which is called when the Wizard completes. From there, call

owningTab?.close()

. This will prevent the normal

close()

call (or at least it's effect, since the Tab will be disconnected by the time the Wizard calls close()).

I'll see if I can make a change to

close()

so it will close the tab instead of the Window if it can find an owning tab 🙂

oh I see... I am stupid 😄

Works now! Thanks!

Hehe 🙂 Sweet!

Is there another method for

onCancel

?

looks like cancel will call

close()

instantly

@thomasnield this is cool!

thomas is a true wizard

i wish to be like thou

Hi everyone, after packaging my TornadoFx app, I realized that each time I launch the app it checks for updates. Is there a way to disable that? It is really critical. Please help.

Thanks

Is it possible to stretch controls inside a

field

in a

form

? I'm using

form { fieldset { flowpane { field { combobox { ... } } } } }

, and setting

field { minWidth = 200.px; maxWidth = 200.px }

in corresponding stylesheet. It seems that a

fieldset

has maximum width of

200

, but fields overlap in less than

200

. I want all fields to be of fixed width with controls stretched inside

@ValV The Form control wasn't built to not make trouble if you embed layout containers between fieldsets and fields, but some things might need special attention if you do so. Could you make a small sample app that displays the issue you're having?

Of course, it looks like this

Initial idea was to make some kind of "blocks" for every control, also use flow layout to be able to align those blocks as horizontal toolbar, vertical toolbar, or even square control set (depending on width: combo boxes vertically -- one beneath the other, and buttons below)

Perhaps, it's misuse of form-field concept, perhaps, I should do it with just flow layout + hbox/vbox