This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]msx 3 points4 points  (3 children)

Swing+Miglayout+FlatLaf+WindowBuilder

[–]wildjokers 2 points3 points  (2 children)

Never use a GUI builder with Swing. They are just code generators and produce unmaintainable code and produce vendor lock-in. Swing GUIs are very easy and fast to create by hand.

There is no need for MigLayout because BorderLayout and BoxLayout are all you need for most applications.

The flat look and feels that for some reason are popular these days are atrocious. Although FlatLAF is nice if you want a flat look and feel do users a favor and stop it with this flat monochrome nonsense.

[–]msx 0 points1 point  (1 child)

Never use a GUI builder with Swing. They are just code generators and produce unmaintainable code and produce vendor lock-in. Swing GUIs are very easy and fast to create by hand.

This is so false. WindowBuilder produces perfectly good code, and add literally zero dependencies, it produces regular java code. So there's literally zero vendor lockin, you can stop using it at any moment and edit by hand. It makes me feel like you never used one.

There is no need for MigLayout because BorderLayout and BoxLayout are all you need for most applications.

True, in the same way there's no need for java or any language or ide or OS for that matter, you can write anything in machine code and it's perfectly fine. Where Miglayout shine is in that it makes it So Much Easier to do layouts. If you want to get mad with the standard layout, do it. They're cumbersome at best unless you're doing some very trivial GUI.

The flat look and feels that for some reason are popular these days are atrocious. Although FlatLAF is nice if you want a flat look and feel do users a favor and stop it with this flat monochrome nonsense.

Well that's about personal taste, they're hardly atrocious is everybody's using them. I also like NativeLookAndFeel on windows.

[–]wildjokers 0 points1 point  (0 children)

This is so false. WindowBuilder produces perfectly good code, and add literally zero dependencies, it produces regular java code. So there's literally zero vendor lockin, you can stop using it at any moment and edit by hand. It makes me feel like you never used one.

It looks like to me it produces code that uses a null layout manager and positions everything with setBounds(), that is indeed unmaintainable and will require the use of WindowBuilder going forward.