Re: swing design questions
conrad wrote:
1) I want to have a menu bar and options selected from
the menu bar will change the content pane. Would the
ideal way of doing this be as follows: for the menu item
selected add the necessary componenets to the content
pane for that menu item, and when finished just remove
those components from the content pane.
This is the way I would start. If the items to be added are fairly
simple, this is this almost certainly the easiest way to go.
If your components are more complex, the second ways seems attractive.
Create the objects one, keep a reference to them, and then just swap
them into the content pane when you need them. This way also might be
more amenable to using a GUI layout editor like Matisse (which comes
with NetBeans).
2) In terms of populating your content pane with
swing components, I've seen the method of
following a has-a relationship. You might
start out with a class that creates a panel and
adds some buttons. Another class, say for
creating a check box, would extend your
You started out good, then lost me. I'm not sure that "class" is the
right level of decomposition here. Methods work fine. It's also a bit
odd to me that a whole class would be devoted just to a checkbox.
Although, if you had a very specialzied sort of checkbox, I guess it
might be worth while.
panel/button class. In the case from 1) above,
where a menu system creates a branching
effect for different kinds of interfaces(content
panes with different components that are removed
when a different menu item is selected), what kind
of design methodology should be followed? It
doesn't seem like the above panel/button <-- checkbox
containment example would work here.
Again I'm not following. A simple example might help. Could you post
up an SCCEE? I don't see anything wrong with adding a checkbox to
panel, but the whole "checkbox needs a second class" thing has me confused.
<http://www.pscode.org/sscce.html>