-.kt

created a property delegate so that I can bind a config name with a property

ok

so where do you suggest I load the config - layout time or onDock()?

it's too late at layout time. the initial config could be loaded at creation time (ex, root = vbox{}) for the secondary views. I pull from the database in onDock so that I can get a progressbar up and active

pulling from database is done way ahead, during splash window... when the primary stage shows, all the config is available in memory as a map

so creation time is the ideal place you suggest?

and let javafx do the layout?

yes. versus an after-the-fact adjustment

great.. thanks a lot Carl 🙂 really appreciate your help and time..

np...i think app.config could benefit from an abstraction to allow for DB loading (not app.properties)

right now there's some JSON stuff that might not be appropriate for the general case

if you guys want I can share my repo with you

whatever parts you think will be good for tfx, I can create a PR for it

please. we have an intern here who uses other people's repos as educational materials too

here you go - https://gitlab.com/anidotnet/lb-research

this is just a prototype of the actual app (a cross-platform email client) I am building

it has plugin system, config system and functional IOC (without reflection) till now

great. this could be an important showcase. it also has a Dark Theme example which someone was asking about this past week

Dark them is not done.. Only the theme as a plugin is done..

Css stuff is not there yet.. Just building the whole framework now

@anidotnet nice I will have a look at it tomorrow 👍

How can I filter the rows of a table that has cells from a specific column with the dirty state?

How can i change trayicon image ? something like this ?

icon?.image = Toolkit.getDefaultToolkit().getImage("/connection-off.png")

@Roman Unfortunately, the Tray Icon is still in AWT. I've also run into display problems (transparency) on the various Linux desktops I run. I've moved this requirement into the app. If that's possible for you, this post might help. It has the big plus that I can use JavaFX binding techniques. https://courses.bekwam.net/public_tutorials/bkcourse_trayapp_binding.html

^ That's a comment on the System Tray.

@edvin i saw your note on #770. agree on the best practices involving the model, but how would you handle different Fragment objects of the same class? the examples I've seen have unique identities like "MenuFragment" or "StatusFragment" that can bind to specific ViewModel fields #770 has different Address instances and they can't all bind to the same field (ex "mailing address" versus "billing address"). So, an Address class can't have a statement like bind(viewModel.mailingAddress)

Same_Class__Different_Fragment_Objects.kt

I feel like there's a Bindings.select( obs, "a.b.c" ) solution in there

@carlw I would create the

Address

objects and pass them as parameters to each fragment, or use scopes. I tend to always use scopes 🙂