• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Best approach for CardLayout

 
Chicken Farmer ()
Posts: 1932
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm writing an application that uses CardLayout. The first card shows 3 buttons, Edit Add and Finish. The Edit and Add cards have the same layout except for one place. Edit has a drop JComboBox showing current values for the application, Add has a JTextField that allows you to add a new value and submit it. Otherwise, the two cards are identical.
I've played around with using inner classes (super and subclasses), duplicating all of the fields for each card, and using various types of logic to switch between the combobox and the textfield, but I either get some pretty funky results, or the code becomes so garbled as to be unreadable. Writing three separate classes would be nice, but since the application pulls values from all the fields, I haven't figured a way to do that yet (without passing an extremely lengthy list of parameters or adding extra objects to the application to get/set the values for the fields).
Anyone have an idea of how to approach this?
Thanks in advance,
Jason
 
Ranch Hand
Posts: 148
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
I tried using card layout for a GUI which had different components one different cards, so what I did was created different classes for different components ( for eg. RadioButtonComponent, ButtonComponent classes etc. The classes were generic that it had methods to set / get values & error checking based on component type. All the cards info was put in XML, so I used to read the XML first & then form the cards. I had one class for the main Panel & used to add the different component based class objects to it.
When I clicked "Next" my action listeners of the component class would take care of values & error checking, same time I would grab values from the components & store them.
Also I used to keep a collection of the components in a vector, that would help in keeping track.
Hope u get the logic.
Vinod
 
Ranch Hand
Posts: 2823
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Jason,
Have you tried making a JPanel class and depending on which type you have either place the combo or text field.
 
jason adam
Chicken Farmer ()
Posts: 1932
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Ok, I think I'm almost there. Problem is now with the buttons. If I have two panels, one for card2 and one for card3, and I have a panel called buttonPanel that holds two buttons that are used for both Card2 and Card3, can I not do a card2.add( buttonPanel ) and card3.add( buttonPanel)? I have this coded, but the buttons only show up on card3.
Is there a way to have the buttons show up for both cards? I guess I could create a panel that holds two unique buttons for card2, and a whole new set of panel/buttons for card3. Is that the best approach?
Jason
 
Paul Stevens
Ranch Hand
Posts: 2823
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Are you creating 2 separate instances or buttonPanel. You need to.
 
jason adam
Chicken Farmer ()
Posts: 1932
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
nope, was doing just one and adding that instance to each panel. I take it that means I'll need to create two instances of the buttons, also, to stick on the buttonPanel?
 
Paul Stevens
Ranch Hand
Posts: 2823
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Doesn't your button panel create its own buttons? If not, yes you need those as well. If you don't all you are doing by adding them to multiple components is move them.
 
jason adam
Chicken Farmer ()
Posts: 1932
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I don't have a separate class for my button panel, if that is what you mean...? I finally worked it so that I do
buttonPanel = new JPanel();
cancel = new JButton( "Cancel" );
submit = new JButton( "Submit" );
//add action listeners, layout managers, etc.
buttonPanel.add( cancel );
buttonPanel.add( submit );
card2.add( buttonPanel );
buttonPanel = new JPanel();
cancel = new JButton( "Cancel" );
submit = new JButton( "Submit" );
//add action listeners, layout managers, etc.
buttonPanel.add( cancel );
buttonPanel.add( submit );
card3.add( buttonPanel );
Don't know if that is the best way, but it works for now.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic