undecorate | Let your decorations be

To make it work as you want it you can specify the owner Window for the stage. This has to happen before the stage is visible.

call Platform.exit() instead of System.exit();

this refers to the most inner class you currently are, so the anonymous MouseAdapter. Use EntranceScreen.this instead.

Firstly I am not sure what type of shadow you are expecting. It will be helpful if you can provide the example for shadow you tried, so that we may know the actual issue.

Having said that, have you tired using -fx-effect on VBox.? The below code creates a shadow effect around the green box.

Well, it seems like you have tried first of three ways to migrate and did not liked it. But this way is only recommended when:

This is the recommended approach if you want to drop decorators in your code base, and the project isn't yet too big.

But I agree that this way of writing stores is indeed quite hard with TS, lots of duplication and etc.

If you want continue to use decorators just keep them where they are, and and call makeObservable(this) in the constructor, just like the docs says:

Leave all the decorators and call makeObservable(this) in the constructor. This will pick up the metadata generated by the decorators. This is the recommended way if you want to limit the impact of a MobX 6 migration.

There is also a third way, which I my opinion, is the best way right now without any bloat:

Remove decorators and use makeAutoObservable(this) in the class constructor's.

I just quoted the docs that you have already read and I can't suggest any other way to migrate. If you have really big project with decorators then use the second way at first, then gradually migrate to the third if you like it.

How can I set JFrames to be undecorated from a look and feel?

That's not the job of a PLAF, so they don't offer that ability.

OTOH a PLAF can change the look of a title-bar, as seen here:

The PLAF's style of title bar only appears if the following method is called: JFrame.setDefaultLookAndFeelDecorated(boolean).

Provides a hint as to whether or not newly created JFrames should have their Window decorations (such as borders, widgets to close the window, title...) provided by the current look and feel. If defaultLookAndFeelDecorated is true, the current LookAndFeel supports providing window decorations, and the current window manager supports undecorated windows, then newly created JFrames will have their Window decorations provided by the current LookAndFeel. ..

I think this is a general problem in JavaFX (I mean not specific with TornadoFX).

The root cause for this is because of setting the maximized property of stage to true. Not sure what JavaFX internally does, but when you open the window from task bar and if the maximized value is true, then it renders in full screen mode.

You can fix this in two ways.

Approach #1:

When the window is opened from task bar, the iconfied property will turn off, set the stage dimensions again to screen bounds if maximized is true.

You can use oe-pkgdata-util find-path '*libz.so*' to find the actual package providing the missing library which you can then add to RDEPENDS.

The point of using layout managers is the is makes you think logically about how to group all your components and how those components should react when the frame is resized. Even though this application may not resize, you need to know this information for the future.

Then the layout is typically done by starting with the default BorderLayout of the JFrame and then creating child panel with different layout managers. You can also nest panels for your desired layout.

So start by reading the Swing tutorial on Layout Manager for the basics of each layout manager.

So I see:

1. You start with a JPanel that you can add to the BorderLayout.LINE_START. This panel could use a vertical BoxLayout. You can then add "glue" between each group of components to give spacing as well as a "vertical strut" between each component in a group.

2. Then you create another panel "center" that again uses a BorderLayout and add this panel to the BorderLayout.CENTER. This panel will have 3 more child panels:

3. To the "center" panel add a panel to the BorderLayout.PAGE_START. This panel might use a horizontal BoxLayout or FlowLayout.

4. To the "center" panel add a panel to the BorderLayout.CENTER. This panel could use a GridBagLayout.

5. To the "center" panel add a panel to the BorderLayout.PAGE_END. This panel will use a GridLayout.

Yes, it will take a little more time the first few times you design your GUI, but in the long run it is time well spent since you are spending the time learning Java/Swing and not time learning how to use the IDE. You code will be maintainable no matter what IDE you use, instead of being dependent on a given IDE. Use the IDE to help debug etc. but don't let it generate any IDE dependent code.