Bug #214
closedRedesign query plugin
0%
Description
Need to redesign query plugin. Agreed that it should no longer be a "tab" in
the user interface, but rather should be called up as a dialog box. Each
resultset should be a window. Result sets list data sets (data packages) that
are returned from the query. Double clicking on a dataset record opens that
data set by calling the data package module that Chad is building. All types of
queries end up with a pathquery document, which is sent to a query execution
engine (regardless of whether it is local or remote). There is a distinct query
composition module that is used to combine different types of queries together
(like text and taxonomic).
Related issues
Updated by Matt Jones over 23 years ago
Query package has now redesign and contains the QueryPlugin, QueryDialog, Query,
QueryGroup, and QueryTerm classes. The QueryDialog generates a Query, which can
then be "execute()" 'ed, which produces a ResultSet (which maintains a reference
to the Query) which can be embedded in a ResultPanel for display. ResultPanels
have buttons for Revising the saved Query (Revise) and for refreshing the
results by re-executing the saved query (Refresh).