• 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 ...
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

GUI thoughts

Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I�ve been working on the assignment now for about a week. Its pretty much done, and im quite confident in my design . Many thanks to this excellent resource and to the people contributing to it.
I do have a major concern, and it�s about my GUI. When designing it, I strictly followed the Java design guidelines, used MVC etc just like I usually do. By following these guidelines, I was forced to make small but reusable tools such as a menu and button factory for creating GUI components from a resource (internationalization is a design guideline).
The result is slick, but im afraid it might bee just too much and too extensive. Not that its deviating from the requirements or anything, its just _big_ (28 files, 97K). It doesn�t contain any special bells and whistles except for menu and button images and a few custom table renderers.
The basic layout is:
- SDI application with a single frame.
- A menubar and a toolbar with shared Action handlers.
- A Statusbar.
- An expandable search pane.
This pane is not displayed by default, its expanded and retracted with a button/menu command. It contains two comboboxes for origin and dest. airports and a search button. When the search pane is retracted, the table shows all flights again.
- A flight info table pane.
Contains a JTable displaying the various flights, either all of them or the ones matching the search criteria. An image is displayed in the left-most column that indicates if the flight has available seats or not.
- A details pane.
Contains a JEditorPane that displays selected flight info in HMTL.
There is one dialog for logging in that allows the user to choose a local or remote data source. One dialog for booking a flight which asks for the number of seats and one about box.
All this stuff adds up to quite a large gui. Although its decomposed into many files, its still a lot of code. After reading other posts on the GUI subject, where people are using only a single menu choice and still get 20/20, i was thinking no way..

Any comments would be appreciated.
Posts: 17346
Mac IntelliJ IDE Spring
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Kai, it sounds to me like you have a great grasp on Swing, so I am not worried that in your going beyond the requirements will cause you to lose any points. And It is not like you went overborad in that area.
You use of a Toolbar wasn't needed but you did you the Action class and they are pretty easy to put together an ddo it correctly, so I think that is fine.
While you can get a 20/20 with a simpler design, you will still probably get 20/20 on your design.
I like the way you have extra features that are cool, but doesn't add difficulty to the user.
Good job, and I wouldn't worry.
Good Luck
Kai Niemi
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for your remarks, Mark.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic