Newer
Older
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE root [
<!ENTITY nbsp " ">
]>
<html xmlns:frx="urn:FrxReports">
<head>
<title>Layout</title>
<frx:category>Help</frx:category>
<frx:options hidden="1"></frx:options>
<frx:parameters>
</frx:parameters>
<frx:docgen></frx:docgen>
<frx:fields>
<frx:field id="title" link="reports/{name}"></frx:field>
</frx:fields>
</head>
<body>
<div id="design_topics_block" frx:block="forena_help/design_topics">
<p>In the layout tab, you can edit the body of the report, save
the report as another, and control which document exports are
available. Explanation of the opions on this form are as
follows:</p>
<p>
<strong>Body -;</strong> The html body of the
report.
</p>
<p>
<strong>Category</strong> - This controls under which group the
report appears under the My Reports link.
</p>
<p>
<strong>Menu</strong> - Specify configuration options for a drupal menu
here.
</p>
<p><strong>Skin</strong> - The skin determines the look and feel of the report.
In conventional report writers this can be thought of as
what kinid of paper form the report printed on. In the
modern days of the web most layout is controlled by Cascacding
Style Sheets (CSS) and Javascript Libraries. See the section on
Report Skins for additional information on creating report skins.</p>
<p>
<strong>Hidden</strong> - Checking this box will cause the report
not to be listed in the My Reports list regardless of the Category
set.
</p>
<ul>
<li id="design_topics" frx:foreach="*">{title}</li>
</ul>
</div>
</body>