blob: 5375a40a480fed7d00fa198d0a87695e0e2cf64b [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Extension Point Schema Compiler Preferences</title>
<link href="../../book.css" rel="stylesheet" type="text/css">
<style type="text/css">
<!--
.style1 {
font-size: 18px;
font-weight: bold;
}
.style2 {
font-size: 12pt;
font-weight: bold;
}
-->
</style>
</head>
<body>
<p class="style1">Extension Point Schema Compiler Preferences</p>
<p>PDE validates extension point schemas and flags syntactic problems as errors. Optional features of the PDE schema builder include the real-time generation of reference documentation for schemas and the flagging of unmatched tags in the schema documentation. </p>
<p>&nbsp;</p>
<p><img src="../../images/preferences/compilers_schemas.png" alt="Schema Compiler Options" hspace="30"></p>
<p>&nbsp;</p>
<p class="style2">HTML Document Generation Preference</p>
<p>The <strong>HTML Document Generation</strong> preference gives the option to generate reference HTML documents from extension point schemas as soon as the schema is modified and saved. The location where the HTML documents are to be generated is customizable with the default location being a folder named <em>doc</em> at the root of the plug-in project. </p>
<p>&nbsp;</p>
<p class="style2">Unmatched Tags Preference </p>
<p>The documentation portions of extension point schemas allow HTML tags. Missing closing tags for those HTML tags that require it may result in badly formatted HTML documentation. The PDE builder validates the documentation sections of extension schemas and flag unmatched tags with a <em>Warning</em> by default. The severity level of this problem can be raised to <em>Error</em> or lowered to <em>Ignore</em>.</p>
<p>&nbsp; </p>
<p></p>
<p>&nbsp;</p>
</body>
</html>