Pathagoras Help System

Benefits of <<*Ask*>> Prompts

Benefits of <<*Ask*>> Prompts

Previous topic Next topic  

Benefits of <<*Ask*>> Prompts

Previous topic Next topic  

Benefits of <<*Ask*>> prompts:

   You can create better questions for the end users. (A typical Options block may or may not contain an answer that is sufficiently descriptive. Sometimes the Options block is simply "<<*Options(radio)*!Client!*him/her/them>>". The choice presented to the end user is, therefore, "him" "her" and "them" with a reference to "Client" in the Group box at the top of the selection screen.  The <<*Ask*>>prompt can read something like "<<*AskOptions(radio)*!Client!Our client is a male/Our client is a female/Our client is more than one person*>>")

   The experienced user will observe that any <<*Options*>> block (including the one above) can be edited to provide the identical prompts as can be provided in the <<*Ask*>> prompt. While true, we still commend the use of the <<*Ask*>> prompt. Here are several reasons why:

  When you add prompts to an <<*Options*>> block, the amount of 'real estate' it consumes can be substantial.  When the block appears in the middle of a paragraph, it can be difficult to visually process (both to the editor and the end user who may peruse the document before processing it.)

  There is something intangibly better about compositional questions being at the top or, and segregated from the body of, the main text.

  Best reason: Once you have your 'best' questions composed and residing nicely within one of your documents, you can copy and paste an entire collection of <<*Ask*>> prompts into any other document containing similar <<*Options/Optional*>> blocks. This assures a consistency in the questions that are posed to the end user.

  You can also save the AskTable as a separate clause, calling it in along with other clauses to build, and then process, the document.

  Try that with other programs!