Browser sends XML

Agreements

Scalar widgets

All scalar widgets send values in xml-attribute text. For example, constructions

<select name=a>
 <option value=k1>g1</option>
 <option value=k2>g2</option>
 <option value=k3>g3</option>
</select>

<input type=radio name=a value=k1>g1<br>
<input type=radio name=a value=k2>g2<br>
<input type=radio name=a value=k3>

<a text=k2>

Diagnostics

Besides that, if form refers to textual file in local file system, then xml-data will be added in the end of this file. And if file don't exist, then browser create a textual (with path and name, specified in attribute) and write down XML-datas into it.

It is impossible to display page send to: program_name.exe parameters: <work profession="chemist" graduating="1900" experience="10"> <workplace in_date="01.90" out_date="01.91" ltd="AAA" why="aaa"> <workplace in_date="01.92" out_date="01.93" ltd="BBB" why="bbb"> <workplace in_date="01.94" out_date="01.95" ltd="CCC" why="ccc"> <workplace in_date="01.96" out_date="01.97" ltd="DDD" why="ddd"> </work>

To pick up a coordinates of point of broken or curves line is more convenient by using drag-and-drop of points and sections.

Characteristic NEXT

I offer to enter new characteristic next of tag form for specifing a behaviour of a browser after reception of information.

• Value, ordering to interpret a received information as a new document and to display it in a window, is next=document (it's default value). A received file can be html-document or document of xml-data (i.e. containing link to a xsl-file).

  form {
    next: document;
  }
  

• Value, ordering to interpret a received information as xml-command for movement of this document objects, is next=movement (if a xml-file, referring to xsl-file, will be received, then it will not be drawn in a browser).

  form {
    next: movement;
  }
  

• Value, ordering to interpret a received information as new html-objects, which replace objects of this document or are added to them, is next=rotation.

  form {
    next: rotation;
  }
  

  Received objects (they are named as rotations) make following influences (old and new tags should have equal tag name and value of attribute id, attributes "parent" and "after" exist only in communication channel):

  <r rs=542> <ti id=origin_id> ... <ti> </r>	replacement of tag: deleting old tag and cascade deleting its sub-tags and adding new tag with attributes and sub-tags
  <r rs=542> {ti id=origin_id} </r>	deleting of tag and cascade deleting its sub-tags (new tag is sent in braces)
  <r rs=542> <ti parent=tag_name after=origin_id> ... <ti> </r>	adding new tag with attributes and sub-tags and placing it directly after such tag, which name and unique identifier are specified in attributes "parent" and "after"

  One data can be in html-document several times, so several tags with identical name and value of attribute id can be in document. Rotation will be applied to all tags with specified tag_name and origin_id, independently of how many such tags are.
  
  Let's remind, that different tags can have identical value of attribute kind.
  
  
• Value next=execute orders to execute received information in local operational system (mainly value next=execute is intended for those cases, when form's address specifies into local file system).

  form {
    next: execute;
  }
  

  Block will be putted to standard input of executable program, standard output will be directed into the same browser window and will be used for drawing a new document (yellow colour designates two consecutive states of browser window)
  

  Earlier we can not take advantage of writing tag to standard output, only because they will get from standard output into new window of operational system. Now tags go from standard output into browser. We will receive new and new pages, depending of behaviour of user.

  So, once started from html-form, program can communicate further in html-pages.

  
  

  If points coordinates are specified in a separate file in document, sending a form

  <line>
    <link type="point" src=/dir/p.txt>
  </line>
  

  and user has dragged (drag-and-drop) a point before sending a form, then browser should remember new points coordinates. If file from the same address will be need during drawing new document, then browser will use saved coordinates.
  

  Anti-GUI

  Using a lines and performance a programs in local file system simultaneously allows to simulate various phenomena and systems.

  Anti-command string

  Now program receive parameters in start moment by one of the following ways:

  • get parameters (keys) from command string
  • read configuration file
  • user fill some questionnaire (for example, installer "InstallShield")

  First two ways are extremely inconvenient for user: reading a documentation is necessary, there is no intuitive interface.

  Last is very heavy: we used a compiling programming languages for writing these questionnaires, because transfering parameters from html-form to standard input of program was impossible. Now it's possible for making.

Characteristic WAIT

I offer to enter new characteristic wait of tag form, which specifies, whether it's necessary to wait block's end for beginning to update browser window.

• Value wait=no (default value) orders to update a window in process of reception a block

  form {
    wait: no;
  }
  

• If wait=yes, then window will not be updated, until reception of block will be finished

  form {
    wait: yes;
  }
  

Resume

html60author