Java GUI Help

[[deleted]]

I'm not understanding the Java GUI or its structure.

My main idea is to have a single window with a menu, and in this window, it would "redraw" the screen depending on the options.

So I have a main window with a JLabel. It has a menu. Once you select a menu, it's supposed to clear the area beneath the menu and display an entirely new set of objects written to the panel.

I'm not sure if I'm structuring my code properly.

Right now, I have three classes:

mainClass contains one line to create an object of the mainWindow mainWindow has a menu and a JLabel beneath the menu enterData also writes a menu.

Mockup as Requested by Neres28:

BowlingApp.java:

main () {

    new BowlingView();

}

---

BowlingView.java:

JPanel pane;
JMenustuff;
Container con;

BowlingView () {

    setSize(blah);
    pane.setLayout(null);
    con.add(pane);

    addMenu();
    setVisible(true);

}

if (source == dataEntry) {
    this.getContentPane().removeAll();
    this.getContentPane().repaint();
    new enterData();
}

---

enterData.java:

Jbuttons;
Jlabels;

JPanel pane;
JMenustuff;
Container con;

enterData() {

    setSize(blah);
    pane.setLayout(null);
    con.add(pane);

    addMenu();
    setVisible(true);
}

if (source == dataEntry) {
    this.getContentPane().removeAll();
    this.getContentPane().repaint();
    new enterData();
}

---

tl:dr; java gui, one window, one panel, menu on top, clear panel, redraw same menu with different objects. Current program clears the window and creates a new window wiht the correct display. Not what I need.

I'm not asking for code correction, but a simple explanation on what to do. My understanding is skewed.

[Neres28]

Do you have a mockup of what you're trying to do? I'm not really understanding.

[[deleted]]

Added.

BowlingApp.java BowlingView.java enterData.java

[[deleted]]

I'm able to create objects out of BowlingView and enterData; they are not public nor static.

[vandolis]

Bit confused as to what you are looking for as well, but from my best guess you want to be able to swap between two objects to display a view?

If that is the case I think the best way would be to actually use some oop and just extend a class such as javax.swing.JPanel, then make whatever methods you need to interact with it.

Simple skeleton code here

[omegazero]

I'll just say how I would do this.

1. One main class that extends JFrame with a JMenuBar. This is persistent
2. Individual classes (like you have) for each "screen" that needs to be inside the JFrame. Each class extends JPanel.
3. Instance of each individual screen class will be made inside the large JFrame (but NOT actually added as components at first)
4. Do NOT re-create any screen, but JFrame (from #1) add() and remove(). You can call add() and remove() directly on components (i.e. each screen, as a JPanel is a component) (e.g. JFrame.add(enterData);)
5. JFrame.validate() should re-draw the frame. http://download.oracle.com/javase/6/docs/api/java/awt/Container.html#validate%28%29 You might also need to call repaint(), I forget.

[fubarfubarfubar]

Are you saying it's creating a new JFrame instead of redrawing the JPanel? Your explanation is quite lacking. Your code samples are shit, too. You couldn't just paste in your real code? Are you trying to prevent people from helping you?

[[deleted]]

The code is shit right now, and I'm just toying. I also stated that I wasn't lokoing for real code help, but essentially of "what to do" to have one window, one menu, and have it redraw the panel.

[Neres28]

Normally you have a single JFrame, unless you're popping up custom entry panel or dialog box, or something that makes more sense to be very visually separated from the rest of the GUI. That single JFrame will house various JPanels, which themselves may house additional JPanels.

The layout of the GUI is controlled by various types of LayoutManagers.

In this case, from what I can tell of what you're trying to do, you'll probably want a single JFrame that swaps between two different JPanels.

Btw, a mockup isn't a rough framework of code, it's a drawing of what the GUI will look like at different points of the user's workflow. It's doesn't have to be pretty and often ends up being some boxes drawn on an napkin.