Albatross's templating engine supports a number of special html tags which interact with the application framework.

• Application tags

  • <al-value>

  • <al-a>

  • <al-form>

  • <al-input>

    • If check1 isn't already set in your context, in your page_setup method you can initialise it using:

         1     ctx.locals.check1 = 1
      

      Invoke the html in your html view:

          <al-input type="checkbox" name="group" value="check1">

      When the page comes back from the server, you can inspect the value using:

         1     if ctx.local.check1:
         2         selected()
         3     else:
         4         unselected()
      

  • <al-select>/<al-option>

  • <al-lookup>/<al-item>

    • The following is a table which translates the internal program value into HTML for display.

      <al-lookup name="bug-severity">
       <al-item expr="btsvalues.TRIVIAL"><font color="green">Trivial</font></al-item>
       <al-item expr="btsvalues.MINOR">Minor</al-item>
       <al-item expr="btsvalues.NORMAL">Normal</al-item>
       <al-item expr="btsvalues.MAJOR"><font color="red">Major</font></al-item>
       <al-item expr="btsvalues.CRITICAL"><font color="red"><b>Critical</b></font></al-item>
      </al-lookup>

      The btsvalues module must be visible when the <al-lookup> tag is executed. You can place the btsvalues module in the the global namespace of the execution context by importing the btsvalues module in the same module which creates the execution context.

      We invoke the lookup table by using the lookup attribute of the <al-value> tag.

      Severity: <al-value expr="bug.severity" lookup="bug-severity">

      Note that the btsvalues module does not need to be in the namespace at this point.
• Flow control

  • <al-for>

  • <al-if>/<al-else>

  • <al-exec>

• Substitution

  • <al-include>

  • <al-macro>/<al-expand>