(and closing of main windows)

I would consider the main page to bring out multiple instances of an app

But because the components are always the same minus the grid creation, I wanted to refactor and reduce my code so that controllers determine what data goes into making a grid

the contents of the inner view is also the same, the only thing that is different is the data

I'll post a shortened version of the code in a minute

ok. i'm not sure if editScope is trying to toggle a model component. i'd expect the model component to stay the same through the life of the window (multple instance of the app). scopes make sure that the right instance gets the right model. for example, instance 1 may show "Accounting Grid Layout" in its model and instance 2 could show the "Marketing Grid Layout #999" in instance 2's model.

whatever edit function instance 1 has would modify "Account". the same edit function -- without any scope switching -- would modify "Marketing" in instance 2

@amanda.hinchman-dominguez uploaded a file: Instance Snippet

Quite a bit of code, but should cover my attempt at accomplishing what I'm trying to do

New IDEA plugin also

My veteran Python coworker has been heavily committing Kotlin code the past week, with no JVM experience and only Intellij/JDK setup help from me. This says a lot about the Kotlin platform. Also, he picked up TornadoFX almost instantly just by looking at my code.

is this still the way to go?

tabpane {
                tab("category view", find(CategoryTabView::class).root) { tabClosingPolicy = UNAVAILABLE }
                tab("Whats new", find(WhatsNewTabView::class).root) { tabClosingPolicy = UNAVAILABLE }
            }

especially the

find

@ron negative.

@thomasnield uploaded a file: Untitled

What's cool I discovered too is the title of that view will be the tab's label

Edvin hid all kinds of little gems

oh that is a nice one

yeah I checked the book......

Might need to mention that then.

interesting when I use that syntax I get a warning that the workspace is experimental, if I use the old syntax I dont get that

@thomasnield Hehe, the Tab thing - I figured it would be good to reuse the View title 🙂

changes are going so fast, that the guide is hard to maintain?

Not in this case, it was just an attempt to explain what was going on, and it backfired a little.. hehe

And changes have slowed down substantially. I think that's a good thing actually 🙂

btw @edvin did you see my remark about the different behaviour between the old syntax and the new syntax?

I said.. as I made a change.

@ron No, scrolling up to see what I've missed.

@ron There is no warning about experimental workspace anymore, that was removed in 1.7.5