Win a copy of Machine Learning Systems: Designs that scale this week in the Scala forum
or Xamarin in Action: Creating native cross-platform mobile apps in the Android forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Exclusively Swing  RSS feed

Ranch Hand
Posts: 33
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

While going through a final checklist of must be's before submission,
I couldn't help but get stuck with the following requirement:

It (the user interface) must be composed exclusively with
components from the Java Foundation Classes (Swing components).

Now, I perfectly understand that we have to use JButtons, JFrames etc.
instead of Buttons and Frames. However, certain Swing features like event
handlers and most layouts are still part of AWT.

I've also found a previous discussion which pretty much concludes as I did:
We can use the required classes from AWT as long as they don't have a Swing
equivalent. But that exclusively phrase is worrying me a lot.

My question is Swing has some layouts such as BoxLayout, but I use
GridLayout and GridBagLayout which are defined in AWT quite a lot in my code. Should I stick to using Swing only layouts? (Man, I would be pissed
off if I have to

Just in case, here are my imports for the client GUI:

Does anyone see an inappropriate class that I shouldn't have used?

Thanks a lot.
Ranch Hand
Posts: 319
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi there.

I think the key words here are "Swing components". I.e. Visible stuff you see on screen.

IMO, using those awt features is perfectly fine and needed.
Some of my imports were as follows:

import java.awt.*;
import java.awt.event.*;

Hope that helps.

I am not young enough to know everything. - Oscar Wilde This tiny ad thinks it knows more than Oscar:
Rocket Oven Kickstarter - from the trailboss
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!