Originally posted by Jason Nesbitt:
The requirements of the user interface state that "It must allow the user to search the data for all records, or for records where the name and/or location fields exactly match values specified by the user."
Would it be enough to have the search return all records when no criteria is specified or does there need to be an explicit option to return all records such as having another button that says "List All"?
Also, I noticed that there are a bunch of different versions of the URLyBird assignment floating around out there. Are these given out at random or does it depend on the time that you buy the assignment? Mine is 1.1.1
Originally posted by Sean Gildea:
Thats what I believe also. I dont think you need to list all records button. I have the URLyBird assignment as well.
In the DBAccess interface, under findByCriteria, the comments for it say...
"Field n in the database file is described by criteria[n]. A null value in criteria[n] matches any field value."
I'm confused, do we need to implement every record value is matching that in criteria or can we just implement it so a record value matches the name and location in the criteria?
[ November 11, 2004: Message edited by: Sean Gildea ]
However, it does not say must anywhere, so I doubt it would be an automatic failure.
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.
Originally posted by Paul Bourdeaux:
I don't think you would fail the assignment, but it wouldn't surprise me if you lose some points. I have the B&S assignment, and it has a similar findByCriteria(String criteria) method. Even though the client will only have the ability to search by Name or City, my method has the functionality to search by any field, or combination or multiple fields. I think this falls under the "future functionality enhancements" clause in the instructions: However, it does not say must anywhere, so I doubt it would be an automatic failure.
Originally posted by Inuka Vincit:
I had a drop boxes with the all option , and options for selecting the different choices in the database. I also had clear buttons so that user could clear the fields, and the blank fields did an all search as well, as the requirements stated. In this way the user could either chose the different options or type in the search and the program would perform and exact match. I thought the exact match requirement screamed for a drop box so I put one in. I got full marks for the GUI with my approach, you should add what ever feature you think will help the user, just dont over complicate it.
[ January 07, 2005: Message edited by: Inuka Vincit ]
// Returns an array of record numbers that match the specified
// criteria. Field n in the database file is described by
// criteria[n]. A null value in criteria[n] matches any field
// value. A non-null value in criteria[n] matches any field
// value that begins with criteria[n]. (For example, "Fred"
// matches "Fred" or "Freddy".)
Originally posted by Inuka Vincit:
No each field of the array corresponds to a column in the table. So that way it wont display all the fields
to search java hilton
this is an example from my head carnt remeber what the specs said
search = null //corresponding to rooms
search = null //corresponding to date
search= "java" //correspons to location column
search="hilton" //correspons to name column
I think your thinking its search or search  or .... search type of thing. Rather its name== search and location ==search and ... search== rooms type of thing(conceptually). Hope I dont sound confusing.... thats how I did the implementation and interpreted the requirements. Otherwise yes the search would be meaningless
[ January 08, 2005: Message edited by: Inuka Vincit ]
Originally posted by David Abramowicz:
I've got a question regarding the omnipotent JComboBox. Do you guys perform a search everytime the JComboBox is touched before the values are displayed?
I'm just worried that otherwise the JComboBoxes wont have the latest data.
Originally posted by Matt Sheehan.: