Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

NX: URLyBird Search Results

 
Alexei Antipin
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The specification states that the search result must be placed in a JTable.
The application uses the same table for presenting search results as well as for presenting the complete data set. By other words, searching by criteria is considered as filtering the entire data set by these criteria. This approach requires user interface to show the mode it operates ? filtered or non-filtered. This is done by means of a check box, situated in the bottom of the client frame. Checking and unchecking this box causes clearing the filter or re-applying it with current set of criteria.
How do you think, is this approach acceptable? Or there should be a separate search result table?
 
George Marinkovich
Ranch Hand
Posts: 619
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Alexei Antipin:
The specification states that the search result must be placed in a JTable.
The application uses the same table for presenting search results as well as for presenting the complete data set. By other words, searching by criteria is considered as filtering the entire data set by these criteria.

Absolutely.
Originally posted by Alexei Antipin:
This approach requires user interface to show the mode it operates ? filtered or non-filtered. This is done by means of a check box, situated in the bottom of the client frame. Checking and unchecking this box causes clearing the filter or re-applying it with current set of criteria.
How do you think, is this approach acceptable?

I guess you can make this distinction between filtered and not filtered. I choose to display all the records by default. I guess that would correspond to your non-filtered mode. When a user entered search criteria I kept the search criteria around (didn't blank them out after the search) so the user would see the search results and also the search criteria at the same time, which I guess corresponds to your filtered mode. So how does the user know whether the table is filtered or non-filtered? In my case the user looks at the search criteria. If they're all blank they are seeing the non-filtered mode; if there are entries, then they're seeing the filtered mode (and additionally they are seeing precisely what that filter was).
Originally posted by Alexei Antipin:
Or there should be a separate search result table?

In my opinion, no.
Hope that helps,
George
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic