The green highlighing indicates an unbooked record. You can sort in ascending/descening order on all columns.
The problem I have is what to do with that big ugly chunk of white space. I've tried putting some buttons there, but they look out of place.
I was thinking of having buttons there which could switch mode - i.e Search & Book | Create | Update | Delete .. which would show a different frame on the left hand side. Two problems with this, as I mentioned the buttons look out of place, and two, I havent implemented create/update/delete functions in my business layer or gui, so I cant really add the buttons. But the intention is that for the future someone could add these extra buttons and functionality.
The file menu is also a bit bare! But the application looks all wrong without one..
Thoughts, criticisms, tips, all welcome. Regards, Alan
For the white space at left bottom, what do you think of some nice statistics about the whole booking system or some aditional information about the selected record? I can't think of something now...
For example, you select a record and there you show me what are hotels in the location, what is the most expensive and what's the cheapest and nearest availability date.
Another option could be to put the search criteria and booking mechanism in a floating window. That way the grid could populate the whole screen. You could hide or show the floating window based on user events.
Another option is to use listboxes instead of comboboxes, they occupy more space, altough not necessarily will look better.
Or you could always put a picture of yourselft writing all that code.
Darwin, but do you think that might be "over-engineered"? The Sun instruction file makes it very clear that "you receive no award for making things which are not required". I guess it may be nice to have, but we should not spend time on it unless we actually learn s/t, regarding our craft, out of it . Just my opinion.
Joined: Dec 31, 2004
Yeah, I guess you're probably right, Leo. Maybe the best is just to reorganize the current layout.
It looks well anyway.
Joined: Sep 18, 2003
I don't think this is overdone, Not everything has to be spell out. Consider the fact that a lot of people followed Denny's DVD sample and got 18/30 on GUI. Isn't that pretty much what the spec required? Why didn't everyone get 30/30?.
The and/or search was not clear from the spec, thus he put in as an option for the user. I would consider sorting of columns as a standard. When is the last time you see a table that is not sortable by header? The filtering of 48 hours + booked item is again an unclear item from the spec. I think this is not overdone at all. However, putting stuffs to fill the space so that it'll look better might be over engineered. [ April 09, 2006: Message edited by: Ed Tse ]
Regarding the 18/30 score for people following the DVD gui I think the following instruction could be one reason:
"Your user interface should be designed with the expectation of future functionality enhancements, and it should establish a framework that will support this with minimal disruption to the users when this occurs."
I think I will add disabled buttons for adding and deleting records to my gui. This will make the user familiar with the gui and the disruption would be minimal as it is stated by the instructions. the quiestion about this is whether this is a good approach for the gui.
Alan Mc Kernan
Joined: Oct 13, 2005
I think thats a bad idea to be honest...
I think they just mean that your code should be extensible, i.e using a good architecture.
And that you should have space in your GUI real-estate for adding some extra buttons etc.
If you're still interested, it might be a good idea to fill the bottom-right space with some kind of a usage-guide. You mentioned that different colours in your table means different things. Showing those colours and their meanings will be a greathelp for first time users (assesors... )
I agree with Leo Ho. On one hand, good for you for putting all his cool stuff in your GUI. It looks great. Because of your attention to detail and other hard work, you will probably get a good score on the exam.
However, for most of us, please keep in mind that Kathy Sierra and Bert Bates even said, in Chapter 10 of their famous SCJP/SCJD study guide: "And dont even think about showing off your programming prowess by revising the specification to do something even better and cooler than whats asked for."
I basically stuck to the "musts" in my instructions.html. I don't have any of these cool features in my GUI. Admittedly, they look nice, but the more functionaity I provide, the more chances of there being some kind of error or something going wrong.
I want to show that I am a team player and that I will only provide what I am asked. Because maybe that is all that the customer paid for and my supervisor needs me to move onto the next project, involving a higher paying customer. Or maybe the marketing people have a plan to include all these cool GUI features in a subsequent release.
Just to let everyone know: There may be no harm in avoiding lots of cool GUI features and sticking to the basic requirements, and that in many cases it may even be preferrable.
I hope this makes sense.
SCJP - 1.4
SCJD - (B&S) Used 1.5 And It Runs On Solaris10
SCWCD - Thanks to HFSJ!!