so, one checkbox for the one flag mapped to a globally-available property

and that drives rendering, not data. you wouldn't tamper with the filename data field just to render it differently

that's how I feel/felt about it. However, my concern is that this is in a fragment. So that global is actually a local to the Frag I guess

That's where components like Controller come in. Controller is a singleton that can be injected into a Fragment

I know I can pass a variable

AH BINGO!]

The other way (Controller accessing a Fragment) puts a local Fragment object in the Controller which usually isn't what you want (sometimes it is though).

🙂

thanks

Hi there

I've been using TornadoFX for a year now and I'm planning to port some things from it like

Property

, the event bus, the MVC pattern to a Kotlin common project I know

Propery

is from JavaFX so I was wondering whether there are some legal constraints or not?

I'm planning to use the Apache2 license as TornadoFX does

I ended up using a CSS file

I used the

modena.css

as a starting point

and I use this:

override fun start(stage: Stage) {
        super.start(stage)
        stage.isResizable = false
        Application.setUserAgentStylesheet(null)
        StyleManager.getInstance().addUserAgentStylesheet("styles.css")
    }

in the

App

although I'm not sure whether this is a best practice

@carlw I got my file extensions to work.. but a quick question

what is the best way to assign a controller to a Fragment

I can use the inject by. HOWEVER, I want to pass a generic controller in

so do I just use the parameter option or is there a way already thought of for Fragments?

i.e. set up secondary parameter for controller?

Actually, I've created an interface for my controller and then I create my types from that and pass it in. Works well. Just wondered if there was a method on Fragment I'm supposed to use instead? Can't figure out which

Can you just pass in an operation or two as you did with section? or does the Controller hold some program state

that's what I'm doing 🙂

but I have a need for different 'flavours', hence the interface. Sorry, typing my design. I'll stop it

You pass in something like this as a param to your Fragment when you do a find?

varying_operation_parameter_from_mapOf__.kt

and call your fragment like this rather than use CDI

Passing_operation_as_param.kt

where it operation is