A custom look-and-feel is used, by default, for BlackBerry 5.0.
Each screen has a block, a <div>. Each div has a form, <form>, where the controls are hosted. Each form has a number of divs. The first div has a block put aside for use to display help, a <span> element. The next div is a built-in element that can be used to find the top of the form. The last div is another built-in element that can be used to find the bottom of the form. All the divs in the form will correspond to the controls put on that screen in the mobile workflow forms editor. You might get, for example, a div that holds a label, <label>, and a textbox, <input>.
- Each screen has a block, contained in a <div> element, and each <div> has a form, where the controls are hosted.
- The first <div> is a block put aside for use to display help, a <span> element.
- The next <div> is a built-in element that can be used to find the top of the form.
- The last <div> is another built-in element that can be used to find the bottom of the form.
- All the divs in the form will correspond to the controls put on that screen in the mobile workflow forms editor. You might get, for example, a <div> that holds a label, <label>, and a textbox, <input>.
Example 1
A typical mobile workflow with this look-and-feel, without extraneous attributes, looks similar to this:
<html>
<body onload="onWorkflowLoad();">
<div id="Department_createScreenDiv">
<form name="Department_createForm" id="Department_createForm">
<div class="customTopOfFormStyle" ><span id="Department_createForm_help" class="help"></span></div>
<div class="customTopOfFormStyle" id="topOfDepartment_createForm"></div>
<div class="editbox">
<label class="left" for="Department_create_dept_name_paramKey">Dept id:</label>
<input class="right" type="text" id="Department_create_dept_name_paramKey"/><span id="Department_create_Department_create_dept_id_paramKey_help" class="help"></span>
</div>
</form>
</div>
</body>
</html>