Meaningless Drivel is fun!
The moose likes Developer Certification (SCJD/OCMJD) and the fly likes NX: Client design Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Developer Certification (SCJD/OCMJD)
Bookmark "NX: Client design" Watch "NX: Client design" New topic

NX: Client design

Maria Lepschy
Ranch Hand

Joined: Jan 12, 2004
Posts: 78
Hi all,

Please comment on my design:

The client side is implemented using the MVC pattern. I didn't implemented this in the common sence, means for each view a modell and a controller. I have only one Controller and one model for the main window ContractorView and also for the view where the user can book a contractor (which shows the fields from the selected row and has a editable textfield to perform booking).
The model is the contractor table model. I found I don't need a separate contractor and model for the book contractor view.
For the configuration window I didn't use a controller and model because the business logic is too simple - the 3 relevant data are stored in the system properties.
The congiguration window and the main window are JFrame and the book contractor view is a JDialog. I allow the user to return from the main window to the configuration window and to show or change the configuration.

I am now writing the choices.txt and I don't know very well how can I argue
my design choice. Can I say that I used MVC?

Maria Lepschy
Ranch Hand

Joined: Jan 12, 2004
Posts: 78
Hi ranchers,
I need your help!
I agree. Here's the link:
subject: NX: Client design
It's not a secret anymore!