Tutorial User Guide > Drive Pages > Drive Page Style Guide
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">   
Drive Page Style Guide
Place a <defsteps> tag at the top of the “Home Page” file. Each <ds> tag contained in the <defsteps> should be on one line, and formatted so that each attribute lines up vertically.
<advisor>
<defsteps>
<ds stepid="2." steplabel="Acquire Geometry"> </ds>
<ds stepid="3." steplabel="Extract Surface(s)"> </ds>
<ds stepid="4." steplabel="Finite Element Mesh"> </ds>
<ds stepid="5." steplabel="Strut Reaction Constraint"> </ds>
<ds stepid="6." steplabel="Shaft Pivot Constraint"> </ds>
<ds stepid="7." steplabel="Cable Load"> </ds>
<ds stepid="8." steplabel="Analyze"> </ds>
<ds stepid="9." steplabel="Show Results"> </ds>
</defsteps>
A <step> tag for each stepid should follow in order. Place a comment at the top of each step to clearly mark the beginning of the step tag.
<!--
 ***
 *** Step 2 "Acquire Geometry"
 ***
 *** -->
<step stepid = "2."
  stephelp = "helpdocs/st2help.html">
The first tag within the <step> tag should be the <uresponse> tag. Each <response> tag should be on one line, and formatted so that each attribute lines up vertically.
<uresponse>
<response name="thickness"  type="REAL"> </response>
<response name="complete"   type="STRING" values="C,X"        readonly> </response>
<response name="geomsource" type="STRING" values="ug,express" readonly> </response>
</uresponse>
The next tag within the <step> tag should be the <lrule> tags. Each ‘if’ should be indented, and each body of the ‘if’ statement should be indented. Always end with an ‘else’ statement to guarantee that the logic rule will send the program flow to a dialog or another <lrule>. Note that <lrule> tags are optional.
<lrule ruleid="gchk">
   if(step("8.").uresponse("Complete")=="C")
      page(".").step("8.").dialog("exclude");
   else if(step("3.").uresponse("complete")=="C")
      page(".").step(".").dialog("doover");
   else if(step("3.").uresponse("complete")=="X")
      page(".").step(".").dialog("undostep");
   else if(step("2.").uresponse("complete")=="C")
      page(".").step(".").dialog("extract");
   else page(".").step(".").dialog("exclude");
</lrule>
Finally, the <step> tag can contain one or many <dialog> tags. Each attribute should be indented. If a function attribute has more then one function, those should be indented to have the ‘F’ start in the same column and should only have one function per line.
The <dialog> tags should be grouped in such a way that makes sense to someone trying to follow the logic flow of the drive page.
<dialog dlgid="mesh"
  inputid="lever_automesh"
  quedlg=".#4.#st4ck1"
  errordlg=".#4.#st4ck2"
  initftn="F:ga_view_aa_set;R:0.;R:0.;R:0.;
           F:gu_fit_view" >