Changes between Version 1 and Version 2 of WebInterface/RunningSemanticQueries
- Timestamp:
- Mar 28, 2012, 1:18:59 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WebInterface/RunningSemanticQueries
v1 v2 1 1 = Semantic queries = 2 This service is available under ”Queries” menu.2 This service is available under the ”Queries” menu. 3 3 == Constructing semantic queries == 4 The query construct assistant is located at the top-left corner of the page. While typing into the text-box, the interface offers possible continuations for the actual, uncompleted sub-term. The offered option can be chosen from a drop-down list. This auto-complete mechanism helps new !RefactorErl users to use the language, and also all developers to speed up query construction and to avoidconstructing wrong queries.4 The query construct assistant is located at the top-left corner of the page. While typing a query the interface offers possible continuations for uncompleted sub-terms. An offered option can be chosen from a drop-down list. This auto-complete mechanism helps new !RefactorErl users using the language, and also all developers to speed up query constructions and avoiding constructing wrong queries. 5 5 6 Pressing the ”Run” button evaluates the query and displays the result. 7 == Position based queries == 8 A file browser is placed at the left side of ’Queries’ page at ’File browser’ tab. One of the previously loaded files can be opened in text view from the file browser panel, by clicking on the magnifying glass icon after selecting a file. By selecting a region or pointing at a position in the text- box, where the contents of the file are loaded in, one can specify the exact position as starting point. Also the result of the previous query can still be reused as a starting point. 9 == Node based queries == 10 Previously loaded files can also be opened in ''links view'' from the file browser panel, by clicking the link icon after selecting a file. In this view queries can be started from a specific node. You can select a node by clicking on it (only text in bold can be selected). The selected node will be marked with red color. 11 [[BR]] 6 Pressing ”Run” evaluates the query and displays the result. 7 == Starting queries == 8 A file browser is placed at the left side of the page under the ’File browser’ tab. A file can be viewed by clicking on it. 9 You can set a starting point for a query in two ways: 10 * Selecting a region or pointing at a position in the shown code. You can only start queries from the query construct assistant this way. 11 * Clicking on a node (bold text) - the selected node will be highlighted. 12 12 13 After selecting a node you can either: 13 * Run pre-defined queries for that node from the top-right corner of the screen .14 * Run pre-defined queries for that node from the top-right corner of the screen - the result of these won't appear in the ’previous queries’ tab. 14 15 * Run previously made queries for that node type by selecting one from the ''Choose previous query'' dropdown box. 15 16 * Run a query from the query construct assistant text-box, which will start from that node. 16 The first result of the query will be shown (if there was any). Results can be browsed with the appearing ''Prev'' and ''Next'' buttons. The total number of results as well as the currently shown result's number are displayed under those buttons.17 17 18 ''NOTE: This feature is still under development, and does not support every query. Please use the Position based queries when you need more explicit results.'' 19 == Global queries == 20 If the ''Global queries'' checkbox is checked, all queries run from the query construct assistant text-box will work as in ''text view'' (and not starting from the selected node). This setting is only important when browsing a file in ''links view'', and a node is currently selected. 18 The first result of the query will be shown (if there was any). Results can be browsed with the appearing ''Prev'' and ''Next'' buttons. The total number of results as well as the currently shown result's number are displayed under those buttons. You can also select results from the ”Last result” tab. 19 21 20 == Alias-able queries == 22 We made queries alias-able, cause of named queries can be identified easier, and are more readable for humans, too.21 We made queries alias-able, because named queries can be identified easier, and are also more readable. 23 22 24 After a query has been successfully run first, it appears at the left side of ’Queries’ page at’Previous Queries’ tab.23 Successful queries appear at the left side of the page under the ’Previous Queries’ tab. 25 24 26 By clicking the corresponding ’E’ button, a text-field appears, which contains the query string. By replacing the query string with the name, what is wanted to assign to the query, and clicking the ’Save’ button the query will be named. After a name has been assigned to the query, the name appears at ’Previous Queries’ tab instead of the query string. If the name of the query should be changed, the same mechanism should be done as described above.25 You can rename a query by clicking on the corresponding ’E’ button, writing a new name in the appearing text-field, then pressing the ’Save’ button. 27 26 28 The query string can be shown as an information element by clicking the ’?’ button. 27 The actual query string can be shown by clicking the ’?’ button. 28 29 29 == Previous Queries == 30 30 For your convenience, the interface stores previously exe- cuted queries and their results, which are listed at the left side of the page at ”Previous Queries” tab. One can choose to list only the queries which belong to the current user, or all the queries stored in the system.