Changes between Version 3 and Version 4 of WebInterface/RunningSemanticQueries


Ignore:
Timestamp:
Mar 28, 2012, 2:12:52 PM (13 years ago)
Author:
manualwiki
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WebInterface/RunningSemanticQueries

    v3 v4  
    3333Users can add or modify a comment on any query by clicking the corresponding ”C” icon. 
    3434== Running Queries == 
    35 The list of currently running queries is displayed at the left side of the page at ”Running Queries” tab. The list is updated in every second. A running query,which has been started by the current user, can be aborted by pressing the corresponding X icon. The current user, who started the query, is notified about the success of the abort. 
     35The list of currently running queries are displayed at the left side of the page under the ”Running Queries” tab. The list is updated every second. A running query (started by the current user) can be aborted by pressing the corresponding ’X’ icon. The user is notified about the success of the abort. 
    3636== Displaying the result of queries == 
    37 Results are displayed at the left side of the page at ”Last Result” tab in a table. The source of the entries of the result’s can be visualised by clicking on the given entry in the detail. If the source is loaded to the database, it will be shown in a text-box located to the right of the table. The part of the source code responsible for the entry will be highlighted in the text-box. 
     37The results of the last query are displayed at the left side of the page under the ”Last Result” tab. Clicking on an entry shows that result by either selecting the result node or highlighting the result depending on that node being selectable or not. 
    3838== Skeleton of queries == 
    39 Large amount of queries are similar to each-other. The difference usually originates from the actual value of their filter parameter or from the used sub-query. Examples are shown below. 
     39Large amounts of queries are similar to each-other. The only difference is usually the actual value of their filter parameter or the used sub-query. Some examples are shown below. 
    4040 
    4141{{{ 
     
    5151}}} 
    5252 
    53 A new abstract level is introduced, where those queries are not only similar to each-other, but those queries do equal to each-other, we called it Skeleton. Examples are shown below. 
     53A new abstract level is introduced, where these queries are not only similar to each-other, but are equal, we called these Skeletons. They are actually queries with parameters. Examples are shown below. 
    5454 
    5555{{{ 
     
    5757mods.funs[$FunSubQuery$] 
    5858}}} 
    59 == Usage of the skeleton == 
    60 The service of the skeletons is available under ’Queries’ menu. A skeleton can be constructed by typing its body, which observes the rules of the valid skeleton, into the query construct assistant, than ’Save as skeleton’ button should be pressed. By pressing the ’Save as skeleton’ button, a dialogue box appears, where the wanted name of the constructed skeleton should be typed. By clicking the ’Save’ button, which is placed in the dialogue box, the skeleton will be saved. The constructed skeleton appears in the list of available skeletons, which is located at the ’Skeletons’ tab, whether the save was success. If any error occurs during the save, an error message will be shown. 
     59== Usage of skeletons == 
     60A skeleton can be constructed by typing its body into the query construct assistant, then clicking the ’Save as skeleton’ button. The desired name of the constructed skeleton can be typed in the appearing textbox. The skeleton can be saved by clicking the ’Save’ button. If any error occurs during saving, an error message is shown. Constructed skeletons are listed under the ’Skeletons’ tab. 
    6161 
    6262A previously saved skeleton can be evaluated by calling as a function with the actual values of the parameters. A valid actual parameter can contain nearly anything, only the {{{’}}} character is needed to avoid, because the {{{’}}} character is the delimiter of the value of an actual parameter. Auto-complete does not only offer the possible endings, but also does offer the joint skeletons.