I use GridBagLyout quite a lot, but like many others before me, I quickly found out it can be quite verbose. There are many examples on the web of how users wrote utility methods and/or classes to help them generate GBL code. I’ll show you what I do. 1) First, I created 2 enums that … Read more
Here are a few suggestions: Use a GridLayout for the top panel; in this case, zero means the number of rows is determined by the specified number of columns and the total number of components in the layout: JPanel north = new JPanel(new GridLayout(0, 9)); Here’s an outline of how you can make your center … Read more
Here is a mcve demonstrating how you could use CardLayout as suggested by Andrew Thompson: import java.awt.BorderLayout; import java.awt.CardLayout; import java.awt.Color; import java.awt.Dimension; import javax.swing.JButton; import javax.swing.JFrame; import javax.swing.JPanel; public class GuiController extends JFrame { private boolean isRedShowing; public GuiController(){ setTitle(“CardLayout Demo”); setDefaultCloseOperation(EXIT_ON_CLOSE); setLocationRelativeTo(null); CentreFrameController centreFrameController = new CentreFrameController(); centreFrameController.showRedPane(); isRedShowing = true; setLayout(new BorderLayout()); … Read more
I am afraid the desired layout is not so simple with simple GridBagLayout restriction. GBL does not respect proportions with gridwidth. It means it can’t detect 2/3 of component’s width. So if you define c1 (gridwidth=2) c2 (gridwidth=1) c3 (gridwidth=3) Expecting to get |****|**| |*******| The result will be |**|**| |*****| The camickr’s example works … Read more
This is too long for a comment… First and this is unrelated to the rest of this answer: there are many different MVCs out there and the one you used in that piece of code you posted here is not the same as the one used in the article you linked to: http://www.oracle.com/technetwork/articles/javase/mvc-136693.html The article … Read more
Following up with @MadProgrammer comment: You really need to learn how to use Layout Mangers. Setting sizes is not the way to go, as they will perform different on different machines. One important thing to know about Layout Managers are which layouts respect the preferred sizes of its internal components. The ones that do not … Read more
You might also want to look at OverlayLayout, seen here. It’s not included in the conventional gallery, but it may be of interest. import java.awt.BorderLayout; import java.awt.Color; import java.awt.Dimension; import javax.swing.JFrame; import javax.swing.JLabel; import javax.swing.JPanel; import javax.swing.OverlayLayout; /** @see http://stackoverflow.com/a/13437388/230513 */ public class OverlaySample { public static void main(String args[]) { JFrame frame = new … Read more
The default preferred size calculation is to use the layout manager to determine the preferred size of a component. This means the layout manager iterates through all the child components to determine the preferred size of each. For a JPanel, which is meant to be used as a Container this calculation is used. However, for … Read more
I think the original (non-broken) layout looks quirky and would make it difficult for the end user to follow the rows and labels/fields. I suggest instead using a GroupLayout to right align the labels, and left align the fields that contain the values. Like this: import java.awt.*; import java.util.HashMap; import java.util.Map; import javax.swing.*; class TwoColumnLayoutWithHeader … Read more
You’re mis-interpreting the information given to you. You should avoid using Swing components with AWT components. It’s OK to use Swing with the AWT listener structure, layout managers, etc. and in fact it’s impossible not to.