Hello, I just found out about this site and it is great! I have a question regarding how to implement the criteria UI. The documentation states that "The user should be able to select the origin and destination flights." I take this to mean that I need to at least add that feature to the UI, but can I also add other UI elements to extend the search criteria to include text fields so the user can also search via carrier, time, etc? I am going with my intuition and adding the other fields since the documentation for the criteriaFind method mentions the carrier attribute. Finally, is the app expected to modify the db file? Are we supposed to change the number of seats in the bd file when the user books a flight? I got the impression that we are not to modify the db file at all. Thanks for a great site.
I think that most people agree that the actual criteriaFind method should be as generic as possible so that any changes in the future can be accomplished with minimal changes. However, I am choosing not to put ANY extra functionality in to the client. It adds complexity and time to the project which is not needed. The only item that I am debating about is collecting customer information when a flight is booked. But even if I choose to add the customer information in it will be just the framework - basic design. Bottom line - try to keep it simple!
My advice would be: stick religiously to the requirements. On one hand, they ask for a completely generic criteriaFind() and an UI that is amenable to expansion later. On the other hand, they ask for the ability to search for origin and destination in the UI, and it's best to stick to that. - Peter
What a stench! Central nervous system shutting down. Save yourself tiny ad!
Devious Experiments for a Truly Passive Greenhouse!