path stringlengths 5 312 | repo_name stringlengths 5 116 | content stringlengths 2 1.04M |
|---|---|---|
doc/api/org/deidentifier/arx/io/CSVHierarchyInput.html | kentoa/arx | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<!-- NewPage -->
<html lang="de">
<head>
<title>CSVHierarchyInput (ARX API Documentation)</title>
<link rel="stylesheet" type="text/css" href="../../../../stylesheet.css" title="Style">
</head>
<body>
<script type="text/javascript"><!--
if (location.href.indexOf('is-external=true') == -1) {
parent.document.title="CSVHierarchyInput (ARX API Documentation)";
}
//-->
</script>
<noscript>
<div>JavaScript is disabled on your browser.</div>
</noscript>
<!-- ========= START OF TOP NAVBAR ======= -->
<div class="topNav"><a name="navbar_top">
<!-- -->
</a><a href="#skip-navbar_top" title="Skip navigation links"></a><a name="navbar_top_firstrow">
<!-- -->
</a>
<ul class="navList" title="Navigation">
<li><a href="../../../../overview-summary.html">Overview</a></li>
<li><a href="package-summary.html">Package</a></li>
<li class="navBarCell1Rev">Class</li>
<li><a href="class-use/CSVHierarchyInput.html">Use</a></li>
<li><a href="package-tree.html">Tree</a></li>
<li><a href="../../../../deprecated-list.html">Deprecated</a></li>
<li><a href="../../../../index-files/index-1.html">Index</a></li>
<li><a href="../../../../help-doc.html">Help</a></li>
</ul>
</div>
<div class="subNav">
<ul class="navList">
<li><a href="../../../../org/deidentifier/arx/io/CSVDataOutput.html" title="class in org.deidentifier.arx.io"><span class="strong">Prev Class</span></a></li>
<li><a href="../../../../org/deidentifier/arx/io/CSVSyntax.html" title="class in org.deidentifier.arx.io"><span class="strong">Next Class</span></a></li>
</ul>
<ul class="navList">
<li><a href="../../../../index.html?org/deidentifier/arx/io/CSVHierarchyInput.html" target="_top">Frames</a></li>
<li><a href="CSVHierarchyInput.html" target="_top">No Frames</a></li>
</ul>
<ul class="navList" id="allclasses_navbar_top">
<li><a href="../../../../allclasses-noframe.html">All Classes</a></li>
</ul>
<div>
<script type="text/javascript"><!--
allClassesLink = document.getElementById("allclasses_navbar_top");
if(window==top) {
allClassesLink.style.display = "block";
}
else {
allClassesLink.style.display = "none";
}
//-->
</script>
</div>
<div>
<ul class="subNavList">
<li>Summary: </li>
<li>Nested | </li>
<li>Field | </li>
<li><a href="#constructor_summary">Constr</a> | </li>
<li><a href="#method_summary">Method</a></li>
</ul>
<ul class="subNavList">
<li>Detail: </li>
<li>Field | </li>
<li><a href="#constructor_detail">Constr</a> | </li>
<li><a href="#method_detail">Method</a></li>
</ul>
</div>
<a name="skip-navbar_top">
<!-- -->
</a></div>
<!-- ========= END OF TOP NAVBAR ========= -->
<!-- ======== START OF CLASS DATA ======== -->
<div class="header">
<div class="subTitle">org.deidentifier.arx.io</div>
<h2 title="Class CSVHierarchyInput" class="title">Class CSVHierarchyInput</h2>
</div>
<div class="contentContainer">
<ul class="inheritance">
<li>java.lang.Object</li>
<li>
<ul class="inheritance">
<li>org.deidentifier.arx.io.CSVHierarchyInput</li>
</ul>
</li>
</ul>
<div class="description">
<ul class="blockList">
<li class="blockList">
<hr>
<br>
<pre>public class <span class="strong">CSVHierarchyInput</span>
extends java.lang.Object</pre>
<div class="block">Reads a CSV encoded generalization hierarchy.</div>
</li>
</ul>
</div>
<div class="summary">
<ul class="blockList">
<li class="blockList">
<!-- ======== CONSTRUCTOR SUMMARY ======== -->
<ul class="blockList">
<li class="blockList"><a name="constructor_summary">
<!-- -->
</a>
<h3>Constructor Summary</h3>
<table class="overviewSummary" border="0" cellpadding="3" cellspacing="0" summary="Constructor Summary table, listing constructors, and an explanation">
<caption><span>Constructors</span><span class="tabEnd"> </span></caption>
<tr>
<th class="colOne" scope="col">Constructor and Description</th>
</tr>
<tr class="altColor">
<td class="colOne"><code><strong><a href="../../../../org/deidentifier/arx/io/CSVHierarchyInput.html#CSVHierarchyInput(java.io.File)">CSVHierarchyInput</a></strong>(java.io.File file)</code>
<div class="block">Instantiate.</div>
</td>
</tr>
<tr class="rowColor">
<td class="colOne"><code><strong><a href="../../../../org/deidentifier/arx/io/CSVHierarchyInput.html#CSVHierarchyInput(java.io.File, char)">CSVHierarchyInput</a></strong>(java.io.File file,
char delimiter)</code>
<div class="block">Instantiate.</div>
</td>
</tr>
<tr class="altColor">
<td class="colOne"><code><strong><a href="../../../../org/deidentifier/arx/io/CSVHierarchyInput.html#CSVHierarchyInput(java.io.File, char, char)">CSVHierarchyInput</a></strong>(java.io.File file,
char delimiter,
char quote)</code>
<div class="block">Instantiate.</div>
</td>
</tr>
<tr class="rowColor">
<td class="colOne"><code><strong><a href="../../../../org/deidentifier/arx/io/CSVHierarchyInput.html#CSVHierarchyInput(java.io.File, char, char, char)">CSVHierarchyInput</a></strong>(java.io.File file,
char delimiter,
char quote,
char escape)</code>
<div class="block">Instantiate.</div>
</td>
</tr>
<tr class="altColor">
<td class="colOne"><code><strong><a href="../../../../org/deidentifier/arx/io/CSVHierarchyInput.html#CSVHierarchyInput(java.io.File, char, char, char, char[])">CSVHierarchyInput</a></strong>(java.io.File file,
char delimiter,
char quote,
char escape,
char[] linebreak)</code>
<div class="block">Instantiate.</div>
</td>
</tr>
<tr class="rowColor">
<td class="colOne"><code><strong><a href="../../../../org/deidentifier/arx/io/CSVHierarchyInput.html#CSVHierarchyInput(java.io.File, org.deidentifier.arx.io.CSVSyntax)">CSVHierarchyInput</a></strong>(java.io.File file,
<a href="../../../../org/deidentifier/arx/io/CSVSyntax.html" title="class in org.deidentifier.arx.io">CSVSyntax</a> config)</code>
<div class="block">Instantiate.</div>
</td>
</tr>
<tr class="altColor">
<td class="colOne"><code><strong><a href="../../../../org/deidentifier/arx/io/CSVHierarchyInput.html#CSVHierarchyInput(java.io.InputStream)">CSVHierarchyInput</a></strong>(java.io.InputStream stream)</code>
<div class="block">Instantiate.</div>
</td>
</tr>
<tr class="rowColor">
<td class="colOne"><code><strong><a href="../../../../org/deidentifier/arx/io/CSVHierarchyInput.html#CSVHierarchyInput(java.io.InputStream, char)">CSVHierarchyInput</a></strong>(java.io.InputStream stream,
char delimiter)</code>
<div class="block">Instantiate.</div>
</td>
</tr>
<tr class="altColor">
<td class="colOne"><code><strong><a href="../../../../org/deidentifier/arx/io/CSVHierarchyInput.html#CSVHierarchyInput(java.io.InputStream, char, char)">CSVHierarchyInput</a></strong>(java.io.InputStream stream,
char delimiter,
char quote)</code>
<div class="block">Instantiate.</div>
</td>
</tr>
<tr class="rowColor">
<td class="colOne"><code><strong><a href="../../../../org/deidentifier/arx/io/CSVHierarchyInput.html#CSVHierarchyInput(java.io.InputStream, char, char, char)">CSVHierarchyInput</a></strong>(java.io.InputStream stream,
char delimiter,
char quote,
char escape)</code>
<div class="block">Instantiate.</div>
</td>
</tr>
<tr class="altColor">
<td class="colOne"><code><strong><a href="../../../../org/deidentifier/arx/io/CSVHierarchyInput.html#CSVHierarchyInput(java.io.InputStream, char, char, char, char[])">CSVHierarchyInput</a></strong>(java.io.InputStream stream,
char delimiter,
char quote,
char escape,
char[] linebreak)</code>
<div class="block">Instantiate.</div>
</td>
</tr>
<tr class="rowColor">
<td class="colOne"><code><strong><a href="../../../../org/deidentifier/arx/io/CSVHierarchyInput.html#CSVHierarchyInput(java.io.InputStream, org.deidentifier.arx.io.CSVSyntax)">CSVHierarchyInput</a></strong>(java.io.InputStream stream,
<a href="../../../../org/deidentifier/arx/io/CSVSyntax.html" title="class in org.deidentifier.arx.io">CSVSyntax</a> config)</code>
<div class="block">Instantiate.</div>
</td>
</tr>
<tr class="altColor">
<td class="colOne"><code><strong><a href="../../../../org/deidentifier/arx/io/CSVHierarchyInput.html#CSVHierarchyInput(java.lang.String)">CSVHierarchyInput</a></strong>(java.lang.String filename)</code>
<div class="block">Instantiate.</div>
</td>
</tr>
<tr class="rowColor">
<td class="colOne"><code><strong><a href="../../../../org/deidentifier/arx/io/CSVHierarchyInput.html#CSVHierarchyInput(java.lang.String, char)">CSVHierarchyInput</a></strong>(java.lang.String filename,
char delimiter)</code>
<div class="block">Instantiate.</div>
</td>
</tr>
<tr class="altColor">
<td class="colOne"><code><strong><a href="../../../../org/deidentifier/arx/io/CSVHierarchyInput.html#CSVHierarchyInput(java.lang.String, char, char)">CSVHierarchyInput</a></strong>(java.lang.String filename,
char delimiter,
char quote)</code>
<div class="block">Instantiate.</div>
</td>
</tr>
<tr class="rowColor">
<td class="colOne"><code><strong><a href="../../../../org/deidentifier/arx/io/CSVHierarchyInput.html#CSVHierarchyInput(java.lang.String, char, char, char)">CSVHierarchyInput</a></strong>(java.lang.String filename,
char delimiter,
char quote,
char escape)</code>
<div class="block">Instantiate.</div>
</td>
</tr>
<tr class="altColor">
<td class="colOne"><code><strong><a href="../../../../org/deidentifier/arx/io/CSVHierarchyInput.html#CSVHierarchyInput(java.lang.String, char, char, char, char[])">CSVHierarchyInput</a></strong>(java.lang.String filename,
char delimiter,
char quote,
char escape,
char[] linebreak)</code>
<div class="block">Instantiate.</div>
</td>
</tr>
<tr class="rowColor">
<td class="colOne"><code><strong><a href="../../../../org/deidentifier/arx/io/CSVHierarchyInput.html#CSVHierarchyInput(java.lang.String, org.deidentifier.arx.io.CSVSyntax)">CSVHierarchyInput</a></strong>(java.lang.String filename,
<a href="../../../../org/deidentifier/arx/io/CSVSyntax.html" title="class in org.deidentifier.arx.io">CSVSyntax</a> config)</code>
<div class="block">Instantiate.</div>
</td>
</tr>
</table>
</li>
</ul>
<!-- ========== METHOD SUMMARY =========== -->
<ul class="blockList">
<li class="blockList"><a name="method_summary">
<!-- -->
</a>
<h3>Method Summary</h3>
<table class="overviewSummary" border="0" cellpadding="3" cellspacing="0" summary="Method Summary table, listing methods, and an explanation">
<caption><span>Methods</span><span class="tabEnd"> </span></caption>
<tr>
<th class="colFirst" scope="col">Modifier and Type</th>
<th class="colLast" scope="col">Method and Description</th>
</tr>
<tr class="altColor">
<td class="colFirst"><code>java.lang.String[][]</code></td>
<td class="colLast"><code><strong><a href="../../../../org/deidentifier/arx/io/CSVHierarchyInput.html#getHierarchy()">getHierarchy</a></strong>()</code>
<div class="block">Returns the hierarchy.</div>
</td>
</tr>
</table>
<ul class="blockList">
<li class="blockList"><a name="methods_inherited_from_class_java.lang.Object">
<!-- -->
</a>
<h3>Methods inherited from class java.lang.Object</h3>
<code>equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait</code></li>
</ul>
</li>
</ul>
</li>
</ul>
</div>
<div class="details">
<ul class="blockList">
<li class="blockList">
<!-- ========= CONSTRUCTOR DETAIL ======== -->
<ul class="blockList">
<li class="blockList"><a name="constructor_detail">
<!-- -->
</a>
<h3>Constructor Detail</h3>
<a name="CSVHierarchyInput(java.io.File)">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>CSVHierarchyInput</h4>
<pre>public CSVHierarchyInput(java.io.File file)
throws java.io.IOException</pre>
<div class="block">Instantiate.</div>
<dl><dt><span class="strong">Parameters:</span></dt><dd><code>file</code> - the file</dd>
<dt><span class="strong">Throws:</span></dt>
<dd><code>java.io.IOException</code> - Signals that an I/O exception has occurred.</dd></dl>
</li>
</ul>
<a name="CSVHierarchyInput(java.io.File, char)">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>CSVHierarchyInput</h4>
<pre>public CSVHierarchyInput(java.io.File file,
char delimiter)
throws java.io.IOException</pre>
<div class="block">Instantiate.</div>
<dl><dt><span class="strong">Parameters:</span></dt><dd><code>file</code> - the file</dd><dd><code>delimiter</code> - the delimiter</dd>
<dt><span class="strong">Throws:</span></dt>
<dd><code>java.io.IOException</code> - Signals that an I/O exception has occurred.</dd></dl>
</li>
</ul>
<a name="CSVHierarchyInput(java.io.File, char, char)">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>CSVHierarchyInput</h4>
<pre>public CSVHierarchyInput(java.io.File file,
char delimiter,
char quote)
throws java.io.IOException</pre>
<div class="block">Instantiate.</div>
<dl><dt><span class="strong">Parameters:</span></dt><dd><code>file</code> - the file</dd><dd><code>delimiter</code> - the delimiter</dd><dd><code>quote</code> - the quote</dd>
<dt><span class="strong">Throws:</span></dt>
<dd><code>java.io.IOException</code> - Signals that an I/O exception has occurred.</dd></dl>
</li>
</ul>
<a name="CSVHierarchyInput(java.io.File, char, char, char)">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>CSVHierarchyInput</h4>
<pre>public CSVHierarchyInput(java.io.File file,
char delimiter,
char quote,
char escape)
throws java.io.IOException</pre>
<div class="block">Instantiate.</div>
<dl><dt><span class="strong">Parameters:</span></dt><dd><code>file</code> - the file</dd><dd><code>delimiter</code> - the delimiter</dd><dd><code>quote</code> - the quote</dd><dd><code>escape</code> - the escape</dd>
<dt><span class="strong">Throws:</span></dt>
<dd><code>java.io.IOException</code> - Signals that an I/O exception has occurred.</dd></dl>
</li>
</ul>
<a name="CSVHierarchyInput(java.io.File, char, char, char, char[])">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>CSVHierarchyInput</h4>
<pre>public CSVHierarchyInput(java.io.File file,
char delimiter,
char quote,
char escape,
char[] linebreak)
throws java.io.IOException</pre>
<div class="block">Instantiate.</div>
<dl><dt><span class="strong">Parameters:</span></dt><dd><code>file</code> - the file</dd><dd><code>delimiter</code> - the delimiter</dd><dd><code>quote</code> - the quote</dd><dd><code>escape</code> - the escape</dd><dd><code>linebreak</code> - the linebreak</dd>
<dt><span class="strong">Throws:</span></dt>
<dd><code>java.io.IOException</code> - Signals that an I/O exception has occurred.</dd></dl>
</li>
</ul>
<a name="CSVHierarchyInput(java.io.File, org.deidentifier.arx.io.CSVSyntax)">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>CSVHierarchyInput</h4>
<pre>public CSVHierarchyInput(java.io.File file,
<a href="../../../../org/deidentifier/arx/io/CSVSyntax.html" title="class in org.deidentifier.arx.io">CSVSyntax</a> config)
throws java.io.IOException</pre>
<div class="block">Instantiate.</div>
<dl><dt><span class="strong">Parameters:</span></dt><dd><code>file</code> - the file</dd><dd><code>config</code> - the config</dd>
<dt><span class="strong">Throws:</span></dt>
<dd><code>java.io.IOException</code> - Signals that an I/O exception has occurred.</dd></dl>
</li>
</ul>
<a name="CSVHierarchyInput(java.io.InputStream)">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>CSVHierarchyInput</h4>
<pre>public CSVHierarchyInput(java.io.InputStream stream)
throws java.io.IOException</pre>
<div class="block">Instantiate.</div>
<dl><dt><span class="strong">Parameters:</span></dt><dd><code>stream</code> - the stream</dd>
<dt><span class="strong">Throws:</span></dt>
<dd><code>java.io.IOException</code> - Signals that an I/O exception has occurred.</dd></dl>
</li>
</ul>
<a name="CSVHierarchyInput(java.io.InputStream, char)">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>CSVHierarchyInput</h4>
<pre>public CSVHierarchyInput(java.io.InputStream stream,
char delimiter)
throws java.io.IOException</pre>
<div class="block">Instantiate.</div>
<dl><dt><span class="strong">Parameters:</span></dt><dd><code>stream</code> - the stream</dd><dd><code>delimiter</code> - the delimiter</dd>
<dt><span class="strong">Throws:</span></dt>
<dd><code>java.io.IOException</code> - Signals that an I/O exception has occurred.</dd></dl>
</li>
</ul>
<a name="CSVHierarchyInput(java.io.InputStream, char, char)">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>CSVHierarchyInput</h4>
<pre>public CSVHierarchyInput(java.io.InputStream stream,
char delimiter,
char quote)
throws java.io.IOException</pre>
<div class="block">Instantiate.</div>
<dl><dt><span class="strong">Parameters:</span></dt><dd><code>stream</code> - the stream</dd><dd><code>delimiter</code> - the delimiter</dd><dd><code>quote</code> - the quote</dd>
<dt><span class="strong">Throws:</span></dt>
<dd><code>java.io.IOException</code> - Signals that an I/O exception has occurred.</dd></dl>
</li>
</ul>
<a name="CSVHierarchyInput(java.io.InputStream, char, char, char)">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>CSVHierarchyInput</h4>
<pre>public CSVHierarchyInput(java.io.InputStream stream,
char delimiter,
char quote,
char escape)
throws java.io.IOException</pre>
<div class="block">Instantiate.</div>
<dl><dt><span class="strong">Parameters:</span></dt><dd><code>stream</code> - the stream</dd><dd><code>delimiter</code> - the delimiter</dd><dd><code>quote</code> - the quote</dd><dd><code>escape</code> - the escape</dd>
<dt><span class="strong">Throws:</span></dt>
<dd><code>java.io.IOException</code> - Signals that an I/O exception has occurred.</dd></dl>
</li>
</ul>
<a name="CSVHierarchyInput(java.io.InputStream, char, char, char, char[])">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>CSVHierarchyInput</h4>
<pre>public CSVHierarchyInput(java.io.InputStream stream,
char delimiter,
char quote,
char escape,
char[] linebreak)
throws java.io.IOException</pre>
<div class="block">Instantiate.</div>
<dl><dt><span class="strong">Parameters:</span></dt><dd><code>stream</code> - the stream</dd><dd><code>delimiter</code> - the delimiter</dd><dd><code>quote</code> - the quote</dd><dd><code>escape</code> - the escape</dd><dd><code>linebreak</code> - the linebreak</dd>
<dt><span class="strong">Throws:</span></dt>
<dd><code>java.io.IOException</code> - Signals that an I/O exception has occurred.</dd></dl>
</li>
</ul>
<a name="CSVHierarchyInput(java.io.InputStream, org.deidentifier.arx.io.CSVSyntax)">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>CSVHierarchyInput</h4>
<pre>public CSVHierarchyInput(java.io.InputStream stream,
<a href="../../../../org/deidentifier/arx/io/CSVSyntax.html" title="class in org.deidentifier.arx.io">CSVSyntax</a> config)
throws java.io.IOException</pre>
<div class="block">Instantiate.</div>
<dl><dt><span class="strong">Parameters:</span></dt><dd><code>stream</code> - the stream</dd><dd><code>config</code> - the config</dd>
<dt><span class="strong">Throws:</span></dt>
<dd><code>java.io.IOException</code> - Signals that an I/O exception has occurred.</dd></dl>
</li>
</ul>
<a name="CSVHierarchyInput(java.lang.String)">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>CSVHierarchyInput</h4>
<pre>public CSVHierarchyInput(java.lang.String filename)
throws java.io.IOException</pre>
<div class="block">Instantiate.</div>
<dl><dt><span class="strong">Parameters:</span></dt><dd><code>filename</code> - the filename</dd>
<dt><span class="strong">Throws:</span></dt>
<dd><code>java.io.IOException</code> - Signals that an I/O exception has occurred.</dd></dl>
</li>
</ul>
<a name="CSVHierarchyInput(java.lang.String, char)">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>CSVHierarchyInput</h4>
<pre>public CSVHierarchyInput(java.lang.String filename,
char delimiter)
throws java.io.IOException</pre>
<div class="block">Instantiate.</div>
<dl><dt><span class="strong">Parameters:</span></dt><dd><code>filename</code> - the filename</dd><dd><code>delimiter</code> - the delimiter</dd>
<dt><span class="strong">Throws:</span></dt>
<dd><code>java.io.IOException</code> - Signals that an I/O exception has occurred.</dd></dl>
</li>
</ul>
<a name="CSVHierarchyInput(java.lang.String, char, char)">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>CSVHierarchyInput</h4>
<pre>public CSVHierarchyInput(java.lang.String filename,
char delimiter,
char quote)
throws java.io.IOException</pre>
<div class="block">Instantiate.</div>
<dl><dt><span class="strong">Parameters:</span></dt><dd><code>filename</code> - the filename</dd><dd><code>delimiter</code> - the delimiter</dd><dd><code>quote</code> - the quote</dd>
<dt><span class="strong">Throws:</span></dt>
<dd><code>java.io.IOException</code> - Signals that an I/O exception has occurred.</dd></dl>
</li>
</ul>
<a name="CSVHierarchyInput(java.lang.String, char, char, char)">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>CSVHierarchyInput</h4>
<pre>public CSVHierarchyInput(java.lang.String filename,
char delimiter,
char quote,
char escape)
throws java.io.IOException</pre>
<div class="block">Instantiate.</div>
<dl><dt><span class="strong">Parameters:</span></dt><dd><code>filename</code> - the filename</dd><dd><code>delimiter</code> - the delimiter</dd><dd><code>quote</code> - the quote</dd><dd><code>escape</code> - the escape</dd>
<dt><span class="strong">Throws:</span></dt>
<dd><code>java.io.IOException</code> - Signals that an I/O exception has occurred.</dd></dl>
</li>
</ul>
<a name="CSVHierarchyInput(java.lang.String, char, char, char, char[])">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>CSVHierarchyInput</h4>
<pre>public CSVHierarchyInput(java.lang.String filename,
char delimiter,
char quote,
char escape,
char[] linebreak)
throws java.io.IOException</pre>
<div class="block">Instantiate.</div>
<dl><dt><span class="strong">Parameters:</span></dt><dd><code>filename</code> - the filename</dd><dd><code>delimiter</code> - the delimiter</dd><dd><code>quote</code> - the quote</dd><dd><code>escape</code> - the escape</dd><dd><code>linebreak</code> - the linebreak</dd>
<dt><span class="strong">Throws:</span></dt>
<dd><code>java.io.IOException</code> - Signals that an I/O exception has occurred.</dd></dl>
</li>
</ul>
<a name="CSVHierarchyInput(java.lang.String, org.deidentifier.arx.io.CSVSyntax)">
<!-- -->
</a>
<ul class="blockListLast">
<li class="blockList">
<h4>CSVHierarchyInput</h4>
<pre>public CSVHierarchyInput(java.lang.String filename,
<a href="../../../../org/deidentifier/arx/io/CSVSyntax.html" title="class in org.deidentifier.arx.io">CSVSyntax</a> config)
throws java.io.IOException</pre>
<div class="block">Instantiate.</div>
<dl><dt><span class="strong">Parameters:</span></dt><dd><code>filename</code> - the filename</dd><dd><code>config</code> - the config</dd>
<dt><span class="strong">Throws:</span></dt>
<dd><code>java.io.IOException</code> - Signals that an I/O exception has occurred.</dd></dl>
</li>
</ul>
</li>
</ul>
<!-- ============ METHOD DETAIL ========== -->
<ul class="blockList">
<li class="blockList"><a name="method_detail">
<!-- -->
</a>
<h3>Method Detail</h3>
<a name="getHierarchy()">
<!-- -->
</a>
<ul class="blockListLast">
<li class="blockList">
<h4>getHierarchy</h4>
<pre>public java.lang.String[][] getHierarchy()</pre>
<div class="block">Returns the hierarchy.</div>
<dl><dt><span class="strong">Returns:</span></dt><dd>the hierarchy</dd></dl>
</li>
</ul>
</li>
</ul>
</li>
</ul>
</div>
</div>
<!-- ========= END OF CLASS DATA ========= -->
<!-- ======= START OF BOTTOM NAVBAR ====== -->
<div class="bottomNav"><a name="navbar_bottom">
<!-- -->
</a><a href="#skip-navbar_bottom" title="Skip navigation links"></a><a name="navbar_bottom_firstrow">
<!-- -->
</a>
<ul class="navList" title="Navigation">
<li><a href="../../../../overview-summary.html">Overview</a></li>
<li><a href="package-summary.html">Package</a></li>
<li class="navBarCell1Rev">Class</li>
<li><a href="class-use/CSVHierarchyInput.html">Use</a></li>
<li><a href="package-tree.html">Tree</a></li>
<li><a href="../../../../deprecated-list.html">Deprecated</a></li>
<li><a href="../../../../index-files/index-1.html">Index</a></li>
<li><a href="../../../../help-doc.html">Help</a></li>
</ul>
</div>
<div class="subNav">
<ul class="navList">
<li><a href="../../../../org/deidentifier/arx/io/CSVDataOutput.html" title="class in org.deidentifier.arx.io"><span class="strong">Prev Class</span></a></li>
<li><a href="../../../../org/deidentifier/arx/io/CSVSyntax.html" title="class in org.deidentifier.arx.io"><span class="strong">Next Class</span></a></li>
</ul>
<ul class="navList">
<li><a href="../../../../index.html?org/deidentifier/arx/io/CSVHierarchyInput.html" target="_top">Frames</a></li>
<li><a href="CSVHierarchyInput.html" target="_top">No Frames</a></li>
</ul>
<ul class="navList" id="allclasses_navbar_bottom">
<li><a href="../../../../allclasses-noframe.html">All Classes</a></li>
</ul>
<div>
<script type="text/javascript"><!--
allClassesLink = document.getElementById("allclasses_navbar_bottom");
if(window==top) {
allClassesLink.style.display = "block";
}
else {
allClassesLink.style.display = "none";
}
//-->
</script>
</div>
<div>
<ul class="subNavList">
<li>Summary: </li>
<li>Nested | </li>
<li>Field | </li>
<li><a href="#constructor_summary">Constr</a> | </li>
<li><a href="#method_summary">Method</a></li>
</ul>
<ul class="subNavList">
<li>Detail: </li>
<li>Field | </li>
<li><a href="#constructor_detail">Constr</a> | </li>
<li><a href="#method_detail">Method</a></li>
</ul>
</div>
<a name="skip-navbar_bottom">
<!-- -->
</a></div>
<!-- ======== END OF BOTTOM NAVBAR ======= -->
</body>
</html>
|
play2-maven-plugin/1.0.0-alpha7/play2-maven-plugin/xref/com/google/code/play2/plugin/AbstractPlay2ServerMojo.html | play2-maven-plugin/play2-maven-plugin.github.io | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head><meta http-equiv="content-type" content="text/html; charset=UTF-8" />
<title>AbstractPlay2ServerMojo xref</title>
<link type="text/css" rel="stylesheet" href="../../../../../stylesheet.css" />
</head>
<body>
<div id="overview"><a href="../../../../../../apidocs/com/google/code/play2/plugin/AbstractPlay2ServerMojo.html">View Javadoc</a></div><pre>
<a class="jxr_linenumber" name="L1" href="#L1">1</a> <em class="jxr_comment">/*</em>
<a class="jxr_linenumber" name="L2" href="#L2">2</a> <em class="jxr_comment"> * Copyright 2013-2014 Grzegorz Slowikowski (gslowikowski at gmail dot com)</em>
<a class="jxr_linenumber" name="L3" href="#L3">3</a> <em class="jxr_comment"> *</em>
<a class="jxr_linenumber" name="L4" href="#L4">4</a> <em class="jxr_comment"> * Licensed under the Apache License, Version 2.0 (the "License");</em>
<a class="jxr_linenumber" name="L5" href="#L5">5</a> <em class="jxr_comment"> * you may not use this file except in compliance with the License.</em>
<a class="jxr_linenumber" name="L6" href="#L6">6</a> <em class="jxr_comment"> * You may obtain a copy of the License at</em>
<a class="jxr_linenumber" name="L7" href="#L7">7</a> <em class="jxr_comment"> *</em>
<a class="jxr_linenumber" name="L8" href="#L8">8</a> <em class="jxr_comment"> * <a href="http://www.apache.org/licenses/LICENSE-2." target="alexandria_uri">http://www.apache.org/licenses/LICENSE-2.</a>0</em>
<a class="jxr_linenumber" name="L9" href="#L9">9</a> <em class="jxr_comment"> *</em>
<a class="jxr_linenumber" name="L10" href="#L10">10</a> <em class="jxr_comment"> * Unless required by applicable law or agreed to in writing,</em>
<a class="jxr_linenumber" name="L11" href="#L11">11</a> <em class="jxr_comment"> * software distributed under the License is distributed on an</em>
<a class="jxr_linenumber" name="L12" href="#L12">12</a> <em class="jxr_comment"> * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY</em>
<a class="jxr_linenumber" name="L13" href="#L13">13</a> <em class="jxr_comment"> * KIND, either express or implied. See the License for the</em>
<a class="jxr_linenumber" name="L14" href="#L14">14</a> <em class="jxr_comment"> * specific language governing permissions and limitations</em>
<a class="jxr_linenumber" name="L15" href="#L15">15</a> <em class="jxr_comment"> * under the License.</em>
<a class="jxr_linenumber" name="L16" href="#L16">16</a> <em class="jxr_comment"> */</em>
<a class="jxr_linenumber" name="L17" href="#L17">17</a>
<a class="jxr_linenumber" name="L18" href="#L18">18</a> <strong class="jxr_keyword">package</strong> com.google.code.play2.plugin;
<a class="jxr_linenumber" name="L19" href="#L19">19</a>
<a class="jxr_linenumber" name="L20" href="#L20">20</a> <strong class="jxr_keyword">import</strong> java.io.File;
<a class="jxr_linenumber" name="L21" href="#L21">21</a> <strong class="jxr_keyword">import</strong> java.io.IOException;
<a class="jxr_linenumber" name="L22" href="#L22">22</a> <em class="jxr_comment">//import java.net.ServerSocket;</em>
<a class="jxr_linenumber" name="L23" href="#L23">23</a> <em class="jxr_comment">//import java.util.ArrayList;</em>
<a class="jxr_linenumber" name="L24" href="#L24">24</a> <em class="jxr_comment">//import java.util.Collection;</em>
<a class="jxr_linenumber" name="L25" href="#L25">25</a> <strong class="jxr_keyword">import</strong> java.util.Iterator;
<a class="jxr_linenumber" name="L26" href="#L26">26</a> <em class="jxr_comment">//import java.util.List;</em>
<a class="jxr_linenumber" name="L27" href="#L27">27</a> <em class="jxr_comment">//import java.util.Map;</em>
<a class="jxr_linenumber" name="L28" href="#L28">28</a> <strong class="jxr_keyword">import</strong> java.util.Set;
<a class="jxr_linenumber" name="L29" href="#L29">29</a>
<a class="jxr_linenumber" name="L30" href="#L30">30</a> <strong class="jxr_keyword">import</strong> org.apache.maven.artifact.Artifact;
<a class="jxr_linenumber" name="L31" href="#L31">31</a> <strong class="jxr_keyword">import</strong> org.apache.maven.plugin.MojoExecutionException;
<a class="jxr_linenumber" name="L32" href="#L32">32</a> <strong class="jxr_keyword">import</strong> org.apache.maven.plugins.annotations.Parameter;
<a class="jxr_linenumber" name="L33" href="#L33">33</a> <strong class="jxr_keyword">import</strong> org.apache.maven.project.MavenProject;
<a class="jxr_linenumber" name="L34" href="#L34">34</a>
<a class="jxr_linenumber" name="L35" href="#L35">35</a> <strong class="jxr_keyword">import</strong> org.apache.tools.ant.Project;
<a class="jxr_linenumber" name="L36" href="#L36">36</a> <strong class="jxr_keyword">import</strong> org.apache.tools.ant.taskdefs.Java;
<a class="jxr_linenumber" name="L37" href="#L37">37</a> <strong class="jxr_keyword">import</strong> org.apache.tools.ant.types.Path;
<a class="jxr_linenumber" name="L38" href="#L38">38</a>
<a class="jxr_linenumber" name="L39" href="#L39">39</a> <em class="jxr_javadoccomment">/**</em>
<a class="jxr_linenumber" name="L40" href="#L40">40</a> <em class="jxr_javadoccomment"> * Base class for Play&#33; server mojos.</em>
<a class="jxr_linenumber" name="L41" href="#L41">41</a> <em class="jxr_javadoccomment"> */</em>
<a class="jxr_linenumber" name="L42" href="#L42">42</a> <strong class="jxr_keyword">public</strong> <strong class="jxr_keyword">abstract</strong> <strong class="jxr_keyword">class</strong> <a href="../../../../../com/google/code/play2/plugin/AbstractPlay2ServerMojo.html">AbstractPlay2ServerMojo</a>
<a class="jxr_linenumber" name="L43" href="#L43">43</a> <strong class="jxr_keyword">extends</strong> <a href="../../../../../com/google/code/play2/plugin/AbstractAntJavaBasedPlay2Mojo.html">AbstractAntJavaBasedPlay2Mojo</a>
<a class="jxr_linenumber" name="L44" href="#L44">44</a> {
<a class="jxr_linenumber" name="L45" href="#L45">45</a> <em class="jxr_javadoccomment">/**</em>
<a class="jxr_linenumber" name="L46" href="#L46">46</a> <em class="jxr_javadoccomment"> * Alternative server port.</em>
<a class="jxr_linenumber" name="L47" href="#L47">47</a> <em class="jxr_javadoccomment"> * </em>
<a class="jxr_linenumber" name="L48" href="#L48">48</a> <em class="jxr_javadoccomment"> * @since 1.0.0</em>
<a class="jxr_linenumber" name="L49" href="#L49">49</a> <em class="jxr_javadoccomment"> */</em>
<a class="jxr_linenumber" name="L50" href="#L50">50</a> @Parameter( property = <span class="jxr_string">"play2.httpPort"</span>, defaultValue = <span class="jxr_string">""</span> )
<a class="jxr_linenumber" name="L51" href="#L51">51</a> <strong class="jxr_keyword">private</strong> String httpPort;
<a class="jxr_linenumber" name="L52" href="#L52">52</a>
<a class="jxr_linenumber" name="L53" href="#L53">53</a> <em class="jxr_javadoccomment">/**</em>
<a class="jxr_linenumber" name="L54" href="#L54">54</a> <em class="jxr_javadoccomment"> * Alternative server port for secure connection (https protocol).</em>
<a class="jxr_linenumber" name="L55" href="#L55">55</a> <em class="jxr_javadoccomment"> * </em>
<a class="jxr_linenumber" name="L56" href="#L56">56</a> <em class="jxr_javadoccomment"> * @since 1.0.0</em>
<a class="jxr_linenumber" name="L57" href="#L57">57</a> <em class="jxr_javadoccomment"> */</em>
<a class="jxr_linenumber" name="L58" href="#L58">58</a> @Parameter( property = <span class="jxr_string">"play2.httpsPort"</span>, defaultValue = <span class="jxr_string">""</span> )
<a class="jxr_linenumber" name="L59" href="#L59">59</a> <strong class="jxr_keyword">private</strong> String httpsPort;
<a class="jxr_linenumber" name="L60" href="#L60">60</a>
<a class="jxr_linenumber" name="L61" href="#L61">61</a> <em class="jxr_javadoccomment">/**</em>
<a class="jxr_linenumber" name="L62" href="#L62">62</a> <em class="jxr_javadoccomment"> * Additional JVM arguments passed to Play! server's JVM</em>
<a class="jxr_linenumber" name="L63" href="#L63">63</a> <em class="jxr_javadoccomment"> * </em>
<a class="jxr_linenumber" name="L64" href="#L64">64</a> <em class="jxr_javadoccomment"> * @since 1.0.0</em>
<a class="jxr_linenumber" name="L65" href="#L65">65</a> <em class="jxr_javadoccomment"> */</em>
<a class="jxr_linenumber" name="L66" href="#L66">66</a> @Parameter( property = <span class="jxr_string">"play2.serverJvmArgs"</span>, defaultValue = <span class="jxr_string">""</span> )
<a class="jxr_linenumber" name="L67" href="#L67">67</a> <strong class="jxr_keyword">private</strong> String serverJvmArgs;
<a class="jxr_linenumber" name="L68" href="#L68">68</a>
<a class="jxr_linenumber" name="L69" href="#L69">69</a> <strong class="jxr_keyword">protected</strong> Java prepareAntJavaTask( <strong class="jxr_keyword">boolean</strong> fork )
<a class="jxr_linenumber" name="L70" href="#L70">70</a> <strong class="jxr_keyword">throws</strong> MojoExecutionException, IOException
<a class="jxr_linenumber" name="L71" href="#L71">71</a> {
<a class="jxr_linenumber" name="L72" href="#L72">72</a> File baseDir = project.getBasedir();
<a class="jxr_linenumber" name="L73" href="#L73">73</a>
<a class="jxr_linenumber" name="L74" href="#L74">74</a> Project antProject = createProject();
<a class="jxr_linenumber" name="L75" href="#L75">75</a> Path classPath = getProjectClassPath( antProject );
<a class="jxr_linenumber" name="L76" href="#L76">76</a>
<a class="jxr_linenumber" name="L77" href="#L77">77</a> Java javaTask = <strong class="jxr_keyword">new</strong> Java();
<a class="jxr_linenumber" name="L78" href="#L78">78</a> javaTask.setTaskName( <span class="jxr_string">"play"</span> );
<a class="jxr_linenumber" name="L79" href="#L79">79</a> javaTask.setProject( antProject );
<a class="jxr_linenumber" name="L80" href="#L80">80</a> javaTask.setClassname( <span class="jxr_string">"play.core.server.NettyServer"</span> );
<a class="jxr_linenumber" name="L81" href="#L81">81</a> javaTask.setClasspath( classPath );
<a class="jxr_linenumber" name="L82" href="#L82">82</a> javaTask.setFork( fork );
<a class="jxr_linenumber" name="L83" href="#L83">83</a> <strong class="jxr_keyword">if</strong> ( fork )
<a class="jxr_linenumber" name="L84" href="#L84">84</a> {
<a class="jxr_linenumber" name="L85" href="#L85">85</a> javaTask.setDir( baseDir );
<a class="jxr_linenumber" name="L86" href="#L86">86</a>
<a class="jxr_linenumber" name="L87" href="#L87">87</a> String jvmArgs = getServerJvmArgs();
<a class="jxr_linenumber" name="L88" href="#L88">88</a> <strong class="jxr_keyword">if</strong> ( jvmArgs != <strong class="jxr_keyword">null</strong> )
<a class="jxr_linenumber" name="L89" href="#L89">89</a> {
<a class="jxr_linenumber" name="L90" href="#L90">90</a> jvmArgs = jvmArgs.trim();
<a class="jxr_linenumber" name="L91" href="#L91">91</a> <strong class="jxr_keyword">if</strong> ( jvmArgs.length() > 0 )
<a class="jxr_linenumber" name="L92" href="#L92">92</a> {
<a class="jxr_linenumber" name="L93" href="#L93">93</a> String[] args = jvmArgs.split( <span class="jxr_string">" "</span> );
<a class="jxr_linenumber" name="L94" href="#L94">94</a> <strong class="jxr_keyword">for</strong> ( String arg : args )
<a class="jxr_linenumber" name="L95" href="#L95">95</a> {
<a class="jxr_linenumber" name="L96" href="#L96">96</a> javaTask.createJvmarg().setValue( arg );
<a class="jxr_linenumber" name="L97" href="#L97">97</a> getLog().debug( <span class="jxr_string">" Adding jvmarg '"</span> + arg + <span class="jxr_string">"'"</span> );
<a class="jxr_linenumber" name="L98" href="#L98">98</a> }
<a class="jxr_linenumber" name="L99" href="#L99">99</a> }
<a class="jxr_linenumber" name="L100" href="#L100">100</a> }
<a class="jxr_linenumber" name="L101" href="#L101">101</a>
<a class="jxr_linenumber" name="L102" href="#L102">102</a> <strong class="jxr_keyword">if</strong> ( httpPort != <strong class="jxr_keyword">null</strong> && httpPort.length() > 0 )
<a class="jxr_linenumber" name="L103" href="#L103">103</a> {
<a class="jxr_linenumber" name="L104" href="#L104">104</a> addSystemProperty( javaTask, <span class="jxr_string">"http.port"</span>, httpPort );
<a class="jxr_linenumber" name="L105" href="#L105">105</a> }
<a class="jxr_linenumber" name="L106" href="#L106">106</a> <strong class="jxr_keyword">if</strong> ( httpsPort != <strong class="jxr_keyword">null</strong> && httpsPort.length() > 0 )
<a class="jxr_linenumber" name="L107" href="#L107">107</a> {
<a class="jxr_linenumber" name="L108" href="#L108">108</a> addSystemProperty( javaTask, <span class="jxr_string">"https.port"</span>, httpsPort );
<a class="jxr_linenumber" name="L109" href="#L109">109</a> }
<a class="jxr_linenumber" name="L110" href="#L110">110</a> }
<a class="jxr_linenumber" name="L111" href="#L111">111</a> <strong class="jxr_keyword">else</strong>
<a class="jxr_linenumber" name="L112" href="#L112">112</a> {
<a class="jxr_linenumber" name="L113" href="#L113">113</a> <em class="jxr_comment">// find and add all system properties in "serverJvmArgs"</em>
<a class="jxr_linenumber" name="L114" href="#L114">114</a> String jvmArgs = getServerJvmArgs();
<a class="jxr_linenumber" name="L115" href="#L115">115</a> <strong class="jxr_keyword">if</strong> ( jvmArgs != <strong class="jxr_keyword">null</strong> )
<a class="jxr_linenumber" name="L116" href="#L116">116</a> {
<a class="jxr_linenumber" name="L117" href="#L117">117</a> jvmArgs = jvmArgs.trim();
<a class="jxr_linenumber" name="L118" href="#L118">118</a> <strong class="jxr_keyword">if</strong> ( jvmArgs.length() > 0 )
<a class="jxr_linenumber" name="L119" href="#L119">119</a> {
<a class="jxr_linenumber" name="L120" href="#L120">120</a> String[] args = jvmArgs.split( <span class="jxr_string">" "</span> );
<a class="jxr_linenumber" name="L121" href="#L121">121</a> <strong class="jxr_keyword">for</strong> ( String arg : args )
<a class="jxr_linenumber" name="L122" href="#L122">122</a> {
<a class="jxr_linenumber" name="L123" href="#L123">123</a> <strong class="jxr_keyword">if</strong> ( arg.startsWith( <span class="jxr_string">"-D"</span> ) )
<a class="jxr_linenumber" name="L124" href="#L124">124</a> {
<a class="jxr_linenumber" name="L125" href="#L125">125</a> arg = arg.substring( 2 );
<a class="jxr_linenumber" name="L126" href="#L126">126</a> <strong class="jxr_keyword">int</strong> p = arg.indexOf( '=' );
<a class="jxr_linenumber" name="L127" href="#L127">127</a> <strong class="jxr_keyword">if</strong> ( p >= 0 )
<a class="jxr_linenumber" name="L128" href="#L128">128</a> {
<a class="jxr_linenumber" name="L129" href="#L129">129</a> String key = arg.substring( 0, p );
<a class="jxr_linenumber" name="L130" href="#L130">130</a> String value = arg.substring( p + 1 );
<a class="jxr_linenumber" name="L131" href="#L131">131</a> getLog().debug( <span class="jxr_string">" Adding system property '"</span> + arg + <span class="jxr_string">"'"</span> );
<a class="jxr_linenumber" name="L132" href="#L132">132</a> addSystemProperty( javaTask, key, value );
<a class="jxr_linenumber" name="L133" href="#L133">133</a> }
<a class="jxr_linenumber" name="L134" href="#L134">134</a> <strong class="jxr_keyword">else</strong>
<a class="jxr_linenumber" name="L135" href="#L135">135</a> {
<a class="jxr_linenumber" name="L136" href="#L136">136</a> <em class="jxr_comment">// TODO - throw an exception</em>
<a class="jxr_linenumber" name="L137" href="#L137">137</a> }
<a class="jxr_linenumber" name="L138" href="#L138">138</a> }
<a class="jxr_linenumber" name="L139" href="#L139">139</a> }
<a class="jxr_linenumber" name="L140" href="#L140">140</a> }
<a class="jxr_linenumber" name="L141" href="#L141">141</a> }
<a class="jxr_linenumber" name="L142" href="#L142">142</a> }
<a class="jxr_linenumber" name="L143" href="#L143">143</a> <em class="jxr_comment">// addSystemProperty( javaTask, "play.home", playHome.getAbsolutePath() );</em>
<a class="jxr_linenumber" name="L144" href="#L144">144</a> <em class="jxr_comment">// addSystemProperty( javaTask, "play.id", ( playId != null ? playId : "" ) );</em>
<a class="jxr_linenumber" name="L145" href="#L145">145</a> <em class="jxr_comment">// addSystemProperty( javaTask, "application.path", baseDir.getAbsolutePath() );</em>
<a class="jxr_linenumber" name="L146" href="#L146">146</a>
<a class="jxr_linenumber" name="L147" href="#L147">147</a> <strong class="jxr_keyword">return</strong> javaTask;
<a class="jxr_linenumber" name="L148" href="#L148">148</a> }
<a class="jxr_linenumber" name="L149" href="#L149">149</a>
<a class="jxr_linenumber" name="L150" href="#L150">150</a> <strong class="jxr_keyword">protected</strong> Path getProjectClassPath( Project antProject )
<a class="jxr_linenumber" name="L151" href="#L151">151</a> <strong class="jxr_keyword">throws</strong> MojoExecutionException, IOException
<a class="jxr_linenumber" name="L152" href="#L152">152</a> {
<a class="jxr_linenumber" name="L153" href="#L153">153</a> Path classPath = <strong class="jxr_keyword">new</strong> Path( antProject );
<a class="jxr_linenumber" name="L154" href="#L154">154</a>
<a class="jxr_linenumber" name="L155" href="#L155">155</a> Artifact projectArtifact = getProject().getArtifact();
<a class="jxr_linenumber" name="L156" href="#L156">156</a> File projectArtifactFile = projectArtifact.getFile();
<a class="jxr_linenumber" name="L157" href="#L157">157</a> <strong class="jxr_keyword">if</strong> ( projectArtifactFile == <strong class="jxr_keyword">null</strong> )
<a class="jxr_linenumber" name="L158" href="#L158">158</a> {
<a class="jxr_linenumber" name="L159" href="#L159">159</a> File classesDirectory = <strong class="jxr_keyword">new</strong> File( getProject().getBuild().getOutputDirectory() );
<a class="jxr_linenumber" name="L160" href="#L160">160</a> <strong class="jxr_keyword">if</strong> ( !classesDirectory.isDirectory() )
<a class="jxr_linenumber" name="L161" href="#L161">161</a> {
<a class="jxr_linenumber" name="L162" href="#L162">162</a> <strong class="jxr_keyword">throw</strong> <strong class="jxr_keyword">new</strong> MojoExecutionException( <span class="jxr_string">"Project artifact file not available"</span> ); <em class="jxr_comment">//TODO improve message</em>
<a class="jxr_linenumber" name="L163" href="#L163">163</a> }
<a class="jxr_linenumber" name="L164" href="#L164">164</a> projectArtifactFile = classesDirectory;
<a class="jxr_linenumber" name="L165" href="#L165">165</a> <em class="jxr_comment">//TODO - add warning, that classes may be not up to date</em>
<a class="jxr_linenumber" name="L166" href="#L166">166</a> }
<a class="jxr_linenumber" name="L167" href="#L167">167</a> getLog().debug( String.format( <span class="jxr_string">"CP: %s:%s:%s (%s)"</span>, projectArtifact.getGroupId(),
<a class="jxr_linenumber" name="L168" href="#L168">168</a> projectArtifact.getArtifactId(), projectArtifact.getType(),
<a class="jxr_linenumber" name="L169" href="#L169">169</a> projectArtifact.getScope() ) );
<a class="jxr_linenumber" name="L170" href="#L170">170</a> classPath.createPathElement().setLocation( projectArtifactFile );
<a class="jxr_linenumber" name="L171" href="#L171">171</a>
<a class="jxr_linenumber" name="L172" href="#L172">172</a> Set<?> classPathArtifacts = getProject().getArtifacts();
<a class="jxr_linenumber" name="L173" href="#L173">173</a> <strong class="jxr_keyword">for</strong> ( Iterator<?> iter = classPathArtifacts.iterator(); iter.hasNext(); )
<a class="jxr_linenumber" name="L174" href="#L174">174</a> {
<a class="jxr_linenumber" name="L175" href="#L175">175</a> Artifact artifact = (Artifact) iter.next();
<a class="jxr_linenumber" name="L176" href="#L176">176</a> getLog().debug( String.format( <span class="jxr_string">"CP: %s:%s:%s (%s)"</span>, artifact.getGroupId(), artifact.getArtifactId(),
<a class="jxr_linenumber" name="L177" href="#L177">177</a> artifact.getType(), artifact.getScope() ) );
<a class="jxr_linenumber" name="L178" href="#L178">178</a> classPath.createPathElement().setLocation( artifact.getFile() );
<a class="jxr_linenumber" name="L179" href="#L179">179</a> }
<a class="jxr_linenumber" name="L180" href="#L180">180</a> <strong class="jxr_keyword">return</strong> classPath;
<a class="jxr_linenumber" name="L181" href="#L181">181</a> }
<a class="jxr_linenumber" name="L182" href="#L182">182</a>
<a class="jxr_linenumber" name="L183" href="#L183">183</a> <strong class="jxr_keyword">protected</strong> String getHttpPort()
<a class="jxr_linenumber" name="L184" href="#L184">184</a> {
<a class="jxr_linenumber" name="L185" href="#L185">185</a> <strong class="jxr_keyword">return</strong> httpPort;
<a class="jxr_linenumber" name="L186" href="#L186">186</a> }
<a class="jxr_linenumber" name="L187" href="#L187">187</a>
<a class="jxr_linenumber" name="L188" href="#L188">188</a> <strong class="jxr_keyword">protected</strong> String getHttpsPort()
<a class="jxr_linenumber" name="L189" href="#L189">189</a> {
<a class="jxr_linenumber" name="L190" href="#L190">190</a> <strong class="jxr_keyword">return</strong> httpsPort;
<a class="jxr_linenumber" name="L191" href="#L191">191</a> }
<a class="jxr_linenumber" name="L192" href="#L192">192</a>
<a class="jxr_linenumber" name="L193" href="#L193">193</a> <strong class="jxr_keyword">protected</strong> String getServerJvmArgs()
<a class="jxr_linenumber" name="L194" href="#L194">194</a> {
<a class="jxr_linenumber" name="L195" href="#L195">195</a> <strong class="jxr_keyword">return</strong> serverJvmArgs;
<a class="jxr_linenumber" name="L196" href="#L196">196</a> }
<a class="jxr_linenumber" name="L197" href="#L197">197</a>
<a class="jxr_linenumber" name="L198" href="#L198">198</a> <strong class="jxr_keyword">protected</strong> MavenProject getProject()
<a class="jxr_linenumber" name="L199" href="#L199">199</a> {
<a class="jxr_linenumber" name="L200" href="#L200">200</a> <strong class="jxr_keyword">return</strong> project;
<a class="jxr_linenumber" name="L201" href="#L201">201</a> }
<a class="jxr_linenumber" name="L202" href="#L202">202</a>
<a class="jxr_linenumber" name="L203" href="#L203">203</a> }
</pre>
<hr/>
<div id="footer">Copyright © 2013–2014. All rights reserved.</div>
</body>
</html>
|
cms/smarty/templates/5/ehhbzt1394243285/footer.html | royalwang/saivi | <div class="clear"></div>
<div class="footbg">
<div class="footnav">
<ul>
{if $navChannels}
{foreach from=$navChannels item=n key=m}
{if $m<5}
<li><a href="{$n.link}" title="{$n.name}">{$n.shortname}</a></li>
{/if}
{/foreach}
{/if}
</ul>
</div>
<div class="footbar">
<div class="search">
<form id="search" name="search" method="post" action="?m=site&c=home&a=search&token={$token}" data-ajax="false">
<input type="text" class="search_txt" name="SeaStr" id="SeaStr" data-role="none" placeholder="请输入关键词"/>
<input type="submit" class="search_but" data-role="none" value="">
</form>
</div>
<div class="footer">
<ul>
<li class="foottel" style="border-left:0;"><a href="http://site.tg.qq.com/forwardToPhonePage?siteId=1&phone={$company.tel}" title="电话"><img src="smarty/templates/tpls/{$site.template}/tel.png" />电话</a></li>
<li class="footmess"><a href="sms:{$company.mp}" title="短信"><img src="smarty/templates/tpls/{$site.template}/mess.png" />短信</a></li>
<li class="footmap"><a href="?token={$token}&m=site&c=home&a=map" title="地图"><img src="smarty/templates/tpls/{$site.template}/map.png" />地图</a></li>
<li class="footshare" style="border-right:0;">
<!--分享(-->
<a href="?token={$token}&m=site&c=home&a=share" ><img src="smarty/templates/tpls/{$site.template}/share.png" >分享</a>
<!--)分享-->
</li>
</ul>
</div>
</div>
</div>
</div>
<!--menu start-->
{if $showPlugMenu}
<link rel="stylesheet" href="/tpl/Wap/default/common/css/flash/css/plugmenu.css">
<div class="plug-div">
<div class="plug-phone">
<div class="plug-menu themeStyle" style="background:{$site.plugmenucolor}"><span class="close"></span></div>
{foreach from=$plugmenus item=vo key=k}
<div class="themeStyle plug-btn plug-btn{$k+1} close" style="background:{$site.plugmenucolor}">
<a href="{$vo.url}">
<span style="background-image: url(/tpl/Wap/default/common/css/flash/images/img/{$vo.name}.png);" ></span>
</a>
</div>
{/foreach}
<div class="plug-btn plug-btn5 close"></div>
</div>
</div>
<script src="/tpl/Wap/default/common/css/flash/js/zepto.min.js" type="text/javascript"></script>
<script src="/tpl/Wap/default/common/css/flash/js/plugmenu.js" type="text/javascript"></script>
{/if}
<!--menu end-->
</body>
</html>
|
src/main/webapp/weixinfront/front/index01.html | jansonlwj/ordermanege | <!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="initial-scale=1, maximum-scale=1, user-scalable=no, width=device-width">
<title></title>
<link href="lib/css/ionic.css" rel="stylesheet">
<link href="lib/css/ionic.min.css" rel="stylesheet">
<!-- ionic/angularjs js -->
<script src="lib/js/ionic.bundle.js"></script>
<!-- cordova script (this will be a 404 during development) -->
<!-- your app's js -->
<script src="js/app.js"></script>
<script src="js/controllers.js"></script>
</head>
<body ng-app="myApp">
<!--
The nav bar that will be updated as we navigate between views.
-->
<ion-side-menus>
<ion-side-menu-content>
<div class="bar bar-header bar-positive" >
<div class="button icon ion-navicon"></div>
<div class="title">订单管理</div>
<div class="button icon ion-android-add"></div>
</div>
<div class="scroll-content has-header">
<div class="list">
<a class="item item-icon-right"href="#">
<h2>2016-03-14 12:28</h2>
<p>未发货</p>
<div class="icon ion-chevron-right"></div>
</a>
<a class="item item-icon-right"href="#">
<h2>2016-03-11 11:31</h2>
<p style="color: gray">已完成</p>
<div class="icon ion-chevron-right"></div>
</a>
</div>
</div>
</ion-side-menu-content>
<ion-side-menu side="left" width="150" class="balanced-bg">
左侧区域
</ion-side-menu>
</ion-side-menus>
<ion-nav-bar class="bar-positive">
<ion-nav-back-button>
</ion-nav-back-button>
</ion-nav-bar>
<ion-nav-view></ion-nav-view>
</body>
</html>
|
examples/scroller/scroller.html | phish108/CoreMVC | <html>
<head>
<style>
/*[data-view][role~=group] { display: none; }
[data-view][role~=group].active { display: block;}*/
.container {
height: 50vh;
overflow: scroll;
}
.content {
height: 100vh;
border: 1px solid black;
border-bottom: 5px solid red;
}
.content div:first-child {
height: 90vh;
}
[role=button] {
cursor: pointer;
}
</style>
</head>
<body>
<div role="group" data-view="start" data-event="click tap">
<div role="button">
<a data-bind="changeTo" href="#scroller">Switch to Scroller View</a>
</div>
</div>
<div role="group" data-view="scroller" data-event="click tap" hidden>
<div id="barScrollCounter">0</div>
<div id="barScrollContent" class="container" data-event="scroll">
<div class="content">
<div>
<p>hi! I am the Scroller View!</p>
<p>Scroll down, to get back</p>
</div>
<div role="button" data-bind="changeTo" href="#start">
<a data-bind="changeTo" href="#start">back</a>
</div>
</div>
</div>
</div>
<!-- always first -->
<script src="../../DelegateProxy.js" type="text/javascript"></script>
<script src="../../ApVy.js" type="text/javascript"></script>
<!-- app-specific logic -->
<script src="scroller.js" type="text/javascript"></script>
</body>
</html>
|
library-lift-jpa/src/main/webapp/authors/index.html | escalante/escalante-quickstart | <lift:surround with="default" at="content">
<table>
<tr>
<th>Name</th>
<th>Books</th>
<th>dfd</th>
</tr>
<tr class="lift:authors.list">
<td class="name">Name</td>
<td><a class="books"></a></td>
<td><a class="edit">Edit</a></td>
</tr>
<a href="add">Add</a>
</table>
</lift:surround>
|
css/style.css | kylienic/Thesis-Wireframe | /*why can't i get my sliders to center vertically?*/
body{
/*font-family: "Ubuntu", Sans-Serif;*/
font-size: 10pt;
font-weight: 400pt;
}
.col-noRpad{
padding-right: 0px;
}
.adjustment-holder{
margin-bottom: 10px;
height: 40px;
position: absolute;
left: 25px;
top:25px;
/*why does this stop floating when i toggle off input?*/
}
.control-slider{
/*position: relative;
margin-top: auto;
margin-bottom: auto;*/
}
.sharpen{
width: 100%;
border: none;
}
.control-slider-wrapper{
display: inline-block;
margin-top: auto;
margin-bottom: auto;
height:22px;
}
.icon{
position: relative;
margin-left:10px;
margin-bottom: 10px;
margin-top: 10px;
}
.image-canvas{
position: relative;
left: 119px;
top: 70px;
width: 1000px;
}
.slider-label{
position: relative;
display: inline;
margin-top: auto;
margin-bottom: auto;
top: -7px;
}
#Brightness{
display: inline-block;
position: relative;
width: 520px;
text-align: top;
left: 150px;
top: 40px;
}
#cont-label{
top:-20px;
}
#canvas{
margin-left: 15px;
}
#inject-contrast{
display: inline-block;
left: 5px;
top: -20px;
}
#Contrast{
display: inline-block;
position: relative;
width: 520px;
text-align: top;
/*left: 150px;*/
top: 40px;
}
#interface{
position: absolute;
top: 420px;
}
#navbar{
width: 100px;
height: 100%;
fill: #000000;
background-color: #000000;
position: absolute;
right: 0px;
top: 0px;
}
.widget-wrapper{
width: 1040px;
position: relative;
margin-right: auto;
margin-left: auto;
float: none;
display: block;
padding-right: 250px;
} |
views/links.html | Tomella/fsdf-elvis | <!doctype html>
<html lang="en-us" id="ng-app" ng-app="StartApp">
<head>
<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-151317804-1"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'UA-151317804-1');
</script>
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>Foundation Spatial Data</title>
<meta charset="utf-8">
<link rel="icon" type="image/png" href="icsm/resources/img/SiteFavIcon.png" />
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="author" content="Geoscience Australia">
<meta name="version" content="BUILD-VERSION">
<link rel="stylesheet" href="//maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap.css" crossorigin="anonymous">
<link href="//cdn.leafletjs.com/leaflet-0.7.5/leaflet.css" rel="stylesheet" />
<link href="icsm/resources/css/ga.css" rel="stylesheet" />
<link href="icsm/resources/css/app.header.footer.css?v=VERSION_NO" rel="stylesheet" />
<link href="icsm/resources/css/mars.css?v=VERSION_NO" rel="stylesheet" />
<link href="icsm/bower_components/explorer-ui-components/dist/ga-explorer-ui.css" rel="stylesheet" />
<link href="icsm/bower_components/bg-splitter/css/style.css" rel="stylesheet" />
<link href="icsm/bower_components/components-font-awesome/css/font-awesome.min.css" rel="stylesheet">
<link href="icsm/bower_components/leaflet-draw/dist/leaflet.draw.css" rel="stylesheet" />
<link href="icsm/bower_components/ga-explorer-map-components/dist/vendor/leaflet-locationfilter/locationfilter.css" rel="stylesheet" />
<link href="icsm/bower_components/ga-explorer-map-components/dist/vendor/leaflet-measurecontrol/leaflet.measurecontrol.css" rel="stylesheet" />
<link href="icsm/bower_components/ga-explorer-map-components/dist/ga-explorer-map.css" rel="stylesheet" />
<link href='icsm/bower_components/seiyria-bootstrap-slider/dist/css/bootstrap-slider.css' rel="stylesheet" />
<link href="icsm/assets/icsm.css?v=VERSION_NO" rel="stylesheet"/>
<body ng-controller="RootCtrl as root">
<!-- BEGIN: Sticky Header -->
<div icsm-header class="navbar navbar-default navbar-fixed-top"
heading="'Foundation Spatial Data'"
headingtitle="'Foundation Spatial Data'"
breadcrumbs="[{name:'Reload', title: 'Reload Foundation Spatial Data', url: 'start.html'}]"
helptitle="'Get help about Foundation Spatial Data'"
helpalttext="'Get help about Foundation Spatial Data'">
</div>
<!-- END: Sticky Header -->
<!-- Messages go here. They are fixed to the tab bar. -->
<div explorer-messages class="marsMessages noPrint"></div>
<!-- BEGIN: Page Content -->
<start-navigation></start-navigation>
<!-- END: Page Content -->
<!-- BEGIN: Sticky Footer -->
<div page-footer style="z-index:5; " class="noPrint"></div>
<!-- END: Sticky Footer -->
<script src="https://maps.googleapis.com/maps/api/js?client=gme-geoscienceaustralia&v=3&language=en&libraries=places"></script>
<script src="//ajax.googleapis.com/ajax/libs/jquery/2.2.4/jquery.min.js"></script>
<script src="//maxcdn.bootstrapcdn.com/bootstrap/3.3.5/js/bootstrap.min.js" integrity="sha512-K1qjQ+NcF2TYO/eI3M6v8EiNYZfA95pQumfvcVrTHtwQVDG+aHRqLi/ETn2uB+1JqwYqVG3LIvdm9lj6imS/pQ==" crossorigin="anonymous"></script>
<script src="//cdn.leafletjs.com/leaflet-0.7.5/leaflet.js"></script>
<script src="//cdn.jsdelivr.net/leaflet.esri/1.0.0/esri-leaflet.js"></script>
<script src="//ajax.googleapis.com/ajax/libs/angularjs/1.4.11/angular.min.js"></script>
<script src="//ajax.googleapis.com/ajax/libs/angularjs/1.4.11/angular-animate.min.js"></script>
<script src="//ajax.googleapis.com/ajax/libs/angularjs/1.4.11/angular-route.min.js"></script>
<script src="//ajax.googleapis.com/ajax/libs/angularjs/1.4.11/angular-sanitize.min.js"></script>
<script src="//ajax.googleapis.com/ajax/libs/angularjs/1.4.11/angular-aria.min.js"></script>
<script src="//ajax.googleapis.com/ajax/libs/angularjs/1.4.11/angular-messages.min.js"></script>
<script src="//cdnjs.cloudflare.com/ajax/libs/d3/3.5.6/d3.min.js" charset="utf-8"></script>
<script src="//cdnjs.cloudflare.com/ajax/libs/angular-ui-bootstrap/1.3.3/ui-bootstrap-tpls.min.js"></script>
<script src="icsm/bower_components/ngAutocomplete/src/ngAutocomplete.js"></script>
<script src="icsm/bower_components/seiyria-bootstrap-slider/dist/bootstrap-slider.min.js"></script>
<script src="icsm/bower_components/leaflet-draw/dist/leaflet.draw.js"></script>
<script src="icsm/bower_components/ga-explorer-map-components/dist/vendor/leaflet-locationfilter/locationfilter.js"></script>
<script src="icsm/bower_components/ga-explorer-map-components/dist/vendor/leaflet-plotter/leaflet-plotter.js"></script>
<script src="icsm/bower_components/ga-explorer-map-components/dist/vendor/leaflet-measurecontrol/leaflet.measurecontrol.js"></script>
<script src="icsm/bower_components/ga-explorer-map-components/dist/ga-explorer-map.js"></script>
<script src="icsm/bower_components/explorer-ui-components/dist/ga-explorer-ui.js"></script>
<!-- These are the "ICSM" specific includes of modules -->
<script src="icsm/assets/common.js?v=VERSION_NO"></script>
<script src="icsm/assets/start.js?v=VERSION_NO"></script>
</body>
</html>
|
doc/cds-api/classcds_1_1container_1_1cuckoo_1_1empty__refinable__stat.html | IMCG/CDS | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=9"/>
<meta name="generator" content="Doxygen 1.8.3.1"/>
<title>cds: cds::container::cuckoo::empty_refinable_stat Class Reference</title>
<link href="tabs.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="jquery.js"></script>
<script type="text/javascript" src="dynsections.js"></script>
<link href="doxygen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="top"><!-- do not remove this div, it is closed by doxygen! -->
<div id="titlearea">
<table cellspacing="0" cellpadding="0">
<tbody>
<tr style="height: 56px;">
<td style="padding-left: 0.5em;">
<div id="projectname">cds
 <span id="projectnumber">1.4.0</span>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<!-- end header part -->
<!-- Generated by Doxygen 1.8.3.1 -->
<div id="navrow1" class="tabs">
<ul class="tablist">
<li><a href="index.html"><span>Main Page</span></a></li>
<li><a href="modules.html"><span>Modules</span></a></li>
<li><a href="namespaces.html"><span>Namespaces</span></a></li>
<li class="current"><a href="annotated.html"><span>Data Structures</span></a></li>
<li><a href="files.html"><span>Files</span></a></li>
</ul>
</div>
<div id="navrow2" class="tabs2">
<ul class="tablist">
<li><a href="annotated.html"><span>Data Structures</span></a></li>
<li><a href="hierarchy.html"><span>Class Hierarchy</span></a></li>
<li><a href="functions.html"><span>Data Fields</span></a></li>
</ul>
</div>
<div id="nav-path" class="navpath">
<ul>
<li class="navelem"><a class="el" href="namespacecds.html">cds</a></li><li class="navelem"><a class="el" href="namespacecds_1_1container.html">container</a></li><li class="navelem"><a class="el" href="namespacecds_1_1container_1_1cuckoo.html">cuckoo</a></li><li class="navelem"><a class="el" href="classcds_1_1container_1_1cuckoo_1_1empty__refinable__stat.html">empty_refinable_stat</a></li> </ul>
</div>
</div><!-- top -->
<div class="header">
<div class="headertitle">
<div class="title">cds::container::cuckoo::empty_refinable_stat Class Reference</div> </div>
</div><!--header-->
<div class="contents">
<p>Empty refinable internal statistics. This is typedef for <a class="el" href="structcds_1_1intrusive_1_1cuckoo_1_1empty__refinable__stat.html" title="Dummy internal statistics for refinable mutex policy.">intrusive::cuckoo::empty_refinable_stat</a>.
<a href="classcds_1_1container_1_1cuckoo_1_1empty__refinable__stat.html#details">More...</a></p>
<p><code>#include <cds/container/cuckoo_base.h></code></p>
<a name="details" id="details"></a><h2 class="groupheader">Detailed Description</h2>
<div class="textblock"><p>Empty refinable internal statistics. This is typedef for <a class="el" href="structcds_1_1intrusive_1_1cuckoo_1_1empty__refinable__stat.html" title="Dummy internal statistics for refinable mutex policy.">intrusive::cuckoo::empty_refinable_stat</a>. </p>
</div><hr/>The documentation for this class was generated from the following file:<ul>
<li>cds/container/cuckoo_base.h</li>
</ul>
</div><!-- contents -->
<hr/>
<div align="right">
<b>cds</b> <b>1.4.0</b>
Developed by <i>Maxim Khiszinsky aka khizmax</i> 2007 - 2012
<br/>
<i>Autogenerated Mon May 20 2013 00:37:58 by Doxygen 1.8.3.1</i>
</div>
</BODY>
</HTML>
|
DoxygenDocs.docset/html/search/all_74.html | jflasher/IgniteTools | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html><head><title></title>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<link rel="stylesheet" type="text/css" href="search.css"/>
<script type="text/javascript" src="search.js"></script>
</head>
<body class="SRPage">
<div id="SRIndex">
<div class="SRStatus" id="Loading">Loading...</div>
<div class="SRResult" id="SR_tabbarcontroller">
<div class="SREntry">
<a id="Item0" onkeydown="return searchResults.Nav(event,0)" onkeypress="return searchResults.Nav(event,0)" onkeyup="return searchResults.Nav(event,0)" class="SRSymbol" href="javascript:searchResults.Toggle('SR_tabbarcontroller')">tabBarController</a>
<div class="SRChildren">
<a id="Item0_c0" onkeydown="return searchResults.NavChild(event,0,0)" onkeypress="return searchResults.NavChild(event,0,0)" onkeyup="return searchResults.NavChild(event,0,0)" class="SRScope" href="../interface_app_delegate__i_pad.html#a5986d836c9498ccc8b009cf148304823" target="_parent">AppDelegate_iPad::tabBarController()</a>
<a id="Item0_c1" onkeydown="return searchResults.NavChild(event,0,1)" onkeypress="return searchResults.NavChild(event,0,1)" onkeyup="return searchResults.NavChild(event,0,1)" class="SRScope" href="../interface_app_delegate__i_phone.html#a3cdc072789a263d947b7d78d70abfa25" target="_parent">AppDelegate_iPhone::tabBarController()</a>
</div>
</div>
</div>
<div class="SRResult" id="SR_twitterbutton">
<div class="SREntry">
<a id="Item1" onkeydown="return searchResults.Nav(event,1)" onkeypress="return searchResults.Nav(event,1)" onkeyup="return searchResults.Nav(event,1)" class="SRSymbol" href="../interface_presenter_detail_view_controller.html#afd0f19a4a211d573f0b550f75398d647" target="_parent">twitterButton</a>
<span class="SRScope">PresenterDetailViewController</span>
</div>
</div>
<div class="SRResult" id="SR_twitterid">
<div class="SREntry">
<a id="Item2" onkeydown="return searchResults.Nav(event,2)" onkeypress="return searchResults.Nav(event,2)" onkeyup="return searchResults.Nav(event,2)" class="SRSymbol" href="javascript:searchResults.Toggle('SR_twitterid')">twitterID</a>
<div class="SRChildren">
<a id="Item2_c0" onkeydown="return searchResults.NavChild(event,2,0)" onkeypress="return searchResults.NavChild(event,2,0)" onkeyup="return searchResults.NavChild(event,2,0)" class="SRScope" href="../interface_avatar_download.html#ae8b03f5c3cfdd03820e4430bd5331d49" target="_parent">AvatarDownload::twitterID()</a>
<a id="Item2_c1" onkeydown="return searchResults.NavChild(event,2,1)" onkeypress="return searchResults.NavChild(event,2,1)" onkeyup="return searchResults.NavChild(event,2,1)" class="SRScope" href="../interface_presenter.html#ae40f1b402228d35d9f157c922528c249" target="_parent">Presenter::twitterID()</a>
</div>
</div>
</div>
<div class="SRResult" id="SR_">
<div class="SREntry">
<a id="Item3" onkeydown="return searchResults.Nav(event,3)" onkeypress="return searchResults.Nav(event,3)" onkeyup="return searchResults.Nav(event,3)" class="SRSymbol" href="../interface_presenter_detail_view_controller.html#a2cf84dd9ba28d4bb71d87787755fb6b0" target="_parent"></a>
<span class="SRScope">PresenterDetailViewController</span>
</div>
</div>
<div class="SRStatus" id="Searching">Searching...</div>
<div class="SRStatus" id="NoMatches">No Matches</div>
<script type="text/javascript"><!--
document.getElementById("Loading").style.display="none";
document.getElementById("NoMatches").style.display="none";
var searchResults = new SearchResults("searchResults");
searchResults.Search();
--></script>
</div>
</body>
</html>
|
doc/alu/HyperSpec/Body/sec_2-4-8-17.html | jasom/eclipse-lisp | <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<!-- Common Lisp HyperSpec (TM), version 3.0 generated by kmp on Thu, 2-May-1996 10:21am EDT -->
<HTML>
<HEAD>
<TITLE>CLHS: Section 2.4.8.17</TITLE>
<META HTTP-EQUIV="Author" CONTENT="Kent M. Pitman">
<META HTTP-EQUIV="Organization" CONTENT="The Harlequin Group Limited">
<LINK REL=TOP HREF="../FrontMatter/index.html">
<LINK REL=COPYRIGHT HREF="../FrontMatter/About-HyperSpec.html#Legal">
<LINK REL=DISCLAIMER HREF="../FrontMatter/About-HyperSpec.html#Disclaimer">
<LINK REL=PREV HREF="sec_2-4-8-16.html">
<LINK REL=UP HREF="sec_2-4-8.html">
<LINK REL=NEXT HREF="sec_2-4-8-18.html">
</HEAD>
<BODY BGCOLOR="#c0c0c0">
<H1><A REV=MADE HREF="http://www.harlequin.com/"><IMG ALT="[HARLEQUIN]" SRC="../Graphics/Harlequin-Small.gif" ALIGN=Bottom></A><A REL=TOP HREF="../FrontMatter/index.html"><IMG ALT="[Common Lisp HyperSpec (TM)]" SRC="../Graphics/HyperSpec-Small.gif" ALIGN=Bottom></A> <A REL=PREV HREF="sec_2-4-8-16.html"><IMG ALT="[Previous]" SRC="../Graphics/Prev.gif" ALIGN=Bottom></A><A REL=UP HREF="sec_2-4-8.html"><IMG ALT="[Up]" SRC="../Graphics/Up.gif" ALIGN=Bottom></A><A REL=NEXT HREF="sec_2-4-8-18.html"><IMG ALT="[Next]" SRC="../Graphics/Next.gif" ALIGN=Bottom></A></H1>
<HR>
<H2>
2.4.8.17 Sharpsign Plus</H2> <P>
<TT>#+</TT> provides a read-time conditionalization facility; the syntax is <TT>#+</TT><I>test</I><TT> </TT><I>expression</I><TT></TT>. If the <A REL=DEFINITION HREF="glo_f.html#feature_expression"><I>feature expression</I></A> <I>test</I> succeeds, then this textual notation represents an <A REL=DEFINITION HREF="glo_o.html#object"><I>object</I></A> whose printed representation is <I>expression</I>. If the <A REL=DEFINITION HREF="glo_f.html#feature_expression"><I>feature expression</I></A> <I>test</I> fails, then this textual notation is treated as <A REL=DEFINITION HREF="glo_w.html#whitespace"><I>whitespace</I></A>[2]; that is, it is as if the ``<TT>#+</TT> <I>test</I> <I>expression</I>'' did not appear and only a <A REL=DEFINITION HREF="glo_s.html#space"><I>space</I></A> appeared in its place. <P>
For a detailed description of success and failure in <A REL=DEFINITION HREF="glo_f.html#feature_expression"><I>feature expressions</I></A>, see <A REL=CHILD HREF="sec_24-1-2-1.html">Section 24.1.2.1 (Feature Expressions)</A>. <P>
<TT>#+</TT> operates by first reading the <A REL=DEFINITION HREF="glo_f.html#feature_expression"><I>feature expression</I></A> and then skipping over the <I>form</I> if the <A REL=DEFINITION HREF="glo_f.html#feature_expression"><I>feature expression</I></A> fails. While reading the <I>test</I>, the <A REL=DEFINITION HREF="glo_c.html#current_package"><I>current package</I></A> is the <TT>KEYWORD</TT> package. Skipping over the <I>form</I> is accomplished by <A REL=DEFINITION HREF="glo_b.html#binding"><I>binding</I></A> <A REL=DEFINITION HREF="var_stread-suppressst.html#STread-suppressST"><B>*read-suppress*</B></A> to <A REL=DEFINITION HREF="glo_t.html#true"><I>true</I></A> and then calling <A REL=DEFINITION HREF="fun_readcm_re_g-whitespace.html#read"><B>read</B></A>. <P>
For examples, see <A REL=CHILD HREF="sec_24-1-2-1-1.html">Section 24.1.2.1.1 (Examples of Feature Expressions)</A>. <P>
<P><HR>The following <A REL=META HREF="../FrontMatter/X3J13-Issues.html">X3J13 cleanup issue</A>, <I>not part of the specification</I>, applies to this section:<P><UL><LI> <A REL=CHILD HREF="../Issues/iss318.html">SHARPSIGN-PLUS-MINUS-PACKAGE:KEYWORD</A><P></UL>
<HR>
<A REL=NAVIGATOR HREF="../FrontMatter/Starting-Points.html"><IMG ALT="[Starting Points]" SRC="../Graphics/Starting-Points.gif" ALIGN=Bottom></A><A REL=TOC HREF="../FrontMatter/Chapter-Index.html"><IMG ALT="[Contents]" SRC="../Graphics/Contents.gif" ALIGN=Bottom></A><A REL=INDEX HREF="../FrontMatter/Master-Index.html"><IMG ALT="[Index]" SRC="../Graphics/Index.gif" ALIGN=Bottom></A><A REL=INDEX HREF="../FrontMatter/Symbol-Index.html"><IMG ALT="[Symbols]" SRC="../Graphics/Symbols.gif" ALIGN=Bottom></A><A REL=GLOSSARY HREF="../Body/sec_26-1.html"><IMG ALT="[Glossary]" SRC="../Graphics/Glossary.gif" ALIGN=Bottom></A><A HREF="../Issues/Issues-Categorized.html"><IMG ALT="[Issues]" SRC="../Graphics/Issues.gif" ALIGN=Bottom></A><BR>
<A REL=COPYRIGHT HREF="../FrontMatter/About-HyperSpec.html#Legal"><I>Copyright 1996, The Harlequin Group Limited. All Rights Reserved.</I></A><P>
</BODY>
</HTML>
|
packages/NaturalSpec.1.4.2.1/docs/main.css | zoetrope/RosSharp | body {
margin: 0;
padding: 0;
font-family: Verdana,Arial,Helvetica,sans-serif;
font-size: 90%;
}
.header {
background: #048;
border-bottom: 3px solid #006;
margin: 0;
color: #FFF;
padding: 10px;
clear: left;
font-size: 13px;
}
.header p {
margin: 0 0 4px 0;
}
.header .class {
font-size: 24px;
font-weight: bold;
}
.header strong {
font-size: 13px;
width: 100px;
float: left;
}
.header a {
background: transparent;
color: #FFF;
}
.header a:hover {
background: #FFF;
color: #039;
}
.sub-header {
margin: 0 20px;
}
.sub-header ul {
margin: 0 0 0 30px;
padding: 0;
list-style: none;
}
.sub-header ul li {
float: left;
margin: 0 15px 0 0;
padding: 0;
text-indent: 0;
}
.section {
color: #333;
border-bottom: 1px solid #999;
margin: 10px 10px 0 10px;
padding: 10px 0 0 0;
clear: left;
}
div.method {
background: #EFEFEF;
border: 1px dotted #CCC;
margin: 5px 10px 15px 10px;
padding: 0;
}
div.method h4 {
background: #CCC;
border-bottom: 1px solid #666;
color: #000;
padding: 2px 5px;
margin: 0 0 10px 0;
font-weight: normal;
}
div.method h4 a {
background: transparent;
}
div.method .content {
padding: 0 10px 5px 10px;
}
div.parameters, div.return {
background: #fff;
border: 1px solid #ccc;
padding: 10px;
margin-top: 10px;
}
div.parameters h5, div.return h5 {
color: #666;
margin: -10px 0 0 -10px;
padding: 3px;
font-weight: normal;
font-size: 10px;
border-bottom: 1px solid #ccc;
border-right: 1px solid #ccc;
float: left;
}
div.parameters h6, div.return h6 {
clear: left;
font-size: 14px;
font-weight: normal;
margin: 0;
padding: 6px 0 3px 0;
}
div.parameters p, div.return p {
border-top: 1px solid #ccc;
margin: 0;
padding: 3px 3px 0 3px;
}
#summary {
background: #EFEFEF;
border: 1px dotted #999999;
margin: 5px 10px 15px 10px;
padding: 5px 10px;
}
#namespaces {
width: 50%;
float: left;
background: #FFF;
}
#types {
width: 50%;
float: left;
background: #FFF;
margin-left: -1px;
}
h2.fixed {
background: #CCC;
color: #000;
border-top: 1px solid #999;
border-bottom: 1px solid #999;
margin: 0;
padding: 2px 10px;
font-size: 12px;
font-weight: bold;
}
div.scroll {
overflow: scroll;
height: 150px;
}
#namespaces ul, #types ul {
list-style: none;
margin: 0 0 10px 0;
padding: 0;
}
#namespaces ul li, #types ul li {
text-indent: 0;
padding-left: 10px;
}
a {
background: #eef;
color: #039;
text-decoration: none;
}
a:hover {
color: #FFF;
background: #039;
}
#namespaces a.current, #types a.current {
background: #039;
color: #FFF;
text-decoration: none;
}
#footer {
text-align: center;
font-size: 10px;
color: #888;
clear: left;
padding-top: 10px;
}
blockquote {
margin: 10px;
padding: 6px;
background: #F5F5F5;
border-top: 3px solid #CCC;
border-bottom: 3px solid #CCC;
}
.value {
border-top-width: 1px;
border-bottom-width: 1px;
font-size: 90%;
} |
themes/pmem-hugo/layouts/pmemkv/single.html | pbalcer/pbalcer.github.io | {{ define "main" }}
<!-- silder -->
<section id="page-title" class="page-title-parallax page-title-center page-title-dark include-header skrollable skrollable-between" style="background-image: url('{{.Params.bg_image}}'); background-size: cover; padding: 120px 0px; margin-top: -157.05px">
<div class="container clearfix mt-4">
<div class="slider-title text-light">
<h2 style="color: white">{{ .Params.header | markdownify }}</h2>
</div>
</div>
</section>
<div class="section m-0 bg-transparent library-section dark-mode">
<div class="container">
<div class="row justify-content-between">
<div class="col mt-0 lib-content">
{{ .Content | replaceRE "<table>" "<table class=\"table table-bordered pmem-table dark-mode\">" | markdownify }}
</div>
</div>
<!-- disclaimer -->
<div class="divider"></div>
<p class="text-center"><small>{{ .Params.disclaimer | safeHTML }}</small></p>
<!-- end disclaimer -->
</div>
</div>
{{ end }} |
vendor/flot/examples/turning-series.html | antifuchs/autobench | <!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=utf-8">
<title>Flot Examples</title>
<link href="layout.css" rel="stylesheet" type="text/css"></link>
<!--[if IE]><script language="javascript" type="text/javascript" src="../excanvas.min.js"></script><![endif]-->
<script language="javascript" type="text/javascript" src="../jquery.js"></script>
<script language="javascript" type="text/javascript" src="../jquery.flot.js"></script>
</head>
<body>
<h1>Flot Examples</h1>
<div id="placeholder" style="width:600px;height:300px;"></div>
<p>Here is an example with real data: military budgets for
various countries in constant (2005) million US dollars (source: <a href="http://www.sipri.org/">SIPRI</a>).</p>
<p>Since all data is available client-side, it's pretty easy to
make the plot interactive. Try turning countries on/off with the
checkboxes below.</p>
<p id="choices">Show:</p>
<script id="source" language="javascript" type="text/javascript">
$(function () {
var datasets = {
"usa": {
label: "USA",
data: [[1988, 483994], [1989, 479060], [1990, 457648], [1991, 401949], [1992, 424705], [1993, 402375], [1994, 377867], [1995, 357382], [1996, 337946], [1997, 336185], [1998, 328611], [1999, 329421], [2000, 342172], [2001, 344932], [2002, 387303], [2003, 440813], [2004, 480451], [2005, 504638], [2006, 528692]]
},
"russia": {
label: "Russia",
data: [[1988, 218000], [1989, 203000], [1990, 171000], [1992, 42500], [1993, 37600], [1994, 36600], [1995, 21700], [1996, 19200], [1997, 21300], [1998, 13600], [1999, 14000], [2000, 19100], [2001, 21300], [2002, 23600], [2003, 25100], [2004, 26100], [2005, 31100], [2006, 34700]]
},
"uk": {
label: "UK",
data: [[1988, 62982], [1989, 62027], [1990, 60696], [1991, 62348], [1992, 58560], [1993, 56393], [1994, 54579], [1995, 50818], [1996, 50554], [1997, 48276], [1998, 47691], [1999, 47529], [2000, 47778], [2001, 48760], [2002, 50949], [2003, 57452], [2004, 60234], [2005, 60076], [2006, 59213]]
},
"germany": {
label: "Germany",
data: [[1988, 55627], [1989, 55475], [1990, 58464], [1991, 55134], [1992, 52436], [1993, 47139], [1994, 43962], [1995, 43238], [1996, 42395], [1997, 40854], [1998, 40993], [1999, 41822], [2000, 41147], [2001, 40474], [2002, 40604], [2003, 40044], [2004, 38816], [2005, 38060], [2006, 36984]]
},
"denmark": {
label: "Denmark",
data: [[1988, 3813], [1989, 3719], [1990, 3722], [1991, 3789], [1992, 3720], [1993, 3730], [1994, 3636], [1995, 3598], [1996, 3610], [1997, 3655], [1998, 3695], [1999, 3673], [2000, 3553], [2001, 3774], [2002, 3728], [2003, 3618], [2004, 3638], [2005, 3467], [2006, 3770]]
},
"sweden": {
label: "Sweden",
data: [[1988, 6402], [1989, 6474], [1990, 6605], [1991, 6209], [1992, 6035], [1993, 6020], [1994, 6000], [1995, 6018], [1996, 3958], [1997, 5780], [1998, 5954], [1999, 6178], [2000, 6411], [2001, 5993], [2002, 5833], [2003, 5791], [2004, 5450], [2005, 5521], [2006, 5271]]
},
"norway": {
label: "Norway",
data: [[1988, 4382], [1989, 4498], [1990, 4535], [1991, 4398], [1992, 4766], [1993, 4441], [1994, 4670], [1995, 4217], [1996, 4275], [1997, 4203], [1998, 4482], [1999, 4506], [2000, 4358], [2001, 4385], [2002, 5269], [2003, 5066], [2004, 5194], [2005, 4887], [2006, 4891]]
}
};
// hard-code color indices to prevent them from shifting as
// countries are turned on/off
var i = 0;
$.each(datasets, function(key, val) {
val.color = i;
++i;
});
// insert checkboxes
var choiceContainer = $("#choices");
$.each(datasets, function(key, val) {
choiceContainer.append('<br/><input type="checkbox" name="' + key +
'" checked="checked" >' + val.label + '</input>');
});
choiceContainer.find("input").click(plotAccordingToChoices);
function plotAccordingToChoices() {
var data = [];
choiceContainer.find("input:checked").each(function () {
var key = $(this).attr("name");
if (key && datasets[key])
data.push(datasets[key]);
});
if (data.length > 0)
$.plot($("#placeholder"), data, {
yaxis: { min: 0 },
xaxis: { tickDecimals: 0 }
});
}
plotAccordingToChoices();
});
</script>
</body>
</html>
|
src/olympia/devhub/templates/devhub/includes/addons_edit_nav.html | andymckay/addons-server | {% set urls = [
(addon.get_dev_url(), _('Edit Listing')),
(addon.get_dev_url('owner'), _('Manage Authors & License')),
(addon.get_dev_url('profile'), _('Manage Developer Profile')),
(addon.get_dev_url('payments'), _('Manage Payments')),
(addon.get_dev_url('versions'), _('Manage Status & Versions')),
] %}
<section class="secondary" role="complementary">
<div class="addon-status">
<img class="addon-icon" src="{{ addon.icon_url }}" alt="">
<ul class="addon-details">
{% include "devhub/includes/addon_details.html" %}
</ul>
<p class="addon-upload">
{% if not addon.is_incomplete() and not addon.is_disabled %}
<strong>
<a href="{{ addon.get_dev_url('versions') }}#version-upload" class="version-upload"
>{{ upload_file_label|default(_('Upload New Version')) }}</a>
</strong>
·
{% endif %}
<a href="{{ addon.get_dev_url('versions') }}">{{ _('View All' ) }}</a>
</p>
</div>
<div class="highlight" id="edit-addon-nav">
<ul class="refinements">
{% for url, title in urls %}
<li {% if url in request.path %}class="selected"{% endif %}>
<a href="{{ url }}">{{ title }}</a></li>
{% endfor %}
</ul>
<ul class="refinements">
{% if addon.is_listed %}<li><a href="{{ addon.get_url_path() }}">
{{ _('View Listing') }}</a></li>{% endif %}
<li><a href="{{ url('devhub.feed', addon.slug) }}">
{{ _('View Recent Changes') }}</a></li>
{% if not theme %}
<li class="view-stats"><a href="{{ url('stats.overview', addon.slug) }}">
{{ _('View Statistics Dashboard') }}</a></li>
<li class="compat-reports">
<a href="{{ url('compat.reporter_detail', addon.guid) }}">
<span>{{ _('Compatibility Reports') }}</span>
<br />
{% set compat_counts = get_compat_counts(addon) %}
<b class="failure" title="{{ _('{0} failure reports')|f(compat_counts.failure) }}">
{{ compat_counts.failure|numberfmt }}</b>
<b class="success" title="{{ _('{0} success reports')|f(compat_counts.success) }}">
{{ compat_counts.success|numberfmt }}</b>
</a>
</li>
{% endif %}
</ul>
</div>
</section>
|
app/templates/verification_email.html | ctsit/barebones-flask-app |
<p> Hello {{ user.get_name() }}, </p>
<p>
Please click on the provided link to verify your email for accessing the application.
<br />
<a href="{{ url_for('api_verify_email', tok=token, _external=True) }}">VERIFY EMAIL</a>
</p>
<p>Regards, </p>
<p> The support team. </p>
<a href="mailto:{{ sender }}"> {{ sender }} </a>
|
sjmiles/maker/maker2/dev/elements.html | PolymerLabs/labs | <link rel="import" href="/polymer/polymer-elements/polymer-layout/polymer-layout.html">
<link rel="import" href="/polymer/polymer-elements/polymer-grid-layout/polymer-grid-layout.html">
<link rel="import" href="/polymer/polymer-elements/polymer-ajax/polymer-ajax.html">
<link rel="import" href="/polymer/polymer-ui-elements/polymer-ui-toolbar/polymer-ui-toolbar.html">
<link rel="import" href="/polymer/polymer-ui-elements/polymer-ui-icon-button/polymer-ui-icon-button.html">
<link rel="import" href="/polymer/polymer-ui-elements/polymer-ui-menu-item/polymer-ui-menu-item.html">
<link rel="import" href="/polymer/polymer-ui-elements/polymer-ui-submenu-item/polymer-ui-submenu-item.html">
<link rel="import" href="/polymer/polymer-ui-elements/polymer-ui-menu/polymer-ui-menu.html">
<link rel="import" href="/polymer/polymer-ui-elements/polymer-ui-tabs/polymer-ui-tabs.html">
<link rel="import" href="/polymer/polymer-ui-elements/polymer-ui-pages/polymer-ui-pages.html">
<link rel="import" href="/polymer/polymer-ui-elements/polymer-ui-field/polymer-ui-field.html">
<link rel="import" href="/polymer/polymer-ui-elements/polymer-ui-overlay/polymer-ui-overlay.html">
<!--<link rel="import" href="/polymer/polymer-ui-elements/polymer-ui-menu-button/polymer-ui-menu-button.html">-->
<link rel="import" href="/polymer/more-elements/code-mirror/code-mirror.html">
<link rel="import" href="/polymer/labs/sjmiles/x-elements/x-meta/x-meta.html">
<link rel="import" href="/polymer/labs/sjmiles/x-elements/x-palette/x-palette.html">
<link rel="import" href="/polymer/labs/sjmiles/x-elements/x-designable/x-designable.html">
<link rel="import" href="/polymer/labs/sjmiles/x-elements/x-designer/x-designer.html">
<link rel="import" href="file-document.html">
|
v0.13.2/generated/statsmodels.sandbox.regression.gmm.IVGMMResults.ssr.html | statsmodels/statsmodels.github.io |
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="generator" content="Docutils 0.17.1: http://docutils.sourceforge.net/" />
<meta name="viewport" content="width=device-width,initial-scale=1">
<meta http-equiv="x-ua-compatible" content="ie=edge">
<meta name="lang:clipboard.copy" content="Copy to clipboard">
<meta name="lang:clipboard.copied" content="Copied to clipboard">
<meta name="lang:search.language" content="en">
<meta name="lang:search.pipeline.stopwords" content="True">
<meta name="lang:search.pipeline.trimmer" content="True">
<meta name="lang:search.result.none" content="No matching documents">
<meta name="lang:search.result.one" content="1 matching document">
<meta name="lang:search.result.other" content="# matching documents">
<meta name="lang:search.tokenizer" content="[\s\-]+">
<link href="https://fonts.gstatic.com/" rel="preconnect" crossorigin>
<link href="https://fonts.googleapis.com/css?family=Roboto+Mono:400,500,700|Roboto:300,400,400i,700&display=fallback" rel="stylesheet">
<style>
body,
input {
font-family: "Roboto", "Helvetica Neue", Helvetica, Arial, sans-serif
}
code,
kbd,
pre {
font-family: "Roboto Mono", "Courier New", Courier, monospace
}
</style>
<link rel="stylesheet" href="../_static/stylesheets/application.css"/>
<link rel="stylesheet" href="../_static/stylesheets/application-palette.css"/>
<link rel="stylesheet" href="../_static/stylesheets/application-fixes.css"/>
<link rel="stylesheet" href="../_static/fonts/material-icons.css"/>
<meta name="theme-color" content="#3f51b5">
<script src="../_static/javascripts/modernizr.js"></script>
<title>statsmodels.sandbox.regression.gmm.IVGMMResults.ssr — statsmodels</title>
<link rel="icon" type="image/png" sizes="32x32" href="../_static/icons/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="../_static/icons/favicon-16x16.png">
<link rel="manifest" href="../_static/icons/site.webmanifest">
<link rel="mask-icon" href="../_static/icons/safari-pinned-tab.svg" color="#919191">
<meta name="msapplication-TileColor" content="#2b5797">
<meta name="msapplication-config" content="../_static/icons/browserconfig.xml">
<link rel="stylesheet" href="../_static/stylesheets/examples.css">
<link rel="stylesheet" href="../_static/stylesheets/deprecation.css">
<link rel="stylesheet" type="text/css" href="../_static/pygments.css" />
<link rel="stylesheet" type="text/css" href="../_static/material.css" />
<link rel="stylesheet" type="text/css" href="../_static/graphviz.css" />
<link rel="stylesheet" type="text/css" href="../_static/plot_directive.css" />
<script data-url_root="../" id="documentation_options" src="../_static/documentation_options.js"></script>
<script src="../_static/jquery.js"></script>
<script src="../_static/underscore.js"></script>
<script src="../_static/doctools.js"></script>
<script crossorigin="anonymous" integrity="sha256-Ae2Vz/4ePdIu6ZyI/5ZGsYnb+m0JlOmKPjt6XZ9JJkA=" src="https://cdnjs.cloudflare.com/ajax/libs/require.js/2.3.4/require.min.js"></script>
<link rel="shortcut icon" href="../_static/favicon.ico"/>
<link rel="author" title="About these documents" href="../about.html" />
<link rel="index" title="Index" href="../genindex.html" />
<link rel="search" title="Search" href="../search.html" />
<link rel="next" title="statsmodels.sandbox.regression.gmm.IVGMMResults.tvalues" href="statsmodels.sandbox.regression.gmm.IVGMMResults.tvalues.html" />
<link rel="prev" title="statsmodels.sandbox.regression.gmm.IVGMMResults.resid" href="statsmodels.sandbox.regression.gmm.IVGMMResults.resid.html" />
</head>
<body dir=ltr
data-md-color-primary=indigo data-md-color-accent=blue>
<svg class="md-svg">
<defs data-children-count="0">
<svg xmlns="http://www.w3.org/2000/svg" width="416" height="448" viewBox="0 0 416 448" id="__github"><path fill="currentColor" d="M160 304q0 10-3.125 20.5t-10.75 19T128 352t-18.125-8.5-10.75-19T96 304t3.125-20.5 10.75-19T128 256t18.125 8.5 10.75 19T160 304zm160 0q0 10-3.125 20.5t-10.75 19T288 352t-18.125-8.5-10.75-19T256 304t3.125-20.5 10.75-19T288 256t18.125 8.5 10.75 19T320 304zm40 0q0-30-17.25-51T296 232q-10.25 0-48.75 5.25Q229.5 240 208 240t-39.25-2.75Q130.75 232 120 232q-29.5 0-46.75 21T56 304q0 22 8 38.375t20.25 25.75 30.5 15 35 7.375 37.25 1.75h42q20.5 0 37.25-1.75t35-7.375 30.5-15 20.25-25.75T360 304zm56-44q0 51.75-15.25 82.75-9.5 19.25-26.375 33.25t-35.25 21.5-42.5 11.875-42.875 5.5T212 416q-19.5 0-35.5-.75t-36.875-3.125-38.125-7.5-34.25-12.875T37 371.5t-21.5-28.75Q0 312 0 260q0-59.25 34-99-6.75-20.5-6.75-42.5 0-29 12.75-54.5 27 0 47.5 9.875t47.25 30.875Q171.5 96 212 96q37 0 70 8 26.25-20.5 46.75-30.25T376 64q12.75 25.5 12.75 54.5 0 21.75-6.75 42 34 40 34 99.5z"/></svg>
</defs>
</svg>
<input class="md-toggle" data-md-toggle="drawer" type="checkbox" id="__drawer">
<input class="md-toggle" data-md-toggle="search" type="checkbox" id="__search">
<label class="md-overlay" data-md-component="overlay" for="__drawer"></label>
<a href="#generated/statsmodels.sandbox.regression.gmm.IVGMMResults.ssr" tabindex="1" class="md-skip"> Skip to content </a>
<header class="md-header" data-md-component="header">
<nav class="md-header-nav md-grid">
<div class="md-flex navheader">
<div class="md-flex__cell md-flex__cell--shrink">
<a href="../index.html" title="statsmodels"
class="md-header-nav__button md-logo">
<img src="../_static/statsmodels-logo-v2-bw.svg" height="26"
alt="statsmodels logo">
</a>
</div>
<div class="md-flex__cell md-flex__cell--shrink">
<label class="md-icon md-icon--menu md-header-nav__button" for="__drawer"></label>
</div>
<div class="md-flex__cell md-flex__cell--stretch">
<div class="md-flex__ellipsis md-header-nav__title" data-md-component="title">
<span class="md-header-nav__topic">statsmodels v0.13.2</span>
<span class="md-header-nav__topic"> statsmodels.sandbox.regression.gmm.IVGMMResults.ssr </span>
</div>
</div>
<div class="md-flex__cell md-flex__cell--shrink">
<label class="md-icon md-icon--search md-header-nav__button" for="__search"></label>
<div class="md-search" data-md-component="search" role="dialog">
<label class="md-search__overlay" for="__search"></label>
<div class="md-search__inner" role="search">
<form class="md-search__form" action="../search.html" method="get" name="search">
<input type="text" class="md-search__input" name="q" placeholder="Search"
autocapitalize="off" autocomplete="off" spellcheck="false"
data-md-component="query" data-md-state="active">
<label class="md-icon md-search__icon" for="__search"></label>
<button type="reset" class="md-icon md-search__icon" data-md-component="reset" tabindex="-1">

</button>
</form>
<div class="md-search__output">
<div class="md-search__scrollwrap" data-md-scrollfix>
<div class="md-search-result" data-md-component="result">
<div class="md-search-result__meta">
Type to start searching
</div>
<ol class="md-search-result__list"></ol>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="md-flex__cell md-flex__cell--shrink">
<div class="md-header-nav__source">
<a href="https://github.com/statsmodels/statsmodels" title="Go to repository" class="md-source" data-md-source="github">
<div class="md-source__icon">
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" viewBox="0 0 24 24" width="28" height="28">
<use xlink:href="#__github" width="24" height="24"></use>
</svg>
</div>
<div class="md-source__repository">
statsmodels
</div>
</a>
</div>
</div>
<script src="../_static/javascripts/version_dropdown.js"></script>
<script>
var json_loc = "../../versions-v2.json",
target_loc = "../../",
text = "Versions";
$( document ).ready( add_version_dropdown(json_loc, target_loc, text));
</script>
</div>
</nav>
</header>
<div class="md-container">
<nav class="md-tabs" data-md-component="tabs">
<div class="md-tabs__inner md-grid">
<ul class="md-tabs__list">
<li class="md-tabs__item"><a href="../user-guide.html" class="md-tabs__link">User Guide</a></li>
<li class="md-tabs__item"><a href="../gmm.html" class="md-tabs__link">Generalized Method of Moments <code class="xref py py-mod docutils literal notranslate"><span class="pre">gmm</span></code></a></li>
<li class="md-tabs__item"><a href="statsmodels.sandbox.regression.gmm.IVGMMResults.html" class="md-tabs__link">statsmodels.sandbox.regression.gmm.IVGMMResults</a></li>
</ul>
</div>
</nav>
<main class="md-main">
<div class="md-main__inner md-grid" data-md-component="container">
<div class="md-sidebar md-sidebar--primary" data-md-component="navigation">
<div class="md-sidebar__scrollwrap">
<div class="md-sidebar__inner">
<nav class="md-nav md-nav--primary" data-md-level="0">
<label class="md-nav__title md-nav__title--site" for="__drawer">
<a href="../index.html" title="statsmodels" class="md-nav__button md-logo">
<img src="../_static/statsmodels-logo-v2-bw.svg" alt=" logo" width="48" height="48">
</a>
<a href="../index.html"
title="statsmodels">statsmodels v0.13.2</a>
</label>
<div class="md-nav__source">
<a href="https://github.com/statsmodels/statsmodels" title="Go to repository" class="md-source" data-md-source="github">
<div class="md-source__icon">
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" viewBox="0 0 24 24" width="28" height="28">
<use xlink:href="#__github" width="24" height="24"></use>
</svg>
</div>
<div class="md-source__repository">
statsmodels
</div>
</a>
</div>
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="../install.html" class="md-nav__link">Installing statsmodels</a>
</li>
<li class="md-nav__item">
<a href="../gettingstarted.html" class="md-nav__link">Getting started</a>
</li>
<li class="md-nav__item">
<a href="../user-guide.html" class="md-nav__link">User Guide</a>
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="../user-guide.html#background" class="md-nav__link">Background</a>
</li>
<li class="md-nav__item">
<a href="../user-guide.html#regression-and-linear-models" class="md-nav__link">Regression and Linear Models</a>
</li>
<li class="md-nav__item">
<a href="../user-guide.html#time-series-analysis" class="md-nav__link">Time Series Analysis</a>
</li>
<li class="md-nav__item">
<a href="../user-guide.html#other-models" class="md-nav__link">Other Models</a>
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="../duration.html" class="md-nav__link">Methods for Survival and Duration Analysis</a>
</li>
<li class="md-nav__item">
<a href="../nonparametric.html" class="md-nav__link">Nonparametric Methods <code class="xref py py-mod docutils literal notranslate"><span class="pre">nonparametric</span></code></a>
</li>
<li class="md-nav__item">
<a href="../gmm.html" class="md-nav__link">Generalized Method of Moments <code class="xref py py-mod docutils literal notranslate"><span class="pre">gmm</span></code></a>
</li>
<li class="md-nav__item">
<a href="../miscmodels.html" class="md-nav__link">Other Models <code class="xref py py-mod docutils literal notranslate"><span class="pre">miscmodels</span></code></a>
</li>
<li class="md-nav__item">
<a href="../multivariate.html" class="md-nav__link">Multivariate Statistics <code class="xref py py-mod docutils literal notranslate"><span class="pre">multivariate</span></code></a>
</li></ul>
</li>
<li class="md-nav__item">
<a href="../user-guide.html#statistics-and-tools" class="md-nav__link">Statistics and Tools</a>
</li>
<li class="md-nav__item">
<a href="../user-guide.html#data-sets" class="md-nav__link">Data Sets</a>
</li>
<li class="md-nav__item">
<a href="../user-guide.html#sandbox" class="md-nav__link">Sandbox</a>
</li></ul>
</li>
<li class="md-nav__item">
<a href="../examples/index.html" class="md-nav__link">Examples</a>
</li>
<li class="md-nav__item">
<a href="../api.html" class="md-nav__link">API Reference</a>
</li>
<li class="md-nav__item">
<a href="../about.html" class="md-nav__link">About statsmodels</a>
</li>
<li class="md-nav__item">
<a href="../dev/index.html" class="md-nav__link">Developer Page</a>
</li>
<li class="md-nav__item">
<a href="../release/index.html" class="md-nav__link">Release Notes</a>
</li>
</ul>
</nav>
</div>
</div>
</div>
<div class="md-sidebar md-sidebar--secondary" data-md-component="toc">
<div class="md-sidebar__scrollwrap">
<div class="md-sidebar__inner">
<nav class="md-nav md-nav--secondary">
<ul class="md-nav__list" data-md-scrollfix="">
<li class="md-nav__item"><a class="md-nav__extra_link" href="../_sources/generated/statsmodels.sandbox.regression.gmm.IVGMMResults.ssr.rst.txt">Show Source</a> </li>
<li id="searchbox" class="md-nav__item"></li>
</ul>
</nav>
</div>
</div>
</div>
<div class="md-content">
<article class="md-content__inner md-typeset" role="main">
<section id="statsmodels-sandbox-regression-gmm-ivgmmresults-ssr">
<h1 id="generated-statsmodels-sandbox-regression-gmm-ivgmmresults-ssr--page-root">statsmodels.sandbox.regression.gmm.IVGMMResults.ssr<a class="headerlink" href="#generated-statsmodels-sandbox-regression-gmm-ivgmmresults-ssr--page-root" title="Permalink to this headline">¶</a></h1>
<dl class="py attribute">
<dt class="sig sig-object py" id="statsmodels.sandbox.regression.gmm.IVGMMResults.ssr">
<span class="sig-prename descclassname"><span class="pre">IVGMMResults.</span></span><span class="sig-name descname"><span class="pre">ssr</span></span><a class="headerlink" href="#statsmodels.sandbox.regression.gmm.IVGMMResults.ssr" title="Permalink to this definition">¶</a></dt>
<dd><p>Sum of square errors</p>
</dd></dl>
</section>
</article>
</div>
</div>
</main>
</div>
<footer class="md-footer">
<div class="md-footer-nav">
<nav class="md-footer-nav__inner md-grid">
<a href="statsmodels.sandbox.regression.gmm.IVGMMResults.resid.html" title="statsmodels.sandbox.regression.gmm.IVGMMResults.resid"
class="md-flex md-footer-nav__link md-footer-nav__link--prev"
rel="prev">
<div class="md-flex__cell md-flex__cell--shrink">
<i class="md-icon md-icon--arrow-back md-footer-nav__button"></i>
</div>
<div class="md-flex__cell md-flex__cell--stretch md-footer-nav__title">
<span class="md-flex__ellipsis">
<span
class="md-footer-nav__direction"> Previous </span> statsmodels.sandbox.regression.gmm.IVGMMResults.resid </span>
</div>
</a>
<a href="statsmodels.sandbox.regression.gmm.IVGMMResults.tvalues.html" title="statsmodels.sandbox.regression.gmm.IVGMMResults.tvalues"
class="md-flex md-footer-nav__link md-footer-nav__link--next"
rel="next">
<div class="md-flex__cell md-flex__cell--stretch md-footer-nav__title"><span
class="md-flex__ellipsis"> <span
class="md-footer-nav__direction"> Next </span> statsmodels.sandbox.regression.gmm.IVGMMResults.tvalues </span>
</div>
<div class="md-flex__cell md-flex__cell--shrink"><i
class="md-icon md-icon--arrow-forward md-footer-nav__button"></i>
</div>
</a>
</nav>
</div>
<div class="md-footer-meta md-typeset">
<div class="md-footer-meta__inner md-grid">
<div class="md-footer-copyright">
<div class="md-footer-copyright__highlight">
© Copyright 2009-2019, Josef Perktold, Skipper Seabold, Jonathan Taylor, statsmodels-developers.
</div>
Last updated on
Feb 08, 2022.
<br/>
Created using
<a href="http://www.sphinx-doc.org/">Sphinx</a> 4.4.0.
and
<a href="https://github.com/bashtage/sphinx-material/">Material for
Sphinx</a>
</div>
</div>
</div>
</footer>
<script src="../_static/javascripts/application.js"></script>
<script>app.initialize({version: "1.0.4", url: {base: ".."}})</script>
</body>
</html> |
bak/bpoc/index.html | mwharris333/webgl-poc | <html>
<head>
<style>
canvas {
padding-left: 0;
padding-right: 0;
margin-left: auto;
margin-right: auto;
display: block;
background-color: rgba(0,0,0,1);
}
</style>
<script src="glUtil.js"></script>
<script src="main.js"></script>
<!-- =========================================================== -->
<script id="VertexShader" type="Vertex-Shader">
attribute vec2 position;
void main() {
gl_Position = vec4(position, 0, 1);
}
</script>
<!-- =========================================================== -->
<script id="FragmentShader" type="Fragment-Shader">
void main() {
gl_FragColor = vec4(0,0,1,1); // green
}
</script>
<!-- =========================================================== -->
</head>
<body onload="main();">
<canvas id="glCanvas"></canvas>
</body>
</html> |
docs/apidocs/net/sourceforge/pmd/jsp/ast/class-use/CharStream.html | pscadiz/pmd-4.2.6-gds | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<!--NewPage-->
<HTML>
<HEAD>
<!-- Generated by javadoc (build 1.6.0_22) on Wed Sep 14 22:21:33 CEST 2011 -->
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<TITLE>
Uses of Interface net.sourceforge.pmd.jsp.ast.CharStream (PMD 4.2.6 API)
</TITLE>
<META NAME="date" CONTENT="2011-09-14">
<LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
<SCRIPT type="text/javascript">
function windowTitle()
{
if (location.href.indexOf('is-external=true') == -1) {
parent.document.title="Uses of Interface net.sourceforge.pmd.jsp.ast.CharStream (PMD 4.2.6 API)";
}
}
</SCRIPT>
<NOSCRIPT>
</NOSCRIPT>
</HEAD>
<BODY BGCOLOR="white" onload="windowTitle();">
<HR>
<!-- ========= START OF TOP NAVBAR ======= -->
<A NAME="navbar_top"><!-- --></A>
<A HREF="#skip-navbar_top" title="Skip navigation links"></A>
<TABLE BORDER="0" WIDTH="100%" CELLPADDING="1" CELLSPACING="0" SUMMARY="">
<TR>
<TD COLSPAN=2 BGCOLOR="#EEEEFF" CLASS="NavBarCell1">
<A NAME="navbar_top_firstrow"><!-- --></A>
<TABLE BORDER="0" CELLPADDING="0" CELLSPACING="3" SUMMARY="">
<TR ALIGN="center" VALIGN="top">
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../../../../../../overview-summary.html"><FONT CLASS="NavBarFont1"><B>Overview</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../package-summary.html"><FONT CLASS="NavBarFont1"><B>Package</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/CharStream.html" title="interface in net.sourceforge.pmd.jsp.ast"><FONT CLASS="NavBarFont1"><B>Class</B></FONT></A> </TD>
<TD BGCOLOR="#FFFFFF" CLASS="NavBarCell1Rev"> <FONT CLASS="NavBarFont1Rev"><B>Use</B></FONT> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../package-tree.html"><FONT CLASS="NavBarFont1"><B>Tree</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../../../../../../deprecated-list.html"><FONT CLASS="NavBarFont1"><B>Deprecated</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../../../../../../index-all.html"><FONT CLASS="NavBarFont1"><B>Index</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../../../../../../help-doc.html"><FONT CLASS="NavBarFont1"><B>Help</B></FONT></A> </TD>
</TR>
</TABLE>
</TD>
<TD ALIGN="right" VALIGN="top" ROWSPAN=3><EM>
</EM>
</TD>
</TR>
<TR>
<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
PREV
NEXT</FONT></TD>
<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
<A HREF="../../../../../../index.html?net/sourceforge/pmd/jsp/ast//class-useCharStream.html" target="_top"><B>FRAMES</B></A>
<A HREF="CharStream.html" target="_top"><B>NO FRAMES</B></A>
<SCRIPT type="text/javascript">
<!--
if(window==top) {
document.writeln('<A HREF="../../../../../../allclasses-noframe.html"><B>All Classes</B></A>');
}
//-->
</SCRIPT>
<NOSCRIPT>
<A HREF="../../../../../../allclasses-noframe.html"><B>All Classes</B></A>
</NOSCRIPT>
</FONT></TD>
</TR>
</TABLE>
<A NAME="skip-navbar_top"></A>
<!-- ========= END OF TOP NAVBAR ========= -->
<HR>
<CENTER>
<H2>
<B>Uses of Interface<br>net.sourceforge.pmd.jsp.ast.CharStream</B></H2>
</CENTER>
<TABLE BORDER="1" WIDTH="100%" CELLPADDING="3" CELLSPACING="0" SUMMARY="">
<TR BGCOLOR="#CCCCFF" CLASS="TableHeadingColor">
<TH ALIGN="left" COLSPAN="2"><FONT SIZE="+2">
Packages that use <A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/CharStream.html" title="interface in net.sourceforge.pmd.jsp.ast">CharStream</A></FONT></TH>
</TR>
<TR BGCOLOR="white" CLASS="TableRowColor">
<TD><A HREF="#net.sourceforge.pmd.jsp.ast"><B>net.sourceforge.pmd.jsp.ast</B></A></TD>
<TD> </TD>
</TR>
</TABLE>
<P>
<A NAME="net.sourceforge.pmd.jsp.ast"><!-- --></A>
<TABLE BORDER="1" WIDTH="100%" CELLPADDING="3" CELLSPACING="0" SUMMARY="">
<TR BGCOLOR="#CCCCFF" CLASS="TableHeadingColor">
<TH ALIGN="left" COLSPAN="2"><FONT SIZE="+2">
Uses of <A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/CharStream.html" title="interface in net.sourceforge.pmd.jsp.ast">CharStream</A> in <A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/package-summary.html">net.sourceforge.pmd.jsp.ast</A></FONT></TH>
</TR>
</TABLE>
<P>
<TABLE BORDER="1" WIDTH="100%" CELLPADDING="3" CELLSPACING="0" SUMMARY="">
<TR BGCOLOR="#CCCCFF" CLASS="TableSubHeadingColor">
<TH ALIGN="left" COLSPAN="2">Fields in <A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/package-summary.html">net.sourceforge.pmd.jsp.ast</A> declared as <A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/CharStream.html" title="interface in net.sourceforge.pmd.jsp.ast">CharStream</A></FONT></TH>
</TR>
<TR BGCOLOR="white" CLASS="TableRowColor">
<TD ALIGN="right" VALIGN="top" WIDTH="1%"><FONT SIZE="-1">
<CODE>protected <A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/CharStream.html" title="interface in net.sourceforge.pmd.jsp.ast">CharStream</A></CODE></FONT></TD>
<TD><CODE><B>JspParserTokenManager.</B><B><A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/JspParserTokenManager.html#input_stream">input_stream</A></B></CODE>
<BR>
</TD>
</TR>
</TABLE>
<P>
<TABLE BORDER="1" WIDTH="100%" CELLPADDING="3" CELLSPACING="0" SUMMARY="">
<TR BGCOLOR="#CCCCFF" CLASS="TableSubHeadingColor">
<TH ALIGN="left" COLSPAN="2">Methods in <A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/package-summary.html">net.sourceforge.pmd.jsp.ast</A> with parameters of type <A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/CharStream.html" title="interface in net.sourceforge.pmd.jsp.ast">CharStream</A></FONT></TH>
</TR>
<TR BGCOLOR="white" CLASS="TableRowColor">
<TD ALIGN="right" VALIGN="top" WIDTH="1%"><FONT SIZE="-1">
<CODE> void</CODE></FONT></TD>
<TD><CODE><B>JspParserTokenManager.</B><B><A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/JspParserTokenManager.html#ReInit(net.sourceforge.pmd.jsp.ast.CharStream)">ReInit</A></B>(<A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/CharStream.html" title="interface in net.sourceforge.pmd.jsp.ast">CharStream</A> stream)</CODE>
<BR>
Reinitialise parser.</TD>
</TR>
<TR BGCOLOR="white" CLASS="TableRowColor">
<TD ALIGN="right" VALIGN="top" WIDTH="1%"><FONT SIZE="-1">
<CODE> void</CODE></FONT></TD>
<TD><CODE><B>JspParser.</B><B><A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/JspParser.html#ReInit(net.sourceforge.pmd.jsp.ast.CharStream)">ReInit</A></B>(<A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/CharStream.html" title="interface in net.sourceforge.pmd.jsp.ast">CharStream</A> stream)</CODE>
<BR>
Reinitialise.</TD>
</TR>
<TR BGCOLOR="white" CLASS="TableRowColor">
<TD ALIGN="right" VALIGN="top" WIDTH="1%"><FONT SIZE="-1">
<CODE> void</CODE></FONT></TD>
<TD><CODE><B>JspParserTokenManager.</B><B><A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/JspParserTokenManager.html#ReInit(net.sourceforge.pmd.jsp.ast.CharStream, int)">ReInit</A></B>(<A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/CharStream.html" title="interface in net.sourceforge.pmd.jsp.ast">CharStream</A> stream,
int lexState)</CODE>
<BR>
Reinitialise parser.</TD>
</TR>
</TABLE>
<P>
<TABLE BORDER="1" WIDTH="100%" CELLPADDING="3" CELLSPACING="0" SUMMARY="">
<TR BGCOLOR="#CCCCFF" CLASS="TableSubHeadingColor">
<TH ALIGN="left" COLSPAN="2">Constructors in <A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/package-summary.html">net.sourceforge.pmd.jsp.ast</A> with parameters of type <A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/CharStream.html" title="interface in net.sourceforge.pmd.jsp.ast">CharStream</A></FONT></TH>
</TR>
<TR BGCOLOR="white" CLASS="TableRowColor">
<TD><CODE><B><A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/JspParser.html#JspParser(net.sourceforge.pmd.jsp.ast.CharStream)">JspParser</A></B>(<A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/CharStream.html" title="interface in net.sourceforge.pmd.jsp.ast">CharStream</A> stream)</CODE>
<BR>
Constructor with user supplied CharStream.</TD>
</TR>
<TR BGCOLOR="white" CLASS="TableRowColor">
<TD><CODE><B><A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/JspParserTokenManager.html#JspParserTokenManager(net.sourceforge.pmd.jsp.ast.CharStream)">JspParserTokenManager</A></B>(<A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/CharStream.html" title="interface in net.sourceforge.pmd.jsp.ast">CharStream</A> stream)</CODE>
<BR>
Constructor.</TD>
</TR>
<TR BGCOLOR="white" CLASS="TableRowColor">
<TD><CODE><B><A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/JspParserTokenManager.html#JspParserTokenManager(net.sourceforge.pmd.jsp.ast.CharStream, int)">JspParserTokenManager</A></B>(<A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/CharStream.html" title="interface in net.sourceforge.pmd.jsp.ast">CharStream</A> stream,
int lexState)</CODE>
<BR>
Constructor.</TD>
</TR>
</TABLE>
<P>
<HR>
<!-- ======= START OF BOTTOM NAVBAR ====== -->
<A NAME="navbar_bottom"><!-- --></A>
<A HREF="#skip-navbar_bottom" title="Skip navigation links"></A>
<TABLE BORDER="0" WIDTH="100%" CELLPADDING="1" CELLSPACING="0" SUMMARY="">
<TR>
<TD COLSPAN=2 BGCOLOR="#EEEEFF" CLASS="NavBarCell1">
<A NAME="navbar_bottom_firstrow"><!-- --></A>
<TABLE BORDER="0" CELLPADDING="0" CELLSPACING="3" SUMMARY="">
<TR ALIGN="center" VALIGN="top">
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../../../../../../overview-summary.html"><FONT CLASS="NavBarFont1"><B>Overview</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../package-summary.html"><FONT CLASS="NavBarFont1"><B>Package</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../../../../../../net/sourceforge/pmd/jsp/ast/CharStream.html" title="interface in net.sourceforge.pmd.jsp.ast"><FONT CLASS="NavBarFont1"><B>Class</B></FONT></A> </TD>
<TD BGCOLOR="#FFFFFF" CLASS="NavBarCell1Rev"> <FONT CLASS="NavBarFont1Rev"><B>Use</B></FONT> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../package-tree.html"><FONT CLASS="NavBarFont1"><B>Tree</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../../../../../../deprecated-list.html"><FONT CLASS="NavBarFont1"><B>Deprecated</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../../../../../../index-all.html"><FONT CLASS="NavBarFont1"><B>Index</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../../../../../../help-doc.html"><FONT CLASS="NavBarFont1"><B>Help</B></FONT></A> </TD>
</TR>
</TABLE>
</TD>
<TD ALIGN="right" VALIGN="top" ROWSPAN=3><EM>
</EM>
</TD>
</TR>
<TR>
<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
PREV
NEXT</FONT></TD>
<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
<A HREF="../../../../../../index.html?net/sourceforge/pmd/jsp/ast//class-useCharStream.html" target="_top"><B>FRAMES</B></A>
<A HREF="CharStream.html" target="_top"><B>NO FRAMES</B></A>
<SCRIPT type="text/javascript">
<!--
if(window==top) {
document.writeln('<A HREF="../../../../../../allclasses-noframe.html"><B>All Classes</B></A>');
}
//-->
</SCRIPT>
<NOSCRIPT>
<A HREF="../../../../../../allclasses-noframe.html"><B>All Classes</B></A>
</NOSCRIPT>
</FONT></TD>
</TR>
</TABLE>
<A NAME="skip-navbar_bottom"></A>
<!-- ======== END OF BOTTOM NAVBAR ======= -->
<HR>
Copyright © 2002-2011 InfoEther. All Rights Reserved.
</BODY>
</HTML>
|
nuttx/Documentation/NuttxPortingGuide.html | gcds/project_xxx | <html>
<head>
<title>NuttX Porting Guide</title>
<meta name="author" content="Gregory Nutt">
</head>
<body background="backgd.gif">
<hr><hr>
<table width ="100%">
<tr align="center" bgcolor="#e4e4e4">
<td>
<h1><big><font color="#3c34ec">
<i>NuttX RTOS Porting Guide</i>
</font></big></h1>
<p>Last Updated: August 13, 2013</p>
</td>
</tr>
</table>
<hr><hr>
<table width ="100%">
<tr bgcolor="#e4e4e4">
<td>
<h1>Table of Contents</h1>
</td>
</tr>
</table>
<ul>
<a href="#Introduction">1.0 Introduction</a><br>
<a href="#DirectoryStructure">2.0 Directory Structure</a>
<ul>
<a href="#DirStructDocumentation">2.1 Documentation</a></br>
<a href="#DirStructArch">2.2 arch/</a>
<ul>
<a href="#archdirectorystructure">2.2.1 Subdirectory Structure</a><br>
<a href="#summaryofarchfiles">2.2.2 Summary of Files</a><br>
<a href="#supportedarchitectures">2.2.3 Supported Architectures</a>
</ul>
<a href="#DirStructBinFmt">2.3 binfmt/</a><br>
<a href="#DirStructConfigs">2.4 configs/</a>
<ul>
<a href="#configsdirectorystructure">2.4.1 Subdirectory Structure</a><br>
<a href="#summaryofconfigfiles">2.4.2 Summary of Files</a>
<ul>
<a href="#boardlogic">2.4.2.1 Board Specific Logic</a><br>
<a href="#boardconfigsubdirs">2.4.2.2 Board Specific Configuration Sub-Directories</a>
</ul>
<a href="#supportedboards">2.4.3 Supported Boards</a><br>
<a href="#newboardconfig">2.4.4 Adding a New Board Configuration</a>
</ul>
<a href="#DirStructDrivers">2.5 nuttx/drivers/</a><br>
<a href="#DirStructFs">2.6 nuttx/fs/</a><br>
<a href="#DirStructGraphics">2.7 nuttx/graphics/</a><br>
<a href="#DirStructInclude">2.8 nuttx/include/</a><br>
<a href="#DirStructLib">2.9 nuttx/libc/</a><br>
<a href="#DirStructLibXX">2.10 nuttx/libxx/</a><br>
<a href="#DirStructMm">2.11 nuttx/mm/</a><br>
<a href="#DirStructNet">2.12 nuttx/net</a><br>
<a href="#DirStructSched">2.13 nuttx/sched/</a><br>
<a href="#DirStructSyscall">2.14 nuttx/syscall/</a><br>
<a href="#DirStructTools">2.15 nuttx/tools/</a><br>
<a href="#topmakefile">2.16 nuttx/Makefile</a><br>
<a href="#DirStructNetUtils">2.17 apps/netutils</a><br>
<a href="#DirStructNshLib">2.18 apps/nshlib</a><br>
<a href="#DirStructExamples">2.19 apps/examples/</a>
</ul>
<a href="#configandbuild">3.0 Configuring and Building</a>
<ul>
<a href="#configuringnuttx">3.1 Configuring NuttX</a><br>
<a href="#buildingnuttx">3.2 Building NuttX</a>
</ul>
<a href="#ArchAPIs">4.0 Architecture APIs</a>
<ul>
<a href="#imports">4.1 APIs Exported by Architecture-Specific Logic to NuttX</a>
<ul>
<a href="#upinitialize">4.1.1 <code>up_initialize()</code></a><br>
<a href="#upidle">4.1.2 <code>up_idle()</code></a><br>
<a href="#upinitialstate">4.1.3 <code>up_initial_state()</code></a><br>
<a href="#upcreatestack">4.1.4 <code>up_create_stack()</code></a><br>
<a href="#upusestack">4.1.5 <code>up_use_stack()</code></a><br>
<a href="#upstackframe">4.1.6 <code>up_stack_frame()</code></a><br>
<a href="#upreleasestack">4.1.7 <code>up_release_stack()</code></a><br>
<a href="#upunblocktask">4.1.8 <code>up_unblock_task()</code></a><br>
<a href="#upblocktask">4.1.9 <code>up_block_task()</code></a><br>
<a href="#upreleasepending">4.1.10 <code>up_release_pending()</code></a><br>
<a href="#upreprioritizertr">4.1.11 <code>up_reprioritize_rtr()</code></a><br>
<a href="#_exit">4.1.12 <code>_exit()</code></a><br>
<a href="#upassert">4.1.13 <code>up_assert()</code></a><br>
<a href="#upschedulesigaction">4.1.14 <code>up_schedule_sigaction()</code></a><br>
<a href="#upallocateheap">4.1.15 <code>up_allocate_heap()</code></a><br>
<a href="#upinterruptcontext">4.1.16 <code>up_interrupt_context()</code></a><br>
<a href="#updisableirq">4.1.17 <code>up_disable_irq()</code></a><br>
<a href="#upenableirq">4.1.18 <code>up_enable_irq()</code></a><br>
<a href="#upprioritizeirq">4.1.19 <code>up_prioritize_irq()</code></a></br>
<a href="#upputc">4.1.20 <code>up_putc()</code></a></br>
<a href="#systemtime">4.1.21 System Time and Clock</a><br>
<a href="#addrenv">4.1.22 Address Environments</a>
</ul>
<a href="#exports">4.2 APIs Exported by NuttX to Architecture-Specific Logic</a>
<ul>
<a href="#osstart">4.2.1 <code>os_start()</code></a><br>
<a href="#listmgmt">4.2.2 OS List Management APIs</a><br>
<a href="#schedprocesstimer">4.2.3 <code>sched_process_timer()</code></a><br>
<a href="#irqdispatch">4.2.4 <code>irq_dispatch()</code></a>
</ul>
<a href="#demandpaging">4.3 On-Demand Paging</a><br>
<a href="#ledsupport">4.4 LED Support</a>
<ul>
<a href="#ledheaders">4.3.1 Header Files</a><br>
<a href="#leddefinitions">4.3.2 LED Definitions</a><br>
<a href="#ledapis">4.3.3 Common LED interfaces</a>
</ul>
</ul>
<a href="#NxFileSystem">5.0 NuttX File System</a><br>
<a href="#DeviceDrivers">6.0 NuttX Device Drivers</a>
<ul>
<a href="#chardrivers">6.1 Character Device Drivers</a><br>
<a href="#blockdrivers">6.2 Block Device Drivers</a><br>
<a href="#blockdrivers">6.3 Specialized Device Drivers</a>
<ul>
<a href="#ethdrivers">6.3.1 Ethernet Device Drivers</a><br>
<a href="#spidrivers">6.3.2 SPI Device Drivers</a><br>
<a href="#i2cdrivers">6.3.3 I2C Device Drivers</a><br>
<a href="#serialdrivers">6.3.4 Serial Device Drivers</a><br>
<a href="#fbdrivers">6.3.5 Frame Buffer Drivers</a><br>
<a href="#lcddrivers">6.3.6 LCD Drivers</a><br>
<a href="#mtddrivers">6.3.7 Memory Technology Device Drivers</a><br>
<a href="#sdiodrivers">6.3.8 SDIO Device Drivers</a><br>
<a href="#usbhostdrivers">6.3.9 USB Host-Side Drivers</a><br>
<a href="#usbdevdrivers">6.3.10 USB Device-Side Drivers</a><br>
<a href="#analogdrivers">6.3.11 Analog (ADC/DAC) Drivers</a><br>
<a href="#pwmdrivers">6.3.12 PWM Drivers</a><br>
<a href="#candrivers">6.3.13 CAN Drivers</a><br>
<a href="#quadencoder">6.3.14 Quadrature Encoder Drivers</a><br>
<a href="#wdogdriver">6.3.15 Watchdog Timer Drivers</a><br>
<a href="#kbddriver">6.3.16 Keyboard/Keypad Drivers</a><br>
</ul>
<a href="#pwrmgmt">6.4 Power Management</a>
<ul>
<a href="#pmoverview">6.4.1 Overview</a><br>
<a href="#pminterfaces">6.4.2 Interfaces</a><br>
<a href="#pmcallbacks">6.4.3 Callbacks</a>
</ul>
</ul>
<a href="#apndxconfigs">Appendix A: NuttX Configuration Settings</a><br>
<a href="#apndxtrademarks">Appendix B: Trademarks</a>
</ul>
<table width ="100%">
<tr bgcolor="#e4e4e4">
<td>
<h1>1.0 <a name="Introduction">Introduction</a></h1>
</td>
</tr>
</table>
<p><b>Overview</b>
This document provides and overview of the NuttX build and configuration
logic and provides hints for the incorporation of new processor/board architectures
into the build.
</p>
<p>
See also <code>arch/README.txt</code> and <code>configs/README.txt</code>.
</p>
<table width ="100%">
<tr bgcolor="#e4e4e4">
<td>
<h1>2.0 <a name="DirectoryStructure">Directory Structure</a></h1>
</td>
</tr>
</table>
<p>
<b>Directory Structure</b>.
The general directly layout for NuttX is very similar to the directory structure
of the Linux kernel -- at least at the most superficial layers.
At the top level is the main makefile and a series of sub-directories identified
below and discussed in the following paragraphs:
</p>
<ul><pre>
.
|- nuttx
| |-- <a href="#topmakefile">Makefile</a>
| |-- <a href="#DirStructDocumentation">Documentation</a>
| | `-- <i>(documentation files)</i>/
| |-- <a href="#DirStructArch">arch</a>/
| | |-- <i><arch-name></i>/
| | | |-- include/
| | | | |--<i><chip-name></i>/
| | | | | `-- <i>(chip-specific header files)</i>
| | | | |--<i><other-chips></i>/
| | | | `-- <i>(architecture-specific header files)</i>
| | | `-- src/
| | | |--<i><chip-name></i>/
| | | | `-- <i>(chip-specific source files)</i>
| | | |--<i><other-chips></i>/
| | | `-- <i>(architecture-specific source files)</i>
| | `-- <i><other-architecture directories></i>/
| |-- <a href="#DirStructBinFmt">binfmt</a>/
| | |-- Makefile
| | |-- <i>(binfmt-specific sub-directories)</i>/
| | | `-- <i>(binfmt-specific source files)</i>
| | `-- <i>(common binfmt source files)</i>
| |-- <a href="#DirStructConfigs">configs</a>/
| | |-- <i><board-name></i>/
| | | |-- include/
| | | | `-- <i>(other board-specific header files)</i>
| | | |-- src/
| | | | `-- <i>(board-specific source files)</i>
| | | |---<i><config-name></i>/
| | | | `-- <i>(board configuration-specific source files)</i>
| | | `---<i>(other configuration sub-directories for this board)</i>/
| | `-- <i><(other board directories)></i>/
| |-- <a href="#DirStructDrivers">drivers</a>/
| | |-- Makefile
| | |-- <i>(driver-specific sub-directories)/</i>
| | | `-- <i>(driver-specific source files)</i>
| | `-- <i>(common driver source files)</i>
| |-- <a href="#DirStructFs">fs</a>/
| | |-- Makefile
| | |-- <i>(file system-specific sub-directories)</i>/
| | | `-- <i>(file system-specific source files)</i>
| | `-- <i>(common file system source files)</i>
| |-- <a href="#DirStructGraphics">graphics</a>/
| | |-- Makefile
| | |-- <i>(feature-specific sub-directories)</i>/
| | | `-- <i>(feature-specific source files library source files)</i>
| | `-- <i>(common graphics-related source files)</i>
| |-- <a href="#DirStructInclude">include</a>/
| | |-- <i>(standard header files)</i>
| | |-- <i>(standard include sub-directories)</i>
| | | `-- <i>(more standard header files)</i>
| | |-- <i>(non-standard include sub-directories)</i>
| | `-- <i>(non-standard header files)</i>
| |-- <a href="#DirStructLib">libc</a>/
| | |-- Makefile
| | `-- <i>(libc source files)</i>
| |-- <a href="#DirStructLibXX">libxx</a>/
| | |-- Makefile
| | `-- <i>(libxx management source files)</i>
| |-- <a href="#DirStructMm">mm</a>/
| | |-- Makefile
| | `-- <i>(memory management source files)</i>
| |-- <a href="#DirStructNet">net</a>/
| | |-- Makefile
| | |-- uip/
| | | `-- <i>(uip source files)</i>
| | `-- <i>(BSD socket source files)</i>
| |-- <a href="#DirStructSched">sched</a>/
| | |-- Makefile
| | `-- <i>(sched source files)</i>
| |-- <a href="#DirStructSysCall">syscall</a>/
| | |-- Makefile
| | `-- <i>(syscall source files)</i>
| `-- <a href="#DirStructTools">tools</a>/
| `-- <i>(miscellaneous scripts and programs)</i>
`- apps
|-- <a href="#DirStructNetUtils">netutils</a>/
| |-- Makefile
| |-- <i>(network feature sub-directories)</i>/
| | `-- <i>(network feature source files)</i>
| `-- <i>(netutils common files)</i>
|-- <a href="#DirStructNshLib">nshlib</a>/
| |-- Makefile
| `-- <i>NuttShell (NSH) files</i>
|-- <i>(Board-specific applications)</i>/
| |-- Makefile
| |-- <i>(Board-specific application sub-directories)</i>/
| | `-- <i>(Board-specific application source files)</i>
| `-- <i>(Board-specific common files)</i>
`-- <a href="#DirStructExamples">examples</a>/
`-- <i>(example)</i>/
|-- Makefile
`-- <i>(example source files)</i>
</pre></ul>
<p>
<b>Configuration Files</b>.
The NuttX configuration consists of:
</p>
<ul>
<li>
<i>Processor architecture specific files</i>.
These are the files contained in the <code>arch/</code><i><arch-name></i><code>/</code> directory
and are discussed in a paragraph <a href="#archdirectorystructure">below</a>.
</li>
<li>
<i>Chip/SoC specific files</i>.
Each processor processor architecture is embedded in chip or <i>System-on-a-Chip</i> (SoC) architecture.
The full chip architecture includes the processor architecture plus chip-specific interrupt logic,
clocking logic, general purpose I/O (GIO) logic, and specialized, internal peripherals (such as UARTs, USB, etc.).
<p>
These chip-specific files are contained within chip-specific sub-directories in the
<code>arch/</code><i><arch-name></i><code>/</code> directory and are selected via
the <code>CONFIG_ARCH_name</code> selection.
</p>
</li>
<li>
<i>Board specific configurations</i>.
In order to be usable, the chip must be contained in a board environment.
The board configuration defines additional properties of the board including such things as
peripheral LEDs, external peripherals (such as network, USB, etc.).
<p>
These board-specific configuration files can be found in the
<code>configs/</code><i><board-name></i><code>/</code> sub-directories and are discussed
in a paragraph <a href="#configsdirectorystructure">below</a>.
</p>
</li>
</ul>
<h2>2.1 <a name="DirStructDocumentation">Documentation</a></h2>
<p>
General documentation for the NuttX OS resides in this directory.
</p>
<h2>2.2 <a name="DirStructArch">nuttx/arch</a></h2>
<h3><a name="archdirectorystructure">2.2.1 Subdirectory Structure</a></h3>
<p>
This directory contains several sub-directories, each containing
architecture-specific logic.
The task of porting NuttX to a new processor consists of
add a new subdirectory under <code>arch/</code> containing logic specific
to the new architecture.
The complete board port in is defined by the architecture-specific code in this
directory (plus the board-specific configurations in the <code>config/</code>
subdirectory).
Each architecture must provide a subdirectory, <i><arch-name></i>
under <code>arch/</code> with the following characteristics:
</p>
<ul><pre>
<i><arch-name></i>/
|-- include/
| |--<i><chip-name></i>/
| | `-- <i>(chip-specific header files)</i>
| |--<i><other-chips></i>/
| |-- arch.h
| |-- irq.h
| |-- types.h
| |-- limits.h
| `-- syscall.h
`-- src/
|--<i><chip-name></i>/
| `-- <i>(chip-specific source files)</i>
|--<i><other-chips></i>/
|-- Makefile
`-- <i>(architecture-specific source files)</i>
</pre></ul>
<h3><a name="summaryofarchfiles">2.2.2 Summary of Files</a></h3>
<ul>
<li>
<code>include/</code><i><chip-name></i><code>/</code>
This sub-directory contains chip-specific header files.
</li>
<li>
<code>include/arch.h</code>:
This is a hook for any architecture specific definitions that may
be needed by the system. It is included by <code>include/nuttx/arch.h</code>.
</li>
<li>
<code>include/types.h</code>:
This provides architecture/toolchain-specific definitions for
standard types. This file should <code>typedef</code>:
<ul><code>
_int8_t, _uint8_t, _int16_t, _uint16_t, _int32_t, _uint32_t_t
</code></ul>
<p>and if the architecture supports 24- or 64-bit integers</p>
<ul><code>
_int24_t, _uint24_t, int64_t, uint64_t
</code></ul>
<p>
NOTE that these type names have a leading underscore character. This
file will be included(indirectly) by include/stdint.h and typedef'ed to
the final name without the underscore character. This roundabout way of
doings things allows the stdint.h to be removed from the include/
directory in the event that the user prefers to use the definitions
provided by their toolchain header files
</p>
<p>
And finally
</p>
<ul><code>
irqstate_t
</code></ul>
<p>
Must be defined to the be the size required to hold the interrupt
enable/disable state.
</p>
<p>
This file will be included by include/sys/types.h and be made
available to all files.
</p>
</li>
<li>
<code>include/irq.h</code>:
This file needs to define some architecture specific functions (usually
inline if the compiler supports inlining) and some structures. These include:
<ul>
<li>
<code>struct xcptcontext</code>:
This structures represents the saved context of a thread.
</li>
<li>
<code>irqstate_t irqsave(void)</code>:
Used to disable all interrupts.
</li>
<li>
<code>void irqrestore(irqstate_t flags)</code>:
Used to restore interrupt enables to the same state as before <code>irqsave()</code> was called.
</li>
</ul>
<p>
This file must also define <code>NR_IRQS</code>, the total number of IRQs supported
by the board.
</p>
</li>
<li>
<code>include/syscall.h</code>:
This file needs to define some architecture specific functions (usually
inline if the compiler supports inlining) to support software interrupts
or <i>syscall</i>s that can be used all from user-mode applications into
kernel-mode NuttX functions.
This directory must always be provided to prevent compilation errors.
However, it need only contain valid function declarations if the architecture
supports the <code>CONFIG_NUTTX_KERNEL</code> configuration.
<ul>
<li>
<code>uintptr_t sys_call0(unsigned int nbr)</code>:
<code>nbr</code> is one of the system call numbers that can be found in <code>include/sys/syscall.h</code>.
This function will perform a system call with no (additional) parameters.
</li>
<li>
<code>uintptr_t sys_call1(unsigned int nbr, uintptr_t parm1)</code>:
<code>nbr</code> is one of the system call numbers that can be found in <code>include/sys/syscall.h</code>.
This function will perform a system call with one (additional) parameter.
</li>
<li>
<code>uintptr_t sys_call2(unsigned int nbr, uintptr_t parm1, uintptr_t parm2)</code>:
<code>nbr</code> is one of the system call numbers that can be found in <code>include/sys/syscall.h</code>.
This function will perform a system call with two (additional) parameters.
</li>
<li>
<code>uintptr_t sys_call3(unsigned int nbr, uintptr_t parm1, uintptr_t parm2, uintptr_t parm3)</code>:
<code>nbr</code> is one of the system call numbers that can be found in <code>include/sys/syscall.h</code>.
This function will perform a system call with three (additional) parameters.
</li>
<li>
<code>uintptr_t sys_call4(unsigned int nbr, uintptr_t parm1, uintptr_t parm2, uintptr_t parm3, uintptr_t parm4)</code>:
<code>nbr</code> is one of the system call numbers that can be found in <code>include/sys/syscall.h</code>.
This function will perform a system call with four (additional) parameters.
</li>
<li>
<code>uintptr_t sys_call5(unsigned int nbr, uintptr_t parm1, uintptr_t parm2, uintptr_t parm3, uintptr_t parm4, uintptr_t parm5)</code>:
<code>nbr</code> is one of the system call numbers that can be found in <code>include/sys/syscall.h</code>.
This function will perform a system call with five (additional) parameters.
</li>
<li>
<code>uintptr_t sys_call6(unsigned int nbr, uintptr_t parm1, uintptr_t parm2, uintptr_t parm3, uintptr_t parm4, uintptr_t parm5, uintptr_t parm6)</code>:
<code>nbr</code> is one of the system call numbers that can be found in <code>include/sys/syscall.h</code>.
This function will perform a system call with six (additional) parameters.
</li>
</ul>
<p>
This file must also define <code>NR_IRQS</code>, the total number of IRQs supported
by the board.
</p>
</li>
<li>
<code>src/</code><i><chip-name></i><code>/</code>
This sub-directory contains chip-specific source files.
</li>
<li>
<code>src/Makefile</code>:
This makefile will be executed to build the targets <code>src/libup.a</code> and
<code>src/up_head.o</code>. The <code>up_head.o</code> file holds the entry point into the system
(power-on reset entry point, for example). It will be used in
the final link with <code>libup.a</code> and other system archives to generate the
final executable.
</li>
<li>
<i>(architecture-specific source files)</i>.
The file <code>include/nuttx/arch.h</code> identifies all of the APIs that must
be provided by the architecture specific logic. (It also includes
<code>arch/</code><i><arch-name></i><code>/arch.h</code> as described above).
</li>
</ul>
<h3><a name="supportedarchitectures">2.2.3 Supported Architectures</a></h3>
<p>
<b>Architecture- and Chip-Specific Directories</b>.
All processor architecture-specific directories are maintained in sub-directories of
the <code>arch/</code> directory.
Different chips or SoC's may implement the same processor core.
Chip-specific logic can be found in sub-directories under the architecture
directory.
Current architecture/chip directories are summarized below:
</p>
<ul>
<li><code>arch/sim</code>:
A user-mode port of NuttX to the x86 Linux platform is available.
The purpose of this port is primarily to support OS feature development.
This port does not support interrupts or a real timer (and hence no
round robin scheduler) Otherwise, it is complete.
</li>
<p>NOTE: This target will not run on Cygwin probably for many reasons but
first off because it uses some of the same symbols as does cygwind.dll.
</p>
<li><code>arch/arm</code>:
This directory holds common ARM architectures. At present, this includes
the following subdirectories:
<ul>
<li><code>arch/arm/include</code> and <code>arch/arm/src/common</code>:
Common ARM logic.
</li>
<li><code>arch/arm/include/c5471</code> and <code>arch/arm/src/c5471</code>:
TI TMS320C5471 (also called TMS320DM180 or just C5471).
NuttX operates on the ARM7 of this dual core processor.
This port is complete, verified, and included in the NuttX release 0.1.1.
</li>
<li><code>arch/arm/include/dm320</code> and <code>arch/arm/src/dm320</code>:
TI TMS320DM320 (also called just DM320).
NuttX operates on the ARM9EJS of this dual core processor.
This port complete, verified, and included in the NuttX release 0.2.1.
</li>
<li><code>arch/arm/include/lpc214x</code> and <code>arch/arm/src/lpc214x</code>:
These directories provide support for NXP LPC214x family of
processors.
STATUS: This port boots and passes the OS test (apps/examples/ostest).
The port is complete and verified. As of NuttX 0.3.17, the port includes:
timer interrupts, serial console, USB driver, and SPI-based MMC/SD card
support. A verified NuttShell configuration is also available.
</li>
</ul>
</li>
<li><code>configs/mcu123-lpc214x</code>:
The mcu123.com lpc214x development board.
This is a work in progress.
</li>
<li><code>arch/m68322</code>
A work in progress.
</li>
<li><code>arch/8051</code>:
8051 Microcontroller. This port is not quite ready for prime time.
</li>
<li><code>arch/z16f</code>:
Zilog z16f Microcontroller.
This port uses the Zilog z16f2800100zcog Development Kit.
This port was released with nuttx-0.3.7.
</li>
<li><code>arch/z80</code>:
This directory holds 8-bit ZiLOG architectures. At present, this includes the
Zilog z80, ez80Acclaim! and z8Encore! Microcontrollers.
<ul>
<li><code>arch/z80/include</code> and <code>arch/z80/src/common</code>:
Common logic.
</li>
<li><code>arch/z80/include/z80</code> and <code>arch/z80/src/z80</code>:
The Z80 port was released in nuttx-0.3.6 has been verified using only a
z80 instruction simulator.
The set simulator can be found in the NuttX GIT at
http://sourceforge.net/p/nuttx/git/ci/master/tree/misc/sims/z80sim.
This port also uses the SDCC toolchain (http://sdcc.sourceforge.net/")
(verified with version 2.6.0 and 2.7.0).
</li>
<li><code>arch/z80/include/ez80</code> and <code>arch/z80/src/ez80</code>:
The ez80Acclaim! port uses the ZiLOG ez80f0910200kitg development kit, eZ80F091 part,
with the Zilog ZDS-II Windows command line tools.
The development environment is Cygwin under WinXP.
This is a work in progress. Verified ez80 support will be announced in a future NuttX release.
</li>
<li><code>arch/z80/include/z8</code> and <code>arch/z80/src/z8</code>:
The Z8Encore! port uses either the ZiLOG z8encore000zco development kit, Z8F6403 part,
or the z8f64200100kit development kit, Z8F6423 part with the Zilog ZDS-II Windows command line
tools. The development environment is Cygwin under WinXP.
The initial release, verified only on the ZDS-II ez8 simulator, was released in nuttx-0.3.9.
</li>
</ul>
</li>
</ul>
<p>
<b>Deprecated Architecture Directories</b>.
The following architecture directories are deprecated. They have been
replaced by the logic in <code>arm/arm</code> and will deleted when
<code>arch/arm</code> is fully verified.
</p>
<ul>
<li><code>arch/c5471</code>:
Replaced with <code>arch/arm/include/c5471</code> and
<code>arch/arm/src/c5471</code>.
</li>
<li><code>arch/dm320</code>:
Replaced with <code>arch/arm/include/dm320</code> and
<code>arch/arm/src/dm320</code>.
</li>
</ul>
<p>
Other ports for the for the TI TMS320DM270 and for MIPS are in various states
of progress
</p>
<h2>2.3 <a name="DirStructBinFmt">nuttx/binfmt</a></h2>
<p>
The <code>binfmt/</code> subdirectory contains logic for loading binaries in the file
system into memory in a form that can be used to execute them.
</p>
<h2>2.4 <a name="DirStructConfigs">nuttx/configs</a></h2>
<p>
The <code>configs/</code> subdirectory contains configuration data for each board.
These board-specific configurations plus the architecture-specific configurations in
the <code>arch/</code> subdirectory complete define a customized port of NuttX.
</p>
<h3><a name="configsdirectorystructure">2.4.1 Subdirectory Structure</a></h3>
<p>
The configs directory contains board specific configuration files. Each board must
provide a subdirectory <board-name> under <code>configs/</code> with the following characteristics:
</p>
<ul><pre>
<i><board-name></i>
|-- Kconfig
|-- include/
| |-- board.h
| `-- <i>(board-specific header files)</i>
|-- src/
| |-- Makefile
| `-- <i>(board-specific source files)</i>
|-- <i><config1-dir></i>
| |-- Make.defs
| |-- defconfig
| |-- appconfig<sup>1</sup>
| `-- setenv.sh
|-- <i><config2-dir></i>
| |-- Make.defs
| |-- defconfig
| |-- appconfig<sup>1</sup>
| `-- setenv.sh
| ...
`-- <i>(other board-specific configuration sub-directories)</i>/
</pre>
<p><small>
<sup>1</sup>Optional
</small></p>
</ul>
<h3><a name="summaryofconfigfiles">2.4.2 Summary of Files</a></h3>
<h4><a name="boardlogic">2.4.2.1 Board Specific Logic</a></h4>
<ul>
<li>
<code>include/</code>:
This directory contains board specific header files.
This directory will be linked as <code>include/arch/board</code> at configuration time
and can be included via <code>#include <arch/board/header.h></code>.
These header file can only be included by files in <code>arch/</code><i><arch-name></i><code>/include/</code>
and <code>arch/</code><i><arch-name></i><code>/src/</code>.
</li>
<li>
<code>src/</code>:
This directory contains board specific drivers.
This directory will be linked as <config>arch/</code><i><arch-name></i><code>/src/board</code> at configuration
time and will be integrated into the build system.
</li>
<li>
<code>src/Makefile</code>:
This makefile will be invoked to build the board specific drivers.
It must support the following targets: <code>libext$(LIBEXT)</code>, <code>clean</code>, and <code>distclean</code>.
</li>
</ul>
<h4><a name="boardconfigsubdirs">2.4.2.2 Board Specific Configuration Sub-Directories</a></h4>
<p>
The <code>configs/</code><i><board-name></i><code>/</code> sub-directory holds all of the
files that are necessary to configure NuttX for the particular board.
A board may have various different configurations using the common source files.
Each board configuration is described by three files: <code>Make.defs</code>, <code>defconfig</code>, and <code>setenv.sh</code>.
Typically, each set of configuration files is retained in a separate configuration sub-directory
(<i><config1-dir></i>, <i><config2-dir></i>, .. in the above diagram).
The procedure for configuring NuttX is described <a href="#configuringnuttx">below</a>,
This paragraph will describe the contents of these configuration files.
</p>
<ul>
<li>
<code>Make.defs</code>: This makefile fragment provides architecture and
tool-specific build options. It will be included by all other
makefiles in the build (once it is installed). This make fragment
should define:
<ul>
<li>Tools: <code>CC</code>, <code>LD</code>, <code>AR</code>, <code>NM</code>, <code>OBJCOPY</code>, <code>OBJDUMP</code></li>
<li>Tool options: <code>CFLAGS</code>, <code>LDFLAGS</code></li>
</ul>
<p>
When this makefile fragment runs, it will be passed <code>TOPDIR</code> which
is the path to the root directory of the build. This makefile
fragment should include:
</p>
<ul>
<li><code>$(TOPDIR)/.config </code> : Nuttx configuration</li>
<li><code>$(TOPDIR)/tools/Config.mk</code> : Common definitions</li>
</ul>
<p>
Definitions in the <code>Make.defs</code> file probably depend on some of the
settings in the .<code>config</code> file. For example, the <code>CFLAGS</code> will most likely be
different if <code>CONFIG_DEBUG=y</code>.
</p>
<p>
The included <code>tools/Config.mk</code> file contains additional definitions that may
be overriden in the architecture-specific Make.defs file as necessary:
</p>
<ul>
<li><code>COMPILE</code>, <code>ASSEMBLE</code>, <code>ARCHIVE</code>, <code>CLEAN</code>, and <code>MKDEP</code> macros</li>
</ul>
</li>
<li>
<p>
<code>defconfig</code>: This is a configuration file similar to the Linux
configuration file. In contains variable/value pairs like:
</p>
<ul>
<li><code>CONFIG_VARIABLE</code>=value</li>
</ul>
<p>
This configuration file will be used at build time:
</p>
<p><ol>
<li>As a makefile fragment included in other makefiles, and</li>
<li>to generate <code>include/nuttx/config.h</code> which is included by
most C files in the system.</li>
</ol></p>
</li>
<li>
<p>
<code>appconfig</code>: This is another configuration file that is specific to the
application. This file is copied into the application build directory
when NuttX is configured. See <code>../apps/README.txt</code> for further details.
</p>
</li>
<li>
<p>
<code>setenv.sh</code>: This is a script that you can include that will be installed at
the top level of the directory structure and can be sourced to set any
necessary environment variables.
You will most likely have to customize the default <code>setenv.sh</code> script in order
for it to work correctly in your environment.
</p>
</li>
</ul>
<h3><a name="supportedboards">2.4.3 Supported Boards</a></h3>
<p>
All of the specific boards supported by NuttX are identified below.
These are the specific <i><board-name></i>'s that may be used to configure NuttX
as described <a href="#configuringnuttx">below</a>.
</p>
<ul>
<li><code>configs/avr32dev1</code>:
This is a port of NuttX to the Atmel AVR32DEV1 board. That board is
based on the Atmel AT32UC3B0256 MCU and uses a specially patched
version of the GNU toolchain: The patches provide support for the
AVR32 family. That patched GNU toolchain is available only from the
Atmel website. STATUS: This port is functional but very basic. There
are configurations for NSH and the OS test.
</li>
<li><code>configs/c5471evm</code>:
This is a port to the Spectrum Digital C5471 evaluation board. The
C5471 is a dual core processor from TI with an ARM7TDMI general purpose
processor and a c54 DSP. It is also known as TMS320DA180 or just DA180.
NuttX runs on the ARM core and is built with with a GNU arm-nuttx-elf toolchain
under Linux or Cygwin. This port is complete and verified.
</li>
<li><code>configs/demo9s12ne64</code>:
Feescale DMO9S12NE64 board based on the MC9S12NE64 hcs12 cpu. This
port uses the m9s12x GCC toolchain. STATUS: (Still) under development; it
is code complete but has not yet been verified.
</li>
<li><code>configs/ea3131</code>:
Embedded Artists EA3131 Development bard. This board is based on the
an NXP LPC3131 MCU. This OS is built with the arm-nuttx-elf toolchain.
STATUS: This port is complete and mature.
</li>
<li><code>configs/eagle100</code>:
Micromint Eagle-100 Development board. This board is based on the
an ARM Cortex-M3 MCU, the Luminary LM3S6918. This OS is built with the
arm-nuttx-elf toolchain. STATUS: This port is complete and mature.
</li>
<li><code>configs/ez80f0910200kitg</code>
ez80Acclaim! Microcontroller. This port use the Zilog ez80f0910200kitg
development kit, eZ80F091 part, and the Zilog ZDS-II Windows command line
tools. The development environment is Cygwin under WinXP.
</li>
<li><code>configs/ez80f910200zco</code>:
ez80Acclaim! Microcontroller. This port use the Zilog ez80f0910200zco
development kit, eZ80F091 part, and the Zilog ZDS-II Windows command line
tools. The development environment is Cygwin under WinXP.
</li>
<li><code>configs/lm3s6965-ek</code>:
Stellaris LM3S6965 Evaluation Kit. This board is based on the
an ARM Cortex-M3 MCU, the Luminary/TI LM3S6965. This OS is built with the
arm-nuttx-elf toolchain. STATUS: This port is complete and mature.
</li>
<li><code>configs/lm3s8962-ek</code>:
Stellaris LMS38962 Evaluation Kit. STATUS: contributed.
</li>
<li><code>configs/lpcxpresso-lpc1768</code>:
Embedded Artists base board with NXP LPCExpresso LPC1768. This board
is based on the NXP LPC1768. The Code Red toolchain is used by default.
STATUS: Under development.
</li>
<li><code>configs/m68322evb</code>:
This is a partial port for the venerable m68322evb board from Motorola.
This port was never completed and there are no plans to complete.
It will probably just be removed from the source tree at some point.
</li>
<li><code>configs/mbed</code>:
The configurations in this directory support the mbed board (http://mbed.org)
that features the NXP LPC1768 microcontroller. This OS is also built
with the arm-nuttx-elf toolchain. STATUS: Contributed.
</li>
<li><code>configs/mcu123-lpc214x</code>:
This port is for the NXP LPC2148 as provided on the mcu123.com
lpc214x development board.
This OS is also built with the arm-nuttx-elf toolchain* under Linux or Cygwin.
The port supports serial, timer0, spi, and usb.
</li>
<li><code>configs/mirtoo</code>:
This is the port to the DTX1-4000L "Mirtoo" module.
This module uses MicroChipPIC32MX250F128D.
See the <a href="http://www.dimitech.com/">Dimitech</a> website for further information.
</li>
<li><code>configs/mx1ads</code>:
This is a port to the Motorola MX1ADS development board. That board
is based on the Freescale i.MX1 processor. The i.MX1 is an ARM920T.
STATUS: This port is nearly code complete but was never fully
integrated due to tool-related issues.
</li>
<li><code>configs/ne64badge</code>:
Future Electronics Group NE64 /PoE Badge board based on the
MC9S12NE64 hcs12 cpu. This port uses the m9s12x GCC toolchain.
STATUS: Under development. The port is code-complete but has
not yet been fully tested.
</li>
<li><code>configs/ntosd-dm320</code>:
This port uses the Neuros OSD with a GNU arm-nuttx-elf toolchain* under Linux or Cygwin.
See <a href="http://wiki.neurostechnology.com/index.php/Developer_Welcome">Neuros Wiki</a>
for further information.
NuttX operates on the ARM9EJS of this dual core processor.
STATUS: This port is code complete, verified, and included in the
NuttX 0.2.1 release.
</li>
<li><code>configs/nucleus2g</code>:
This port uses the Nucleus 2G board (with Babel CAN board).
This board features an NXP LPC1768 processor.
See the <a href="http://www.2g-eng.com/">2G Engineering</a> website for more information about the Nucleus 2G.
</li>
<li><code>configs/olimex-lpc1766stk</code>:
This port uses the Olimex LPC1766-STK board and a GNU GCC toolchain under
Linux or Cygwin. STATUS: Complete and mature.
</li>
<li><code>configs/olimex-lpc2378</code>:
This port uses the Olimex-lpc2378 board and a GNU arm-nuttx-elf toolchain under
Linux or Cygwin. STATUS: ostest and NSH configurations available.
</li>
<li><code>configs/olimex-strp711</code>:
This port uses the Olimex STR-P711 board arm-nuttx-elf toolchain* under Linux or Cygwin.
See the <a href="http://www.olimex.com/dev/str-p711.html">Olimex</a> web site
for further information.
STATUS: Configurations for the basic OS test and NSH are complete and verified.
</li>
<li><code>configs/pcblogic-pic32mx</code>:
This is the port of NuttX to the PIC32MX board from PCB Logic Design Co.
This board features the MicroChip PIC32MX460F512L.
The board is a very simple -- little more than a carrier for the PIC32
MCU plus voltage regulation, debug interface, and an OTG connector.
STATUS: Code complete but testing has been stalled due to tool related problems
(PICkit 2 does not work with the PIC32).
</li>
<li><code>configs/pjrc-8051</code>:
8051 Microcontroller. This port uses the PJRC 87C52 development system
and the <a href="http://sdcc.sourceforge.net/">SDCC</a> toolchain under Linux or Cygwin.
This port is not quite ready for prime time.
</li>
<li><code>configs/qemu-i486</code>:
Port of NuttX to QEMU in i486 mode. This port will also run on real i486
hardwared (Google the Bifferboard).
</li>
<li><code>configs/rgmp</code>:
RGMP stands for RTOS and GPOS on Multi-Processor. RGMP is a project for
running GPOS and RTOS simultaneously on multi-processor platforms. You can
port your favorite RTOS to RGMP together with an unmodified Linux to form a
hybrid operating system. This makes your application able to use both RTOS
and GPOS features.
See the <a href="http://rgmp.sourceforge.net/wiki/index.php/Main_Page">RGMP Wiki</a> for further information about RGMP.
</li>
<li><code>configs/sam3u-ek</code>:
The port of NuttX to the Atmel SAM3U-EK development board.
</li>
<li><code>configs/skp16c26</code>:
Renesas M16C processor on the Renesas SKP16C26 StarterKit. This port
uses the GNU m32c toolchain. STATUS: The port is complete but untested
due to issues with compiler internal errors.
</li>
<li><code>configs/stm3210e-eval</code>:
STMicro STM3210E-EVAL development board based on the STMicro STM32F103ZET6
microcontroller (ARM Cortex-M3). This port uses the GNU Cortex-M3
toolchain.
</li>
<li><code>configs/sim</code>:
A user-mode port of NuttX to the x86 Linux platform is available.
The purpose of this port is primarily to support OS feature development.
This port does not support interrupts or a real timer (and hence no
round robin scheduler) Otherwise, it is complete.
</li>
<li><code>configs/us7032evb1</code>:
This is a port of the Hitachi SH-1 on the Hitachi SH-1/US7032EVB1 board.
STATUS: This port is available as of release 0.3.18 of NuttX. The port is basically
complete and many examples run correctly. However, there are remaining instabilities
that make the port un-usable. The nature of these is not understood; the behavior is
that certain SH-1 instructions stop working as advertised. This could be a silicon
problem, some pipeline issue that is not handled properly by the gcc 3.4.5 toolchain
(which has very limited SH-1 support to begin with), or perhaps with the CMON debugger.
At any rate, I have exhausted all of the energy that I am willing to put into this cool
old processor for the time being.
</li>
<li><code>configs/vsn</code>:
ISOTEL NetClamps VSN V1.2 ready2go sensor network platform based on the
STMicro STM32F103RET6. Contributed by Uros Platise.
See the <a href="http://isotel.eu/NetClamps/">Isotel</a> web site for further information
about the NetClamps board.
</li>
<li><code>configs/xtrs</code>:
TRS80 Model 3. This port uses a vintage computer based on the Z80.
An emulator for this computer is available to run TRS80 programs on a
Linux platform (http://www.tim-mann.org/xtrs.html).
</li>
<li><code>configs/z16f2800100zcog</code>
z16f Microcontroller.
This port use the Zilog z16f2800100zcog development kit and the
Zilog ZDS-II Windows command line tools.
The development environment is Cygwin under WinXP.
</li>
<li><code>configs/z80sim</code>:
z80 Microcontroller. This port uses a Z80 instruction set simulator.
That simulator can be found in the NuttX GIT
<a href="http://sourceforge.net/p/nuttx/git/ci/master/tree/misc/sims/z80sim">here</a>.
This port also the <a href="http://sdcc.sourceforge.net/">SDCC</a> toolchain
under Linux or Cygwin(verified with version 2.6.0).
</li>
<li><code>configs/z8encore000zco</code>
z8Encore! Microcontroller. This port use the Zilog z8encore000zco
development kit, Z8F6403 part, and the Zilog ZDS-II Windows command line
tools. The development environment is Cygwin under WinXP.
</li>
<li><code>configs/z8encore000zco</code>
z8Encore! Microcontroller. This port use the Zilog z8f64200100kit
development kit, Z8F6423 part, and the Zilog ZDS-II Windows command line
tools. The development environment is Cygwin under WinXP.
</li>
<li><code>configs/z8f64200100kit</code>:
z8Encore! Microcontroller. This port use the Zilog z8f64200100kit
development kit, Z8F6423 part, and the Zilog ZDS-II Windows command line
tools. The development environment is Cygwin under WinXP.
</li>
</ul>
<p><small><blockquote>
* A customized version of the <a href="http://www.buildroot.org">buildroot</a>
is available to build these toolchains under Linux or Cygwin.
</blockquote></small></p>
<h3><a name="newboardconfig">2.4.4 Adding a New Board Configuration</a></h3>
<p>
Okay, so you have created a new board configuration directory.
Now, how do you hook this board into the configuration system so that you can select with <code>make menuconfig</code>?
</p>
<p>
You will need modify the file <code>configs/Kconfig</code>.
Let's look at the STM32F4-Discovery configuration in the <code>Kconfig</code> file and see how we would add a new board directory to the configuration.
For this configuration let's say that you new board resides in the directory <code>configs/myboard</code>;
It uses an MCU selected with <code>CONFIG_ARCH_CHIP_MYMCU</code>; and you want the board to be selected with <code>CONFIG_ARCH_BOARD_MYBOARD</code>.
Then here is how you can clone the STM32F4-Discovery configuration in <code>configs/Kconfig</code> to support your new board configuration.
</p>
<p>
In <code>configs/Kconfig</code> for the stm32f4-discovery, you will see a configuration definition like this:
<p>
<ul><pre>
config ARCH_BOARD_STM32F4_DISCOVERY
bool "STMicro STM32F4-Discovery board"
depends on ARCH_CHIP_STM32F407VG
select ARCH_HAVE_LEDS
select ARCH_HAVE_BUTTONS
select ARCH_HAVE_IRQBUTTONS
---help---
STMicro STM32F4-Discovery board based on the STMicro STM32F407VGT6 MCU.
</pre></ul>
<p>
The above selects the STM32F4-Discovery board.
The <code>select</code> lines say that the board has both LEDs and buttons and that the board can generate interrupts from the button presses.
You can just copy the above configuration definition to a new location (notice that they the configurations are in alphabetical order).
Then you should edit the configuration to support your board.
The final configuration definition might look something like:
</p>
<ul><pre>
config ARCH_BOARD_MYBOARD
bool "My very own board configuration"
depends on ARCH_CHIP_MYMCU
select ARCH_HAVE_LEDS
select ARCH_HAVE_BUTTONS
select ARCH_HAVE_IRQBUTTONS
---help---
This options selects the board configuration for my very own board
based on the MYMCU processor.
</pre></ul>
<p>
Later in the <code>configs/Kconfig</code> file, you will see a long, long string configuration with lots of defaults like this:
</p>
<ul><pre>
config ARCH_BOARD
string
default "amber" if ARCH_BOARD_AMBER
default "avr32dev1" if ARCH_BOARD_AVR32DEV1
default "c5471evm" if ARCH_BOARD_C5471EVM
...
default "stm32f4discovery" if ARCH_BOARD_STM32F4_DISCOVERY
...
</pre></ul>
<p>
This logic will assign string value to a configuration variable called <code>CONFIG_ARCH_BOARD</code> that will name the directory where the board-specific files reside.
In our case, these files reside in <code>configs/myboard</code> and we add the following to the long list of defaults (again in alphabetical order):
</p>
<ul><pre>
default "myboar" if ARCH_BOARD_MYBOARD
</pre></ul>
<p>
Now the build system knows where to find your board configuration!
</p>
<p>
And finally, add something like this near the bottom of <code>configs/myboard</code>:
</p>
<ul><pre>
if ARCH_BOARD_MYBOARD
source "configs/myboard/Kconfig"
endif
</pre></ul>
<p>
This includes additional, board-specific configuration variabled defintion in <code>configs/myboard/Kconfig</code>.
</p>
<h2>2.5 <a name="DirStructDrivers">nuttx/drivers</a></h2>
<p>
This directory holds architecture-independent device drivers.
</p>
<ul><pre>
drivers/
|-- Kconfig
|-- Makefile
|-- analog/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(Common ADC and DAC driver source files)</i>
|-- bch/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(bch driver source files)</i>
|-- input/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(Common touchscreen and keypad driver source files)</i>
|-- lcd/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(Common LCD driver source files)</i>
|-- mmcsd/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(Common MMC/SD card driver source files)</i>
|-- mtd/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(Common memory technology device driver source files)</i>
|-- net/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(Common network driver source files)</i>
|-- sensors/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(Common sensor driver source files)</i>
|-- serial/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(Files for the Calypso SERCOMM driver)</i>
|-- serial/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(Common front-end character drivers for chip-specific UARTs)</i>
|-- usbdev/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(Common USB device driver source files)</i>
|-- usbhost/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(Common USB host driver source files)</i>
|-- wireless/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(Common wireless driver source files)</i>
`-- <i>(Various common driver source files)</i>
</pre></ul>
<h2>2.6 <a name="DirStructFs">nuttx/fs</a></h2>
<p>
This directory contains the NuttX file system.
This file system is described <a href="#NxFileSystem">below</a>.
</p>
<ul><pre>
fs/
|-- Kconfig
|-- Makefile
|-- fat/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(FAT file system source files)</i>
|-- mmap/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(RAM-based file mapping source files)</i>
|-- nfs/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(NFS client file system source files)</i>
|-- nxffs/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(NuttX Flash File System (NXFFS) source files)</i>
|-- romfs/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(ROMFS file system source files)</i>
`-- <i>(common file system source files)</i>
</pre></ul>
<h2>2.7 <a name="DirStructGraphics">nuttx/graphics</a></h2>
<p>
This directory contains files for graphics/video support under NuttX.
</p>
<ul><pre>
graphics/
|-- Kconfig
|-- Makefile
|-- nxbe/
| |-- Make.defs
| `-- <i>(NuttX graphics back-end (NXBE) source files)</i>
|-- nxfont/
| |-- Make.defs
| `-- <i>(NuttX graphics font-related (NXFONT) source files)</i>
|-- nxglib/
| |-- Make.defs
| `-- <i>(NuttX graphics library (NXGL) source files)</i>
|-- nxmu/
| |-- Make.defs
| `-- <i>(NuttX graphics multi-user (NXMU) server source files)</i>
|-- nxsu/
| |-- Make.defs
| `-- <i>(NuttX graphics single-user (NXSU) source files)</i>
`-- <i>(common file system source files)</i>
</pre></ul>
<h2>2.8 <a name="DirStructInclude">nuttx/include</a></h2>
<p>
This directory holds NuttX header files.
Standard header files file retained in can be included in the <i>normal</i> fashion:
</p>
<ul>
<code>include <stdio.h></code><br>
<code>include <sys/types.h></code><br>
etc.
</ul>
<p>
Directory structure:
</p>
<ul><pre>
include/
|-- <i>(standard header files)</i>
|-- arpa/
| `-- <i>(Standard header files)</i>
|-- cxx/
| `-- <i>(C++ standard header files)</i>
|-- netinet/
| `-- <i>(Standard header files)</i>
|-- nuttx/
| |-net/
| | `-- uip/
| | `-- <i>(uIP specific header files)</i>
| `-- <i>(NuttX specific header files)</i>
`- sys/
`-- <i>(More standard header files)</i>
</per></ul>
<h2>2.9 <a name="DirStructLib">nuttx/libc</a></h2>
<p>
This directory holds a collection of standard libc-like functions with custom
interfaces into NuttX.
</p>
<p>
Normally the logic in this file builds to a single library (<code>libc.a</code>).
However, if NuttX is built as a separately compiled kernel (with <code>CONFIG_NUTTX_KERNEL=y</code>), then the contents of this directory are built as two libraries:
One for use by user programs (<code>libuc.a</code>) and one for use only within the <kernel> space (<code>libkc.a</code>).
</p>
<p>
These user/kernel space libraries (along with the sycalls of <a href="#DirStructSyscall"><code>nuttx/syscall</code></a>) are needed to support the two differing protection domains.
</p>
<p>
Directory structure:
</p>
<ul><pre>
libc/
|-- libgen/
| `-- <i>(Implementation of functions from libgen.h)</i>
|-- math/
| `-- <i>(Implementation of functions from fixedmath.h)</i>
|-- misc/
| `-- <i>(Implementation of miscellaneous library functions)</i>
|-- mqueue/
| `-- <i>(Implementation of some functions from mqueue.h)</i>
|-- net/
| `-- <i>(Implementation of network-related library functions)</i>
|-- queue/
| `-- <i>(Implementation of functions from queue.h)</i>
|-- sched/
| `-- <i>(Implementation of some functions from sched.h)</i>
|-- semaphore/
| `-- <i>(Implementation of some functions from semaphore.h)</i>
|-- signal/
| `-- <i>(Implementation of some functions from signal.h)</i>
|-- stdio/
| `-- <i>(Implementation of functions from stdio.h)</i>
|-- stdlib/
| `-- <i>(Implementation of functions from stdlib.h)</i>
|-- string/
| `-- <i>(Implementation of functions from string.h)</i>
|-- time/
| `-- <i>(Implementation of some functions from time.h)</i>
`-- unistd/
`-- <i>(Implementation of some functions from unistd.h)</i>
</per></ul>
<h2>2.10 <a name="DirStructLibXX">nuttx/libxx</a></h2>
<p>
This directory holds a tiny, minimal standard std C++ that can be used to
build some, simple C++ applications in NuttX.
</p>
<h2>2.11 <a name="DirStructMm">nuttx/mm</a></h2>
<p>
This is the NuttX memory manager.
</p>
<h2>2.12 <a name="DirStructNet">nuttx/net</a></h2>
<p>
This directory contains the implementation of the NuttX internal socket APIs.
The subdirectory, <code>uip</code> contains the uIP port.
</P>
<h2>2.13 <a name="DirStructSched">nuttx/sched</a></h2>
<p>
The files forming core of the NuttX RTOS reside here.
</p>
<h2>2.14 <a name="DirStructSyscall">nuttx/syscall</a></h2>
<p>
If NuttX is built as a separately compiled kernel (with <code>CONFIG_NUTTX_KERNEL=y</code>),
then the contents of this directory are built.
This directory holds a syscall interface that can be used for communication
between user-mode applications and the kernel-mode RTOS.
</p>
<h2>2.15 <a name="DirStructTools">nuttx/tools</a></h2>
<p>
This directory holds a collection of tools and scripts to simplify
configuring, building and maintaining NuttX.
</p>
<ul><pre>
tools/
|-- Makefile.host
|-- Makefile.export
|-- README.txt
|-- configure.sh / configure.bat
|-- cfgparser.c
|-- cfgparser.h
|-- copydir.sh / copydir.bat
|-- define.sh / define.bat
|-- incdir.sh / indir.bat
|-- indent.sh
|-- link.sh / link.bat
|-- mkconfig.c
|-- mkdeps.sh / mkdeps.bat
|-- mkexport.sh
|-- mkimage.sh
|-- mknulldeps.sh
|-- mkromfsimg.sh
|-- mksyscall.c
|-- mkversion.c
|-- unlink.sh / unlink.bat
|-- version.sh
`-- zipme.sh
</pre></ul>
<p>
Refer to the README file in the <code>tools</code> directory for more information about the individual files.
Some of these tools are discussed below as well in the discussion of <a href="#configandbuild">configuring and building</a> NuttX.
</p>
<h2>2.16 <a name="topmakefile">nuttx/Makefile</a></h2>
<p>
The top-level <code>Makefile</code> in the <code>${TOPDIR}</code> directory contains all of the top-level control
logic to build NuttX.
Use of this <code>Makefile</code> to build NuttX is described <a href="#buildingnuttx">below</a>.
</p>
<h2>2.17 <a name="DirStructNetUtils">apps/netutils</a></h2>
<p>
This directory contains most of the network applications.
Some of these are original with NuttX (like tftpc and dhcpd) and others were leveraged from the uIP-1.0 apps directory.
As the uIP apps/README says, these applications "are not all heavily tested."
</p>
<ul><pre>
netutils/
|-- Kconfig
|-- Makefile
|-- dhcdp/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(DHCP client source files)</i>
|-- dhcpd/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(DHCP server source files)</i>
|-- ftpc/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(FTP client source files)</i>
|-- ftpd/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(FTP server source files)</i>
|-- resolv/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(resolv source files)</i>
|-- resolv/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(resolv source files)</i>
|-- smtp/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(smtp source files)</i>
|-- telnetd/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(Telnet client source files)</i>
|-- tftpc/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(TFTP client source files)</i>
|-- thttpd/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(thttpd HTTP server source files)</i>
|-- uiplib/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(uiplib source files)</i>
|-- weblclient/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(webclient source files)</i>
|-- webserver/
| |-- Kconfig
| |-- Make.defs
| `-- <i>(uIP webserver source files)</i>
`-- <i>(netutils common files)</i>
</pre></ul>
<h2>2.18 <a name="DirStructNshLib">apps/nshlib</a></h2>
<p>
This directory contains for the core of the NuttShell (NSH) application.
</p>
<h2>2.19 <a name="DirStructExamples">apps/examples</a></h2>
<p>
Example and test programs to build against.
</p>
<table width ="100%">
<tr bgcolor="#e4e4e4">
<td>
<h1>3.0 <a name="configandbuild">Configuring and Building</a></h1>
</td>
</tr>
</table>
<h2><a name="configuringnuttx">3.1 Configuring NuttX</a></h2>
<p>
<b>Manual Configuration</b>.
Configuring NuttX requires only copying the
<a href="#boardconfigsubdirs">board-specific configuration files</a> into the top level directory which appears in the make files as the make variable, <code>${TOPDIR}</code>.
This could be done manually as follows:
</p>
<ul>
<li>Copy <code>configs/</code><i><board-name></i><code>/[</code><i><config-dir></i><code>/]Make.defs</code> to <code>${TOPDIR}/Make.defs</code>,<li>
<li>Copy <code>configs/</code><i><board-name></i><code>/[</code><i><config-dir></i><code>/]setenv.sh</code> to <code>${TOPDIR}/setenv.sh</code>, and</li>
<li>Copy <code>configs/</code><i><board-name></i><code>/[</code><i><config-dir></i><code>/]defconfig</code> to <code>${TOPDIR}/.config</code></li>
</ul>
<p>
And if <code>configs/</code><i><board-name></i><code>/[</code><i><config-dir></i><code>/appconfig</code> exists in the board configuration directory:
</p>
<ul>
<li>Copy <code>configs/</code><i><board-name></i><code>/[</code><i><config-dir></i><code>/appconfig</code> to <app-dir><code>/.config</code></li>
<li><code>echo "APPS_LOC=\"<app-dir>\"" >> "${TOPDIR}/.config"</code></li>
</ul>
</p>
<p>
Where <i><board-name></i> is the name of one of the sub-directories of the
NuttX <a href="#DirStructConfigs"><code>configs/</code></a> directory.
This sub-directory name corresponds to one of the supported boards
identified <a href="#supportedboards">above</a>.
<config-dir> is the optional, specific configuration directory for the board.
And <app-dir> is the location of the optonal application directory.
</p>
<p>
<b>Automated Configuration</b>.
There is a script that automates these steps. The following steps will
accomplish the same configuration:
</p>
<ul><pre>
cd tools
./configure.sh <i><board-name></i>[/<i><config-dir></i>]
</pre></ul>
<p>
There is an alternative Windows batch file, <code>configure.bat</code>, that can be used insteach of <code>configure.sh</code> in the windows native enironment like:
</p>
<ul><pre>
cd tools
configure.bat <i><board-name></i>[\<i><config-dir></i>]
</pre></ul>
<p>
See <code>tools/README.txt</code> for more information about these scripts.
</p>
<p>
If <code>configs/</code><i><board-name></i><code>/[</code><i><config-dir></i>]<code>/appconfig</code>
exists and your application directory is not in the standard loction (<config>../apps</config>),
then you should also specify the location of the application directory on the command line like:
</p>
<ul><pre>
cd tools
./configure.sh -a <app-dir> <i><board-name></i>[/<i><config-dir></i>]
</pre></ul>
<p>
<b>Version Files</b>.
The NuttX build expects to find a version file located in the top-level NuttX build directory.
That version file is called <code>.version</code>.
The correct version file is installed in each versioned NuttX released.
However, if you are working from an GIT snapshot, then there will be no version file.
If there is no version file, the top-level <code>Makefile</code> will create a dummy <code>.version</code> file on the first make.
This dummy version file will contain all zeroes for version information.
If that is not what you want, they you should run the <code>version.sh</code> script to create a better <code>.version</code> file.
</p>
<p>
You can get help information from the <code>version.sh</code> script using the <code>-h</code> option.
For example:
</p>
<ul><pre>
$ tools/version.sh -h
tools/version.sh is a tool for generation of proper version files for the NuttX build
USAGE: tools/version.sh [-d|-h] [-b build] -v <major.minor> <outfile-path>
Where:
-d
Enable script debug
-h
show this help message and exit
-v <major.minor>
The NuttX version number expressed a major and minor number separated
by a period
<outfile-path>
The full path to the version file to be created
</pre></ul>
<p>
As an example, the following command will generate a version file for version 6.1 using the current GIT revision number:
</p>
<ul><pre>
tools/version.h -v 6.1 .version
</pre></ul>
<p>
The <code>.version</code> file is also used during the build process to create a C header file at <code>include/nuttx/version.h</code> that contains the same version information.
That version file may be used by your C applications for, as an example, reporting version information.
</p>
<p>
<b>Additional Configuration Steps</b>.
The remainder of configuration steps will be performed by <a href="#topmakefile"><code>${TOPDIR}/Makefile</code></a>
the first time the system is built as described below.
</p>
<h2><a name="buildingnuttx">3.2 Building NuttX</a></h2>
<p>
<b>Building NuttX</b>.
Once NuttX has been configured as described <a href="#configuringnuttx">above</a>, it may be built as follows:
</p>
<ul><pre>
cd ${TOPDIR}
source ./setenv.sh
make
</pre></ul>
<p>
The <code>${TOPDIR}</code> directory holds:
</p>
<ul>
<li>The top level <a href="#topmakefile"><code>Makefile</code></a> that controls the NuttX build.
</ul>
<p>
That directory also holds:
</p>
<ul>
<li>The makefile fragment <a href="#boardconfigsubdirs"><code>.config</code></a> that describes the current configuration.</li>
<li>The makefile fragment <a href="#boardconfigsubdirs"><code>Make.defs</code></a> that provides customized build targets, and</li>
<li>The shell script <a href="#boardconfigsubdirs"><code>setenv.sh</code></a> that sets up the configuration environment for the build.</li>
</ul>
<p>
The <a href="#boardconfigsubdirs"><code>setenv.sh</code></a> contains Linux/Cygwin environmental settings that are needed for the build.
The specific environmental definitions are unique for each board but should include, as a minimum, updates to the <code>PATH</code> variable to include the full path to the architecture-specific toolchain identified in <a href="#boardconfigsubdirs"><code>Make.defs</code></a>.
The <a href="#boardconfigsubdirs"><code>setenv.sh</code></a> only needs to be source'ed at the beginning of a session.
The system can be re-made subsequently by just typing <code>make</code>.
</p>
<p>
<b>First Time Make.</b>
Additional configuration actions will be taken the first time that system is built.
These additional steps include:
</p>
<ul>
<li>Auto-generating the file <code>include/nuttx/config.h</code> using the <code>${TOPDIR}/.config</code> file.</li>
<li>Auto-generating the file <code>${TOPDIR}/.version</code> with version 0.0 if one does not exist.</li>
<li>Auto-generating the file <code>include/nuttx/version.h</code> using the <code>${TOPDIR}/.version</code> file.</li>
<li>Creating a link to <code>${TOPDIR}/arch/</code><i><arch-name></i><code>/include</code> at <code>${TOPDIR}/include/arch</code>.</li>
<li>Creating a link to <code>${TOPDIR}/configs/</code><i><board-name></i><code>/include</code> at <code>${TOPDIR}/include/arch/board</code>.</li>
<li>Creating a link to <code>${TOPDIR}/configs/</code><i><board-name></i><code>/src</code> at <code>${TOPDIR}/arch/</code><i><arch-name></i><code>/src/board</code></li>
<li>Creating a link to <code>${APPDIR}/include</code> at <code>${TOPDIR}/include/apps</code></li>
<li>Creating make dependencies.
</ul>
<table width ="100%">
<tr bgcolor="#e4e4e4">
<td>
<h1>4.0 <a name="ArchAPIs">Architecture APIs</a></h1>
</td>
</tr>
</table>
<p>
The file <code>include/nuttx/arch.h</code> identifies by prototype all of the APIs that must
be provided by the architecture specific logic.
The internal OS APIs that architecture-specific logic must
interface with also also identified in <code>include/nuttx/arch.h</code> or in
other header files.
</p>
<h2><a name="imports">4.1 APIs Exported by Architecture-Specific Logic to NuttX</a></h2>
<h3><a name="upinitialize">4.1.1 <code>up_initialize()</code></a></h3>
<p><b>Prototype</b>: <code>void up_initialize(void);</code></p>
<p><b>Description</b>.
<code>up_initialize()</code> will be called once during OS
initialization after the basic OS services have been
initialized. The architecture specific details of
initializing the OS will be handled here. Such things as
setting up interrupt service routines, starting the
clock, and registering <a href="#DeviceDrivers">device drivers</a> are some of the
things that are different for each processor and hardware
platform.
</p>
<p>
<code>up_initialize()</code> is called after the OS initialized but
before the init process has been started and before the
libraries have been initialized. OS services and driver
services are available.
</p>
<h3><a name="upidle">4.1.2 <code>up_idle()</code></a></h3>
<p><b>Prototype</b>: <code>void up_idle(void);</code></p>
<p><b>Description</b>.
<code>up_idle()</code> is the logic that will be executed
when their is no other ready-to-run task. This is processor
idle time and will continue until some interrupt occurs to
cause a context switch from the idle task.
</p>
<p>
Processing in this state may be processor-specific. e.g.,
this is where power management operations might be performed.
</p>
<h3><a name="upinitialstate">4.1.3 <code>up_initial_state()</code></a></h3>
<p><b>Prototype</b>: <code>void up_initial_state(FAR struct tcb_s *tcb);</code></p>
<p><b>Description</b>.
A new thread is being started and a new TCB has been created.
This function is called to initialize the processor specific portions of the new TCB.
</p>
<p>
This function must setup the initial architecture registers and/or stack so that execution
will begin at tcb->start on the next context switch.
</p>
<p>
This function may also need to set up processor registers so that the new thread executes
with the correct privileges.
If <code>CONFIG_NUTTX_KERNEL</code> has been selected in the NuttX configuration,
then special initialization may need to be performed depending on the task type specified
in the TCB's flags field:
Kernel threads will require kernel-mode privileges;
User tasks and pthreads should have only user-mode privileges.
If <code>CONFIG_NUTTX_KERNEL</code> has <i>not</i> been selected,
then all threads should have kernel-mode privileges.
</p>
<h3><a name="upcreatestack">4.1.4 <code>up_create_stack()</code></a></h3>
<p><b>Prototype</b>: <code>STATUS up_create_stack(FAR struct tcb_s *tcb, size_t stack_size, uint8_t ttype);</code></p>
<p><b>Description</b>.
Allocate a stack for a new thread and setup up stack-related information in the TCB.
</p>
<p>
The following TCB fields must be initialized:
</p>
<ul>
<li><code>adj_stack_size</code>: Stack size after adjustment for hardware,
processor, etc. This value is retained only for debug
purposes.</li>
<li><code>stack_alloc_ptr</code>: Pointer to allocated stack</li>
<li><code>adj_stack_ptr</code>: Adjusted <code>stack_alloc_ptr</code> for HW. The
initial value of the stack pointer.
</ul>
<p>
This API is <i>NOT</i> required if <code>CONFIG_CUSTOM_STACK</code> is defined.
</p>
<p><b>Input Parameters</b>:</p>
<ul>
<li>
<p>
<code>tcb</code>: The TCB of new task.
</p>
</li>
<li>
<p>
<code>stack_size</code>: The requested stack size. At least this much must be allocated.
</p>
</li>
<li>
<p>
<code>ttype</code>: The thread type.
This may be one of following (defined in <code>include/nuttx/sched.h</code>):
</p>
<ul>
<li><code>TCB_FLAG_TTYPE_TASK</code>: Normal user task</li>
<li><code>TCB_FLAG_TTYPE_PTHREAD</code>: User pthread</li>
<li><code>TCB_FLAG_TTYPE_KERNEL</code>: Kernel thread</li>
</ul>
<p>
This thread type is normally available in the flags field of the TCB, however, there are certain contexts where the TCB may not be fully initialized when up_create_stack is called.
</p>
<p>
If <code>CONFIG_NUTTX_KERNEL</code> is defined, then this thread type may affect how the stack is allocated. For example, kernel thread stacks should be allocated from protected kernel memory. Stacks for user tasks and threads must come from memory that is accessible to user code.
</p>
</li>
</ul>
<h3><a name="upusestack">4.1.5 <code>up_use_stack()</code></a></h3>
<p><b>Prototype</b>:
<code>STATUS up_use_stack(FAR struct tcb_s *tcb, FAR void *stack, size_t stack_size);</code>
</p>
<p><b>Description</b>.
Setup up stack-related information in the TCB using pre-allocated stack memory.
This function is called only from <code>task_init()</code> when a task or kernel thread is started (never for pthreads).
</p>
<p>
The following TCB fields must be initialized:
</p>
<ul>
<li><code>adj_stack_size</code>: Stack size after adjustment for hardware,
processor, etc. This value is retained only for debug
purposes.</li>
<li><code>stack_alloc_ptr</code>: Pointer to allocated stack</li>
<li><code>adj_stack_ptr</code>: Adjusted <code>stack_alloc_ptr</code> for HW. The
initial value of the stack pointer.
</ul>
<p>
This API is <i>NOT</i> required if <code>CONFIG_CUSTOM_STACK</code> is defined.
</p>
<p><b>Input Parameters:</b></p>
<ul>
<li>
<code>tcb</code>: The TCB of new task.
</li>
<li>
<code>stack_size</code>: The allocated stack size.
</li>
</ul>
<p>
NOTE: Unlike <code>up_stack_create()</code> and <code>up_stack_release</code>, this function does not require the task type (<code>ttype</code>) parameter.
The TCB flags will always be set to provide the task type to <code>up_use_stack()</code> if the information needs that information.
</p>
<h3><a name="upstackframe">4.1.6 <code>up_stack_frame()</code></a></h3>
<p><b>Prototype</b>: <code>FAR void *up_stack_frame(FAR struct tcb_s *tcb, size_t frame_size);</code></p>
<p>
<b>Description</b>.
Allocate a stack frame in the TCB's stack to hold thread-specific data.
This function may be called anytime after <code>up_create_stack()</code> or <code>up_use_stack()</code> have been called but before the task has been started.
</p>
<p>
Thread data may be kept in the stack (instead of in the TCB) if it is accessed by the user code directly.
This includes such things as <code>argv[]</code>.
The stack memory is guaranteed to be in the same protection domain as the thread.
</p>
<p>
The following TCB fields will be re-initialized:
</p>
<ul>
<li>
<code>adj_stack_size</code>: Stack size after removal of the stack frame from the stack.
</li>
<li>
<code>adj_stack_ptr</code>: Adjusted initial stack pointer after the frame has been removed from the stack.
This will still be the initial value of the stack pointer when the task is started.
</li>
</ul>
<p>
This API is <i>NOT</i> required if <code>CONFIG_NUTTX_KERNEL</code> is undefined or if <code>CONFIG_CUSTOM_STACK</code> is defined.
</p>
<p><b>Input Parameters:</b></p>
<ul>
<li>
<p>
<code>tcb</code>:
The TCB of new task.
</p>
</li>
<li>
<p>
<code>frame_size</code>:
The size of the stack frame to allocate.
</p>
</li>
</ul>
<p>
<b>Returned Value:</b>
A pointer to bottom of the allocated stack frame.
NULL will be returned on any failures.
The alignment of the returned value is the same as the alignment of the stack itself
</p>
<h3><a name="upreleasestack">4.1.7 <code>up_release_stack()</code></a></h3>
<p><b>Prototype</b>: <code>void up_release_stack(FAR struct tcb_s *dtcb);</code></p>
<p><b>Description</b>.
A task has been stopped.
Free all stack related resources retained int the defunct TCB.
</p>
<p>
This API is <i>NOT</i> required if <code>CONFIG_CUSTOM_STACK</code> is defined.
</p>
<p><b>Input Parameters:</b></p>
<ul>
<li>
<p>
<code>dtcb</code>:
The TCB containing information about the stack to be released.
</p>
</li>
<li>
<p>
<code>ttype</code>: The thread type.
This may be one of following (defined in <code>include/nuttx/sched.h</code>):
</p>
<ul>
<li><code>TCB_FLAG_TTYPE_TASK</code>: Normal user task</li>
<li><code>TCB_FLAG_TTYPE_PTHREAD</code>: User pthread</li>
<li><code>TCB_FLAG_TTYPE_KERNEL</code>: Kernel thread</li>
</ul>
<p>
This thread type is normally available in the flags field of the TCB, however, there are certain error recovery contexts where the TCB may not be fully initialized when up_release_stack is called.
</p>
<p>
If <code>CONFIG_NUTTX_KERNEL</code> is defined, then this thread type may affect how the stack is freed.
For example, kernel thread stacks may have been allocated from protected kernel memory.
Stacks for user tasks and threads must have come from memory that is accessible to user
</p>
</li>
</ul>
<h3><a name="upunblocktask">4.1.8 <code>up_unblock_task()</code></a></h3>
<p><b>Prototype</b>: <code>void up_unblock_task(FAR struct tcb_s *tcb);</code></p>
<p><b>Description</b>.
A task is currently in an inactive task list
but has been prepped to execute. Move the TCB to the
ready-to-run list, restore its context, and start execution.
</p>
<p>
This function is called only from the NuttX scheduling
logic. Interrupts will always be disabled when this
function is called.
</p>
<p><b>Input Parameters</b>:
<ul>
<li><code>tcb</code>: Refers to the tcb to be unblocked. This tcb is
in one of the waiting tasks lists. It must be moved to
the ready-to-run list and, if it is the highest priority
ready to run tasks, executed.
</li>
</ul>
<h3><a name="upblocktask">4.1.9 <code>up_block_task()</code></a></h3>
<p><b>Prototype</b>: <code>void up_block_task(FAR struct tcb_s *tcb, tstate_t task_state);</code></p>
<p><b>Description</b>.
The currently executing task at the head of
the ready to run list must be stopped. Save its context
and move it to the inactive list specified by task_state.
This function is called only from the NuttX scheduling
logic. Interrupts will always be disabled when this
function is called.
<p><b>Input Parameters:</b></p>
<ul>
<li><code>tcb</code>: Refers to a task in the ready-to-run list (normally
the task at the head of the list). It most be
stopped, its context saved and moved into one of the
waiting task lists. It it was the task at the head
of the ready-to-run list, then a context to the new
ready to run task must be performed.
</li>
<li><code>task_state</code>: Specifies which waiting task list should be
hold the blocked task TCB.
</li>
</ul>
<h3><a name="upreleasepending">4.1.10 <code>up_release_pending()</code></a></h3>
<p><b>Prototype</b>: <code>void up_release_pending(void);</code></p>
<p><b>Description</b>.
When tasks become ready-to-run but cannot run because pre-emption
is disabled, they are placed into a pending task list.
This function releases and makes ready-to-run all of the tasks that have
collected in the pending task list. This can cause a
context switch if a new task is placed at the head of
the ready to run list.
</p>
<p>
This function is called only from the NuttX scheduling logic when
pre-emption is re-enabled. Interrupts will always be disabled when this
function is called.
</p>
<h3><a name="upreprioritizertr">4.1.11 <code>up_reprioritize_rtr()</code></a></h3>
<p><b>Prototype</b>: <code>void up_reprioritize_rtr(FAR struct tcb_s *tcb, uint8_t priority);</code></p>
<p><b>Description</b>.
Called when the priority of a running or
ready-to-run task changes and the reprioritization will
cause a context switch. Two cases:
</p>
<ol>
<li>
The priority of the currently running task drops and the next
task in the ready to run list has priority.
</li>
<li>
An idle, ready to run task's priority has been raised above the
the priority of the current, running task and it now has the
priority.
</li>
</ol>
<p>
This function is called only from the NuttX scheduling
logic. Interrupts will always be disabled when this
function is called.
</p>
<p><b>Input Parameters:</b></p>
<ul>
<li>
<code>tcb</code>: The TCB of the task that has been reprioritized
</li>
<li>
<code>priority</code>: The new task priority
</li>
</ul>
<h3><a name="_exit">4.1.12 <code>_exit()</code></a></h3>
<p><b>Prototype</b>: <code>void _exit(int status) noreturn_function;</code></p>
<p><b>Description</b>.
This function causes the currently executing task to cease
to exist. This is a special case of task_delete().
</p>
<p>
Unlike other UP APIs, this function may be called
directly from user programs in various states. The
implementation of this function should disable interrupts
before performing scheduling operations.
</p>
<h3><a name="upassert">4.1.13 <code>up_assert()</code></a></h3>
<p><b>Prototype</b>:<br>
<code>void up_assert(FAR const uint8_t *filename, int linenum);</code>
</p>
<p><b>Description</b>.
Assertions may be handled in an architecture-specific way.
</p>
<h3><a name="upschedulesigaction">4.1.14 <code>up_schedule_sigaction()</code></a></h3>
<p><b>Prototype</b>:
<code>void up_schedule_sigaction(FAR struct tcb_s *tcb, sig_deliver_t sigdeliver);</code>
</p>
<p><b>Description</b>.
This function is called by the OS when one or more
signal handling actions have been queued for execution.
The architecture specific code must configure things so
that the 'sigdeliver' callback is executed on the thread
specified by 'tcb' as soon as possible.
</p>
<p>
This function may be called from interrupt handling logic.
</p>
<p>
This operation should not cause the task to be unblocked
nor should it cause any immediate execution of sigdeliver.
Typically, a few cases need to be considered:
</p>
<ol>
<li>
This function may be called from an interrupt handler
During interrupt processing, all xcptcontext structures
should be valid for all tasks. That structure should
be modified to invoke sigdeliver() either on return
from (this) interrupt or on some subsequent context
switch to the recipient task.
</li>
<li>
If not in an interrupt handler and the tcb is NOT
the currently executing task, then again just modify
the saved xcptcontext structure for the recipient
task so it will invoke sigdeliver when that task is
later resumed.
</li>
<li>
If not in an interrupt handler and the tcb IS the
currently executing task -- just call the signal
handler now.
</li>
</ol>
<p>
This API is <i>NOT</i> required if <code>CONFIG_DISABLE_SIGNALS</code>
is defined.
</p>
<h3><a name="upallocateheap">4.1.15 <code>up_allocate_heap()</code></a></h3>
<p><b>Prototype</b>: <code>void up_allocate_heap(FAR void **heap_start, size_t *heap_size);</code></p>
<p><b>Description</b>.
This function will be called to dynamically set aside the heap region.
</p>
<p>
For the kernel build (<code>CONFIG_NUTTX_KERNEL</code>=y) with both kernel- and user-space heaps (<code>CONFIG_MM_KERNEL_HEAP</code>=y), this function provides the size of the unprotected, user-space heap.
If a protected kernel-space heap is provided, the kernel heap must be allocated (and protected) by an analogous <code>up_allocate_kheap()</code>.
</p>
<h3><a name="upinterruptcontext">4.1.16 <code>up_interrupt_context()</code></a></h3>
<p><b>Prototype</b>: <code>bool up_interrupt_context(void)</code></p>
<p><b>Description</b>.
Return true if we are currently executing in the interrupt handler context.
</p>
<h3><a name="updisableirq">4.1.17 <code>up_disable_irq()</code></a></h3>
<p><b>Prototype</b>:</p>
<ul><pre>
#ifndef CONFIG_ARCH_NOINTC
void up_disable_irq(int irq);
#endif
</pre></ul>
<p><b>Description</b>.
Disable the IRQ specified by 'irq'
On many architectures, there are three levels of interrupt enabling: (1)
at the global level, (2) at the level of the interrupt controller,
and (3) at the device level. In order to receive interrupts, they
must be enabled at all three levels.
</p>
<p>
This function implements enabling of the device specified by 'irq'
at the interrupt controller level if supported by the architecture
(irqsave() supports the global level, the device level is hardware
specific).
<p>
If the architecture does not support <code>up_disable_irq</code>,
<code>CONFIG_ARCH_NOINTC</code> should be defined in the NuttX configuration file.
Since this API cannot be supported on all architectures, it should be
avoided in common implementations where possible.
</p>
<h3><a name="upenableirq">4.1.18 <code>up_enable_irq()</code></a></h3>
<p><b>Prototype</b>:</p>
<ul><pre>
#ifndef CONFIG_ARCH_NOINTC
void up_enable_irq(int irq);
#endif
</pre></ul>
<p><b>Description</b>.
This function implements disabling of the device specified by 'irq'
at the interrupt controller level if supported by the architecture
(irqrestore() supports the global level, the device level is hardware
specific).
</p>
<p>
If the architecture does not support <code>up_disable_irq</code>,
<code>CONFIG_ARCH_NOINTC</code> should be defined in the NuttX configuration file.
Since this API cannot be supported on all architectures, it should be
avoided in common implementations where possible.
</p>
<h3><a name="upprioritizeirq">4.1.19 <code>up_prioritize_irq()</code></a></h3>
<p><b>Prototype</b>:</p>
<ul><pre>
#ifdef CONFIG_ARCH_IRQPRIO
void up_enable_irq(int irq);
#endif
</pre></ul>
<p><b>Description</b>.
Set the priority of an IRQ.
</p>
<p>
If the architecture supports <code>up_enable_irq</code>,
<code>CONFIG_ARCH_IRQPRIO</code> should be defined in the NuttX configuration file.
Since this API cannot be supported on all architectures, it should be
avoided in common implementations where possible.
</p>
<h3><a name="upputc">4.1.20 <code>up_putc()</code></a></h3>
<p><b>Prototype</b>: <code>int up_putc(int ch);</code></p>
<p><b>Description</b>.
This is a debug interface exported by the architecture-specific logic.
Output one character on the console
</p>
<h3><a name="systemtime">4.1.21 System Time and Clock</a></h3>
<h4>4.1.21.1 Basic System Timer</h4>
<p><b>System Timer</b>
In most implementations, system time is provided by a timer interrupt.
That timer interrupt runs at rate determined by <code>CONFIG_MSEC_PER_TICKS</code> (default 10 or 100Hz).
The timer generates an interrupt each <code>CONFIG_MSEC_PER_TICKS</code> milliseconds and increments a counter called <code>g_system_timer</code>.
<code>g_system_timer</code> then provides a time-base for calculating <i>up-time</i> and elapsed time intervals in units of <code>CONFIG_MSEC_PER_TICKS</code>.
The range of <code>g_system_timer</code> is, by default, 32-bits.
However, if the MCU supports type <code>long long</code> and <code>CONFIG_SYSTEM_TIME16</code> is selected,
a 64-bit system timer will be supported instead.
</p>
<p><b>System Timer Accuracy</b>
On many system, the exact timer interval specified by <code>CONFIG_MSEC_PER_TICKS</code> cannot be achieved due to limitations in frequencies or in dividers.
As a result, the time interval specified by <code>CONFIG_MSEC_PER_TICKS</code> may only be approximate and there may be small errors in the apparent <i>up-time</i> time.
These small errors, however, will accumulate over time and after a long period of time may have an unacceptably large error in the apparent <i>up-time</i> of the MCU.
</p>
If the timer tick period generated by the hardware is not exactly <code>CONFIG_MSEC_PER_TICKS</code> <i>and</i> if there you require accurate up-time for the MCU, then there are measures that you can take:
</p>
<ul>
<li>
Perhaps you can adjust <code>CONFIG_MSEC_PER_TICKS</code> to a different value so that an exactly <code>CONFIG_MSEC_PER_TICKS</code> can be accomplished.
</li>
<li>
Or you can use a technique known as <i>Delta-Sigma Modulation</i>. (Suggested by Uros Platise). Consider the example below.
</li>
</ul>
<p><b>Delta-Sigma Modulation Example</b>.
Consider this case: The system timer is a count-up timer driven at 32.768KHz.
There are dividers that can be used, but a divider of one yields the highest accuracy.
This counter counts up until the count equals a match value, then a timer interrupt is generated.
The desire frequency is 100Hz (<code>CONFIG_MSEC_PER_TICKS</code> is 10).
</p>
<p>
This exact frequency of 100Hz cannot be obtained in this case.
In order to obtain that exact frequency a match value of 327.68 would have to be provided.
The closest integer value is 328 but the ideal match value is between 327 and 328.
The closest value, 328, would yield an actual timer frequency of 99.9Hz!
That will may cause significant timing errors in certain usages.
</p>
<p>
Use of Delta-Sigma Modulation can eliminate this error in the long run.
Consider this example implementation:
</p>
<ol>
<li>
Initially an accumulator is zero an the match value is programmed to 328:
<ul><pre>
accumulator = 0;
match = 328;
</pre></ul>
</li>
<li>
On each timer interrupt, accumulator is updated with difference that, in this reflects, 100* the error in interval that just passed.
So on the first timer interrupt, the accumulator would be updated like:
<ul><pre>
if (match == 328)
{
accumulator += 32; // 100*(328 - 327.68)
}
else
{
accumulator -= 68; // (100*(327 - 327.68)
}
</pre></ul>
</li>
<li>
And on that same timer interrupt a new match value would be programmed:
<ul><pre>
if (accumulator < 0)
{
match = 328;
}
else
{
match = 327;
}
</pre></ul>
</ol>
<p>
In this way, the timer interval is controlled from interrupt-to-interrupt to produce an average frequency of exactly 100Hz.
</p>
<h4>4.1.21.2 Hardware</h4>
<p>
To enable hardware module use the following configuration options:
<p>
<ul><dl>
<dt><code>CONFIG_RTC</code>
<dd>Enables general support for a hardware RTC.
Specific architectures may require other specific settings.
<dt><code>CONFIG_RTC_DATETIME</code>
<dd>There are two general types of RTC: (1) A simple battery backed counter that keeps the time when power
is down, and (2) A full date / time RTC the provides the date and time information, often in BCD format.
If <code>CONFIG_RTC_DATETIME</code> is selected, it specifies this second kind of RTC.
In this case, the RTC is used to "seed"" the normal NuttX timer and the NuttX system timer
provides for higher resoution time.
<dt><code>CONFIG_RTC_HIRES</code>
<dd>If <code>CONFIG_RTC_DATETIME</code> not selected, then the simple, battery backed counter is used.
There are two different implementations of such simple counters based on the time resolution of the counter:
The typical RTC keeps time to resolution of 1 second, usually supporting a 32-bit <code>time_t</code> value.
In this case, the RTC is used to "seed" the normal NuttX timer and the NuttX timer provides for higher resoution time.
If <code>CONFIG_RTC_HIRES</code> is enabled in the NuttX configuration, then the RTC provides higher resolution time and completely replaces the system timer for purpose of date and time.
<dt><code>CONFIG_RTC_FREQUENCY</code>
<dd>If <code>CONFIG_RTC_HIRES</code> is defined, then the frequency of the high resolution RTC must be provided.
If <code>CONFIG_RTC_HIRES</code> is not defined, <code>CONFIG_RTC_FREQUENCY</code> is assumed to be one.
<dt><code>CONFIG_RTC_ALARM</code>
<dd>Enable if the RTC hardware supports setting of an alarm.
A callback function will be executed when the alarm goes off
</dl></ul>
<p>
which requires the following base functions to read and set time:
</p>
<ul>
<li><code>up_rtcinitialize()</code>.
Initialize the hardware RTC per the selected configuration.
This function is called once during the OS initialization sequence
</li>
<li><code>up_rtc_time()</code>.
Get the current time in seconds. This is similar to the standard <code>time()</code> function.
This interface is only required if the low-resolution RTC/counter hardware implementation selected.
It is only used by the RTOS during intialization to set up the system time when <code>CONFIG_RTC</code> is set
but neither <code>CONFIG_RTC_HIRES</code> nor <code>CONFIG_RTC_DATETIME</code> are set.
</li>
<li><code>up_rtc_gettime()</code>.
Get the current time from the high resolution RTC clock/counter.
This interface is only supported by the hight-resolution RTC/counter hardware implementation.
It is used to replace the system timer (<code>g_system_tick</code>).
</li>
<li><code>up_rtc_settime()</code>.
Set the RTC to the provided time.
All RTC implementations must be able to set their time based on a standard timespec.
</li>
<li><code>up_rtc_setalarm()</code>.
Set up an alarm.
</li>
</ul>
<h4>4.1.21.3 System Tick and Time</h4>
<p>
The system tick is represented by::
</p>
<ul>
<li><code>g_system_timer</code></li>
</ul>
<p>
Running at rate of system base timer, used for time-slicing, and so forth.
</p>
<p>
If hardware RTC is present (<code>CONFIG_RTC</code>) and and high-resolution timing
is enabled (<code>CONFIG_RTC_HIRES</code>), then after successful
initiliazation variables are overriden by calls to <code>up_rtc_gettime()</code> which is
running continously even in power-down modes.
</p>
<p>
In the case of <code>CONFIG_RTC_HIRES</code> is set the <code>g_system_timer</code>
keeps counting at rate of a system timer, which however, is disabled in power-down mode.
By comparing this time and RTC (actual time) one may determine the actual system active time.
To retrieve that variable use:
</p>
<h3><a name="addrenv">4.1.22 Address Environments</a></h3>
<p>
CPUs that support memory management units (MMUs) may provide <i>address environments</i> within which tasks and their child threads execute.
The configuration indicates the CPUs ability to support address environments by setting the configuration varabile <code>CONFIG_ADDRENV=y</code>.
These address environments are created only when tasks are created via <code>exec()</code> or <code>exec_module()</code> (see <code>include/nuttx/binfmt/binfmt.h</code>).
</p>
<p>
When <code>CONFIG_ADDRENV=y</code> is set in the board configuration, the CPU-specific logic must provide a set of interfaces as defined in the header file <code>include/nuttx/arch.h</code>.
These interfaces are listed below and described in detail in the following paragraphs.
</p>
<p>
The CPU-specific logic must provide two categories in interfaces:
</p>
<ol>
<li>
<p>
<b>Binary Loader Support</b>.
These are low-level interfaces used in <code>binfmt/</code> to instantiate tasks with address environments.
These interfaces all operate on type <code>task_addrenv_t</code> which is an abstract representation of a asks's address environment and must be defined in arch/arch.h if <code>CONFIG_ADDRENV</code> is defined.
These low-level interfaces include:
</p>
<ul>
<li>
<a href="#up_addrenv_create">4.1.22.1 <code>up_addrenv_create()</code></a>:
Create an address environment.
</li>
<li>
<a href="#up_addrenv_vaddr">4.1.22.2 <code>up_addrenv_vaddr()</code></a>:
Returns the virtual base address of the address environment.
</li>
<li>
<a href="#up_addrenv_select">4.1.22.3 <code>up_addrenv_select()</code></a>:
Instantiate an address environment.
</li>
<li>
<a href="#up_addrenv_restore">4.1.22.4 <code>up_addrenv_restore()</code></a>:
Restore an address environment.
</li>
<li>
<a href="#up_addrenv_destroy">4.1.22.5 <code>up_addrenv_destroy()</code></a>:
Destroy an address environment.
</li>
<li>
<a href="#up_addrenv_assign">4.1.22.6 <code>up_addrenv_assign()</code></a>:
Assign an address environment to a TCB.
</li>
</ul>
</li>
<li>
<p>
<b>Tasking Support</b>.
Other interfaces must be provided to support higher-level interfaces used by the NuttX tasking logic.
These interfaces are* used by the functions in <code>sched/</code> and all operate on the TCB which as been assigned an address environment by <code>up_addrenv_assign()</code>.
</p>
<ul>
<li>
<a href="#up_addrenv_share">4.1.22.7 <code>up_addrenv_share()</code></a>:
Clone the address environment assigned to one TCB to another.
This operation is done when a pthread is created that share's the same address environment.
</li>
<li>
<a href="#up_addrenv_release">4.1.22.8 <code>up_addrenv_release()</code></a>:
Release the TCB's reference to an address environment when a task/thread exits.
</li>
</ul>
</li>
</ol>
<h4><a name="up_addrenv_create">4.1.22.1 <code>up_addrenv_create()</code></a></h4>
<p><b>Prototype</b>:</p>
<ul>
<code>int up_addrenv_create(size_t envsize, FAR task_addrenv_t *addrenv);</code>
</ul>
<p><b>Description</b>:</p>
<ul>
This function is called from the binary loader logic when a new task is created in order to instantiate an address environment for the task.
<code>up_addrenv_create()</code> is essentially the allocator of the physical memory for the new task.
</ul>
<p><b>Input Parameters</b>:</p>
<ul>
<li><code>envsize</code>: The size (in bytes) of the address environment needed by the task.</li>
<li><code>addrenv</code>: The location to return the representation of the task address environment.</li>
</ul>
<p><b>Returned Value</b>:</p>
<ul>
Zero (<code>OK</code>) on success; a negated <code>errno</code> value on failure.
</ul>
<h4><a name="up_addrenv_vaddr">4.1.22.2 <code>up_addrenv_vaddr()</code></a></h4>
<p><b>Prototype</b>:<p>
<ul>
<code>int up_addrenv_vaddr(FAR task_addrenv_t addrenv, FAR void **vaddr);</code>
</ul>
<p><b>Description</b>:</p>
<ul>
Return the virtual address associated with the newly create address environment.
This function is used by the binary loaders in order get an address that can be used to initialize the new task.
</ul>
<p><b>Input Parameters</b>:</p>
<ul>
<li><code>addrenv</code>: The representation of the task address environment previously returned by up_addrenv_create.</li>
<li><code>vaddr</code>: The location to return the virtual address.</li>
</ul>
<p><b>Returned Value</b>:</p>
<ul>
Zero (<code>OK</code>) on success; a negated <code>errno</code> value on failure.
</ul>
<h4><a name="up_addrenv_select">4.1.22.3 <code>up_addrenv_select()</code></a></h4>
<p><b>Prototype</b>:<p>
<ul>
<code>int up_addrenv_select(task_addrenv_t addrenv, hw_addrenv_t *oldenv);</code>
</ul>
<p><b>Description</b>:</p>
<ul>
After an address environment has been established for a task (via <code>up_addrenv_create())</code>, this function may be called to to instantiate that address environment in the virtual address space.
This might be necessary, for example, to load the code for the task from a file or to access address environment private data.
</ul>
<p><b>Input Parameters</b>:</p>
<ul>
<li><code>addrenv</code>: The representation of the task address environment previously returned by up_addrenv_create.</li>
<li><code>oldenv</code>:
The address environment that was in place before <code>up_addrenv_select()</code> was called.
This may be used with <code>up_addrenv_restore()</code> to restore the original address environment that was in place before <code>up_addrenv_select()</code> was called.
Note that this may be a task agnostic, hardware representation that is different from <code>task_addrenv_t</code>.
</li>
</ul>
<p><b>Returned Value</b>:</p>
<ul>
Zero (<code>OK</code>) on success; a negated <code>errno</code> value on failure.
</ul>
<h4><a name="up_addrenv_restore">4.1.22.4 <code>up_addrenv_restore()</code></a></h4>
<p><b>Prototype</b>:<p>
<ul>
<code>int up_addrenv_restore(hw_addrenv_t oldenv);</code>
</ul>
<p><b>Description</b>:</p>
<ul>
After an address environment has been temporarilty instantiated by <code>up_addrenv_select</code>,
this function may be called to to restore the original address environment.
</ul>
<p><b>Input Parameters</b>:</p>
<ul>
<li><code>oldenv</code>: The hardware representation of the address environment previously returned by <code>up_addrenv_select()</code>.</li>
</ul>
<p><b>Returned Value</b>:</p>
<ul>
Zero (<code>OK</code>) on success; a negated <code>errno</code> value on failure.
</ul>
<h4><a name="up_addrenv_destroy">4.1.22.5 <code>up_addrenv_destroy()</code></a></h4>
<p><b>Prototype</b>:<p>
<ul>
<code>int up_addrenv_destroy(task_addrenv_t addrenv);</code>
</ul>
<p><b>Description</b>:</p>
<ul>
Called from the binary loader loader during error handling to destroy the address environment previously created by <code>up_addrenv_create()</code>.
</ul>
<p><b>Input Parameters</b>:</p>
<ul>
<li><code>addrenv</code>: The representation of the task address environment previously returned by up_addrenv_create.</li>
</ul>
<p><b>Returned Value</b>:</p>
<ul>
Zero (<code>OK</code>) on success; a negated <code>errno</code> value on failure.
</ul>
<h4><a name="up_addrenv_assign">4.1.22.6 <code>up_addrenv_assign()</code></a></h4>
<p><b>Prototype</b>:<p>
<ul>
<code>int up_addrenv_assign(task_addrenv_t addrenv, FAR struct tcb_s *tcb);</code>
</ul>
<p><b>Description</b>:</p>
<ul>
Assign an address environment to a TCB.
</ul>
<p><b>Input Parameters</b>:</p>
<ul>
<li><code>addrenv</code>: The representation of the task address environment previously returned by up_addrenv_create.</li>
<li><code>tcb</code>: The TCB of the task to receive the address environment.</li>
</ul>
<p><b>Returned Value</b>:</p>
<ul>
Zero (<code>OK</code>) on success; a negated <code>errno</code> value on failure.
</ul>
<h4><a name="up_addrenv_share">4.1.22.7 <code>up_addrenv_share()</code></a></h4>
<p><b>Prototype</b>:<p>
<ul>
<code>int up_addrenv_share(FAR const struct tcb_s *ptcb, FAR struct tcb_s *ctcb);</code>
</ul>
<p><b>Description</b>:</p>
<ul>
This function is called from the core scheduler logic when a thread is created that needs to share the address ennvironment of its parent task.
In this case, the parent's address environment needs to be "cloned" for the child thread.
</ul>
<p><b>Input Parameters</b>:</p>
<ul>
<li><code>ptcb</code>: The TCB of the parent task that has the address environment.</li>
<li><code>ctcb</code>: The TCB of the child thread needing the address environment.</li>
</ul>
<p><b>Returned Value</b>:</p>
<ul>
Zero (<code>OK</code>) on success; a negated <code>errno</code> value on failure.
</ul>
<h4><a name="up_addrenv_release">4.1.22.8 <code>up_addrenv_release()</code></a></h4>
<p><b>Prototype</b>:<p>
<ul>
<code>int up_addrenv_release(FAR struct tcb_s *tcb);</code>
</ul>
<p><b>Description</b>:</p>
<ul>
This function is called when a task or thread exits in order to release its reference to an address environment.
When there are no furtherreferences to an address environment, that address environment should
be destroyed.
</ul>
<p><b>Input Parameters</b>:</p>
<ul>
<li><code>tcb</code>: The TCB of the task or thread whose the address environment will be released.</li>
</ul>
<p><b>Returned Value</b>:</p>
<ul>
Zero (<code>OK</code>) on success; a negated <code>errno</code> value on failure.
</ul>
<h2><a name="exports">4.2 APIs Exported by NuttX to Architecture-Specific Logic</a></h2>
<p>
These are standard interfaces that are exported by the OS
for use by the architecture specific logic.
</p>
<h3><a name="osstart">4.2.1 <code>os_start()</code></a></h3>
<p>
<b><i>To be provided</i></b>
</p>
<h3><a name="listmgmt">4.2.2 OS List Management APIs</a></h3></h3>
<p>
<b><i>To be provided</i></b>
</p>
<h3><a name="schedprocesstimer">4.2.3 <code>sched_process_timer()</code></a></h3>
<p><b>Prototype</b>: <code>void sched_process_timer(void);</code></p>
<p><b>Description</b>.
This function handles system timer events.
The timer interrupt logic itself is implemented in the
architecture specific code, but must call the following OS
function periodically -- the calling interval must be
<code>MSEC_PER_TICK</code>.
</p>
<h3><a name="irqdispatch">4.2.4 <code>irq_dispatch()</code></a></h3>
<p><b>Prototype</b>: <code>void irq_dispatch(int irq, FAR void *context);</code></p>
<p><b>Description</b>.
This function must be called from the architecture-
specific logic in order to display an interrupt to
the appropriate, registered handling logic.
</p>
<h2><a name="demandpaging">4.3 On-Demand Paging</a></h2>
<p>
The NuttX On-Demand Paging feature permits embedded MCUs with some limited RAM space to execute large programs from some non-random access media.
If the platform meets certiain requirements, then NuttX can provide on-demand paging:
It can copy .text from the large program in non-volatile media into RAM as needed to execute a huge program from the small RAM.
Design and porting issues for this feature are discussed in a sepate document.
Please see the <a href="NuttXDemandPaging.html">NuttX Demand Paging</a> design document for further information.
</p>
<h2><a name="ledsupport">4.4 LED Support</a></h2>
<p>
A board architecture may or may not have LEDs.
If the board does have LEDs, then most architectures provide similar LED support that is enabled when <code>CONFIG_ARCH_LEDS</code>
is selected in the NuttX configuration file.
This LED support is part of architecture-specific logic and is not managed by the core NuttX logic.
However, the support provided by each architecture is sufficiently similar that it can be documented here.
</p>
<h3><a name="ledheaders">4.3.1 Header Files</a></h3>
<p>
LED-related definitions are provided in two header files:
<ul>
<li>
LED definitions are provided for each board in the <code>board.h</code> that resides
in the <code><i><board-name></i>/include/board.h</code> file (which is also
linked to <code>include/arch/board/board.h</code> when the RTOS is configured).
Those definitions are discussed <a href="#leddefinitions">below</a>.
</li>
<li>
The board-specific logic provides unique instances of the LED interfaces.
This is because the implementation of LED support may be very different
on different boards.
Prototypes for these board-specific implementations are, however, provided
in architecture-common header files.
That header file is usually at <code><i><arch-name></i>/src/common/up_internal.h</code>,
but could be at other locations in particular architectures.
These prototypes are discussed <a href="#ledapis">below</a>.
</li>
</ul>
</p>
<h3><a name="leddefinitions">4.3.2 LED Definitions</a></h3>
<p>
The implementation of LED support is very specific to a board architecture.
Some boards have several LEDS, others have only one or two.
Some have none.
Others LED matrices and show alphanumeric data, etc.
The NuttX logic does not refer to specific LEDS, rather, it refers to an event to be shown on the LEDS
in whatever manner is appropriate for the board;
the way that this event is presented depends upon the hardware available on the board.
</p>
<p>
The model used by NuttX is that the board can show 8 events defined as follows in <code><i><board-name></i>/include/board.h</code>:
</p>
<ul><pre>
#define LED_STARTED ??
#define LED_HEAPALLOCATE ??
#define LED_IRQSENABLED ??
#define LED_STACKCREATED ??
#define LED_INIRQ ??
#define LED_SIGNAL ??
#define LED_ASSERTION ??
#define LED_PANIC ??
</pre></ul>
<p>
The specific value assigned to each pre-processor variable can be whatever makes the implementation easiest for the board logic.
The <i>meaning</i> associated with each definition is as follows:
</p>
<ul>
<li>
<code>LED_STARTED</code> is the value that describes the setting of the LEDs when the LED logic is first initialized.
This LED value is set but never cleared.
</li>
<li>
<code>LED_HEAPALLOCATE</code> indicates that the NuttX heap has been configured.
This is an important place in the boot sequence because if the memory is configured wrong, it will probably crash leaving this LED setting.
This LED value is set but never cleared.
</li>
<li>
<code>LED_IRQSENABLED</code> indicates that interrupts have been enabled.
Again, during bring-up (or if there are hardware problems), it is very likely that the system may crash just when interrupts are enabled, leaving this setting on the LEDs.
This LED value is set but never cleared.
</li>
<li>
<code>LED_STACKCREATED</code> is set each time a new stack is created.
If set, it means that the system attempted to start at least one new thread.
This LED value is set but never cleared.
</li>
<li>
<code>LED_INIRQ</code> is set and cleared on entry and exit from each interrupt.
If interrupts are working okay, this LED will have a dull glow.
</li>
<li>
<code>LED_SIGNAL</code> is set and cleared on entry and exit from a signal handler.
Signal handlers are tricky so this is especially useful during bring-up or a new architecture.
</li>
<li>
<code>LED_ASSERTION</code> is set if an assertion occurs.
</li>
<li>
<code>LED_PANIC</code> will blink at around 1Hz if the system panics and hangs.
</li>
</ul>
<h3><a name="ledapis">4.3.3 Common LED interfaces</a></h3>
<p>
The <code><i><arch-name></i>/src/common/up_internal.h</code> probably has definitions
like:
</p>
<ul><pre>
/* Defined in board/up_leds.c */
#ifdef CONFIG_ARCH_LEDS
extern void up_ledinit(void);
extern void up_ledon(int led);
extern void up_ledoff(int led);
#else
# define up_ledinit()
# define up_ledon(led)
# define up_ledoff(led)
#endif
</pre></ul>
<p>
Where:
<p>
<ul>
<li>
<code>void up_ledinit(void)</code> is called early in power-up initialization to initialize the LED hardware.
</li>
<li>
<code>up_ledon(int led)</code> is called to instantiate the LED presentation of the event.
The <code>led</code> argument is one of the definitions provided in <code><i><board-name></i>/include/board.h</code>.
</li>
<li>
<code>up_ledoff(int led</code>is called to terminate the LED presentation of the event.
The <code>led</code> argument is one of the definitions provided in <code><i><board-name></i>/include/board.h</code>.
Note that only <code>LED_INIRQ</code>, <code>LED_SIGNAL</code>, <code>LED_ASSERTION</code>, and <code>LED_PANIC</code>
indications are terminated.
</li>
</ul>
<table width ="100%">
<tr bgcolor="#e4e4e4">
<td>
<h1><a name="NxFileSystem">5.0 NuttX File System</a></h1>
</td>
</tr>
</table>
<p><b>Overview</b>.
NuttX includes an optional, scalable file system.
This file-system may be omitted altogether; NuttX does not depend on the presence
of any file system.
</p>
<p><b>Pseudo Root File System</b>.
Or, a simple <i>in-memory</i>, <i>pseudo</i> file system can be enabled.
This simple file system can be enabled setting the CONFIG_NFILE_DESCRIPTORS
option to a non-zero value (see <a href="#apndxconfigs">Appendix A</a>).
This is an <i>in-memory</i> file system because it does not require any
storage medium or block driver support.
Rather, file system contents are generated on-the-fly as referenced via
standard file system operations (open, close, read, write, etc.).
In this sense, the file system is <i>pseudo</i> file system (in the
same sense that the Linux <code>/proc</code> file system is also
referred to as a pseudo file system).
</p>
<p>
Any user supplied data or logic can be accessed via the pseudo-file system.
Built in support is provided for character and block <a href="#DeviceDrivers">drivers</a> in the
<code>/dev</code> pseudo file system directory.
</p>
<p><b>Mounted File Systems</b>
The simple in-memory file system can be extended my mounting block
devices that provide access to true file systems backed up via some
mass storage device.
NuttX supports the standard <code>mount()</code> command that allows
a block driver to be bound to a mountpoint within the pseudo file system
and to a file system.
At present, NuttX supports the standard VFAT and ROMFS file systems,
a special, wear-leveling NuttX FLASH File System (NXFFS),
as well as a Network File System client (NFS version 3, UDP).
</p>
<p><b>Comparison to Linux</b>
From a programming perspective, the NuttX file system appears very similar
to a Linux file system.
However, there is a fundamental difference:
The NuttX root file system is a pseudo file system and true file systems may be
mounted in the pseudo file system.
In the typical Linux installation by comparison, the Linux root file system
is a true file system and pseudo file systems may be mounted in the true,
root file system.
The approach selected by NuttX is intended to support greater scalability
from the very tiny platform to the moderate platform.
</p>
<table width ="100%">
<tr bgcolor="#e4e4e4">
<td>
<h1><a name="DeviceDrivers">6.0 NuttX Device Drivers</a></h1>
</td>
</tr>
</table>
<p>
NuttX supports a variety of device drivers including:
<ul>
<li><i>Character</i> Device Drivers,</li>
<li><i>Block</i> Device Drivers, and</li>
<li>Other <i>Specialized</i> Drivers.</li>
</ul>
These different device driver types are discussed in the following paragraphs.
Note: device driver support requires that the <i>in-memory</i>, <i>pseudo</i> file system
is enabled by setting the CONFIG_NFILE_DESCRIPTORS in the NuttX configuration file to a
non-zero value.
</p>
<h2><a name="chardrivers">6.1 Character Device Drivers</a></h2>
<p>
Character device drivers have these properties:
</p>
<ul>
<li>
<p>
<b><code>include/nuttx/fs/fs.h</code></b>.
All structures and APIs needed to work with character drivers are provided in this header file.
</p>
</li>
<li>
<p>
<b><code>struct file_operations</code></b>.
Each character device driver must implement an instance of <code>struct file_operations</code>.
That structure defines a call table with the following methods:
<ul>
<p><code>int open(FAR struct file *filp);</code><br>
<code>int close(FAR struct file *filp);</code><br>
<code>ssize_t read(FAR struct file *filp, FAR char *buffer, size_t buflen);</code><br>
<code>ssize_t write(FAR struct file *filp, FAR const char *buffer, size_t buflen);</code><br>
<code>off_t seek(FAR struct file *filp, off_t offset, int whence);</code><br>
<code>int ioctl(FAR struct file *filp, int cmd, unsigned long arg);</code><br>
<code>int poll(FAR struct file *filp, struct pollfd *fds, bool setup);</code></p>
</ul>
</p>
</li>
<li>
<p>
<b><code>int register_driver(const char *path, const struct file_operations *fops, mode_t mode, void *priv);</code></b>.
Each character driver registers itself by calling <code>register_driver()</code>, passing it the
<code>path</code> where it will appear in the <a href="#NxFileSystem">pseudo-file-system</a> and it's
initialized instance of <code>struct file_operations</code>.
</p>
</li>
<li>
<p>
<b>User Access</b>.
After it has been registered, the character driver can be accessed by user code using the standard
<a href="NuttxUserGuide.html#driveroperations">driver operations</a> including
<code>open()</code>, <code>close()</code>, <code>read()</code>, <code>write()</code>, etc.
</p>
</li>
<li>
<p>
<b>Examples</b>:
<code>drivers/dev_null.c</code>, <code>drivers/fifo.c</code>, <code>drivers/serial.c</code>, etc.
</p>
</li>
</ul>
<h2><a name="blockdrivers">6.2 Block Device Drivers</a></h2>
<p>
Block device drivers have these properties:
</p>
<ul>
<li>
<p>
<b><code>include/nuttx/fs/fs.h</code></b>.
All structures and APIs needed to work with block drivers are provided in this header file.
</p>
</li>
<li>
<p>
<b><code>struct block_operations</code></b>.
Each block device driver must implement an instance of <code>struct block_operations</code>.
That structure defines a call table with the following methods:
<ul>
<p><code>int open(FAR struct inode *inode);</code><br>
<code>int close(FAR struct inode *inode);</code><br>
<code>ssize_t read(FAR struct inode *inode, FAR unsigned char *buffer, size_t start_sector, unsigned int nsectors);</code><br>
<code>ssize_t write(FAR struct inode *inode, FAR const unsigned char *buffer, size_t start_sector, unsigned int nsectors);</code><br>
<code>int geometry(FAR struct inode *inode, FAR struct geometry *geometry);</code><br>
<code>int ioctl(FAR struct inode *inode, int cmd, unsigned long arg);</code></p>
</ul>
</p>
</li>
<li>
<p>
<b><code>int register_blockdriver(const char *path, const struct block_operations *bops, mode_t mode, void *priv);</code></b>.
Each block driver registers itself by calling <code>register_blockdriver()</code>, passing it the
<code>path</code> where it will appear in the <a href="#NxFileSystem">pseudo-file-system</a> and it's
initialized instance of <code>struct block_operations</code>.
</p>
</li>
<li>
<p>
<b>User Access</b>.
Users do not normally access block drivers directly, rather, they access block drivers
indirectly through the <code>mount()</code> API.
The <code>mount()</code> API binds a block driver instance with a file system and with a mountpoint.
Then the user may use the block driver to access the file system on the underlying media.
<i>Example</i>: See the <code>cmd_mount()</code> implementation in <code>apps/nshlib/nsh_fscmds.c</code>.
</p>
</li>
<li>
<p>
<b>Accessing a Character Driver as a Block Device</b>.
See the loop device at <code>drivers/loop.c</code>.
<i>Example</i>: See the <code>cmd_losetup()</code> implementation in <code>apps/nshlib/nsh_fscmds.c</code>.
</p>
</li>
<li>
<p>
<b>Accessing a Block Driver as Character Device</b>.
See the Block-to-Character (BCH) conversion logic in <code>drivers/bch/</code>.
<i>Example</i>: See the <code>cmd_dd()</code> implementation in <code>apps/nshlib/nsh_ddcmd.c</code>.
</p>
</li>
<li>
<p>
<b>Examples</b>.
<code>drivers/loop.c</code>, <code>drivers/mmcsd/mmcsd_spi.c</code>, <code>drivers/ramdisk.c</code>, etc.
</p>
</li>
</ul>
<h2><a name="blockdrivers">6.3 Specialized Device Drivers</a></h2>
<h3><a name="ethdrivers">6.3.1 Ethernet Device Drivers</a></h3>
<ul>
<li>
<p>
<b><code>include/nuttx/net/uip/uip-arch.h</code></b>.
All structures and APIs needed to work with Ethernet drivers are provided in this header file.
The structure <code>struct uip_driver_s</code> defines the interface and is passed to uIP via
<code>netdev_register()</code>.
</p>
</li>
<li>
<p>
<b><code>int netdev_register(FAR struct uip_driver_s *dev);</code></b>.
Each Ethernet driver registers itself by calling <code>netdev_register()</code>.
</p>
</li>
<li>
<p>
<b>Examples</b>:
<code>drivers/net/dm90x0.c</code>, <code>arch/drivers/arm/src/c5471/c5471_ethernet.c</code>, <code>arch/z80/src/ez80/ez80_emac.c</code>, etc.
</p>
</li>
</ul>
<h3><a name="spidrivers">6.3.2 SPI Device Drivers</a></h3>
<ul>
<li>
<p>
<b><code>include/nuttx/spi/spi.h</code></b>.
All structures and APIs needed to work with SPI drivers are provided in this header file.
</p>
</li>
<li>
<p>
<b><code>struct spi_ops_s</code></b>.
Each SPI device driver must implement an instance of <code>struct spi_ops_s</code>.
That structure defines a call table with the following methods:
<ul>
<p><code>void lock(FAR struct spi_dev_s *dev);</code></p>
<p><code>void select(FAR struct spi_dev_s *dev, enum spi_dev_e devid, bool selected);</code><br>
<code>uint32_t setfrequency(FAR struct spi_dev_s *dev, uint32_t frequency);</code><br>
<code>void setmode(FAR struct spi_dev_s *dev, enum spi_mode_e mode);</code><br>
<code>void setbits(FAR struct spi_dev_s *dev, int nbits);</code><br>
<code>uint8_t status(FAR struct spi_dev_s *dev, enum spi_dev_e devid);</code><br>
<code>uint16_t send(FAR struct spi_dev_s *dev, uint16_t wd);</code><br>
<code>void exchange(FAR struct spi_dev_s *dev, FAR const void *txbuffer, FAR void *rxbuffer, size_t nwords);</code><br>
<p><code>int registercallback(FAR struct spi_dev_s *dev, mediachange_t callback, void *arg);</code></p>
</ul>
</p>
<li>
<p>
<b>Binding SPI Drivers</b>.
SPI drivers are not normally directly accessed by user code, but are usually bound to another,
higher level device driver.
See for example, <code>int mmcsd_spislotinitialize(int minor, int slotno, FAR struct spi_dev_s *spi)</code> in <code>drivers/mmcsd/mmcsd_spi.c</code>.
In general, the binding sequence is:
</p>
<p>
<ol>
<li>Get an instance of <code>struct spi_dev_s</code> from the hardware-specific SPI device driver, and </li>
<li>Provide that instance to the initialization method of the higher level device driver.</li>
</ol>
</p>
</li>
<li>
<p>
<b>Examples</b>:
<code>drivers/loop.c</code>, <code>drivers/mmcsd/mmcsd_spi.c</code>, <code>drivers/ramdisk.c</code>, etc.
</p>
</li>
</ul>
<h3><a name="i2cdrivers">6.3.3 I2C Device Drivers</a></h3>
<ul>
<li>
<p>
<b><code>include/nuttx/i2c/i2c.h</code></b>.
All structures and APIs needed to work with I2C drivers are provided in this header file.
</p>
</li>
<li>
<p>
<b><code>struct i2c_ops_s</code></b>.
Each I2C device driver must implement an instance of <code>struct i2c_ops_s</code>.
That structure defines a call table with the following methods:
<ul>
<p><code>uint32_t setfrequency(FAR struct i2c_dev_s *dev, uint32_t frequency);</code><br>
<code>int setaddress(FAR struct i2c_dev_s *dev, int addr, int nbits);</code><br>
<code>int write(FAR struct i2c_dev_s *dev, const uint8_t *buffer, int buflen);</code><br>
<code>int read(FAR struct i2c_dev_s *dev, uint8_t *buffer, int buflen);</code></p>
</p>
</ul>
<li>
<p>
<b>Binding I2C Drivers</b>.
I2C drivers are not normally directly accessed by user code, but are usually bound to another,
higher level device driver.
In general, the binding sequence is:
</p>
<p>
<ol>
<li>Get an instance of <code>struct i2c_dev_s</code> from the hardware-specific I2C device driver, and </li>
<li>Provide that instance to the initialization method of the higher level device driver.</li>
</ol>
</p>
</li>
<li>
<p>
<b>Examples</b>:
<code>arch/z80/src/ez80/ez80_i2c.c</code>, <code>arch/z80/src/z8/z8_i2c.c</code>, etc.
</p>
</li>
</ul>
<h3><a name="serialdrivers">6.3.4 Serial Device Drivers</a></h3>
<ul>
<li>
<p>
<b><code>include/nuttx/serial/serial.h</code></b>.
All structures and APIs needed to work with serial drivers are provided in this header file.
</p>
</li>
<li>
<p>
<b><code>struct uart_ops_s</code></b>.
Each serial device driver must implement an instance of <code>struct uart_ops_s</code>.
That structure defines a call table with the following methods:
<ul>
<p><code>int setup(FAR struct uart_dev_s *dev);</code><br>
<code>void shutdown(FAR struct uart_dev_s *dev);</code><br>
<code>int attach(FAR struct uart_dev_s *dev);</code><br>
<code>void detach(FAR struct uart_dev_s *dev);</code><br>
<code>int ioctl(FAR struct file *filep, int cmd, unsigned long arg);</code><br>
<code>int receive(FAR struct uart_dev_s *dev, unsigned int *status);</code><br>
<code>void rxint(FAR struct uart_dev_s *dev, bool enable);</code><br>
<code>bool rxavailable(FAR struct uart_dev_s *dev);</code><br>
<code>void send(FAR struct uart_dev_s *dev, int ch);</code><br>
<code>void txint(FAR struct uart_dev_s *dev, bool enable);</code><br>
<code>bool txready(FAR struct uart_dev_s *dev);</code><br>
<code>bool txempty(FAR struct uart_dev_s *dev);</code></p>
</ul>
</p>
</li>
<li>
<p>
<b><code>int uart_register(FAR const char *path, FAR uart_dev_t *dev);</code></b>.
A serial driver may register itself by calling <code>uart_register()</code>, passing it the
<code>path</code> where it will appear in the <a href="#NxFileSystem">pseudo-file-system</a> and it's
initialized instance of <code>struct uart_ops_s</code>.
By convention, serial device drivers are registered at paths like <code>/dev/ttyS0</code>, <code>/dev/ttyS1</code>, etc.
See the <code>uart_register()</code> implementation in <code>drivers/serial.c</code>.
</p>
</li>
<li>
<p>
<b>User Access</b>.
Serial drivers are, ultimately, normal <a href="#chardrivers">character drivers</a> and are accessed as other character drivers.
</p>
</li>
<li>
<p>
<b>Examples</b>:
<code>arch/arm/src/chip/lm_serial.c</code>, <code>arch/arm/src/lpc214x/lpc214x_serial.c</code>, <code>arch/z16/src/z16f/z16f_serial.c</code>, etc.
</p>
</li>
</ul>
<h3><a name="fbdrivers">6.3.5 Frame Buffer Drivers</a></h3>
<ul>
<li>
<p>
<b><code>include/nuttx/fb.h</code></b>.
All structures and APIs needed to work with frame buffer drivers are provided in this header file.
</p>
</li>
<li>
<p>
<b><code>struct fb_vtable_s</code></b>.
Each frame buffer device driver must implement an instance of <code>struct fb_vtable_s</code>.
That structure defines a call table with the following methods:
</p>
<p>
Get information about the video controller configuration and the configuration of each color plane.
</p>
<ul>
<p><code>int (*getvideoinfo)(FAR struct fb_vtable_s *vtable, FAR struct fb_videoinfo_s *vinfo);</code><br>
<code>int (*getplaneinfo)(FAR struct fb_vtable_s *vtable, int planeno, FAR struct fb_planeinfo_s *pinfo);</code></p>
</ul>
<p>
The following are provided only if the video hardware supports RGB color mapping:
</p>
<ul>
<p><code>int (*getcmap)(FAR struct fb_vtable_s *vtable, FAR struct fb_cmap_s *cmap);</code><br>
<code>int (*putcmap)(FAR struct fb_vtable_s *vtable, FAR const struct fb_cmap_s *cmap);</code></p>
</ul>
<p>
The following are provided only if the video hardware supports a hardware cursor:
</p>
<ul>
<p><code>int (*getcursor)(FAR struct fb_vtable_s *vtable, FAR struct fb_cursorattrib_s *attrib);</code><br>
<code>int (*setcursor)(FAR struct fb_vtable_s *vtable, FAR struct fb_setcursor_s *settings);</code></p>
</ul>
</li>
<li>
<p>
<b>Binding Frame Buffer Drivers</b>.
Frame buffer drivers are not normally directly accessed by user code, but are usually bound to another,
higher level device driver.
In general, the binding sequence is:
</p>
<p>
<ol>
<li>Get an instance of <code>struct fb_vtable_s</code> from the hardware-specific frame buffer device driver, and </li>
<li>Provide that instance to the initialization method of the higher level device driver.</li>
</ol>
</p>
</li>
<li>
<p>
<b>Examples</b>:
<code>arch/sim/src/up_framebuffer.c</code>.
See also the usage of the frame buffer driver in the <code>graphics/</code> directory.
</p>
</li>
</ul>
<h3><a name="lcddrivers">6.3.6 LCD Drivers</a></h3>
<ul>
<li>
<p>
<b><code>include/nuttx/lcd/lcd.h</code></b>.
Structures and APIs needed to work with LCD drivers are provided in this header file.
This header file also depends on some of the same definitions used for the frame buffer driver as privided in <code>include/nuttx/fb.h</code>.
</p>
</li>
<li>
<p>
<b><code>struct lcd_dev_s</code></b>.
Each LCD device driver must implement an instance of <code>struct lcd_dev_s</code>.
That structure defines a call table with the following methods:
</p>
<p>
Get information about the LCD video controller configuration and the configuration of each LCD color plane.
</p>
<ul>
<p>
<code>int (*getvideoinfo)(FAR struct lcd_dev_s *dev, FAR struct fb_videoinfo_s *vinfo);</code><br>
<code>int (*getplaneinfo)(FAR struct lcd_dev_s *dev, unsigned int planeno, FAR struct lcd_planeinfo_s *pinfo);</code>
</p>
</ul>
<p>
The following are provided only if the video hardware supports RGB color mapping:
</p>
<ul>
<p>
<code>int (*getcmap)(FAR struct lcd_dev_s *dev, FAR struct fb_cmap_s *cmap);</code><br>
<code>int (*putcmap)(FAR struct lcd_dev_s *dev, FAR const struct fb_cmap_s *cmap);</code>
</p>
</ul>
<p>
The following are provided only if the video hardware supports a hardware cursor:
</p>
<ul>
<p>
<code>int (*getcursor)(FAR struct lcd_dev_s *dev, FAR struct fb_cursorattrib_s *attrib);</code><br>
<code>int (*setcursor)(FAR struct lcd_dev_s *dev, FAR struct fb_setcursor_s *settings)</code>
</p>
</ul>
<p>
Get the LCD panel power status (0: full off - <code>CONFIG_LCD_MAXPOWER</code>: full on).
On backlit LCDs, this setting may correspond to the backlight setting.
</p>
<ul>
<p>
<code>int (*getpower)(struct lcd_dev_s *dev);</code>
</p>
</ul>
<p>
Enable/disable LCD panel power (0: full off - <code>CONFIG_LCD_MAXPOWER</code>: full on).
On backlit LCDs, this setting may correspond to the backlight setting.
</p>
<ul>
<p>
<code>int (*setpower)(struct lcd_dev_s *dev, int power);</code>
</p>
</ul>
<p>
Get the current contrast setting (0-CONFIG_LCD_MAXCONTRAST) */
</p>
<ul>
<p>
<code>int (*getcontrast)(struct lcd_dev_s *dev);</code>
</p>
</ul>
<p>
Set LCD panel contrast (0-CONFIG_LCD_MAXCONTRAST)
</p>
<ul>
<p>
<code>int (*setcontrast)(struct lcd_dev_s *dev, unsigned int contrast);</code>
</p>
</ul>
</p>
<li>
<p>
<b>Binding LCD Drivers</b>.
LCD drivers are not normally directly accessed by user code, but are usually bound to another,
higher level device driver.
In general, the binding sequence is:
</p>
<p>
<ol>
<li>Get an instance of <code>struct lcd_dev_s</code> from the hardware-specific LCD device driver, and </li>
<li>Provide that instance to the initialization method of the higher level device driver.</li>
</ol>
</p>
</li>
<li>
<p>
<b>Examples</b>:
<code>drivers/lcd/nokia6100.c</code>, <code>drivers/lcd/p14201.c</code>, <code>configs/sam3u-ek/src/up_lcd.c.</code>
See also the usage of the LCD driver in the <code>graphics/</code> directory.
</p>
</li>
</ul>
<h3><a name="mtddrivers">6.3.7 Memory Technology Device Drivers</a></h3>
<ul>
<li>
<p>
<b><code>include/nuttx/mtd.h</code></b>.
All structures and APIs needed to work with MTD drivers are provided in this header file.
</p>
</li>
<li>
<p>
<b><code>struct mtd_dev_s</code></b>.
Each MTD device driver must implement an instance of <code>struct mtd_dev_s</code>.
That structure defines a call table with the following methods:
</p>
<p>
Erase the specified erase blocks (units are erase blocks):
</p>
<ul>
<p><code>int (*erase)(FAR struct mtd_dev_s *dev, off_t startblock, size_t nblocks);</code></p>
</ul>
<p>
Read/write from the specified read/write blocks:
</p>
<ul>
<p><code>ssize_t (*bread)(FAR struct mtd_dev_s *dev, off_t startblock, size_t nblocks, FAR uint8_t *buffer);</code><br>
<code>ssize_t (*bwrite)(FAR struct mtd_dev_s *dev, off_t startblock, size_t nblocks, FAR const uint8_t *buffer);</code></p>
</ul>
<p>
Some devices may support byte oriented reads (optional).
Most MTD devices are inherently block oriented so byte-oriented accesses are not supported.
It is recommended that low-level drivers not support read() if it requires buffering.
</p>
<ul>
<p><code>ssize_t (*read)(FAR struct mtd_dev_s *dev, off_t offset, size_t nbytes, FAR uint8_t *buffer);</code></p>
</ul>
<p>
Some devices may also support byte oriented writes (optional).
Most MTD devices are inherently block oriented so byte-oriented accesses are not supported.
It is recommended that low-level drivers not support read() if it requires buffering.
This interface is only available if <code>CONFIG_MTD_BYTE_WRITE</code> is defined.
</p>
<ul>
<p><code>ssize_t (*write)(FAR struct mtd_dev_s *dev, off_t offset, size_t nbytes, FAR const uint8_t *buffer);</code></p>
</ul>
<p>
Support other, less frequently used commands:
</p>
<ul>
<li><code>MTDIOC_GEOMETRY</code>: Get MTD geometry</li>
<li><code>MTDIOC_XIPBASE:</code>: Convert block to physical address for eXecute-In-Place</li>
<li><code>MTDIOC_BULKERASE</code>: Erase the entire device</li>
</ul>
<p>
is provided via a sinble <code>ioctl</code> method (see <code>include/nuttx/fs/ioctl.h</code>):
</p>
<ul>
<p><code>int (*ioctl)(FAR struct mtd_dev_s *dev, int cmd, unsigned long arg);</code></p>
</ul>
</li>
<li>
<p>
<b>Binding MTD Drivers</b>.
MTD drivers are not normally directly accessed by user code, but are usually bound to another,
higher level device driver.
In general, the binding sequence is:
</p>
<p>
<ol>
<li>Get an instance of <code>struct mtd_dev_s</code> from the hardware-specific MTD device driver, and </li>
<li>Provide that instance to the initialization method of the higher level device driver.</li>
</ol>
</p>
</li>
<li>
<p>
<b>Examples</b>:
<code>drivers/mtd/m25px.c</code> and <code>drivers/mtd/ftl.c</code>
</p>
</li>
</ul>
<h3><a name="sdiodrivers">6.3.8 SDIO Device Drivers</a></h3>
<ul>
<li>
<p>
<b><code>include/nuttx/sdio.h</code></b>.
All structures and APIs needed to work with SDIO drivers are provided in this header file.
</p>
</li>
<li>
<p>
<b><code>struct sdio_dev_s</code></b>.
Each SDIOI device driver must implement an instance of <code>struct sdio_dev_s</code>.
That structure defines a call table with the following methods:
</p>
<p>
Mutual exclusion:
</p>
<ul>
<p>
<code>#ifdef CONFIG_SDIO_MUXBUS</code><br>
<code> int (*lock)(FAR struct sdio_dev_s *dev, bool lock);</code><br>
<code>#endif</code>
</p>
</ul>
<p>
Initialization/setup:
</p>
<ul>
<p><code>void (*reset)(FAR struct sdio_dev_s *dev);</code><br>
<code>uint8_t (*status)(FAR struct sdio_dev_s *dev);</code><br>
<code>void (*widebus)(FAR struct sdio_dev_s *dev, bool enable);</code><br>
<code>void (*clock)(FAR struct sdio_dev_s *dev, enum sdio_clock_e rate);</code><br>
<code>int (*attach)(FAR struct sdio_dev_s *dev);</code><br>
</ul>
<p>
Command/Status/Data Transfer:
</p>
<ul>
<p><code>int (*sendcmd)(FAR struct sdio_dev_s *dev, uint32_t cmd, uint32_t arg);</code><br>
<code>int (*recvsetup)(FAR struct sdio_dev_s *dev, FAR uint8_t *buffer, size_t nbytes);</code><br>
<code>int (*sendsetup)(FAR struct sdio_dev_s *dev, FAR const uint8_t *buffer, size_t nbytes);</code><br>
<code>int (*cancel)(FAR struct sdio_dev_s *dev);</code><br>
<code>int (*waitresponse)(FAR struct sdio_dev_s *dev, uint32_t cmd);</code><br>
<code>int (*recvR1)(FAR struct sdio_dev_s *dev, uint32_t cmd, uint32_t *R1);</code><br>
<code>int (*recvR2)(FAR struct sdio_dev_s *dev, uint32_t cmd, uint32_t R2[4]);</code><br>
<code>int (*recvR3)(FAR struct sdio_dev_s *dev, uint32_t cmd, uint32_t *R3);</code><br>
<code>int (*recvR4)(FAR struct sdio_dev_s *dev, uint32_t cmd, uint32_t *R4);</code><br>
<code>int (*recvR5)(FAR struct sdio_dev_s *dev, uint32_t cmd, uint32_t *R5);</code><br>
<code>int (*recvR6)(FAR struct sdio_dev_s *dev, uint32_t cmd, uint32_t *R6);</code><br>
<code>int (*recvR7)(FAR struct sdio_dev_s *dev, uint32_t cmd, uint32_t *R7);</code></p>
</ul>
<p>
Event/Callback support:
</p>
<ul>
<p><code>void (*waitenable)(FAR struct sdio_dev_s *dev, sdio_eventset_t eventset);</code><br>
<code>sdio_eventset_t (*eventwait)(FAR struct sdio_dev_s *dev, uint32_t timeout);</code><br>
<code>void (*callbackenable)(FAR struct sdio_dev_s *dev, sdio_eventset_t eventset);</code><br>
<code>int (*registercallback)(FAR struct sdio_dev_s *dev, worker_t callback, void *arg);</code></p>
</ul>
<p>
DMA support:
</p>
<ul>
<p><code>bool (*dmasupported)(FAR struct sdio_dev_s *dev);</code><br>
<code>int (*dmarecvsetup)(FAR struct sdio_dev_s *dev, FAR uint8_t *buffer, size_t buflen);</code><br>
<code>int (*dmasendsetup)(FAR struct sdio_dev_s *dev, FAR const uint8_t *buffer, size_t buflen);</code></p>
</ul>
</li>
<li>
<p>
<b>Binding SDIO Drivers</b>.
SDIO drivers are not normally directly accessed by user code, but are usually bound to another,
higher level device driver.
In general, the binding sequence is:
</p>
<p>
<ol>
<li>Get an instance of <code>struct sdio_dev_s</code> from the hardware-specific SDIO device driver, and </li>
<li>Provide that instance to the initialization method of the higher level device driver.</li>
</ol>
</p>
</li>
<li>
<p>
<b>Examples</b>:
<code>arch/arm/src/stm32/stm32_sdio.c</code> and <code>drivers/mmcsd/mmcsd_sdio.c</code>
</p>
</li>
</ul>
<h3><a name="usbhostdrivers">6.3.9 USB Host-Side Drivers</a></h3>
<ul>
<li>
<p>
<b><code>include/nuttx/usb/usbhost.h</code></b>.
All structures and APIs needed to work with USB host-side drivers are provided in this header file.
</p>
</li>
<li>
<p>
<b><code>struct usbhost_driver_s</code> and <code>struct usbhost_connection_s</code></b>.
Each USB host controller driver must implement an instance of <code>struct usbhost_driver_s</code> and <code>struct usbhost_connection_s</code>:
<code>struct usbhost_driver_s</code> provides the interface between the USB host driver and the USB class driver;
<code>struct usbhost_connection_s</code> provides the interface between the USB host driver and platform-specific connection management and device enumeration logoc.
These structures are defined in <code>include/nuttx/usb/usbhost.h</code>.
</p>
<p>
<b>Examples</b>:
<code>arch/arm/src/lpc17xx/lpc17_usbhost.c</code>.
<code>arch/arm/src/stm32/stm32_otgfshost.c</code>.
<code>arch/arm/src/sama5/sam_ohci.c</code>.
</p>
</li>
<li>
<p>
<b><code>struct usbhost_class_s</code></b>.
Each USB host class driver must implement an instance of <code>struct usbhost_class_s</code>.
This structure is also defined in <code>include/nuttx/usb/usbhost.h</code>.
</p>
<p>
<b>Examples</b>:
<code>drivers/usbhost/usbhost_storage.c</code>
</p>
</li>
<li>
<p>
<b>USB Host Class Driver Registry</b>.
The NuttX USB host infrastructure includes a <i>registry</i>.
During its initialization, each USB host class driver must call the interface, <code>usbhost_registerclass()</code>
in order add its interface to the registery.
Later, when a USB device is connected, the USB host controller will look up the USB host class driver that is needed to support the connected device in this registry.
</p>
<p>
<b>Examples</b>:
<code>drivers/usbhost/usbhost_registry.c</code>, <code>drivers/usbhost/usbhost_registerclass.c</code>, and <code>drivers/usbhost/usbhost_findclass.c</code>,
</p>
</li>
<li>
<p>
<b>Detection and Enumeration of Connected Devices</b>.
Each USB host device controller supports two methods that are used to detect and enumeration newly connected devices
(and also detect disconnected devices):
</p>
<p>
<ul>
<li>
<p>
<code>int (*wait)(FAR struct usbhost_connection_s *drvr, FAR const bool *connected);</code>
</p>
<p>
Wait for a device to be connected or disconnected.
</p>
</li>
<li>
<p>
<code>int (*enumerate)(FAR struct usbhost_connection_s *drvr, int rhpndx);</code>
</p>
<p>
Enumerate the device connected to a root hub port.
As part of this enumeration process, the driver will
(1) get the device's configuration descriptor,
(2) extract the class ID info from the configuration descriptor,
(3) call <code>usbhost_findclass(</code>) to find the class that supports this device,
(4) call the <code>create()</code> method on the <code>struct usbhost_registry_s interface</code> to get a class instance, and
finally (5) call the <code>connect()</code> method of the <code>struct usbhost_class_s</code> interface.
After that, the class is in charge of the sequence of operations.
</p>
</ul>
</p>
</li>
<li>
<p>
<b>Binding USB Host-Side Drivers</b>.
USB host-side controller drivers are not normally directly accessed by user code,
but are usually bound to another, higher level USB host class driver.
The class driver exports the standard NuttX device interface so that the connected USB device can be accessed just as with other, similar, on-board devices.
For example, the USB host mass storage class driver (<code>drivers/usbhost/usbhost_storage.c</code>) will register a standard, NuttX block driver interface (like <code>/dev/sda</code>)
that can be used to mount a file system just as with any other other block driver instance.
In general, the binding sequence is:
</p>
<p>
<ol>
<li>
<p>
Each USB host class driver includes an intialization entry point that is called from the
application at initialization time.
This driver calls <code>usbhost_registerclass()</code> during this initialization in order to makes itself available in the event the the device that it supports is connected.
</p>
<p>
<b>Examples</b>:
The function <code>usbhost_storageinit()</code> in the file <code>drivers/usbhost/usbhost_storage.c</code>
</p>
</li>
<li>
<p>
Each application must include a <i>waiter</i> thread thread that (1) calls the USB host controller driver's <code>wait()</code> to detect the connection of a device, and then
(2) call the USB host controller driver's <code>enumerate</code> method to bind the registered USB host class driver to the USB host controller driver.
</p>
<p>
<b>Examples</b>:
The function <code>nsh_waiter()</code> in the file <code>configs/nucleus2g/src/up_nsh.c</code> and
the function <code>nsh_waiter()</code> in the file <code>configs/olimex-lpc1766stk/src/up_nsh.c</code>.
</p>
</li>
<li>
<p>
As part of its operation during the binding operation, the USB host class driver will register an instances of a standard NuttX driver under the <code>/dev</code> directory.
To repeat the above example, the USB host mass storage class driver (<code>drivers/usbhost/usbhost_storage.c</code>) will register a standard, NuttX block driver interface (like <code>/dev/sda</code>)
that can be used to mount a file system just as with any other other block driver instance.
</p>
<p>
<b>Examples</b>:
See the call to <code>register_blockdriver()</code> in the function <code>usbhost_initvolume()</code> in the file <code>drivers/usbhost/usbhost_storage.c</code>.
</p>
</li>
</ol>
</p>
</li>
</ul>
<h3><a name="usbdevdrivers">6.3.10 USB Device-Side Drivers</a></h3>
<ul>
<li>
<p>
<b><code>include/nuttx/usb/usbdev.h</code></b>.
All structures and APIs needed to work with USB device-side drivers are provided in this header file.
</p>
</li>
<li>
<p>
<b><code>include/nuttx/usb/usbdev_trace.h</code></b>.
Declarations needed to work the the NuttX USB device driver trace capability.
That USB trace capability is detailed in <a href="UsbTrace.html">separate document</a>.
</p>
</li>
<li>
<p>
<b><code>struct usbdev_s</code></b>.
Each USB device controller driver must implement an instance of <code>struct usbdev_s</code>.
This structure is defined in <code>include/nuttx/usb/usbdev.h</code>.
</p>
<p>
<b>Examples</b>:
<code>arch/arm/src/dm320/dm320_usbdev.c</code>, <code>arch/arm/src/lpc17xx/lpc17_usbdev.c</code>,
<code>arch/arm/src/lpc214x/lpc214x_usbdev.c</code>, <code>arch/arm/src/lpc313x/lpc313x_usbdev.c</code>, and
<code>arch/arm/src/stm32/stm32_usbdev.c</code>.
</p>
</li>
<li>
<p>
<b><code>struct usbdevclass_driver_s</code></b>.
Each USB device class driver must implement an instance of <code>struct usbdevclass_driver_s</code>.
This structure is also defined in <code>include/nuttx/usb/usbdev.h</code>.
</p>
<p>
<b>Examples</b>:
<code>drivers/usbdev/pl2303.c</code> and <code>drivers/usbdev/usbmsc.c</code>
</p>
</li>
<li>
<p>
<b>Binding USB Device-Side Drivers</b>.
USB device-side controller drivers are not normally directly accessed by user code,
but are usually bound to another, higher level USB device class driver.
The class driver is then configured to export the USB device functionality.
In general, the binding sequence is:
</p>
<p>
<ol>
<li>
<p>
Each USB device class driver includes an intialization entry point that is called from the
application at initialization time.
</p>
<p>
<b>Examples</b>:
The function <code>usbdev_serialinitialize()</code> in the file <code>drivers/usbdev/pl2303.c</code> and
the function <code></code> in the file <code>drivers/usbdev/usbmsc.c</code>
</p>
</li>
<li>
<p>
These initialization functions called the driver API, <code>usbdev_register()</code>.
This driver function will <i>bind</i> the USB class driver to the USB device controller driver,
completing the initialization.
</p>
</li>
</ol>
</p>
</li>
</ul>
<h3><a name="analogdrivers">6.3.11 Analog (ADC/DAC) Drivers</a></h3>
<p>
The NuttX PWM driver is split into two parts:
</p>
<ol>
<li>
An "upper half", generic driver that provides the comman PWM interface to application level code, and
</li>
<li>
A "lower half", platform-specific driver that implements the low-level timer controls to implement the PWM functionality.
</li>
</ol>
<ul>
<li>
General header files for the NuttX analog drivers reside in <code>include/nuttx/analog/</code>.
These header files includes both the application level interface to the analog driver as well as the interface between the "upper half" and "lower half" drivers.
</li>
<li>
Common analog logic and share-able analog drivers reside in the <code>drivers/analog/</code>.
</li>
<li>
Platform-specific drivers reside in <code>arch/</code><i><architecture></i><code>/src/</code><i><chip></i> directory for the specific processor <i><architecture></i> and for the specific <i><chip></i> analog peripheral devices.
</li>
</ul>
<h4><a name="adcdrivers">6.3.11.1 ADC Drivers</a></h4>
<ul>
<li>
<code>include/nuttx/analog/adc.h</code>.
All structures and APIs needed to work with ADC drivers are provided in this header file.
This header file includes:
<ol>
<li>
Structures and interface descriptions needed to develop a low-level,
architecture-specific, ADC driver.
</li>
<li>
To register the ADC driver with a common ADC character driver.
</li>
<li>
Interfaces needed for interfacing user programs with the common ADC character driver.
</li>
</ol>
</li>
<li>
<code>drivers/analog/adc.c</code>.
The implementation of the common ADC character driver.
</li>
</ul>
<h4><a name="dacdrivers">6.3.11.2 DAC Drivers</a></h4>
<ul>
<li>
<code>include/nuttx/analog/dac.h</code>.
All structures and APIs needed to work with DAC drivers are provided in this header file.
This header file includes:
<ol>
<li>
Structures and interface descriptions needed to develop a low-level,
architecture-specific, DAC driver.
</li>
<li>
To register the DAC driver with a common DAC character driver.
</li>
<li>
Interfaces needed for interfacing user programs with the common DAC character driver.
</li>
</ol>
</li>
<li>
<code>drivers/analog/dac.c</code>.
The implementation of the common DAC character driver.
</li>
</ul>
<h3><a name="pwmdrivers">6.3.12 PWM Drivers</a></h3>
<p>
For the purposes of this driver, a PWM device is any device that generates periodic output pulses of controlled frequency and pulse width.
Such a device might be used, for example, to perform pulse-width modulated output or frequency/pulse-count modulated output
(such as might be needed to control a stepper motor).
</p>
<p>
The NuttX PWM driver is split into two parts:
</p>
<ol>
<li>
An "upper half", generic driver that provides the comman PWM interface to application level code, and
</li>
<li>
A "lower half", platform-specific driver that implements the low-level timer controls to implement the PWM functionality.
</li>
</ol>
<p>
Files supporting PWM can be found in the following locations:
</p>
<ul>
<li><b>Interface Definition</b>.
The header file for the NuttX PWM driver reside at <code>include/nuttx/pwm.h</code>.
This header file includes both the application level interface to the PWM driver as well as the interface between the "upper half" and "lower half" drivers.
The PWM module uses a standard character driver framework.
However, since the PWM driver is a devices control interface and not a data transfer interface,
the majority of the functionality available to the application is implemented in driver ioctl calls.
</li>
<li><b>"Upper Half" Driver</b>.
The generic, "upper half" PWM driver resides at <code>drivers/pwm.c</code>.
</li>
<li><b>"Lower Half" Drivers</b>.
Platform-specific PWM drivers reside in <code>arch/</code><i><architecture></i><code>/src/</code><i><chip></i> directory for the specific processor <i><architecture></i> and for the specific <i><chip></i> PWM peripheral devices.
</li>
</ul>
<h3><a name="candrivers">6.3.13 CAN Drivers</a></h3>
<p>
NuttX supports only a very low-level CAN driver.
This driver supports only the data exchange and does not include any high-level CAN protocol.
The NuttX CAN driver is split into two parts:
</p>
<ol>
<li>
An "upper half", generic driver that provides the comman CAN interface to application level code, and
</li>
<li>
A "lower half", platform-specific driver that implements the low-level timer controls to implement the CAN functionality.
</li>
</ol>
<p>
Files supporting CAN can be found in the following locations:
</p>
<ul>
<li><b>Interface Definition</b>.
The header file for the NuttX CAN driver reside at <code>include/nuttx/can.h</code>.
This header file includes both the application level interface to the CAN driver as well as the interface between the "upper half" and "lower half" drivers.
The CAN module uses a standard character driver framework.
</li>
<li><b>"Upper Half" Driver</b>.
The generic, "upper half" CAN driver resides at <code>drivers/can.c</code>.
</li>
<li><b>"Lower Half" Drivers</b>.
Platform-specific CAN drivers reside in <code>arch/</code><i><architecture></i><code>/src/</code><i><chip></i> directory for the specific processor <i><architecture></i> and for the specific <i><chip></i> CAN peripheral devices.
</li>
</ul>
<h3><a name="quadencoder">6.3.14 Quadrature Encoder Drivers</a></h3>
<p>
NuttX supports a low-level, two-part Quadrature Encoder driver.
</p>
<ol>
<li>
An "upper half", generic driver that provides the comman Quadrature Encoder interface to application level code, and
</li>
<li>
A "lower half", platform-specific driver that implements the low-level timer controls to implement the Quadrature Encoder functionality.
</li>
</ol>
<p>
Files supporting the Quadrature Encoder can be found in the following locations:
</p>
<ul>
<li><b>Interface Definition</b>.
The header file for the NuttX Quadrature Encoder driver reside at <code>include/nuttx/sensors/qencoder.h</code>.
This header file includes both the application level interface to the Quadrature Encoder driver as well as the interface between the "upper half" and "lower half" drivers.
The Quadrature Encoder module uses a standard character driver framework.
</li>
<li><b>"Upper Half" Driver</b>.
The generic, "upper half" Quadrature Encoder driver resides at <code>drivers/sensors/qencoder.c</code>.
</li>
<li><b>"Lower Half" Drivers</b>.
Platform-specific Quadrature Encoder drivers reside in <code>arch/</code><i><architecture></i><code>/src/</code><i><chip></i> directory for the specific processor <i><architecture></i> and for the specific <i><chip></i> Quadrature Encoder peripheral devices.
</li>
</ul>
<h3><a name="wdogdriver">6.3.15 Watchdog Timer Drivers</a></h3>
<p>
NuttX supports a low-level, two-part watchdog timer driver.
</p>
<ol>
<li>
An "upper half", generic driver that provides the comman watchdog timer interface to application level code, and
</li>
<li>
A "lower half", platform-specific driver that implements the low-level timer controls to implement the watchdog timer functionality.
</li>
</ol>
<p>
Files supporting the watchdog timer can be found in the following locations:
</p>
<ul>
<li><b>Interface Definition</b>.
The header file for the NuttX watchdog timer driver reside at <code>include/nuttx/watchdog.h</code>.
This header file includes both the application level interface to the watchdog timer driver as well as the interface between the "upper half" and "lower half" drivers.
The watchdog timer driver uses a standard character driver framework.
</li>
<li><b>"Upper Half" Driver</b>.
The generic, "upper half" watchdog timer driver resides at <code>drivers/watchdog.c</code>.
</li>
<li><b>"Lower Half" Drivers</b>.
Platform-specific watchdog timer drivers reside in <code>arch/</code><i><architecture></i><code>/src/</code><i><chip></i> directory for the specific processor <i><architecture></i> and for the specific <i><chip></i> watchdog timer peripheral devices.
</li>
</ul>
<h3><a name="kbddriver">6.3.16 Keyboard/Keypad Drivers</a></h3>
<p>
<b>Keypads vs. Keyboards</b>
Keyboards and keypads are really the same devices for NuttX.
A keypad is thought of as simply a keyboard with fewer keys.
</p>
<p>
<b>Special Commands</b>.
In NuttX, a keyboard/keypad driver is simply a character driver that may have an (optional) encoding/decoding layer on the data returned by the character driver.
A keyboard may return simple text data (alphabetic, numeric, and punctuaction) or control characters (enter, control-C, etc.) when a key is pressed.
We can think about this the "normal" keyboard data stream.
However, in addition, most keyboards support actions that cannot be represented as text or control data.
Such actions include things like cursor controls (home, up arrow, page down, etc.), editing functions (insert, delete, etc.), volume controls, (mute, volume up, etc.) and other special functions.
In this case, some special encoding may be required to multiplex the normal text data and special command key press data streams.
</p>
<p>
<b>Key Press and Release Events</b>
Sometimes the time that a key is released is needed by applications as well.
Thus, in addition to normal and special key press events, it may also be necessary to encode normal and special key release events.
</p>
<p>
<b>Encoding/Decoding</b> Layer</b>.
An optional encoding/decoding layer can be used with the basic character driver to encode the keyboard events into the text data stream.
The function interfaces that comprise that encoding/decoding layer are defined in the header file <code>include/nuttx/input/kbd_code.h</code>.
These functions provide an matched set of (a) driver encoding interfaces, and (b) application decoding interfaces.
</p>
<ol>
<li>
<p>
<b>Driver Encoding Interfaces</b>.
These are interfaces used by the keyboard/keypad driver to encode keyboard events and data.
</p>
<ul>
<li>
<p>
<b><code>kbd_press()</code></b>
</p>
<p><b>Function Prototype:</b></p>
<ul><pre>
#include <nuttx/streams.h>
#include <nuttx/input/kbd_codec.h>
void kbd_press(int ch, FAR struct lib_outstream_s *stream);
</pre></ul>
<p><b>Description:</b></p>
<ul>
Indicates a normal key press event.
Put one byte of normal keyboard data into the output stream.
</ul>
<p><b>Input Pameters:</b></p>
<ul>
<li>
<code>ch</code>: The character to be added to the output stream.
</li>
<li>
<code>stream</code>: An instance of <code>lib_outstream_s</code> to perform the actual low-level put operation.
</li>
</ul>
<p><b>Returned Value:</b></p>
<ul>
None.
</ul>
</li>
<li>
<p>
<b><code>kbd_release()</code></b>
</p>
<p><b>Function Prototype:</b></p>
<ul><pre>
#include <nuttx/streams.h>
#include <nuttx/input/kbd_codec.h>
void kbd_release(uint8_t ch, FAR struct lib_outstream_s *stream);
</pre></ul>
<p><b>Description:</b></p>
<ul>
Encode the release of a normal key.
</ul>
<p><b>Input Pameters:</b></p>
<ul>
<li>
<code>ch</code>: The character associated with the key that was releared.
</li>
<li>
<code>stream</code>: An instance of <code>lib_outstream_s</code> to perform the actual low-level put operation.
</li>
</ul>
<p><b>Returned Value:</b></p>
<ul>
None.
</ul>
</li>
<li>
<p>
<b><code>kbd_specpress()</code></b>
</p>
<p><b>Function Prototype:</b></p>
<ul><pre>
#include <nuttx/streams.h>
#include <nuttx/input/kbd_codec.h>
void kbd_specpress(enum kbd_keycode_e keycode, FAR struct lib_outstream_s *stream);
</pre></ul>
<p><b>Description:</b></p>
<ul>
Denotes a special key press event.
Put one special keyboard command into the output stream.
</ul>
<p><b>Input Pameters:</b></p>
<ul>
<li>
<code>keycode</code>: The command to be added to the output stream.
The enumeration <code>enum kbd_keycode_e keycode</code> identifies all commands known to the system.
</li>
<li>
<code>stream</code>: An instance of <code>lib_outstream_s</code> to perform the actual low-level put operation.
</li>
</ul>
<p><b>Returned Value:</b></p>
<ul>
None.
</ul>
</li>
<li>
<p>
<b><code>kbd_specrel()</code></b>
</p>
<p><b>Function Prototype:</b></p>
<ul><pre>
#include <nuttx/streams.h>
#include <nuttx/input/kbd_codec.h>
void kbd_specrel(enum kbd_keycode_e keycode, FAR struct lib_outstream_s *stream);
</pre></ul>
<p><b>Description:</b></p>
<ul>
Denotes a special key release event.
Put one special keyboard command into the output stream.
</ul>
<p><b>Input Pameters:</b></p>
<ul>
<li>
<code>keycode</code>: The command to be added to the output stream.
The enumeration <code>enum kbd_keycode_e keycode</code> identifies all commands known to the system.
</li>
<li>
<code>stream</code>: An instance of <code>lib_outstream_s</code> to perform the actual low-level put operation.
</li>
</ul>
<p><b>Returned Value:</b></p>
<ul>
None.
</ul>
</li>
</ul>
</li>
<li>
<p>
<b>Application Decoding Interfaces</b>.
These are user interfaces to decode the values returned by the keyboard/keypad driver.
</p>
<ul>
<li>
<p>
<b><code>kbd_decode()</code></b>
</p>
<p><b>Function Prototype:</b></p>
<ul><pre>
#include <nuttx/streams.h>
#include <nuttx/input/kbd_codec.h>
int kbd_decode(FAR struct lib_instream_s *stream, FAR struct kbd_getstate_s *state, FAR uint8_t *pch);
</pre></ul>
<p><b>Description:</b></p>
<ul>
Get one byte of data or special command from the driver provided input buffer.
</ul>
<p><b>Input Pameters:</b></p>
<ul>
<li>
<code>stream</code>: An instance of <code>lib_instream_s</code> to perform the actual low-level get operation.
</li>
<li>
<code>pch</code>: The location to save the returned value.
This may be either a normal, character code or a special command (i.e., a value from <code>enum kbd_getstate_s</code>.
</li>
<li>
<code>state</code>: A user provided buffer to support parsing.
This structure should be cleared the first time that <code>kbd_decode()</code> is called.
</li>
</ul>
<p><b>Returned Value:</b></p>
<ul>
<li>
<b><code>KBD_PRESS</code> (0)</b>:
Indicates the successful receipt of normal, keyboard data.
This corresponds to a keypress event.
The returned value in <code>pch</code> is a simple byte of text or control data.
</li>
<li>
<b><code>KBD_RELEASE</code> (1)</b>:
Indicates a key release event.
The returned value in <code>pch</code> is the byte of text or control data corresponding to the released key.
</li>
<li>
<b><code>KBD_SPECPRESS</code> (2)</b>:
Indicates the successful receipt of a special keyboard command.
The returned value in <code>pch</code> is a value from <code>enum kbd_getstate_s</code>.
</li>
<li>
<b><code>KBD_SPECREL</code> (3)</b>:
Indicates a special command key release event.
The returned value in <code>pch</code> is a value from <code>enum kbd_getstate_s</code>.
</li>
<li>
<b><code>KBD_ERROR</code> (<code>EOF</code>)</b>:
An error has getting the next character (reported by the <code>stream</code>).
Normally indicates the end of file.
</li>
</ul>
</li>
</ul>
</li>
</ol>
<p>
<b>I/O Streams</b>.
Notice the use of the abstract I/O streams in these interfaces.
These stream interfaces are defined in <code>include/nuttx/streams.h</code>.
</p>
<h2><a name="pwrmgmt">6.4 Power Management</a></h2>
<h3><a name="pmoverview">6.4.1 Overview</a></h3>
<p>
NuttX supports a simple power managment (PM) sub-system. This sub-system:
</p>
<ul>
<li>
<p>
Monitors driver activity, and
</p>
</li>
<li>
<p>
Provides hooks to place drivers (and the whole system) into reduce power
modes of operation.
</p>
</li>
</ul>
<p>
<center><img src="pm.png"></center>
</p>
<p>
The PM sub-system integrates the MCU idle loop with a collection of device drivers to support:
</p>
<ul>
<li>
<p>
Reports of relevant driver or other system activity.
</p>
</li>
<li>
<p>
Registration and callback mechanism to interface with individual device drivers.
</p>
</li>
<li>
<p>
IDLE time polling of overall driver activity.
</p>
</li>
<li>
<p>
Coordinated, global, system-wide transitions to lower power usage states.
</p>
</li>
</ul>
<p>
Various "sleep" and low power consumption states have various names and are sometimes used in conflicting ways.
In the NuttX PM logic, we will use the following terminology:
</p>
<dl>
<dt><code>NORMAL</code>
<dd>The normal, full power operating mode.
<dt><code>IDLE</code>
<dd>This is still basically normal operational mode, the system is,
however, <code>IDLE</code> and some simple simple steps to reduce power
consumption provided that they do not interfere with normal
Operation. Simply dimming the a backlight might be an example
somethat that would be done when the system is idle.
<dt><code>STANDBY</code>
<dd>Standby is a lower power consumption mode that may involve more
extensive power management steps such has disabling clocking or
setting the processor into reduced power consumption modes. In
this state, the system should still be able to resume normal
activity almost immediately.
<dt><code>SLEEP</code>
<dd>The lowest power consumption mode. The most drastic power
reduction measures possible should be taken in this state. It
may require some time to get back to normal operation from
<code>SLEEP</code> (some MCUs may even require going through reset).
</dl>
<p>
These various states are represented with type <code>enum pm_state_e</code> in <code>include/nuttx/power/pm.h</code>.
</p>
<h3><a name="pminterfaces">6.4.2 Interfaces</a></h3>
<p>
All PM interfaces are declared in the file <code>include/nuttx/power/pm.h</code>.
</p>
<h4><a name="pminitialize">6.4.2.1 <code>pm_initialize()</code></a></h4>
<p><b>Function Prototype:</b></p>
<ul><pre>
#include <nuttx/power/pm.h>
void pm_initialize(void);
</pre></ul>
<p><b>Description:</b>
This function is called by MCU-specific one-time at power on reset in order to initialize the power management capabilities.
This function must be called <i>very</i> early in the intialization sequence <i>before</i> any other device drivers are initialize (since they may attempt to register with the power management subsystem).
</p>
<p><b>Input Parameters:</b>
None
</p>
<p><b>Returned Value:</b>
None
</p>
<h4><a name="pmregister">6.4.2.2 <code>pm_register()</code></a></h4>
<p><b>Function Prototype:</b></p>
<ul><pre>
#include <nuttx/power/pm.h>
int pm_register(FAR struct pm_callback_s *callbacks);
</pre></ul>
<p><b>Description:</b>
This function is called by a device driver in order to register to receive power management event callbacks.
Refer to the <a href="#pmcallbacks">PM Callback</a> section for more details.
</p>
<p><b>Input Parameters:</b>
<dl>
<dt><code>callbacks</code>
<dd>An instance of <code>struct pm_callback_s</code> providing the driver callback functions.
</dl>
</p>
<p><b>Returned Value:</b>
Zero (<code>OK</code>) on success; otherwise a negater <code>errno</code> value is returned.
</p>
<h4><a name="pmactivity">6.4.2.3 <code>pm_activity()</code></a></h4>
<p><b>Function Prototype:</b></p>
<ul><pre>
#include <nuttx/power/pm.h>
void pm_activity(int priority);
</pre></ul>
<p><b>Description:</b>
This function is called by a device driver to indicate that it is performing meaningful activities (non-idle).
This increment an activty count and/or will restart a idle timer and prevent entering reduced power states.
</p>
<p><b>Input Parameters:</b>
<dl>
<dt><code>priority</code>
<dd>
Activity priority, range 0-9.
Larger values correspond to higher priorities.
Higher priority activity can prevent the system from entering reduced power states for a longer period of time.
As an example, a button press might be higher priority activity because it means that the user is actively interacting with the device.
</dl>
</p>
<p><b>Returned Value:</b>
None
</p>
<p><b>Assumptions:</b>
This function may be called from an interrupt handler (this is the ONLY PM function that may be called from an interrupt handler!).
</p>
<h4><a name="pmcheckstate">6.4.2.4 <code>pm_checkstate()</code></a></h4>
<p><b>Function Prototype:</b></p>
<ul><pre>
#include <nuttx/power/pm.h>
enum pm_state_e pm_checkstate(void);
</pre></ul>
<p><b>Description:</b>
This function is called from the MCU-specific IDLE loop to monitor the the power management conditions.
This function returns the "recommended" power management state based on the PM configuration and activity reported in the last sampling periods.
The power management state is not automatically changed, however.
The IDLE loop must call <code>pm_changestate()</code> in order to make the state change.
</p>
<p>
These two steps are separated because the plaform-specific IDLE loop may have additional situational information that is not available to the the PM sub-system.
For example, the IDLE loop may know that the battery charge level is very low and may force lower power states even if there is activity.
</p>
<p>
NOTE: That these two steps are separated in time and, hence, the IDLE loop could be suspended for a long period of time between calling <code>pm_checkstate()</code> and <code>pm_changestate()</code>.
The IDLE loop may need to make these calls atomic by either disabling interrupts until the state change is completed.
</p>
<p><b>Input Parameters:</b>
None
</p>
<p><b>Returned Value:</b>
The recommended power management state.
</p>
<h4><a name="pmchangestate">6.4.2.5 <code>pm_changestate()</code></a></h4>
<p><b>Function Prototype:</b></p>
<ul><pre>
#include <nuttx/power/pm.h>
int pm_changestate(enum pm_state_e newstate);
</pre></ul>
<p><b>Description:</b>
This function is used by platform-specific power management logic.
It will announce the power management power management state change to all drivers that have registered for power management event callbacks.
</p>
<p><b>Input Parameters:</b>
<dl>
<dt><code>newstate</code>
<dd>Identifies the new PM state
</dl>
</p>
<p><b>Returned Value:</b>
0 (<code>OK</code>) means that the callback function for all registered drivers returned <code>OK</code> (meaning that they accept the state change).
Non-zero means that one of the drivers refused the state change.
In this case, the system will revert to the preceding state.
</p>
<p><b>Assumptions:</b>
It is assumed that interrupts are disabled when this function is called.
This function is probably called from the IDLE loop... the lowest priority task in the system.
Changing driver power management states may result in renewed system activity and, as a result, can
suspend the IDLE thread before it completes the entire state change unless interrupts are disabled throughout the state change.
</p>
<h3><a name="pmcallbacks">6.4.3 Callbacks</a></h3>
<p>
The <code>struct pm_callback_s</code> includes the pointers to the driver callback functions.
This structure is defined <code>include/nuttx/power/pm.h</code>.
These callback functions can be used to provide power management information to the driver.
</p>
<h4><a name="pmprepare">6.4.3.1 <code>prepare()</code></a></h4>
<p><b>Function Prototype:</b></p>
<ul><pre>
int (*prepare)(FAR struct pm_callback_s *cb, enum pm_state_e pmstate);
</pre></ul>
<p><b>Description:</b>
Request the driver to prepare for a new power state.
This is a warning that the system is about to enter into a new power state.
The driver should begin whatever operations that may be required to enter power state.
The driver may abort the state change mode by returning a non-zero value from the callback function.
</p>
<p><b>Input Parameters:</b>
<dl>
<dt><code>cb</code>
<dd>Returned to the driver.
The driver version of the callback strucure may include additional, driver-specific state data at the end of the structure.
<dt><code>pmstate</code>
<dd>Identifies the new PM state
</dl>
</p>
<p><b>Returned Value:</b>
Zero (<code>OK</code>) means the event was successfully processed and that the driver is prepared for the PM state change.
Non-zero means that the driver is not prepared to perform the tasks needed achieve this power setting and will cause the state change to be aborted.
NOTE: The <code>prepare()</code> method will also be called when reverting from lower back to higher power consumption modes (say because another driver refused a lower power state change).
Drivers are not permitted to return non-zero values when reverting back to higher power
consumption modes!
</p>
<h4><a name="pmnotify">6.4.3.1 <code>notify()</code></a></h4>
<p><b>Function Prototype:</b></p>
<ul><pre>
#include <nuttx/power/pm.h>
void (*notify)(FAR struct pm_callback_s *cb, enum pm_state_e pmstate);
</pre></ul>
<p><b>Description:</b>
Notify the driver of new power state.
This callback is called after all drivers have had the opportunity to prepare for the new power state.
</p>
<p><b>Input Parameters:</b>
<dl>
<dt><code>cb</code>
<dd>Returned to the driver.
The driver version of the callback strucure may include additional, driver-specific state data at the end of the structure.
<dt><code>pmstate</code>
<dd>Identifies the new PM state
</dl>
</p>
<p><b>Returned Value:</b>
None.
The driver already agreed to transition to the low power consumption state when when it returned <code>OK</code> to the <code>prepare()</code> call.
</p>
<table width ="100%">
<tr bgcolor="#e4e4e4">
<td>
<h1><a name="apndxconfigs">Appendix A: NuttX Configuration Settings</a></h1>
</td>
</tr>
</table>
<p>
The following variables are recognized by the build (you may
also include architecture-specific settings).
</p>
<p>
<b>Note</b>.
This appendix is deprecated.
Documentation of NuttX configuration is now provided in a separate, auto-generated <a href="NuttXConfigVariables.html">Configuration Variable Document</a>.
That configuration variable document is generated using the <a href="http://sourceforge.net/p/nuttx/git/ci/master/tree/nuttx/tools/kconfig2html.c">kconfig2html</a> tool
That tool analyzes the NuttX <code>Kconfig</code> files and generates the HTML document.
As a consequence, this file may not be present at any given time but can be regenerated following the instructions in <code>tools</code> directory <a href="http://sourceforge.net/p/nuttx/git/ci/master/tree/nuttx/tools/README.txt">README</a> file.
</p>
<h2>Architecture selection</h2>
<p>
The following configuration items select the architecture, chip, and
board configuration for the build.
</p>
<ul>
<li><code>CONFIG_ARCH</code>:
Identifies the arch subdirectory</li>
<li><code>CONFIG_ARCH_name</code>:
For use in C code</li>
<li><code>CONFIG_ARCH_CHIP</code>:
Identifies the arch/*/chip subdirectory</li>
<li><code>CONFIG_ARCH_CHIP_name</code>:
For use in C code</li>
<li><code>CONFIG_ARCH_BOARD</code>:
Identifies the configs subdirectory and hence, the board that supports
the particular chip or SoC.</li>
<li><code>CONFIG_ARCH_BOARD_name</code>:
For use in C code</li>
<li><code>CONFIG_ENDIAN_BIG</code>:
Define if big endian (default is little endian).</li>
<li><code>CONFIG_ARCH_NOINTC</code>:
Define if the architecture does not support an interrupt controller
or otherwise cannot support APIs like up_enable_irq() and up_disable_irq().</li>
<li><code>CONFIG_ARCH_VECNOTIRQ</code>:
Usually the interrupt vector number provided to interfaces like <code>irq_attach()</code>
and <code>irq_detach</code> are the same as IRQ numbers that are provied to IRQ
management functions like <code>up_enable_irq()</code> and <code>up_disable_irq()</code>.
But that is not true for all interrupt controller implementations. For example, the
PIC32MX interrupt controller manages interrupt sources that have a many-to-one
relationship to interrupt vectors.
In such cases, <code>CONFIG_ARCH_VECNOTIRQ</code> must defined so that the OS logic
will know not to assume it can use a vector number to enable or disable interrupts.
<li><code>CONFIG_ARCH_IRQPRIO</code>:
Define if the architecture supports prioritization of interrupts and the
up_prioritize_irq() API.</li>
<li><code>CONFIG_ADDRENV</code>:
The CPU supports an MMU and CPU port supports provision of address
environments for tasks (making the, perhaps, processes).
In this case, the CPU-specific logic must provide a set of address environment interfaces as defined in the <a href="#addrenv">Address Environments</a> paragraph.
</li>
</ul>
<p>
Some architectures require a description of the RAM configuration:
</p>
<ul>
<li><code>CONFIG_RAM_SIZE</code>:
Describes the primary installed RAM.</li>
<li><code>CONFIG_RAM_START</code>:
The start address of primary RAM (physical)</li>
<li><code>CONFIG_RAM_VSTART</code>:
The start address of primary RAM (virtual). This is only needed on platforms that support address mapping.</li>
</ul>
<h2>Build Options</h2>
<p>
General build options:
</p>
<ul>
<li><code>CONFIG_RRLOAD_BINARY</code>:
Make the rrload binary format used with BSPs from <a href="www.ridgerun.com">ridgerun.com</a>
using the <code>tools/mkimage.sh</code> script.
</li>
<li><code>CONFIG_INTELHEX_BINARY</code>:
Make the Intel HEX binary format used with many different loaders using the GNU objcopy program
This option should not be selected if you are not using the GNU toolchain.
</li>
<li><code>CONFIG_MOTOROLA_SREC</code>:
Make the Motorola S-Record binary format used with many different loaders using the GNU objcopy program
Should not be selected if you are not using the GNU toolchain.
</li>
<li><code>CONFIG_RAW_BINARY</code>:
Make a raw binary format file used with many different loaders using the GNU objcopy program.
This option should not be selected if you are not using the GNU toolchain.
</li>
<li><code>CONFIG_HAVE_CXX</code>:
Toolchain supports C++ and <code>CXX</code>, <code>CXXFLAGS</code>, and <code>COMPILEXX</code>
have been defined in the configurations <code>Make.defs</code> file.
</li>
<li><code>CONFIG_HAVE_CXXINITIALIZE</code>:
The platform-specific logic includes support for initialization of static C++ instances for this architecture and for the selected toolchain (via <code>up_cxxinitialize()</code>).
</li>
</ul>
<p>
Building application code:
</p>
<ul>
<li>
<p>
<code>CONFIG_APPS_DIR</code>: Identifies the directory that builds the application to link with NuttX.
This symbol must be assigned to the path of the application build directory <i>relative</i> to the NuttX top build directory.
If the application resides in the top-level <code>../apps/</code> directory, it is not necessary to define <code>CONFIG_APPS_DIR</code>.
If you have an application directory and the NuttX directory each in separate directories such as this:
<ul><pre>
build
|-nuttx
| |
| `- Makefile
`-application
|
`- Makefile
</pre></ul>
Then you would set <code>CONFIG_APPS_DIR=../application</code>.
The default value of <code>CONFIG_APPS_DIR</code> is <code>../apps/</code>.
</p>
<p>
The application direction must contain <code>Makefile</code> and this make file must support the following targets:
<ul>
<li>
<code>libapps$(LIBEXT)</code> (usually <code>libapps.a</code>).
<code>libapps.a</code> is a static library ( an archive) that contains all of application object files.
</li>
<li>
<code>clean</code>.
Do whatever is appropriate to clean the application directories for a fresh build.
</li>
<li>
<code>distclean</code>.
Clean everthing -- auto-generated files, symbolic links etc. -- so that the directory contents are the same as the contents in your configuration management system.
This is only done when you change the NuttX configuration.
</li>
<li>
<code>context</code>.
Perform one-time configuration-related setup.
This might includes such things as creating auto-generated files or symbolic links for directory configurations.
</li>
<li>
<code>depend</code>.
Make or update the application build dependencies.
</li>
</ul>
</p>
<p>
When this application is invoked it will receive the setting <code>TOPDIR</code> like:
<ul>
<code>$(MAKE) -C $(CONFIG_APPS_DIR) TOPDIR="$(TOPDIR)"</code> <target>
</ul>
</p>
<p>
<code>TOPDIR</code> is the full path to the NuttX directory.
It can be used, for example, to include makefile fragments (e.g., <code>.config</code> or <code>Make.defs</code>) or to set up include file paths.
</p>
</li>
</ul>
<p>
Two-pass Build Options.
If the 2 pass build option is selected, then these options configure the make system build a extra link object.
This link object is assumed to be an incremental (relative) link object, but could be a static library (archive)
(some modification to this Makefile would be required if CONFIG_PASS1_TARGET generates an archive).
Pass 1 1ncremental (relative) link objects should be put into the processor-specific source directory
where other link objects will be created - ff the pass1 obect is an archive, it could go anywhere.
</p>
<ul>
<li>
<code>CONFIG_BUILD_2PASS</code>:
Enables the two pass build options.
</li>
</ul>
<p>
When the two pass build option is enabled, the following also apply:
</p>
<ul>
<li>
<p>
<code>CONFIG_PASS1_TARGET</code>: The name of the first pass build target.
</p>
</li>
<li><code>CONFIG_PASS1_BUILDIR</code>:
<p>
The path, relative to the top NuttX build directory to directory that contains the Makefile to build the first pass object.
The Makefile must support the following targets:
</p>
<p>
<ul>
<li>The special target <code>CONFIG_PASS1_TARGET</code> (if defined), and</li>
<li>The usual depend, clean, and distclean targets.</li>
</ul>
</p>
</li>
<li>
<code>CONFIG_PASS1_OBJECT</code>: May be used to include an extra, pass1 object into the final link.
This would probably be the object generated from the <code>CONFIG_PASS1_TARGET</code>.
It may be available at link time in the <code>arch/<architecture>/src</code> directory.
</li>
</ul>
<h2>Debug Options</h2>
<p>
General Debug setup options are provided to (1) enable and control debug console output, (2) to build NuttX for use with a debugger, and (3) to enable specific debug features:
</p>
<ul>
<li>
<code>CONFIG_DEBUG</code>: enables built-in debug options.
This includes more extensive parameter checking, debug assertions, and other debug logic.
This option is also necessary (but not sufficient) to enable debug syslog output;
Debug syslog output must also be enabled on a subsystem-by-subsystem basis as described below.
</li>
<li>
<code>CONFIG_DEBUG_VERBOSE</code>: If debug syslog output is enabled, the option enables more verbose debug output.
Ignored if <code>CONFIG_DEBUG</code> is not defined.
If only <code>CONFIG_DEBUG</code> then the only output will be errors, warnings, and critical information.
If <code>CONFIG_DEBUG_VERBOSE</code> is defined in addition, then general debug comments will also be included in the syslog output.
</li>
<li>
<code>CONFIG_SYSLOG_ENABLE</code>: Support an interface to enable or disable syslog output.
</li>
<li>
<code>CONFIG_DEBUG_SYMBOLS</code>: build without optimization and with debug symbols (needed for use with a debugger).
This option has nothing to do with debug output.
</li>
<li>
<code>CONFIG_DEBUG_STACK</code>: a few ports include logic to monitor stack usage.
If the NuttX port supports this option, it would be enabled with this option.
This option also requires <code>CONFIG_DEBUG</code> to enable general debug features.
</li>
</ul>
<p>
If debug features are enabled with <code>CONFIG_DEBUG</code> (and possibly <code>CONFIG_DEBUG_VERBOSE</code>), then debug console output can also be enabled on a subsystem-by-subsystem basis.
Below are debug subsystems that are generally available on all platforms:
<ul>
<li>
<code>CONFIG_DEBUG_SCHED</code>: enable OS debug output (disabled by default)
</li>
<li>
<code>CONFIG_DEBUG_MM</code>: enable memory management debug output (disabled by default)
</li>
<li>
<code>CONFIG_DEBUG_NET</code>: enable network debug output (disabled by default)
</li>
<li>
<code>CONFIG_DEBUG_USB</code>: enable USB debug output (disabled by default)
</li>
<li>
<code>CONFIG_DEBUG_FS</code>: enable file system debug output (disabled by default)
</li>
<li>
<code>CONFIG_DEBUG_LIB</code>: enable C library debug output (disabled by default)
</li>
<li>
<code>CONFIG_DEBUG_BINFMT</code>: enable binary loader debug output (disabled by default)
</li>
<li>
<code>CONFIG_DEBUG_GRAPHICS</code>: enable NX graphics debug output (disabled by default)
</li>
</ul>
<p>
The following debug options may also be used with certain ports that support these features:
</p>
<ul>
<li>
<code>CONFIG_DEBUG_DMA</code>: enable DMA controller debug output (disabled by default)
</li>
<li>
<code>CONFIG_DEBUG_GPIO</code>: enable detail GPIO usage debug output (disabled by default)
</li>
<li>
<code>CONFIG_DEBUG_PAGING</code>: enable on-demand paging debug output (disabled by default)
</li>
</ul>
<h2>Memory Management</h2>
<ul>
<li>
<code>CONFIG_MM_REGIONS</code>: If the architecture includes multiple
regions of memory to allocate from, this specifies the
number of memory regions that the memory manager must
handle and enables the API <code>mm_addregion(heap, start, end)</code>.
</li>
<li>
<code>CONFIG_MM_SMALL</code>: Each memory allocation has a small allocation
overhead. The size of that overhead is normally determined by
the "width" of the address support by the MCU. MCUs that support
16-bit addressability have smaller overhead than devices that
support 32-bit addressability. However, there are many MCUs
that support 32-bit addressability <i>but</i> have internal SRAM
of size less than or equal to 64K. In this case, CONFIG_MM_SMALL
can be defined so that those MCUs will also benefit from the
smaller, 16-bit-based allocation overhead.
</li>
<li>
<code>CONFIG_HEAP2_BASE</code> and <code>CONFIG_HEAP2_SIZE</code>:
Some architectures use these settings to specify the size of
a second heap region.
</li>
<li>
<code>CONFIG_GRAN</code>:
Enable granual allocator support. Allocations will be aligned to the
granule size; allocations will be in units of the granule size.
Larger granules will give better performance and less overhead but
more losses of memory due to alignment and quantization waste.
NOTE: The current implementation also restricts the maximum
allocation size to 32 granaules. That restriction could be
eliminated with some additional coding effort.
</li>
<li>
<code>CONFIG_GRAN_SINGLE</code>:
Select if there is only one instance of the granule allocator (i.e.,
gran_initialize will be called only once. In this case, (1) there
are a few optimizations that can can be done and (2) the GRAN_HANDLE
is not needed.
</li>
<li>
<code>CONFIG_GRAN_INTR</code>:
Normally mutual exclusive access to granule allocator data is assured using a semaphore.
If this option is set then, instead, mutual exclusion logic will disable interrupts.
While this options is more invasive to system performance, it will also support use of the
granule allocator from interrupt level logic.
</li>
<li>
<code>CONFIG_DEBUG_GRAM</code>:
Just like <code>CONFIG_DEBUG_MM</code>, but only generates ouput from the gran
allocation logic.
</li>
</ul>
<h2>General OS setup</h2>
<ul>
<li>
<code>CONFIG_ARCH_LOWPUTC</code>: architecture supports low-level, boot
time console output
</li>
<li>
<code>CONFIG_NUTTX_KERNEL</code>:
With most MCUs, NuttX is built as a flat, single executable image
containing the NuttX RTOS along with all application code.
The RTOS code and the application run in the same address space and at the same kernel-mode privileges.
If this option is selected, NuttX will be built separately as a monolithic, kernel-mode module and the applications
can be added as a separately built, user-mode module.
In this a system call layer will be built to support the user- to kernel-mode interface to the RTOS.
</li>
<li>
<code>CONFIG_MSEC_PER_TICK</code>: The default system timer is 100Hz
or <code>MSEC_PER_TICK</code>=10. This setting may be defined to inform NuttX
that the processor hardware is providing system timer interrupts at some interrupt
interval other than 10 msec.
</li>
<li>
<code>CONFIG_RR_INTERVAL</code>: The round robin time slice will be set
this number of milliseconds; Round robin scheduling can
be disabled by setting this value to zero.
</li>
<li>
<code>CONFIG_SCHED_INSTRUMENTATION</code>: enables instrumentation in
scheduler to monitor system performance
</li>
<li>
<code>CONFIG_TASK_NAME_SIZE</code>: Specifies that maximum size of a
task name to save in the TCB. Useful if scheduler
instrumentation is selected. Set to zero to disable.
</li>
<li>
<code>CONFIG_SCHED_HAVE_PARENT</code>: Remember the ID of the parent thread when a new child task is created.
This support enables some additional features (such as <code>SIGCHLD</code>) and modifies the behavior of other interfaces.
For example, it makes <code>waitpid()</code> more standards complete by restricting the waited-for tasks to the children of the caller.
Default: disabled.
</li>
<li>
<code>CONFIG_SCHED_CHILD_STATUS</code>: If this option is selected, then the exit status of the child task will be retained after the child task exits.
This option should be selected if you require knowledge of a child process' exit status.
Without this setting, <code>wait()</code>, <code>waitpid()</code> or <code>waitid()</code> may fail.
For example, if you do:
<p><ol>
<li>
Start child task
</li>
<li>
Wait for exit status (using <code>wait()</code>, <code>waitpid()</code> or <code>waitid()</code>).
</li>
</ol></p>
<p>
This can fail because the child task may run to completion before the wait begins.
There is a non-standard work-around in this case:
The above sequence will work if you disable pre-emption using <code>sched_lock()</code> prior to starting the child task, then re-enable pre-emption with <code>sched_unlock()</code> after the wait completes.
This works because the child task is not permitted to run until the wait is in place.
</p>
<p>
The standard solution would be to enable <code>CONFIG_SCHED_CHILD_STATUS</code>.
In this case the exit status of the child task is retained after the child exits and the wait will successful obtain the child task's exit status whether it is called before the child task exits or not.
</p>
<p>
<b>Warning</b>:
If you enable this feature, then your application must either (1) take responsibility for reaping the child status with <code>wait()</code>, <code>waitpid()</code> or <code>waitid()</code>, or (2) suppress retention of child status.
If you do not reap the child status, then you have a memory leak and your system will eventually fail.
</p>
Retention of child status can be suppressed on the parent using logic like:
</p>
<ul><pre>
struct sigaction sa;
sa.sa_handler = SIG_IGN;
sa.sa_flags = SA_NOCLDWAIT;
int ret = sigaction(SIGCHLD, &sa, NULL);
</pre></ul>
</li>
<li>
<code>CONFIG_PREALLOC_CHILDSTATUS</code>: To prevent runaway child status allocations and to improve
allocation performance, child task exit status structures are pre-allocated when the system boots.
This setting determines the number of child status structures that will be pre-allocated.
If this setting is not defined or if it is defined to be zero then a value of 2*<code>MAX_TASKS</code> is used.
<p>
Note that there cannot be more that <code>CONFIG_MAX_TASKS</code> tasks in total.
However, the number of child status structures may need to be significantly larger because this number includes the maximum number of tasks that are running PLUS the number of tasks that have exit'ed without having their exit status reaped (via <code>wait()</code>, <code>waitpid()</code> or <code>waitid()</code>).
</p>
<p>
Obviously, if tasks spawn children indefinitely and never have the exit status reaped, then you may have a memory leak!
If you enable the <code>SCHED_CHILD_STATUS</code> feature, then your application must take responsibility for either (1) reaping the child status with <code>wait()</code>, <code>waitpid()</code> or <code>waitid()</code> or it must (2) suppress retention of child status. Otherwise, your system will eventually fail.
</p>
<p>
Retention of child status can be suppressed on the parent using logic like:
</p>
<ul><pre>
struct sigaction sa;
sa.sa_handler = SIG_IGN;
sa.sa_flags = SA_NOCLDWAIT;
int ret = sigaction(SIGCHLD, &sa, NULL);
</pre></ul>
</li>
<li>
<code>CONFIG_SYSTEM_TIME16</code>:
The range of system time is, by default, 32-bits.
However, if the MCU supports type <code>long long</code> and <code>CONFIG_SYSTEM_TIME16</code> is selected,
a 64-bit system timer will be supported instead.
</li>
<li>
<code>CONFIG_START_YEAR</code>, <code>CONFIG_START_MONTH</code>, <code>CONFIG_START_DAY</code> -
Used to initialize the internal time logic.
</li>
<li>
<code>CONFIG_GREGORIAN_TIME</code>: Enables Gregorian time conversions.
You would only need this if you are concerned about accurate time conversions in
the recent past or in the distant future.
</li>
<li>
<code>CONFIG_JULIAN_TIME</code>: Enables Julian time conversions.
You would only need this if you are concerned about accurate time conversion in the distand past.
You must also define <code>CONFIG_GREGORIAN_TIME</code> in order to use Julian time.
</li>
<li>
<code>CONFIG_DEV_CONSOLE</code>: Set if architecture-specific logic provides <code>/dev/console</code>.
Enables <code>stdout</code>, <code>stderr</code>, and <code>stdin</code>.
This implies the "normal" serial driver provides the console unless another console device is specified
(See <code>CONFIG_DEV_LOWCONSOLE</code>).
</li>
<li>
<code>CONFIG_MUTEX_TYPES</code>: Set to enable support for recursive and
errorcheck mutexes. Enables <code>pthread_mutexattr_settype()</code>.
</li>
<li>
<code>CONFIG_PRIORITY_INHERITANCE</code>: Set to enable support for
priority inheritance on mutexes and semaphores.
Priority inheritance is a strategy of addressing
<a href="NuttxUserGuide.html#priorityinversion"><i>priority inversion</i></a>.
Details of the NuttX implementation of priority inheritance is
discussed <a href="NuttxUserGuide.html#priorityinheritance">elsewhere</a>.
</li>
<li>
<code>CONFIG_SEM_PREALLOCHOLDERS</code>: This setting is only used
if priority inheritance is enabled.
It defines the maximum number of different threads (minus one) that
can take counts on a semaphore with priority inheritance support.
This may be set to zero if priority inheritance is disabled OR if you
are only using semaphores as mutexes (only one holder) OR if no more
than two threads participate using a counting semaphore.
If defined, then this should be a relatively large number because this
is the total number of counts on the total number of semaphores (like
64 or 100).
</li>
<li>
<code>CONFIG_SEM_NNESTPRIO</code>: If priority inheritance is enabled,
then this setting is the maximum number of higher priority threads (minus
1) than can be waiting for another thread to release a count on a semaphore.
This value may be set to zero if no more than one thread is expected to
wait for a semaphore.
If defined, then this should be a relatively small number because this the
number of maximumum of waiters on one semaphore (like 4 or 8).
</li>
<li>
<code>CONFIG_FDCLONE_DISABLE</code>: Disable cloning of all file descriptors
by task_create() when a new task is started.
If set, all files/drivers will appear to be closed in the new task.
</li>
<li>
<code>CONFIG_FDCLONE_STDIO</code>: Disable cloning of all but the first
three file descriptors (stdin, stdout, stderr) by task_create()
when a new task is started.
If set, all files/drivers will appear to be closed in the new task except
for stdin, stdout, and stderr.
</li>
<li>
<code>CONFIG_SDCLONE_DISABLE</code>: Disable cloning of all socket
desciptors by task_create() when a new task is started.
If set, all sockets will appear to be closed in the new task.
</li>
<li>
<code>CONFIG_SCHED_WORKQUEUE</code>: Create a dedicated "worker" thread to
handle delayed processing from interrupt handlers. This feature
is required for some drivers but, if there are not complaints,
can be safely disabled. The worker thread also performs
garbage collection -- completing any delayed memory deallocations
from interrupt handlers. If the worker thread is disabled,
then that clean will be performed by the IDLE thread instead
(which runs at the lowest of priority and may not be appropriate
if memory reclamation is of high priority). If CONFIG_SCHED_WORKQUEUE
is enabled, then the following options can also be used:
</li>
<li>
<code>CONFIG_SCHED_WORKPRIORITY</code>: The execution priority of the worker
thread. Default: 50
</li>
<li>
<code>CONFIG_SCHED_WORKPERIOD</code>: How often the worker thread checks for
work in units of microseconds. Default: 50*1000 (50 MS).
</li>
<li>
<code>CONFIG_SCHED_WORKSTACKSIZE</code>: The stack size allocated for the worker
thread. Default: CONFIG_IDLETHREAD_STACKSIZE.
</li>
<li>
<code>CONFIG_SIG_SIGWORK</code>: The signal number that will be used to wake-up
the worker thread. Default: 17
</li>
<li>
<code>CONFIG_SCHED_LPWORK</code>: If CONFIG_SCHED_WORKQUEUE</code> is defined, then a single work queue is created by default.
If <code>CONFIG_SCHED_LPWORK</code> is also defined then an additional, lower-priority work queue will also be created.
This lower priority work queue is better suited for more extended processing (such as file system clean-up operations)
</li>
<li>
<code>CONFIG_SCHED_LPWORKPRIORITY</code>: The execution priority of the lower priority worker thread. Default: 50
</li>
<li>
<code>CONFIG_SCHED_LPWORKPERIOD</code>: How often the lower priority worker thread checks for work in units of microseconds. Default: 50*1000 (50 MS).
</li>
<li>
<code>CONFIG_SCHED_LPWORKSTACKSIZE</code>: The stack size allocated for the lower priority worker thread. Default: CONFIG_IDLETHREAD_STACKSIZE.
</li>
<li>
<code>CONFIG_SCHED_WAITPID</code>: Enables the <a href="NuttxUserGuide.html#waitpid"><code>waitpid()</code><a> interface in a default, non-standard mode (non-standard in the sense that the waited for PID need not be child of the caller).
If <code>SCHED_HAVE_PARENT</code> is also defined, then this setting will modify the behavior or <a href="NuttxUserGuide.html#waitpid"><code>waitpid()</code><a> (making more spec compliant) and will enable the <a href="NuttxUserGuide.html#waitid"><code>waitid()</code><a> and <a href="NuttxUserGuide.html#wait"><code>waitp()</code><a> interfaces as well.
</li>
<li>
<code>CONFIG_SCHED_ATEXIT</code>: Enables the <a href="NuttxUserGuide.html#atexit">atexit()</code><a> API
</li>
<li>
<code>CONFIG_SCHED_ATEXIT_MAX</code>: By default if <code>CONFIG_SCHED_ATEXIT</code> is selected, only a single <code>atexit()</code> function is supported.
That number can be increased by defined this setting to the number that you require.
</li>
<li>
<code>CONFIG_SCHED_ONEXIT</code>: Enables the <a href="NuttxUserGuide.html#onexit">on_exit()</code><a> API
</li>
<li>
<code>CONFIG_SCHED_ONEXIT_MAX</code>: By default if <code>CONFIG_SCHED_ONEXIT</code> is selected, only a single <code>on_exit()</code> function is supported.
That number can be increased by defined this setting to the number that you require.
</li>
<li>
<code>CONFIG_USER_ENTRYPOINT</code>: The name of the entry point for user
applications.
For the example applications this is of the form <code>app_main</code>
where <code>app</code> is the application name.
If not defined, <code>CONFIG_USER_ENTRYPOINT</code> defaults to
<code>user_start</code>.
</li>
</ul>
<p>
<b>Signal Numbers</b>:
</p>
<ul>
<li>
<code>CONFIG_SIG_SIGUSR1</code>:
Value of standard user signal 1 (<code>SIGUSR1</code>). Default: 1
</li>
<li>
<code>CONFIG_SIG_SIGUSR2</code>:
Value of standard user signal 2 (<code>SIGUSR2</code>). Default: 2
</li>
<li>
<code>CONFIG_SIG_SIGALARM</code>:
Default the standard signal used with POSIX timers (<code>SIGALRM</code>). Default: 3
</li>
<li>
<code>CONFIG_SIG_SIGCHLD</code>:
The <code>SIGCHLD</code> signal is sent to the parent of a child process when it exits, is interrupted (stopped), or resumes after being interrupted.
Default: 4
</li>
<li>
<code>CONFIG_SIG_SIGCONDTIMEDOUT</code>:
This non-standard signal number is used in the implementation of <code>pthread_cond_timedwait()</code>.
Default 16.
</li>
<li>
<code>CONFIG_SIG_SIGWORK</code>:
<code>SIGWORK</code> is a non-standard signal used to wake up the internal NuttX worker thread.
Default: 17.
</li>
</ul>
<p>
<b>Binary Loaders</b>:
</p>
<ul>
<li>
<code>CONFIG_BINFMT_DISABLE</code>: By default, support for loadable binary formats is built.
This logic may be suppressed be defining this setting.
</li>
<li>
<code>CONFIG_BINFMT_EXEPATH</code>: Use the contents of the <code>PATH</code> environment variable to locate executable files. Default: n
</li>
<li>
<code>CONFIG_PATH_INITIAL</code>: The initial value of the <code>PATH</code> variable. This is the colon-separated list of absolute paths. E.g., <code>"/bin:/usr/bin:/sbin"</code>
</li>
<li>
<code>CONFIG_BINFMT_CONSTRUCTORS</code>: Build in support for C++ constructors in loaded modules.
</li>
<li>
<code>CONFIG_SYMTAB_ORDEREDBYNAME</code>: Symbol tables are order by name (rather than value).
</li>
<li>
<code>CONFIG_NXFLAT</code>: Enable support for the NXFLAT binary format.
This format will support execution of NuttX binaries located
in a ROMFS file system (see <code>apps/examples/nxflat</code>).
</li>
<li>
<code>CONFIG_ELF</code>: Enable support for the ELF binary format.
This format will support execution of ELF binaries copied from a file system and relocated into RAM (see <code>apps/examples/elf</code>).
</li>
<p>
If <code>CONFIG_ELF</code> is selected, then these additional options are available:
</p>
<li>
<code>CONFIG_ELF_ALIGN_LOG2</code>: Align all sections to this Log2 value: 0->1, 1->2, 2->4, etc.
</li>
<li>
<code>CONFIG_ELF_STACKSIZE</code>: This is the default stack size that will will be used when starting ELF binaries.
</li>
<li>
<code>CONFIG_ELF_BUFFERSIZE</code>: This is an I/O buffer that is used to access the ELF file. Variable length items will need to be read (such as symbol names).
This is really just this initial size of the buffer; it will be reallocated as necessary to hold large symbol names).
Default: 128
</li>
<li>
<code>CONFIG_ELF_BUFFERINCR</code>: This is an I/O buffer that is used to access the ELF file. Variable length items will need to be read (such as symbol names).
This value specifies the size increment to use each time the buffer is reallocated.
Default: 32
</li>
<li>
<code>CONFIG_ELF_DUMPBUFFER</code>: Dump various ELF buffers for debug purposes.
This option requires <code>CONFIG_DEBUG</code> and <code>CONFIG_DEBUG_VERBOSE</code>.
</li>
</ul>
<p>
<b>System Logging</b>:
</p>
<ul>
<li>
<code>CONFIG_SYSLOG</code>: Enables general system logging support.
</li>
<code>CONFIG_SYSLOG_DEVPATH</code>: The full path to the system logging device.
Default <code>"/dev/ramlog"</code> (RAMLOG) or <code>"dev/ttyS1;</code> (CHARDEV).
<p>
At present, there are two system loggins devices available.
If <code>CONFIG_SYSLOG</code> is selected, then these options are also available.
</p>
<p>
First, any a generic character device that may be used as the SYSLOG.
</p>
<li>
<code>CONFIG_SYSLOG_CHAR</code>:
Enable the generic character device for the SYSLOG.
A disadvantage of using the generic character device for the SYSLOG is that it cannot handle debug output generated from interrupt level handlers.
NOTE: No more than one SYSLOG device should be configured.
<p>
Alternatively, a circular buffer in RAM can be used as the SYSLOGing device.
The contents of this RAM buffer can be dumped using the NSH dmesg command.
</p>
<li>
<code>CONFIG_RAMLOG</code>: Enables the RAM logging feature
</li>
<li>
<code>CONFIG_RAMLOG_CONSOLE</code>: Use the RAM logging device as a system console.
If this feature is enabled (along with <code>CONFIG_DEV_CONSOLE</code>), then all
console output will be re-directed to a circular buffer in RAM. This
is useful, for example, if the only console is a Telnet console. Then
in that case, console output from non-Telnet threads will go to the
circular buffer and can be viewed using the NSH 'dmesg' command.
</li>
<li>
<code>CONFIG_RAMLOG_SYSLOG</code>:
Use the RAM logging device for the syslogging interface.
If this feature is enabled (along with <code>CONFIG_SYSLOG</code>), then all debug output (only) will be re-directed to the circular buffer in RAM.
This RAM log can be view from NSH using the <code>dmesg</code> command.
NOTE: Unlike the limited, generic character driver SYSLOG device, the RAMLOG <i>can</i> be used to generate debug output from interrupt level handlers.
</li>
<li>
<code>CONFIG_RAMLOG_NPOLLWAITERS</code>: The number of threads than can be waiting
for this driver on poll(). Default: 4
</li>
<p>
If <code>CONFIG_RAMLOG_CONSOLE</code> or <code>CONFIG_RAMLOG_SYSLOG</code> is selected, then the
following may also be provided:
</p>
</li>
<li>
<code>CONFIG_RAMLOG_CONSOLE_BUFSIZE</code>: Size of the console RAM log. Default: 1024
</li>
</ul>
<p>
<b>Kernel build options</b>:
</p>
<ul>
<li>
<code>CONFIG_NUTTX_KERNEL</code>: Builds NuttX as a separately compiled kernel.
</li>
<code>CONFIG_SYS_RESERVED</code>: Reserved system call values for use by architecture-specific logic.
</li>
</ul>
<p>
<b>OS setup related to on-demand paging</b>:
</p>
<ul>
<li>
<code>CONFIG_PAGING</code>: If set =y in your configation file, this setting will
enable the on-demand paging feature as described in
<a href="http://www.nuttx.org/Documentation/NuttXDemandPaging.html">NuttXDemandPaging.html</a>.
</li>
</ul>
<p>
If CONFIG_PAGING is selected, then you will probabaly need <code>CONFIG_BUILD_2PASS</code> to correctly position
the code and the following configuration options also apply:
</p>
<ul>
<li>
<code>CONFIG_PAGING_PAGESIZE</code>:
The size of one managed page.
This must be a value supported by the processor's memory management unit.
</li>
<li>
<code>CONFIG_PAGING_NLOCKED</code>:
This is the number of locked pages in the memory map.
The locked address region will then be from <code>CONFIG_RAM_VSTART</code> through
(<code>CONFIG_RAM_VSTART</code> + <code>CONFIG_PAGING_PAGESIZE</code>*<code>CONFIG_PAGING_NLOCKED</code>)
</li>
<li>
<code>CONFIG_PAGING_LOCKED_PBASE</code> and <code>CONFIG_PAGING_LOCKED_VBASE</code>:
These may be defined to determine the base address of the locked page regions.
If neither are defined, the logic will be set the bases to <code>CONFIG_RAM_START</code>
and <code>CONFIG_RAM_VSTART</code> (i.e., it assumes that the base address of the locked
region is at the beginning of RAM).
<b>NOTE</b>:
In some architectures, it may be necessary to take some memory from the beginning
of this region for vectors or for a page table.
In such cases, <code>CONFIG_PAGING_LOCKED_P/VBASE</code> should take that into consideration
to prevent overlapping the locked memory region and the system data at the beginning of SRAM.
</li>
<li>
<code>CONFIG_PAGING_NPPAGED</code>:
This is the number of physical pages available to support the paged text region.
This paged region begins at
(<code>CONFIG_PAGING_LOCKED_PBASE</code> + <code>CONFIG_PAGING_PAGESIZE</code>*<code>CONFIG_PAGING_NPPAGED</code>)
and continues until
(<code>CONFIG_PAGING_LOCKED_PBASE</code> + <code>CONFIG_PAGING_PAGESIZE</code>*(<code>CONFIG_PAGING_NLOCKED</code> +
<code>CONFIG_PAGING_NPPAGED</code>)
</li>
<li>
<code>CONFIG_PAGING_NVPAGED</code>:
This actual size of the paged text region (in pages).
This is also the number of virtual pages required to support the entire paged region.
The on-demand paging feature is intended to support only the case where the virtual paged text
area is much larger the available physical pages.
Otherwise, why would you enable on-demand paging?
</li>
<li>
<code>CONFIG_PAGING_NDATA</code>:
This is the number of data pages in the memory map.
The data region will extend to the end of RAM unless overridden by a setting in the configuration file.
<b>NOTE</b>:
In some architectures, it may be necessary to take some memory from the end of RAM for page tables
or other system usage.
The configuration settings and linker directives must be cognizant of that:
<code>CONFIG_PAGING_NDATA</code> should be defined to prevent the data region from extending all the way to the end of memory.
</li>
<li>
<code>CONFIG_PAGING_DEFPRIO</code>:
The default, minimum priority of the page fill worker thread.
The priority of the page fill work thread will be boosted boosted dynmically so that it matches the
priority of the task on behalf of which it peforms the fill.
This defines the minimum priority that will be used. Default: 50.
</li>
<li>
<code>CONFIG_PAGING_STACKSIZE</code>:
Defines the size of the allocated stack for the page fill worker thread. Default: 1024.
</li>
<li>
<code>CONFIG_PAGING_BLOCKINGFILL</code>:
The architecture specific <code>up_fillpage()</code> function may be blocking or non-blocking.
If defined, this setting indicates that the <code>up_fillpage()</code> implementation will block until the
transfer is completed. Default: Undefined (non-blocking).
</li>
<li>
<code>CONFIG_PAGING_WORKPERIOD</code>:
The page fill worker thread will wake periodically even if there is no mapping to do.
This selection controls that wake-up period (in microseconds).
This wake-up a failsafe that will handle any cases where a single is lost (that would
really be a bug and shouldn't happen!)
and also supports timeouts for case of non-blocking, asynchronous fills (see <code>CONFIG_PAGING_TIMEOUT_TICKS</code>).
</li>
<li>
<code>CONFIG_PAGING_TIMEOUT_TICKS</code>:
If defined, the implementation will monitor the (asynchronous) page fill logic.
If the fill takes longer than this number if microseconds, then a fatal error will be declared.
Default: No timeouts monitored.
</li>
<p>
Some architecture-specific settings.
Defaults are architecture specific.
If you don't know what you are doing, it is best to leave these undefined and try the system defaults:
</p>
<li>
<code>CONFIG_PAGING_VECPPAGE</code>:
This the physical address of the page in memory to be mapped to the vector address.
</li>
<li>
<code>CONFIG_PAGING_VECL2PADDR</code>:
This is the physical address of the L2 page table entry to use for the vector mapping.
</li>
<li>
<code>CONFIG_PAGING_VECL2VADDR</code>:
This is the virtual address of the L2 page table entry to use for the vector mapping.
</li>
<li>
<code>CONFIG_PAGING_BINPATH</code>:
If <code>CONFIG_PAGING_BINPATH</code> is defined, then it is the full path to a file on a mounted file system that contains a binary image of the NuttX executable.
Pages will be filled by reading from offsets into this file that correspond to virtual fault addresses.
</li>
<li>
<code>CONFIG_PAGING_MOUNTPT</code>:
If <code>CONFIG_PAGING_BINPATH</code> is defined, additional options may be provided to control the initialization of underlying devices.
<code>CONFIG_PAGING_MOUNTPT</code> identifies the mountpoint to be used if a device is mounted.
</li>
<li>
<code>CONFIG_PAGING_MINOR</code>:
Some mount operations require a "minor" number to identify the specific device instance.
Default: 0
</li>
<li>
<code>CONFIG_PAGING_SDSLOT</code>:
If <code>CONFIG_PAGING_BINPATH</code> is defined, additional options may be provided to control the initialization of underlying devices.
<code>CONFIG_PAGING_SDSLOT</code> identifies the slot number of the SD device to initialize.
This must be undefined if SD is not being used.
This should be defined to be zero for the typical device that has only a single slot (See <code>CONFIG_MMCSD_NSLOTS</code>).
If defined, <code>CONFIG_PAGING_SDSLOT</code> will instruct certain board-specific logic to initialize the media in this SD slot.
</li>
<li>
<code>CONFIG_PAGING_M25PX</code>:
Use the m25px.c FLASH driver.
If this is selected, then the MTD interface to the M25Px device will be used to support paging.
</li>
<li>
<code>CONFIG_PAGING_AT45DB</code>:
Use the at45db.c FLASH driver.
If this is selected, then the MTD interface to the Atmel AT45DB device will be used to support paging.
</li>
<li>
<code>CONFIG_PAGING_BINOFFSET</code>:
If CONFIG_PAGING_M25PX or CONFIG_PAGING_AT45DB is defined then CONFIG_PAGING_BINOFFSET will be used to specify the offset in bytes into the FLASH device where the NuttX binary image is located.
Default: 0
</li>
<li>
<code>CONFIG_PAGING_SPIPORT</code>:
If CONFIG_PAGING_M25PX or CONFIG_PAGING_AT45DB is defined and the device has multiple SPI busses (ports), then this configuration should be set to indicate which SPI port the device is connected.
Default: 0
</li>
</ul>
<p>
<b>Disabling OS Features</b>.
The following can be used to disable categories of APIs supported
by the OS. If the compiler supports weak functions, then it
should not be necessary to disable functions unless you want to
restrict usage of those APIs.
</p>
<p>
There are certain dependency relationships in these features.
</p>
<ul>
<li>
<code>mq_notify()</code> logic depends on signals to awaken tasks
waiting for queues to become full or empty.
</li>
<li>
<code>pthread_condtimedwait()</code> depends on signals to wake
up waiting tasks.
</li>
</ul>
<ul>
<code>CONFIG_DISABLE_CLOCK</code>, <code>CONFI_DISABLE_POSIX_TIMERS</code>,
<code>CONFIG_DISABLE_PTHREAD</code>, <code>CONFIG_DISABLE_SIGNALS</code>,
<code>CONFIG_DISABLE_MQUEUE</code>, <code>CONFIG_DISABLE_MOUNTPOUNT</code>
</ul>
<h2>Miscellaneous libc settings</h2>
<ul>
<li>
<code>CONFIG_NOPRINTF_FIELDWIDTH</code>: <code>sprintf</code>-related logic is a
little smaller if we do not support fieldwidthes
</li>
<li>
<code>CONFIG_LIBC_FLOATINGPOINT</code>: By default, floating point
support in <code>printf</code>, <code>sscanf</code>, etc. is disabled.
</li>
<li>
<code>CONFIG_LIBC_STRERROR</code>:
<code>strerror()</code> is useful because it decodes <code>errno</code> values into a human readable strings.
But it can also require a lot of memory to store the strings.
If this option is selected, <code>strerror()</code> will still exist in the build but it will not decode error values.
This option should be used by other logic to decide if it should use <code>strerror()</code> or not.
For example, the NSH application will not use <code>strerror()</code> if this option is not selected;
<code>perror(</code>) will not use strerror() is this option is not selected (see also <code>CONFIG_NSH_STRERROR</code>).
</li>
<li>
<code>CONFIG_LIBC_STRERROR_SHORT</code>:
If this option is selected, then <code>strerror()</code> will use a shortened string when it decodes the error.
Specifically, <code>strerror()</code> is simply use the string that is the common name for the error.
For example, the <code>errno</code> value of 2 will produce the string "No such file or directory" if <code>CONFIG_LIBC_STRERROR_SHORT</code> is not defined but the string "ENOENT" if <code>CONFIG_LIBC_STRERROR_SHORT</code> is defined.
</li>
<li>
<code>CONFIG_LIBC_PERROR_STDOUT</code>:
POSIX requires that <code>perror()</code> provide its output on <code>stderr</code>.
This option may be defined, however, to provide <code>perror()</code> output that is serialized with other <code>stdout</code> messages.
</li>
</ul>
<h2>Allow for architecture optimized implementations</h2>
<ul>
<li>
The architecture can provide optimized versions of the following to improve system performance.
</li>
<ul><p>
<code>CONFIG_ARCH_MEMCPY</code>, <code>CONFIG_ARCH_MEMCMP</code>, <code>CONFIG_ARCH_MEMMOVE</code>,
<code>CONFIG_ARCH_MEMSET</code>, <code>CONFIG_ARCH_STRCMP</code>, <code>CONFIG_ARCH_STRCPY</code>,
<code>CONFIG_ARCH_STRNCPY</code>, <code>CONFIG_ARCH_STRLEN</code>, <code>CONFIG_ARCH_STRNLEN</code>,
<code>CONFIG_ARCH_BZERO</code>
</p></ul>
<p><li>
If <code>CONFIG_ARCH_MEMCPY</code> is <b>not</b> selected, then you make also select Daniel
Vik's optimized implementation of <code>memcpy()</code>:
</p>
<ul><li>
<code>CONFIG_MEMCPY_VIK</code>:
Select this option to use the optimized <code>memcpy()</code> function by Daniel Vik.
Select this option for improved performance at the expense of increased size.
See licensing information in the top-level <code>COPYING</code> file.
Default: <code>n</code>.
</li></ul>
<p>
And if <code>CONFIG_MEMCPY_VIK</code> is selected, the following tuning options are available:
</p>
<ul><li>
<code>CONFIG_MEMCPY_PRE_INC_PTRS</code>:
Use pre-increment of pointers.
Default is post increment of pointers.
</li>
<li>
<code>CONFIG_MEMCPY_INDEXED_COPY</code>
Copying data using array indexing.
Using this option, disables the <code>CONFIG_MEMCPY_PRE_INC_PTRS</code> option.
</li>
<li>
<code>CONFIG_MEMCPY_64BIT</code>:
Compiles <code>memcpy()</code> for 64 bit architectures
</li></ul>
<p><li>
If <code>CONFIG_ARCH_MEMSET</code> is <b>not</b> selected, then the following option is also available:
</p>
<ul><li>
<code>CONFIG_MEMSET_OPTSPEED</code>:
Select this option to use a version of <code>memset()</code> optimized for speed.
Default: <code>memset()</code> is optimized for size.
</li></ul>
<p>
And if <code>CONFIG_MEMSET_OPTSPEED</code> is selected, the following tuning option is available:
</p>
<ul><li>
<code>CONFIG_MEMSET_64BIT</code>:
Compiles <code>memset()</code> for 64 bit architectures
</li></ul>
<li>
<p>
The architecture may provide custom versions of certain standard header files:
</p>
<ul>
<li><b><code>CONFIG_ARCH_STDBOOL_H</code></b>.
<p>
The <code>stdbool.h</code> header file can be found at <code>nuttx/include/stdbool.h</code>.
However, that header includes logic to redirect the inclusion of an architecture specific header file like:
</p>
<ul><pre>
#ifdef CONFIG_ARCH_STDBOOL_H
# include <arch/stdbool.h>
#else
...
#endif
</pre></ul>
<p>
Recall that that include path, <code>include/arch</code>, is a symbolic link and will refer to a version of <code>stdbool.h</code> at <code>nuttx/arch/<architecture>/include/stdbool.h</code>.
</p>
</li>
<li><b><code>CONFIG_ARCH_STDINT_H</code></b>.
<p>
Similar logic exists for the <code>stdint.h</code> header file can also be found at <code>nuttx/include/stdint.h</code>.
<ul><pre>
#ifdef CONFIG_ARCH_STDBOOL_H
# include <arch/stdinit.h>
#else
...
#endif
</pre></ul>
</p>
</li>
<li><b><code>CONFIG_ARCH_MATH_H</code></b>.
<p>
There is also a re-directing version of <code>math.h</code> in the source tree. However, it resides out-of-the-way at <code>include/nuttx/math.h</code> because it conflicts too often with the system <code>math.h</code>.
If <code>CONFIG_ARCH_MATH_H=y</code> is defined, however, the top-level makefile will copy the redirecting <code>math.h</code> header file from <code>include/nuttx/math.h</code> to <code>include/math.h</code>.
<code>math.h</code> will then include the architecture-specific version of <code>math.h</code> that you must provide at <code>nuttx/arch/<architecture>/include/math.h</code>.
</p>
<ul><pre>
#ifdef CONFIG_ARCH_MATH_H
# include <arch/math.h>
#endif
</pre></ul>
<p>
So for the architectures that define <code>CONFIG_ARCH_MATH_H=y</code>, <code>include/math.h</code> will be the redirecting <code>math.h</code> header file; for the architectures that don't select <code>CONFIG_ARCH_MATH_H</code>, the redirecting <code>math.h</code> header file will stay out-of-the-way in <code>include/nuttx/</code>.
</p>
</li>
<li><b><code>CONFIG_ARCH_FLOAT_H</code></b>.
<p>
If you enable the generic, built-in math library, then that math library will expect your toolchain to provide the standard <code>float.h</code> header file.
The <code>float.h</code> header file defines the properties of your floating point implementation.
It would always be best to use your toolchain's <code>float.h</code> header file but if none is avaiable, a default <code>float.h</code> header file will provided if this option is selected.
However, there is no assurance that the settings in this float.h are actually correct for your platform!
</p>
</li>
<li><b><code>CONFIG_ARCH_STDARG_H</code></b>.
<p>
There is also a redirecting version of <code>stdarg.h</code> in the source tree as well.
It also resides out-of-the-way at <code>include/nuttx/stdarg.h</code>.
This is because you should normally use your toolchain's <code>stdarg.h</code> file.
But sometimes, your toolchain's <code>stdarg.h</code> file may have other header file dependencies and so may not be usable in the NuttX build environment.
In those cases, you may have to create a architecture-specific <code>stdarg.h</code> header file at <code>nuttx/arch/<architecture>/include/stdarg.h</code>
</p>
<p>
If <code>CONFIG_ARCH_STDARG_H=y</code> is defined, the top-level makefile will copy the re-directing <code>stdarg.h</code> header file from <code>include/nuttx/stdarg.h</code> to <code>include/stdarg.h</code>.
So for the architectures that cannot use their toolchain's <code>stdarg.h</code> file, they can use this alternative by defining <code>CONFIG_ARCH_STDARG_H=y</code> and providing.
If <code>CONFIG_ARCH_STDARG_H</code>, is not defined, then the <code>stdarg.h</code> header file will stay out-of-the-way in <code>include/nuttx/.</code>
</p>
</li>
</ul>
</li>
<li>
<p><code>CONFIG_ARCH_ROMGETC</code>:
There are cases where string data cannot be cannot be accessed by simply de-referencing a string pointer.
As examples:
</p>
<ul>
<li>
In Harvard architectures, data accesses and instruction accesses occur on different busses, perhaps concurrently.
All data accesses are performed on the data bus unless special machine instructions are used to read data from the instruction address space.
Also, in the typical MCU, the available SRAM data memory is much smaller that the non-volatile FLASH instruction memory.
So if the application requires many constant strings, the only practical solution may be to store those constant strings in FLASH memory where they can only be accessed using architecture-specific machine instructions.
</li>
<li>
A similar case is where strings are retained in "external" memory such as EEPROM or serial FLASH.
This case is similar only in that again special operations are required to obtain the string data;
it cannot be accessed directly from a string pointer.
</li>
</ul>
<p>
If <code>CONFIG_ARCH_ROMGETC</code> is defined, then the architecture-specific logic must export the function <code>up_romgetc()</code>.
<code>up_romgetc()</code> will simply read one byte of data from the instruction space.
</p>
<p>
If <code>CONFIG_ARCH_ROMGETC</code>, certain C stdio functions are effected:
(1) All format strings in <code>printf</code>, <code>fprintf</code>, <code>sprintf</code>, etc. are assumed to lie in FLASH
(string arguments for <code>%s</code> are still assumed to reside in SRAM).
And (2), the string argument to <code>puts</code> and <code>fputs</code> is assumed to reside in FLASH.
Clearly, these assumptions may have to modified for the particular needs of your environment.
There is no "one-size-fits-all" solution for this problem.
</p>
</ul>
<h2>Sizes of configurable things (0 disables)</h2>
<ul>
<li>
<code>CONFIG_MAX_TASKS</code>: The maximum number of simultaneously
active tasks. This value must be a power of two.
</li>
<li>
<code>CONFIG_NPTHREAD_KEYS</code>: The number of items of thread-
specific data that can be retained
</li>
<li>
<code>CONFIG_NFILE_DESCRIPTORS</code>: The maximum number of file
descriptors (one for each open)
</li>
<li>
<code>CONFIG_NFILE_STREAMS</code>: The maximum number of streams that
can be fopen'ed
</li>
<li>
<code>CONFIG_NAME_MAX</code>: Maximum number of bytes in a filename (not including terminating null).
Default: 32
</li>
<li>
<code>CONFIG_PATH_MAX</code>: Maximum number of bytes in a pathname, including the terminating null character.
Default: <code>MIN(256,(4*CONFIG_NAME_MAX+1))</code>
</li>
<li>
<code>CONFIG_STDIO_BUFFER_SIZE</code>: Size of the buffer to allocate
on fopen. (Only if CONFIG_NFILE_STREAMS > 0)
</li>
<li>
<code>CONFIG_STDIO_LINEBUFFER</code>:
If standard C buffered I/O is enabled (<code>CONFIG_STDIO_BUFFER_SIZE</code> > 0),
then this option may be added to force automatic, line-oriented flushing the output buffer
for <code>putc()</code>, <code>fputc()</code>, <code>putchar()</code>, <code>puts()</code>, <code>fputs()</code>,
<code>printf()</code>, <code>fprintf()</code>, and <code>vfprintf()</code>.
When a newline character is encountered in the output string, the output buffer will be flushed.
This (slightly) increases the NuttX footprint but supports the kind of behavior that people expect for <code>printf()</code>.
<li>
<code>CONFIG_NUNGET_CHARS</code>: Number of characters that can be
buffered by ungetc() (Only if CONFIG_NFILE_STREAMS > 0)
</li>
<li>
<code>CONFIG_PREALLOC_MQ_MSGS</code>: The number of pre-allocated message
structures. The system manages a pool of preallocated
message structures to minimize dynamic allocations
</li>
<li>
<code>CONFIG_MQ_MAXMSGSIZE</code>: Message structures are allocated with
a fixed payload size given by this setting (does not include
other message structure overhead.
</li>
<li>
<code>CONFIG_PREALLOC_WDOGS</code>: The number of pre-allocated watchdog
structures. The system manages a pool of preallocated
watchdog structures to minimize dynamic allocations
</li>
<li>
<code>CONFIG_PREALLOC_IGMPGROUPS</code>: Pre-allocated IGMP groups are used
Only if needed from interrupt level group created (by the IGMP server).
Default: 4
</li>
<li>
<code>CONFIG_DEV_PIPE_SIZE</code>: Size, in bytes, of the buffer to allocated
for pipe and FIFO support (default is 1024).
</li>
</ul>
<h2>File Systems</h2>
<ul>
<li>
<code>CONFIG_FS_FAT</code>: Enable FAT file system support.
</li>
<li>
<code>CONFIG_FAT_LCNAMES</code>: Enable use of the NT-style upper/lower case 8.3 file name support.
</li>
<li>
<code>CONFIG_FAT_LFN</code>: Enable FAT long file names.
NOTE: Microsoft claims patents on FAT long file name technology.
Please read the disclaimer in the top-level COPYING file and only enable this feature if you understand these issues.
</li>
<li>
<code>CONFIG_FAT_MAXFNAME</code>: If <code>CONFIG_FAT_LFN</code> is defined, then the default, maximum long file name is 255 bytes.
This can eat up a lot of memory (especially stack space).
If you are willing to live with some non-standard, short long file names, then define this value.
A good choice would be the same value as selected for CONFIG_NAME_MAX which will limit the visibility of longer file names anyway.
</li>
<li>
<code>CONFIG_FS_FATTIME</code>: Support FAT date and time.
NOTE: There is not much sense in supporting FAT date and time unless you have a hardware RTC
or other way to get the time and date.
</li>
<li>
<code>CONFIG_FS_NXFFS</code>: Enable NuttX FLASH file system (NXFF) support.
</li>
<li>
<code>CONFIG_NXFFS_ERASEDSTATE</code>: The erased state of FLASH.
This must have one of the values of <code>0xff</code> or <code>0x00</code>.
Default: <code>0xff</code>.
</li>
<li>
<code>CONFIG_NXFFS_PACKTHRESHOLD</code>: When packing flash file data,
don't both with file chunks smaller than this number of data bytes.
Default: 32.
</li>
<li>
<code>CONFIG_NXFFS_MAXNAMLEN</code>: The maximum size of an NXFFS file name.
Default: 255.
</li>
<li>
<code>CONFIG_NXFFS_PACKTHRESHOLD</code>: When packing flash file data,
don't both with file chunks smaller than this number of data bytes.
Default: 32.
</li>
<li>
<code>CONFIG_NXFFS_TAILTHRESHOLD</code>: clean-up can either mean
packing files together toward the end of the file or, if file are
deleted at the end of the file, clean up can simply mean erasing
the end of FLASH memory so that it can be re-used again. However,
doing this can also harm the life of the FLASH part because it can
mean that the tail end of the FLASH is re-used too often. This
threshold determines if/when it is worth erased the tail end of FLASH
and making it available for re-use (and possible over-wear).
Default: 8192.
</li>
<li>
<code>CONFIG_FS_ROMFS</code>: Enable ROMFS file system support
</li>
<li>
<code>CONFIG_NFS</code>: Enable Network File System (NFS) client file system support.
Provided support is version 3 using UDP.
In addition to common prerequisites for mount-able file systems in general,
this option requires UDP networking support;
this would include <code>CONFIG_NET</code> and <code>CONFIG_NET_UDP</code> at a minimum.
</li>
<li>
<code>CONFIG_FS_RAMMAP</code>: For file systems that do not support
XIP, this option will enable a limited form of memory mapping that is
implemented by copying whole files into memory.
</li>
</ul>
<h2>Device Drivers</h2>
<h3>RTC</h3>
<ul>
<li>
<code>CONFIG_RTC</code>:
Enables general support for a hardware RTC.
Specific architectures may require other specific settings.
</li>
<li>
<code>CONFIG_RTC_DATETIME</code>:
There are two general types of RTC: (1) A simple battery backed counter that keeps the time when power
is down, and (2) A full date / time RTC the provides the date and time information, often in BCD format.
If <code>CONFIG_RTC_DATETIME</code> is selected, it specifies this second kind of RTC.
In this case, the RTC is used to "seed"" the normal NuttX timer and the NuttX system timer
provides for higher resoution time.
</li>
<li>
<code>CONFIG_RTC_HIRES</code>:
If <code>CONFIG_RTC_DATETIME</code> not selected, then the simple, battery backed counter is used.
There are two different implementations of such simple counters based on the time resolution of the counter:
The typical RTC keeps time to resolution of 1 second, usually supporting a 32-bit <code>time_t</code> value.
In this case, the RTC is used to "seed" the normal NuttX timer and the NuttX timer provides for higher resoution time.
If <code>CONFIG_RTC_HIRES</code> is enabled in the NuttX configuration, then the RTC provides higher resolution time and completely replaces the system timer for purpose of date and time.
</li>
<li>
<code>CONFIG_RTC_FREQUENCY</code>:
If <code>CONFIG_RTC_HIRES</code> is defined, then the frequency of the high resolution RTC must be provided.
If <code>CONFIG_RTC_HIRES</code> is not defined, <code>CONFIG_RTC_FREQUENCY</code> is assumed to be one.
</li>
<li>
<code>CONFIG_RTC_ALARM</code>:
Enable if the RTC hardware supports setting of an alarm.
A callback function will be executed when the alarm goes off
</li>
</ul>
<h3>CAN driver</h3>
<ul>
<li>
<code>CONFIG_CAN</code>: Enables CAN support
</li>
<li>
<code>CONFIG_CAN_FIFOSIZE</code>: The size of the circular buffer of CAN messages. Default: 8
</li>
<li>
<code>CONFIG_CAN_NPENDINGRTR</code>: The size of the list of pending RTR requests. Default: 4
</li>
<li>
<code>CONFIG_CAN_LOOPBACK</code>: A CAN driver may or may not support a loopback mode for testing.
If the driver does support loopback mode, the setting will enable it.
(If the driver does not, this setting will have no effect).
</li>
</ul>
<h3>SPI driver</h3>
<ul>
<li>
<code>CONFIG_SPI_OWNBUS</code>: Set if there is only one active device
on the SPI bus. No locking or SPI configuration will be performed.
It is not necessary for clients to lock, re-configure, etc..
</li>
<li>
<code>CONFIG_SPI_EXCHANGE</code>: Driver supports a single exchange method
(vs a recvblock() and sndblock ()methods)
</li>
</ul>
<h3>SPI-based MMC/SD driver</h3>
<ul>
<li>
<code>CONFIG_MMCSD_NSLOTS</code>: Number of MMC/SD slots supported by the driver. Default is one.
</li>
<li>
<code>CONFIG_MMCSD_READONLY</code>: Provide read-only access. Default is Read/Write
</li>
<li>
<code>CONFIG_MMCSD_SPICLOCK</code>: Maximum SPI clock to drive MMC/SD card. Default is 20MHz.
</li>
</ul>
<h3>SDIO/SDHC driver</h3>
<ul>
<li>
<code>CONFIG_SDIO_DMA</code>: SDIO driver supports DMA
</li>
<li>
<code>CONFIG_SDIO_MUXBUS</code>: Set this SDIO interface if the SDIO interface
or hardware resources are shared with other drivers.
</li>
<li>
<code>CONFIG_SDIO_WIDTH_D1_ONLY</code>: Select 1-bit transfer mode. Default:
4-bit transfer mode.
</li>
<li>
<code>CONFIG_MMCSD_MULTIBLOCK_DISABLE</code>: Use only the single block transfer method.
This setting is used to work around buggy SDIO drivers that cannot handle
multiple block transfers.
</li>
</ul>
<h3>SDIO-based MMC/SD driver</h3>
<ul>
<li>
<code>CONFIG_FS_READAHEAD</code>: Enable read-ahead buffering
</li>
<li>
<code>CONFIG_FS_WRITEBUFFER</code>: Enable write buffering
</li>
<li>
<code>CONFIG_SDIO_DMA</code>: SDIO driver supports DMA
</li>
<li>
<code>CONFIG_MMCSD_MMCSUPPORT</code>: Enable support for MMC cards
</li>
<li>
<code>CONFIG_MMCSD_HAVECARDDETECT</code>: SDIO driver card detection is 100% accurate
</li>
</ul>
<h3>RiT P14201 OLED driver</h3>
<ul>
<li>
<code>CONFIG_LCD_P14201</code>: Enable P14201 support
</li>
<li>
<code>CONFIG_P14201_SPIMODE</code>: Controls the SPI mode
</li>
<li>
<code>CONFIG_P14201_FREQUENCY</code>: Define to use a different bus frequency
</li>
<li>
<code>CONFIG_P14201_NINTERFACES</code>:
Specifies the number of physical P14201 devices that will be supported.
</li>
<li>
<code>CONFIG_P14201_FRAMEBUFFER</code>:
If defined, accesses will be performed using an in-memory copy of the OLEDs GDDRAM.
This cost of this buffer is 128 * 96 / 2 = 6K.
If this is defined, then the driver will be fully functional.
If not, then it will have the following limitations:
<ul>
<li>Reading graphics memory cannot be supported, and</li>
<li>All pixel writes must be aligned to byte boundaries.</li>
</ul>
The latter limitation effectively reduces the 128x96 disply to 64x96.
</li>
</ul>
<h3>Nokia 6100 Configuration Settings:</h3>
<ul>
<li>
<code>CONFIG_NOKIA6100_SPIMODE</code>: Controls the SPI mode,
</li>
<li>
<code>CONFIG_NOKIA6100_FREQUENCY</code>: Define to use a different bus frequency.
</li>
<li>
<code>CONFIG_NOKIA6100_NINTERFACES</code>:Specifies the number of physical Nokia
6100 devices that will be supported.
</li>
<li>
<code>CONFIG_NOKIA6100_BPP</code>: Device supports 8, 12, and 16 bits per pixel.
</li>
<li>
<code>CONFIG_NOKIA6100_S1D15G10</code>: Selects the Epson S1D15G10 display controller
</li>
<li>
<code>CONFIG_NOKIA6100_PCF8833</code>: Selects the Phillips PCF8833 display controller
</li>
<li>
<code>CONFIG_NOKIA6100_BLINIT</code>: Initial backlight setting
</li>
<p>
The following may need to be tuned for your hardware:
</p>
<li>
<code>CONFIG_NOKIA6100_INVERT</code>: Display inversion, 0 or 1, Default: 1
</li>
<li>
<code>CONFIG_NOKIA6100_MY</code>: Display row direction, 0 or 1, Default: 0
</li>
<li>
<code>CONFIG_NOKIA6100_MX</code>: Display column direction, 0 or 1, Default: 1
</li>
<li>
<code>CONFIG_NOKIA6100_V</code>: Display address direction, 0 or 1, Default: 0
</li>
<li>
<code>CONFIG_NOKIA6100_ML</code>: Display scan direction, 0 or 1, Default: 0
</li>
<li>
<code>CONFIG_NOKIA6100_RGBORD</code>: Display RGB order, 0 or 1, Default: 0
</li>
<p>
Required LCD driver settings:
</p>
<li>
<code>CONFIG_LCD_NOKIA6100</code>: Enable Nokia 6100 support
</li>
<li>
<code>CONFIG_LCD_MAXCONTRAST</code>: Must be 63 with the Epson controller and 127 with
the Phillips controller.
</li>
<li>
<code>CONFIG_LCD_MAXPOWER</code>:Maximum value of backlight setting. The backlight
control is managed outside of the 6100 driver so this value has no
meaning to the driver. Board-specific logic may place restrictions on
this value.
</li>
</ul>
<h3>Input Devices</h3>
<ul>
<li>
<code>CONFIG_INPUT</code>:
Enables general support for input devices
</li>
<li>
<code>CONFIG_INPUT_TSC2007</code>:
If CONFIG_INPUT is selected, then this setting will enable building
of the TI TSC2007 touchscreen driver.
</li>
<li>
<code>CONFIG_TSC2007_MULTIPLE</code>:
Normally only a single TI TSC2007 touchscreen is used. But if
there are multiple TSC2007 touchscreens, this setting will enable
multiple touchscreens with the same driver.
</li>
<li>
<code>CONFIG_INPUT_STMPE811</code>:
Enables support for the STMPE811 driver (Needs <code>CONFIG_INPUT</code>)
</li>
<li>
<code>CONFIG_STMPE811_SPI</code>:
Enables support for the SPI interface (not currenly supported)
</li>
<li>
<code>CONFIG_STMPE811_I2C</code>:
Enables support for the I2C interface
</li>
<li>
<code>CONFIG_STMPE811_MULTIPLE </code>:
Can be defined to support multiple STMPE811 devices on board.
</li>
<li>
<code>CONFIG_STMPE811_ACTIVELOW</code>:
Interrupt is generated by an active low signal (or falling edge).
</li>
<li>
<code>CONFIG_STMPE811_EDGE</code>:
Interrupt is generated on an edge (vs. on the active level)
</li>
<li>
<code>CONFIG_STMPE811_NPOLLWAITERS</code>:
Maximum number of threads that can be waiting on poll() (ignored if
<code>CONFIG_DISABLE_POLL</code> is set).
</li>
<li>
<code>CONFIG_STMPE811_TSC_DISABLE</code>:
Disable driver touchscreen functionality.
</li>
<li>
<code>CONFIG_STMPE811_ADC_DISABLE</code>:
Disable driver ADC functionality.
</li>
<li>
<code>CONFIG_STMPE811_GPIO_DISABLE</code>:
Disable driver GPIO functionlaity.
</li>
<li>
<code>CONFIG_STMPE811_GPIOINT_DISABLE</code>:
Disable driver GPIO interrupt functionality (ignored if GPIO
functionality is disabled).
</li>
<li>
<code>CONFIG_STMPE811_SWAPXY</code>:
Reverse the meaning of X and Y to handle different LCD orientations.
</li>
<li>
<code>CONFIG_STMPE811_TEMP_DISABLE</code>:
Disable driver temperature sensor functionality.
</li>
<li>
<code>CONFIG_STMPE811_REGDEBUG</code>:
Enabled very low register-level debug output. Requires <code>CONFIG_DEBUG</code>.
</li>
<li>
<code>CONFIG_STMPE811_THRESHX</code> and <code>CONFIG_STMPE811_THRESHY</code>:
STMPE811 touchscreen data comes in a a very high rate. New touch positions
will only be reported when the X or Y data changes by these thresholds.
This trades reduces data rate for some loss in dragging accuracy. The
STMPE811 is configure for 12-bit values so the raw ranges are 0-4095. So
for example, if your display is 320x240, then THRESHX=13 and THRESHY=17
would correspond to one pixel. Default: 12
</li>
</ul>
<h3>Analog Devices</h3>
<ul>
<li>
<code>CONFIG_DAC</code>:
Enables general support for Digital-to-Analog conversion devices.
</li>
<li>
<code>CONFIG_ADC</code>:
Enables general support for Analog-to-Digital conversion devices.
</li>
<li>
<code>CONFIG_ADC_ADS125X</code>:
Adds support for the TI ADS 125x ADC.
</li>
</ul>
<h3>ENC28J60 Ethernet Driver Configuration Settings</h3>
<ul>
<li>
<code>CONFIG_ENC28J60</code>: Enabled ENC28J60 support
</li>
<li>
<code>CONFIG_ENC28J60_SPIMODE</code>: Controls the SPI mode
</li>
<li>
<code>CONFIG_ENC28J60_FREQUENCY</code>: Define to use a different bus frequency
</li>
<li>
<code>CONFIG_ENC28J60_NINTERFACES</code>:
Specifies the number of physical ENC28J60 devices that will be supported.
</li>
<li>
<code>CONFIG_ENC28J60_STATS</code>: Collect network statistics
</li>
<li>
<code>CONFIG_ENC28J60_HALFDUPPLEX</code>: Default is full duplex
</li>
</ul>
<h2>Network Support</h2>
<h3>TCP/IP and UDP support via uIP</h3>
<ul>
<li>
<code>CONFIG_NET</code>: Enable or disable all network features
</li>
<li>
<code>CONFIG_NET_SLIP</code>: Selects the Serial Line Internet Protocol (SLIP) data link layer.
(This selection is discussed further <a href="#slipdriver">below</a>).
</li>
<li>
<code>CONFIG_NET_NOINTS</code>: <code>CONFIG_NET_NOINT</code> indicates that uIP not called from the interrupt level.
If <code>CONFIG_NET_NOINTS</code> is defined, critical sections will be managed with semaphores;
Otherwise, it assumed that uIP will be called from interrupt level handling and critical sections will be managed by enabling and disabling interrupts.
</li>
<li>
<code>CONFIG_NET_MULTIBUFFER</code>: Traditionally, uIP has used a single buffer for all incoming and outgoing traffic.
If this configuration is selected, then the driver can manage multiple I/O buffers and can, for example, be filling one input buffer while sending another output buffer.
Or, as another example, the driver may support queuing of concurrent input/ouput and output transfers for better performance.
</li>
<li>
<code>CONFIG_NET_IPv6</code>: Build in support for IPv6
</li>
<li>
<code>CONFIG_NSOCKET_DESCRIPTORS</code>: Maximum number of socket descriptors per task/thread.
</li>
<li>
<code>CONFIG_NET_NACTIVESOCKETS</code>: Maximum number of concurrent socket operations (recv, send, etc.).
Default: <code>CONFIG_NET_TCP_CONNS</code>+<code>CONFIG_NET_UDP_CONNS</code>.
</li>
<li>
<code>CONFIG_NET_SOCKOPTS</code>: Enable or disable support for socket options.
</li>
<li>
<code>CONFIG_NET_BUFSIZE</code>: uIP buffer size
</li>
<li>
<code>CONFIG_NET_TCP</code>: TCP support on or off
</li>
<li>
<code>CONFIG_NET_TCP_CONNS</code>: Maximum number of TCP connections (all tasks).
</li>
<li>
<code>CONFIG_NET_TCPBACKLOG</code>:
Incoming connections pend in a backlog until <code>accept()</code> is called.
The size of the backlog is selected when <code>listen()</code> is called.
</li>
<li>
<code>CONFIG_NET_TCP_READAHEAD_BUFSIZE</code>: Size of TCP read-ahead buffers
</li>
<li>
<code>CONFIG_NET_NTCP_READAHEAD_BUFFERS</code>: Number of TCP read-ahead buffers (may be zero to disable TCP/IP read-ahead buffering)
</li>
<li>
<code>CONFIG_NET_TCP_RECVDELAY</code>: Delay (in deciseconds) after a TCP/IP packet is received.
This delay may allow catching of additional packets when TCP/IP read-ahead is disabled.
Default: 0
</li>
<li>
<code>CONFIG_NET_MAX_LISTENPORTS</code>: Maximum number of listening TCP ports (all tasks).
</li>
<li>
<code>CONFIG_NET_TCPURGDATA</code>: Determines if support for TCP urgent data
notification should be compiled in. Urgent data (out-of-band data)
is a rarely used TCP feature that is very seldom would be required.
</li>
<li>
<code>CONFIG_NET_UDP</code>: UDP support on or off
</li>
<li>
<code>CONFIG_NET_UDP_CHECKSUMS</code>: UDP checksums on or off
</li>
<li>
<code>CONFIG_NET_UDP_CONNS</code>: The maximum amount of concurrent UDP connections
</li>
<li>
<code>CONFIG_NET_ICMP</code>: Enable minimal ICMP support. Includes built-in support
for sending replies to received ECHO (ping) requests.
</li>
<li>
<code>CONFIG_NET_ICMP_PING</code>: Provide interfaces to support application level
support for sending ECHO (ping) requests and associating ECHO replies.
</li>
<li>
<code>CONFIG_NET_IGMP</code>: Enable IGMPv2 client support.
</li>
<li>
<code>CONFIG_PREALLOC_IGMPGROUPS</code>: Pre-allocated IGMP groups are used
Only if needed from interrupt level group created (by the IGMP server).
Default: 4
</li>
<li>
<code>CONFIG_NET_PINGADDRCONF</code>: Use "ping" packet for setting IP address
</li>
<li>
<code>CONFIG_NET_STATISTICS</code>: uIP statistics on or off
</li>
<li>
<code>CONFIG_NET_RECEIVE_WINDOW</code>: The size of the advertised receiver's window
</li>
<li>
<code>CONFIG_NET_ARPTAB_SIZE</code>: The size of the ARP table
</li>
<li>
<code>CONFIG_NET_ARP_IPIN</code>: Harvest IP/MAC address mappings for the ARP table from incoming IP packets.
</li>
<li>
<code>CONFIG_NET_BROADCAST</code>: Incoming UDP broadcast support
</li>
<li>
<code>CONFIG_NET_MULTICAST</code>: Outgoing multi-cast address support
</li>
</ul>
<h3><a name="slipdriver">SLIP</a></h3>
<p>
The NuttX SLIP driver supports point-to-point IP communications over a serial port.
The default data link layer for uIP is Ethernet.
If <code>CONFIG_NET_SLIP</code> is defined in the NuttX configuration file, then SLIP will be supported.
The basic differences between the SLIP and Ethernet configurations is that when SLIP is selected:
<ul>
<li>The link level header (that comes before the IP header) is omitted.</li>
<li>All MAC address processing is suppressed.</li>
<li>ARP is disabled.</li>
</ul>
If <code>CONFIG_NET_SLIP</code> is not selected, then Ethernet will be used
(there is no need to define anything special in the configuration file to use Ethernet -- it is the default).
</p>
<ul>
<li>
<code>CONFIG_NET_SLIP</code>: Enables building of the SLIP driver.
SLIP requires at least one IP protocols selected and the following additional network settings: <code>CONFIG_NET_NOINTS</code> and <code>CONFIG_NET_MULTIBUFFER</code>.
<code>CONFIG_NET_BUFSIZE</code> <i>must</i> be set to 296.
Other optional configuration settings that affect the SLIP driver: <code>CONFIG_NET_STATISTICS</code>.
Default: Ethernet.
</li>
<p>
If SLIP is selected, then the following SLIP options are available:
</p>
<li>
<code>CONFIG_CLIP_NINTERFACES</code>: Selects the number of physical SLIP interfaces to support. Default: 1
</li>
<li>
<code>CONFIG_SLIP_STACKSIZE</code>: Select the stack size of the SLIP RX and TX tasks. Default: 2048
</li>
<li>
<code>CONFIG_SLIP_DEFPRIO</code>: The priority of the SLIP RX and TX tasks. Default: 128
</li>
</li>
</ul>
<h3>UIP Network Utilities</h3>
<ul>
<li>
<code>CONFIG_NET_DHCP_LIGHT</code>: Reduces size of DHCP
</li>
<li>
<code>CONFIG_NET_RESOLV_ENTRIES</code>: Number of resolver entries
</li>
<li>
<code>CONFIG_NET_RESOLV_MAXRESPONSE</code>:
This setting determines the maximum size of response message that can be received by the DNS resolver.
The default is 96 but may need to be larger on enterprise networks (perhaps 176).
</li>
</ul>
<h3>THTTPD</h3>
<ul>
<li>
<code>CONFIG_THTTPD_PORT</code>: THTTPD Server port number
</li>
<li>
<code>CONFIG_THTTPD_IPADDR</code>: Server IP address (no host name)
</li>
<li>
<code>CONFIG_THTTPD_SERVER_ADDRESS</code>: SERVER_ADDRESS: response
</li>
<li>
<code>CONFIG_THTTPD_SERVER_SOFTWARE</code>: SERVER_SOFTWARE: response
</li>
<li>
<code>CONFIG_THTTPD_PATH</code>: Server working directory. Default: <code>/mnt/www</code>.
</li>
<li>
<code>CONFIG_THTTPD_CGI_PATH</code>: Path to CGI executables. Default: <code>/mnt/www/cgi-bin</code>.
</li>
<li>
<code>CONFIG_THTTPD_CGI_PATTERN</code>: Only CGI programs whose expanded paths
match this pattern will be executed. In fact, if this value is not defined
then no CGI logic will be built. Default: <code>/mnt/www/cgi-bin/*</code>.
</li>
<li>
<code>CONFIG_THTTPD_CGI_PRIORITY</code>: Provides the priority of CGI child tasks
</li>
<li>
<code>CONFIG_THTTPD_CGI_STACKSIZE</code>: Provides the initial stack size of
CGI child task (will be overridden by the stack size in the NXFLAT
header)
</li>
<li>
<code>CONFIG_THTTPD_CGI_BYTECOUNT</code>: Byte output limit for CGI tasks.
</li>
<li>
<code>CONFIG_THTTPD_CGI_TIMELIMIT</code>: How many seconds to allow CGI programs
to run before killing them.
</li>
<li>
<code>CONFIG_THTTPD_CHARSET</code>: The default character set name to use with
text MIME types.
</li>
<li>
<code>CONFIG_THTTPD_IOBUFFERSIZE</code>:
</li>
<li>
<code>CONFIG_THTTPD_INDEX_NAMES</code>: A list of index filenames to check. The
files are searched for in this order.
</li>
<li>
<code>CONFIG_AUTH_FILE</code>: The file to use for authentication. If this is
defined then thttpd checks for this file in the local directory
before every fetch. If the file exists then authentication is done,
otherwise the fetch proceeds as usual. If you leave this undefined
then thttpd will not implement authentication at all and will not
check for auth files, which saves a bit of CPU time. A typical
value is ".htpasswd&quout;
</li>
<li>
<code>CONFIG_THTTPD_LISTEN_BACKLOG</code>: The listen() backlog queue length.
</li>
<li>
<code>CONFIG_THTTPD_LINGER_MSEC</code>: How many milliseconds to leave a connection
open while doing a lingering close.
</li>
<li>
<code>CONFIG_THTTPD_OCCASIONAL_MSEC</code>: How often to run the occasional
cleanup job.
</li>
<li>
<code>CONFIG_THTTPD_IDLE_READ_LIMIT_SEC</code>: How many seconds to allow for
reading the initial request on a new connection.
</li>
<li>
<code>CONFIG_THTTPD_IDLE_SEND_LIMIT_SEC</code>: How many seconds before an
idle connection gets closed.
</li>
<li>
<code>CONFIG_THTTPD_TILDE_MAP1 and CONFIG_THTTPD_TILDE_MAP2</code>: Tilde mapping.
Many URLs use ~username to indicate a user's home directory. thttpd
provides two options for mapping this construct to an actual filename.
<ol>
<li>
Map ~username to <prefix>/username. This is the recommended choice.
Each user gets a subdirectory in the main web tree, and the tilde
construct points there. The prefix could be something like "users",
or it could be empty.
</li>
<li>
Map ~username to <user's homedir>/<postfix>. The postfix would be
the name of a subdirectory off of the user's actual home dir,
something like "public_html".
</li>
</ol>
You can also leave both options undefined, and thttpd will not do
anything special about tildes. Enabling both options is an error.
Typical values, if they're defined, are "users" for
CONFIG_THTTPD_TILDE_MAP1 and "public_html" forCONFIG_THTTPD_TILDE_MAP2.
</li>
<li>
<code>CONFIG_THTTPD_GENERATE_INDICES</code>:
</li>
<li>
<code>CONFIG_THTTPD_URLPATTERN</code>: If defined, then it will be used to match
and verify referrers.
</li>
</ul>
<h3>FTP Server</h3>
<ul>
<li>
<code>CONFIG_FTPD_VENDORID</code>: The vendor name to use in FTP communications. Default: "NuttX"
</li>
<li>
<code>CONFIG_FTPD_SERVERID</code>: The server name to use in FTP communications. Default: "NuttX FTP Server"
</li>
<li>
<code>CONFIG_FTPD_CMDBUFFERSIZE</code>: The maximum size of one command. Default: 128 bytes.
</li>
<li>
<code>CONFIG_FTPD_DATABUFFERSIZE</code>: The size of the I/O buffer for data transfers. Default: 512 bytes.
</li>
<li>
<code>CONFIG_FTPD_WORKERSTACKSIZE</code>: The stacksize to allocate for each FTP daemon worker thread. Default: 2048 bytes.
</li>
</ul>
<p>
Other required FTPD configuration settings: Of course TCP networking support is required. But here are a couple that are less obvious:
</p>
<ul>
<li>
<code>CONFIG_DISABLE_PTHREAD=n</code>: pthread support is required
</li>
<li>
<code>CONFIG_DISABLE_POLL=n</code>: poll() support is required
</li>
</ul>
<h2>USB Device-Side Support</h2>
<h3>USB Device Controller Driver</h3>
<ul>
<li>
<code>CONFIG_USBDEV</code>: Enables USB device support
</li>
<li>
<code>CONFIG_USBDEV_COMPOSITE</code>: Enables USB composite device support
</li>
<li>
<code>CONFIG_USBDEV_ISOCHRONOUS</code>: Build in extra support for isochronous endpoints
</li>
<li>
<code>CONFIG_USBDEV_DUALSPEED</code>: Hardware handles high and full speed operation (USB 2.0)
</li>
<li>
<code>CONFIG_USBDEV_SELFPOWERED</code>: Will cause USB features to indicate that the device is self-powered
</li>
<li>
<code>CONFIG_USBDEV_MAXPOWER</code>: Maximum power consumption in mA
</li>
<li>
<code>CONFIG_USBDEV_TRACE</code>: Enables USB tracing for debug
</li>
<li>
<code>CONFIG_USBDEV_TRACE_NRECORDS</code>: Number of trace entries to remember
</li>
</ul>
<h3>USB Serial Device Class Driver (Prolific PL2303 Emulation)</h3>
<ul>
<li>
<code>CONFIG_PL2303</code>: Enable compilation of the USB serial driver
</li>
<li>
<code>CONFIG_PL2303_EPINTIN</code>: The logical 7-bit address of a hardware endpoint that supports interrupt IN operation
</li>
<li>
<code>CONFIG_PL2303_EPBULKOUT</code>: The logical 7-bit address of a hardware endpoint that supports bulk OUT operation
</li>
<li>
<code>CONFIG_PL2303_EPBULKIN</code>: The logical 7-bit address of a hardware endpoint that supports bulk IN operation
</li>
<li>
<code>CONFIG_PL2303_NWRREQS</code> and <code>CONFIG_PL2303_NRDREQS</code>: The number of write/read requests that can be in flight
</li>
<li>
<code>CONFIG_PL2303_VENDORID</code> and <code>CONFIG_PL2303_VENDORSTR</code>: The vendor ID code/string
</li>
<li>
<code>CONFIG_PL2303_PRODUCTID</code> and <code>CONFIG_PL2303_PRODUCTSTR</code>: The product ID code/string
</li>
<li>
<code>CONFIG_PL2303_RXBUFSIZE</code> and <code>CONFIG_PL2303_TXBUFSIZE</code>: Size of the serial receive/transmit buffers
</li>
</ul>
<h3>USB serial device class driver (Standard CDC ACM class)</h3>
<ul>
<li>
<code>CONFIG_CDCACM</code>: Enable compilation of the USB serial driver
</li>
<li>
<code>CONFIG_CDCACM_COMPOSITE</code>:
Configure the CDC serial driver as part of a composite driver
(only if <code>CONFIG_USBDEV_COMPOSITE</code> is also defined)
</li>
<li>
<code>CONFIG_CDCACM_IFNOBASE</code>:
If the CDC driver is part of a composite device, then this may need to
be defined to offset the CDC/ACM interface numbers so that they are
unique and contiguous. When used with the Mass Storage driver, the
correct value for this offset is zero.
</li>
<li>
<code>CONFIG_CDCACM_STRBASE</code>:
If the CDC driver is part of a composite device, then this may need to
be defined to offset the CDC/ACM string numbers so that they are
unique and contiguous. When used with the Mass Storage driver, the
correct value for this offset is four (this value actuallly only needs
to be defined if names are provided for the Notification interface,
<code>CONFIG_CDCACM_NOTIFSTR</code>, or the data interface, <code>CONFIG_CDCACM_DATAIFSTR</code>).
</li>
<li>
<code>CONFIG_CDCACM_EP0MAXPACKET</code>: Endpoint 0 max packet size. Default 64.
</li>
<li>
<code>CONFIG_CDCACM_EPINTIN</code>: The logical 7-bit address of a hardware endpoint that supports
interrupt IN operation. Default 2.
</li>
<li>
<code>CONFIG_CDCACM_EPINTIN_FSSIZE</code>: Max package size for the interrupt IN endpoint if full speed mode. Default 64.
</li>
<li>
<code>CONFIG_CDCACM_EPINTIN_HSSIZE</code>: Max package size for the interrupt IN endpoint if high speed mode. Default 64.
</li>
<li>
<code>CONFIG_CDCACM_EPBULKOUT</code>: The logical 7-bit address of a hardware endpoint that supports
bulk OUT operation.
</li>
<li>
<code>CONFIG_CDCACM_EPBULKOUT_FSSIZE</code>: Max package size for the bulk OUT endpoint if full speed mode. Default 64.
</li>
<li>
<code>CONFIG_CDCACM_EPBULKOUT_HSSIZE</code>: Max package size for the bulk OUT endpoint if high speed mode. Default 512.
</li>
<li>
<code>CONFIG_CDCACM_EPBULKIN</code>: The logical 7-bit address of a hardware endpoint that supports
bulk IN operation
</li>
<li>
<code>CONFIG_CDCACM_EPBULKIN_FSSIZE</code>: Max package size for the bulk IN endpoint if full speed mode. Default 64.
</li>
<li>
<code>CONFIG_CDCACM_EPBULKIN_HSSIZE</code>: Max package size for the bulk IN endpoint if high speed mode. Default 512.
</li>
<li>
<code>CONFIG_CDCACM_NWRREQS</code> and <code>CONFIG_CDCACM_NRDREQS</code>: The number of write/read requests that can be in flight.
<code>CONFIG_CDCACM_NWRREQS</code> includes write requests used for both the interrupt and bulk IN endpoints.
Default 4.
</li>
<li>
<code>CONFIG_CDCACM_VENDORID</code> and <code>CONFIG_CDCACM_VENDORSTR</code>: The vendor ID code/string. Default 0x0525 and "NuttX,"
0x0525 is the Netchip vendor and should not be used in any products.
This default VID was selected for compatibility with the Linux CDC ACM default VID.
</li>
<li>
<code>CONFIG_CDCACM_PRODUCTID</code> and <code>CONFIG_CDCACM_PRODUCTSTR</code>: The product ID code/string. Default 0xa4a7 and "CDC/ACM Serial"
0xa4a7 was selected for compatibility with the Linux CDC ACM default PID.
</li>
<li>
<code>CONFIG_CDCACM_RXBUFSIZE</code> and <code>CONFIG_CDCACM_TXBUFSIZE</code>: Size of the serial receive/transmit buffers. Default 256.
</ul>
<h3>USB Storage Device Configuration</h3>
<ul>
<li>
<code>CONFIG_USBMSC</code>:
Enable compilation of the USB storage driver
</li>
<li>
<code>CONFIG_USBMSC_COMPOSITE</code>:
Configure the mass storage driver as part of a composite driver
(only if <code>CONFIG_USBDEV_COMPOSITE</code> is also defined)
</li>
<li>
<code>CONFIG_USBMSC_IFNOBASE</code>:
If the CDC driver is part of a composite device, then this may need to
be defined to offset the mass storage interface number so that it is
unique and contiguous. When used with the CDC/ACM driver, the
correct value for this offset is two (because of the two CDC/ACM
interfaces that will precede it).
</li>
<li>
<code>CONFIG_USBMSC_STRBASE</code>:
If the CDC driver is part of a composite device, then this may need to
be defined to offset the mass storage string numbers so that they are
unique and contiguous. When used with the CDC/ACM driver, the
correct value for this offset is four (or perhaps 5 or 6, depending
on if <code>CONFIG_CDCACM_NOTIFSTR</code> or <code>CONFIG_CDCACM_DATAIFSTR</code> are defined).
</li>
<li>
<code>CONFIG_USBMSC_EP0MAXPACKET</code>:
Max packet size for endpoint 0
</li>
<li>
<code>CONFIG_USBMSCEPBULKOUT</code> and <code>CONFIG_USBMSC_EPBULKIN</code>:
The logical 7-bit address of a hardware endpoints that support bulk OUT and IN operations
</li>
<li>
<code>CONFIG_USBMSC_NWRREQS</code> and <code>CONFIG_USBMSC_NRDREQS</code>:
The number of write/read requests that can be in flight
</li>
<li>
<code>CONFIG_USBMSC_BULKINREQLEN</code> and <code>CONFIG_USBMSC_BULKOUTREQLEN</code>:
The size of the buffer in each write/read request.
This value needs to be at least as large as the endpoint maxpacket and
ideally as large as a block device sector.
</li>
<li>
<code>CONFIG_USBMSC_VENDORID</code> and <code>CONFIG_USBMSC_VENDORSTR</code>:
The vendor ID code/string
</li>
<li>
<code>CONFIG_USBMSC_PRODUCTID</code> and <code>CONFIG_USBMSC_PRODUCTSTR</code>:
The product ID code/string
</li>
<li>
<code>CONFIG_USBMSC_REMOVABLE</code>:
Select if the media is removable
</li>
</ul>
<h3>USB Composite Device Configuration</h3>
<ul>
<li>
<code>CONFIG_USBDEV_COMPOSITE</code>:
Enables USB composite device support
</li>
<li>
<code>CONFIG_CDCACM_COMPOSITE</code>:
Configure the CDC serial driver as part of a composite driver
(only if CONFIG_USBDEV_COMPOSITE is also defined)
</li>
<li>
<code>CONFIG_UBMSC_COMPOSITE</code>:
Configure the mass storage driver as part of a composite driver
(only if CONFIG_USBDEV_COMPOSITE is also defined)
</li>
<li>
<code>CONFIG_COMPOSITE_IAD</code>:
If one of the members of the composite has multiple interfaces
(such as CDC/ACM), then an Interface Association Descriptor (IAD)
will be necessary. Default: IAD will be used automatically if
needed. It should not be necessary to set this.
</li>
<li>
<code>CONFIG_COMPOSITE_EP0MAXPACKET</code>:
Max packet size for endpoint 0
</li>
<li>
<code>CONFIG_COMPOSITE_VENDORID</code> and <code>CONFIG_COMPOSITE_VENDORSTR</code>:
The vendor ID code/string
</li>
<li>
<code>CONFIG_COMPOSITE_PRODUCTID</code> and <code>CONFIG_COMPOSITE_PRODUCTSTR</code>:
The product ID code/string
</li>
<li>
<code>CONFIG_COMPOSITE_SERIALSTR</code>:
Device serial number string
</li>
<li>
<code>CONFIG_COMPOSITE_CONFIGSTR</code>:
Configuration string
</li>
<li>
<code>CONFIG_COMPOSITE_VERSIONNO</code>:
Interface version number.
</li>
</ul>
<h2>USB Host-Side Support</h2>
<h3>USB Host Controller Driver</h3>
<ul>
<li>
<code>CONFIG_USBHOST</code>: Enables USB host support
</li>
<li>
<code>CONFIG_USBHOST_NPREALLOC</code>: Number of pre-allocated class instances
</li>
<li>
<code>CONFIG_USBHOST_BULK_DISABLE</code>: On some architectures, selecting this setting will reduce driver size by disabling bulk endpoint support
</li>
<li>
<code>CONFIG_USBHOST_INT_DISABLE</code>: On some architectures, selecting this setting will reduce driver size by disabling interrupt endpoint support
</li>
<li>
<code>CONFIG_USBHOST_ISOC_DISABLE</code>: On some architectures, selecting this setting will reduce driver size by disabling isochronous endpoint support
</li>
</ul>
<h3>USB Host HID Class Driver</h3>
<p>
Requires <code>CONFIG_USBHOST=y</code>, <code>CONFIG_USBHOST_INT_DISABLE=n</code>, <code>CONFIG_NFILE_DESCRIPTORS > 0</code>,
<code>CONFIG_SCHED_WORKQUEUE=y</code>, and <code>CONFIG_DISABLE_SIGNALS=n</code>.
</p>
<ul>
<li>
<code>CONFIG_HIDKBD_POLLUSEC</code>: Device poll rate in microseconds. Default: 100 milliseconds.
</li>
<li>
<code>CONFIG_HIDKBD_DEFPRIO</code>: Priority of the polling thread. Default: 50.
</li>
<li>
<code>CONFIG_HIDKBD_STACKSIZE</code>: Stack size for polling thread. Default: 1024
</li>
<li>
<code>CONFIG_HIDKBD_BUFSIZE</code>: Scancode buffer size. Default: 64.
</li>
<li>
<code>CONFIG_HIDKBD_NPOLLWAITERS</code>: If the poll() method is enabled, this defines the maximum number of threads that can be waiting for keyboard events. Default: 2.
</li>
<li>
<code>CONFIG_HIDKBD_RAWSCANCODES</code>: If set to <code>y</code> no conversion will be made on the raw keyboard scan codes. Default: ASCII conversion.
</li>
<li>
<code>CONFIG_HIDKBD_ALLSCANCODES</code>: If set to <code>y</code> all 231 possible scancodes will be converted to something. Default: 104 key US keyboard.
</li>
<li>
<code>CONFIG_HIDKBD_NODEBOUNCE</code>: If set to <code>y</code> normal debouncing is disabled. Default: Debounce/No repeat keys.
</li>
</ul>
<h3>USB Host HID Mass Storage Class Driver</h3>
<p>
Requires <code>CONFIG_USBHOST=y</code>, <code>CONFIG_USBHOST_BULK_DISABLE=n</code>, <code>CONFIG_NFILE_DESCRIPTORS > 0</code>,
and <code>CONFIG_SCHED_WORKQUEUE=y</code>.
</p>
<h2>Graphics related configuration settings</h3>
<li>
<code>CONFIG_NX</code>:
Enables overall support for graphics library and NX
</li>
</ul>
<h3>NX configuration setting</h3>
<ul>
<li>
<code>CONFIG_NX_MULTIUSER</code>:
Configures NX in multi-user mode.
</li>
<li>
<code>CONFIG_NX_NPLANES</code>:
Some YUV color formats requires support for multiple planes,
one for each color component. Unless you have such special
hardware, this value should be undefined or set to 1.
</li>
<li>
<code>CONFIG_NX_WRITEONLY</code>:
Define if the underlying graphics device does not support read operations.
Automatically defined if <code>CONFIG_NX_LCDDRIVER</code> and <code>CONFIG_LCD_NOGETRUN</code>
are defined.
</li>
<li>
<code>CONFIG_NX_DISABLE_1BPP</code>, <code>CONFIG_NX_DISABLE_2BPP</code>,
<code>CONFIG_NX_DISABLE_4BPP</code>, <code>CONFIG_NX_DISABLE_8BPP</code>
<code>CONFIG_NX_DISABLE_16BPP</code>, <code>CONFIG_NX_DISABLE_24BPP</code>, and
<code>CONFIG_NX_DISABLE_32BPP</code>:
NX supports a variety of pixel depths. You can save some
memory by disabling support for unused color depths.
</li>
<li>
<code>CONFIG_NX_PACKEDMSFIRST</code>:
If a pixel depth of less than 8-bits is used, then NX needs
to know if the pixels pack from the MS to LS or from LS to MS
</li>
<li>
<code>CONFIG_NX_LCDDRIVER</code>:
By default, NX builds to use a framebuffer driver (see <code>include/nuttx/fb.h</code>).
If this option is defined, NX will build to use an LCD driver (see <code>include/nuttx/lcd/lcd.h</code>).
</li>
<li>
<code>CONFIG_LCD_MAXPOWER</code>:
The full-on power setting for an LCD device.
</li>
<li>
<code>CONFIG_LCD_MAXCONTRAST</code>:
The maximum contrast value for an LCD device.
</li>
<li>
<code>CONFIG_LCD_LANDSCAPE</code>, <code>CONFIG_LCD_PORTRAIT</code>,
<code>CONFIG_LCD_RLANDSCAPE</code>, and <code>CONFIG_LCD_RPORTRAIT</code>:
Some LCD drivers may support these options to present the display in
landscape, portrait, reverse landscape, or reverse portrait orientations.
Check the <code>README.txt</code> file in each board configuration directory to
see if any of these are supported by the board LCD logic.
</li>
<li>
<code>CONFIG_LCD_NOGETRUN</code>:
NX components need to know if it can read from the LCD or not.
If reading from the LCD is supported, then NxConsole can do more efficient scrolling.
Default: Supported
</li>
<li>
<code>CONFIG_NX_MOUSE</code>:
Build in support for mouse input.
</li>
<li>
<code>CONFIG_NX_KBD</code>:
Build in support of keypad/keyboard input.
</li>
<li>
<code>CONFIG_NXTK_BORDERWIDTH</code>:
Specifies with with of the border (in pixels) used with
framed windows. The default is 4.
</li>
<li>
<code>CONFIG_NXTK_BORDERCOLOR1</code> and <code>CONFIG_NXTK_BORDERCOLOR2</code>:
Specify the colors of the border used with framed windows.
<code>CONFIG_NXTK_BORDERCOLOR2</code> is the shadow side color and so
is normally darker. The default is medium and dark grey,
respectively
</li>
<li>
<code>CONFIG_NXTK_AUTORAISE</code>:
If set, a window will be raised to the top if the mouse position
is over a visible portion of the window. Default: A mouse
button must be clicked over a visible portion of the window.
</li>
<li>
<code>CONFIG_NXFONTS_CHARBITS</code>:
The number of bits in the character set. Current options are
only 7 and 8. The default is 7.
</li>
<li>
<code>CONFIG_NXFONT_SANS17X22</code>:
This option enables support for a tiny, 17x22 san serif font
(font <code>ID FONTID_SANS17X22</code> == 14).
</li>
<li>
<code>CONFIG_NXFONT_SANS20X26</code>:
This option enables support for a tiny, 20x26 san serif font
(font <code>ID FONTID_SANS20X26</code> == 15).
</li>
<li>
<code>CONFIG_NXFONT_SANS23X27</code>:
This option enables support for a tiny, 23x27 san serif font
(font <code>ID FONTID_SANS23X27</code> == 1).
</li>
<li>
<code>CONFIG_NXFONT_SANS22X29</code>:
This option enables support for a small, 22x29 san serif font
(font <code>ID FONTID_SANS22X29</code> == 2).
</li>
<li>
<code>CONFIG_NXFONT_SANS28X37</code>:
This option enables support for a medium, 28x37 san serif font
(font <code>ID FONTID_SANS28X37</code> == 3).
</li>
<li>
<code>CONFIG_NXFONT_SANS39X48</code>:
This option enables support for a large, 39x48 san serif font
(font <code>ID FONTID_SANS39X48</code> == 4).
</li>
<li>
<code>CONFIG_NXFONT_SANS17X23B</code>:
This option enables support for a tiny, 17x23 san serif bold font
(font <code>ID FONTID_SANS17X23B</code> == 16).
</li>
<li>
<code>CONFIG_NXFONT_SANS20X27B</code>:
This option enables support for a tiny, 20x27 san serif bold font
(font <code>ID FONTID_SANS20X27B</code> == 17).
</li>
<li>
<code>CONFIG_NXFONT_SANS22X29B</code>:
This option enables support for a small, 22x29 san serif bold font
(font ID <code>FONTID_SANS22X29B</code> == 5).
</li>
<li>
<code>CONFIG_NXFONT_SANS28X37B</code>:
This option enables support for a medium, 28x37 san serif bold font
(font ID <code>FONTID_SANS28X37B</code> == 6).
</li>
<li>
<code>CONFIG_NXFONT_SANS40X49B</code>:
This option enables support for a large, 40x49 san serif bold font
(font ID <code>FONTID_SANS40X49B</code> == 7).
</li>
<li>
<code>CONFIG_NXFONT_SERIF22X29</code>:
This option enables support for a small, 22x29 font (with serifs)
(font ID <code>FONTID_SERIF22X29</code> == 8).
</li>
<li>
<code>CONFIG_NXFONT_SERIF29X37</code>:
This option enables support for a medium, 29x37 font (with serifs)
(font ID <code>FONTID_SERIF29X37</code> == 9).
</li>
<li>
<code>CONFIG_NXFONT_SERIF38X48</code>:
This option enables support for a large, 38x48 font (with serifs)
(font ID <code>FONTID_SERIF38X48</code> == 10).
</li>
<li>
<code>CONFIG_NXFONT_SERIF22X28B</code>:
This option enables support for a small, 27x38 bold font (with serifs)
(font ID <code>FONTID_SERIF22X28B</code> == 11).
</li>
<li>
<code>CONFIG_NXFONT_SERIF27X38B</code>:
This option enables support for a medium, 27x38 bold font (with serifs)
(font ID <code>FONTID_SERIF27X38B</code> == 12).
</li>
<li>
<code>CONFIG_NXFONT_SERIF38X49B</code>:
This option enables support for a large, 38x49 bold font (with serifs)
(font ID <code>FONTID_SERIF38X49B</code> == 13).
</li>
</ul>
<h3>NX Multi-user only options</h3>
<ul>
<li>
<code>CONFIG_NX_BLOCKING</code>
Open the client message queues in blocking mode. In this case,
<code>nx_eventhandler()</code> will not return until a message is received and processed.
</li>
<li>
<code>CONFIG_NX_MXSERVERMSGS</code> and <code>CONFIG_NX_MXCLIENTMSGS</code>
Specifies the maximum number of messages that can fit in
the message queues. No additional resources are allocated, but
this can be set to prevent flooding of the client or server with
too many messages (<code>CONFIG_PREALLOC_MQ_MSGS</code> controls how many
messages are pre-allocated).
</li>
</ul>
<h2>Stack and heap information</h2>
<ul>
<li>
<code>CONFIG_BOOT_RUNFROMFLASH</code>: Some configurations support XIP
operation from FLASH but must copy initialized .data sections to RAM.
</li>
<li>
<code>CONFIG_BOOT_COPYTORAM</code>: Some configurations boot in FLASH
but copy themselves entirely into RAM for better performance.
</li>
<li>
<code>CONFIG_BOOT_RAMFUNCS</code>: Other configurations may copy just
some functions into RAM, either for better performance or for errata workarounds.
</li>
<li>
<code>CONFIG_STACK_ALIGNMENT</code>: Set if the your application has specific
stack alignment requirements (may not be supported in all architectures).
</li>
<li>
<code>CONFIG_IDLETHREAD_STACKSIZE</code>: The size of the initial stack.
This is the thread that (1) performs the initial boot of the system up
to the point where <code>CONFIG_USER_ENTRYPOINT</code>() is spawned,
and (2) there after is the IDLE thread that executes only when there
is no other thread ready to run.
</li>
<li>
<code>CONFIG_USERMAIN_STACKSIZE</code>: The size of the stack to allocate
for the main user thread that begins at the <code>CONFIG_USER_ENTRYPOINT</code>()
entry point.
</li>
<li>
<code>CONFIG_PTHREAD_STACK_MIN</code>: Minimum pthread stack size
</li>
<li>
<code>CONFIG_PTHREAD_STACK_DEFAULT</code>: Default pthread stack size
</li>
</ul>
<table width ="100%">
<tr bgcolor="#e4e4e4">
<td>
<h1><a name="apndxtrademarks">Appendix B: Trademarks</a></h1>
</td>
</tr>
</table>
<li>ARM, ARM7 ARM7TDMI, ARM9, ARM920T, ARM926EJS, Cortex-M3 are trademarks of Advanced RISC Machines, Limited.</li>
<li>Cygwin is a trademark of Red Hat, Incorporated.</li>
<li>Linux is a registered trademark of Linus Torvalds.</li>
<li>Eagle-100 is a trademark of <a href=" http://www.micromint.com/">Micromint USA, LLC</a>.
<li>LPC2148 is a trademark of NXP Semiconductors.</li>
<li>TI is a trade name of Texas Instruments Incorporated.</li>
<li>UNIX is a registered trademark of The Open Group.</li>
<li>VxWorks is a registered trademark of Wind River Systems, Incorporated.</li>
<li>ZDS, ZNEO, Z16F, Z80, and Zilog are a registered trademark of Zilog, Inc.</li>
<p>
NOTE: NuttX is <i>not</i> licensed to use the POSIX trademark. NuttX uses the POSIX
standard as a development guideline only.
</p>
</body>
</html>
|
wagtail/documents/templates/wagtaildocs/multiple/edit_form.html | FlipperPA/wagtail | {% load i18n %}
{% include "wagtailadmin/shared/non_field_errors.html" %}
<form action="{% url 'wagtaildocs:edit_multiple' doc.id %}" method="POST" enctype="multipart/form-data" novalidate>
<ul class="fields">
{% csrf_token %}
{% for field in form %}
{% if field.is_hidden %}
{{ field }}
{% else %}
{% include "wagtailadmin/shared/field_as_li.html" %}
{% endif %}
{% endfor %}
<li>
<input type="submit" value="{% trans 'Update' %}" class="button" />
<a href="{% url 'wagtaildocs:delete_multiple' doc.id %}" class="delete button button-secondary no">{% trans "Delete" %}</a>
</li>
</ul>
</form>
|
measurer/hotspot-measurer/jdk1.6.0_45/db/docs/html/devguide/cdevstandards806118.html | armoredsoftware/protocol | <!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
<meta name="copyright" content="(C) Copyright 2005" />
<meta name="DC.rights.owner" content="(C) Copyright 2005" />
<meta content="public" name="security" />
<meta content="index,follow" name="Robots" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta content="concept" name="DC.Type" />
<meta name="DC.Title" content="Derby and standards" />
<meta name="abstract" content="Derby adheres to SQL99 or newer standards wherever possible. This section describes those features currently in Derby that are not standard; these features are currently being evaluated and might be removed in future releases." />
<meta name="description" content="Derby adheres to SQL99 or newer standards wherever possible. This section describes those features currently in Derby that are not standard; these features are currently being evaluated and might be removed in future releases." />
<meta content="SQL99 standards, and Derby, data types, CLOB, data types, BLOB" name="DC.subject" />
<meta content="SQL99 standards, and Derby, data types, CLOB, data types, BLOB" name="keywords" />
<meta scheme="URI" name="DC.Relation" content="cdevstandardsxml.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="cdevstandards806118" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
<link href="commonltr.css" type="text/css" rel="stylesheet" />
<title>Derby and standards</title>
</head>
<body id="cdevstandards806118"><a name="cdevstandards806118"><!-- --></a>
<h1 class="topictitle1">Derby and standards</h1>
<div><p><span>Derby</span> adheres
to SQL99 or newer standards wherever possible. This section describes those
features currently in <span>Derby</span> that
are not standard; these features are currently being evaluated and might be
removed in future releases.</p>
<p>This section describes those parts of <span>Derby</span> that
are non-standard or not typical for a database system.</p>
<dl>
<dt class="dlterm">ALTER TABLE syntax</dt>
<dd><span>Derby</span> uses a
slightly different ALTER TABLE syntax for altering column defaults. While
SQL99 uses DROP and SET, <span>Derby</span>
uses DEFAULT.</dd>
<dt class="dlterm">Calling functions and procedures</dt>
<dd><span>Derby</span> supports
the CALL (procedure) statement for calling external procedures declared by
the CREATE PROCEDURE statement. Built-in functions and user-defined functions
declared with the CREATE FUNCTION command can be called as part of an SQL
select statement or by using either a VALUES clause or VALUES expression.</dd>
<dt class="dlterm">CLOB and BLOB data types</dt>
<dd><span>Derby</span> supports the
standard CLOB and BLOB data types. BLOB and CLOB values are limited to a
maximum of 2,147,483,647 characters.</dd>
<dt class="dlterm">Cursors</dt>
<dd><span>Derby</span> uses JDBC's result
sets, and does not provide SQL for manipulating cursors except for positioned
update and delete. <span>Derby</span>'s
scrollable insensitive cursors are provided through JDBC, not through SQL
commands.</dd>
<dt class="dlterm">DECIMAL max precision</dt>
<dd>For <span>Derby</span>, the maximum
precision for DECIMAL columns is 31 digits. SQL99 does not require a specific
maximum precision for decimals, but most products have a maximum precision of
15-32 digits.</dd>
<dt class="dlterm">Dynamic SQL</dt>
<dd><span>Derby</span> uses JDBC's
Prepared Statement, and does not provide SQL commands for dynamic SQL.</dd>
<dt class="dlterm">Expressions on LONGs</dt>
<dd><span>Derby</span> permits
expressions on LONG VARCHAR; however, LONG VARCHAR data types are not allowed
in the following clauses, operations, constraints, functions, and predicates:
<ul>
<li>GROUP BY clauses</li>
<li>ORDER BY clauses</li>
<li>JOIN operations</li>
<li>PRIMARY KEY constraints</li>
<li>Foreign KEY constraints</li>
<li>UNIQUE key constraints</li>
<li>MIN aggregate function</li>
<li>MAX aggregate function</li>
<li>[NOT] IN predicate</li>
<li>UNION, INTERSECT, and EXCEPT operators</li>
</ul>
SQL99 also places some restrictions on expressions on LONG types.
</dd>
<dt class="dlterm">Information schema</dt>
<dd><span>Derby</span> uses its own system
catalog that can be accessed using standard JDBC DatabaseMetadata calls.
<span>Derby</span> does not provide the
standard Information Schema views.</dd>
<dt class="dlterm">NOT NULL characteristic</dt>
<dd>The SQL standard says NOT NULL is a constraint, and can be named and viewed
in the information schema as such.
<span>Derby</span> does not provide naming
for NOT NULL, nor does it present it as a constraint in the information schema,
only as a characteristic of the column.</dd>
<dt class="dlterm">Stored routines and PSM</dt>
<dd><span>Derby</span> supports external
procedures using the Java programming language. Procedures are managed using the
CREATE PROCEDURE and DROP PROCEDURE statements.</dd>
<dt class="dlterm">Transactions</dt>
<dd>All operations in <span>Derby</span>
are transactional. <span>Derby</span>
supports transaction control using JDBC Connection methods. This includes
support for savepoints and for the four JDBC transaction isolation levels. The
only SQL command provided for transaction control is SET TRANSACTION ISOLATION.
</dd>
</dl>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="cdevstandardsxml.html">XML data types and operators</a></strong><br />
Derby supports the XML data type and a set of operators that work with the XML data type, but does not provide JDBC support for the XML data type. The XML data type and operators are based on a small subset of the SQL/XML specification.</li>
</ul>
</div>
</body>
</html> |
tollbackend/web/js/angular-1.5.5/docs/partials/error/$parse/isecfn.html | mudunuriRaju/tlr-live | <a href='https://github.com/angular/angular.js/edit/v1.5.x/docs/content/error/$parse/isecfn.ngdoc?message=docs(error%2Fisecfn)%3A%20describe%20your%20change...'
class='improve-docs btn btn-primary'><i class="glyphicon glyphicon-edit"> </i>Improve this Doc</a>
<h1>Error: $parse:isecfn
<div><span class='hint'>Referencing Function Disallowed</span></div>
</h1>
<div>
<pre class="minerr-errmsg"
error-display="Referencing Function in Angular expressions is disallowed! Expression: {0}">Referencing Function in Angular expressions is disallowed! Expression: {0}</pre>
</div>
<h2>Description</h2>
<div class="description">
<p>Occurs when an expression attempts to access the 'Function' object (constructor for all functions in
JavaScript).</p>
<p>Angular bans access to Function from within expressions since constructor access is a known way to execute
arbitrary Javascript code.</p>
<p>To resolve this error, avoid Function access.</p>
</div>
|
Source/Testing/HtmlRenderer.ExperimentalApp/Data/Files/youtube to mp3/8DD6DB608EE4ECA33516EB0FE4622294.html | todor-dk/HTML-Renderer | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="description" content="WonTube provides free service to let you search your favorite YouTube Video, and download YouTube, or convert YouTube to MP3. You may also search and download free MP3 files." />
<title>WonTube- Download YouTube Video and Convert YouTube to MP3, Search and Download MP3</title>
<link href="style/global.css" rel="stylesheet" type="text/css" />
<link href="style/about.css" rel="stylesheet" type="text/css" />
<script type="text/javascript" src="//ajax.googleapis.com/ajax/libs/jquery/1.8.0/jquery.min.js"></script>
<script type="text/javascript" src="js/social/ga.js"></script>
<script type="text/javascript">
$(function(){
var ref = document.referrer;
var index = ref.indexOf("/world/");
if(index > 0){
$("#w1_div, #f1_div").hide();
$("#w2_div, #f2_div").show();
}
});
</script>
</head>
<body><!-- #BeginLibraryItem "/static/library/header.lbi" -->
<div id="header">
<div id="w1_div">
<h1 id="logo"><a href="http://www.wontube.com" title="Home">WonTube<span></span></a></h1>
<ul id="nav">
<li><a href="http://www.wontube.com/movie/">Movies</a></li>
<li><a href="http://www.wontube.com/tv/">TV</a></li>
<li><a href="http://www.wontube.com/music/">Music</a></li>
<li><a href="http://www.wontube.com/featured/">Featured</a></li>
</ul>
</div>
<div id="w2_div" style="display:none">
<h1 id="logo"><a href="http://www.wontube.com/world/" title="Home">WonTube<span></span></a></h1>
<ul id="nav">
<li><a href="http://www.wontube.com/world/movie/">Movies</a></li>
<li><a href="http://www.wontube.com/world/anime/">Anime</a></li>
<li><a href="http://www.wontube.com/world/music/">Music</a></li>
<li><a href="http://www.wontube.com/world/featured/">Featured</a></li>
</ul>
</div>
</div>
<!-- #EndLibraryItem --><!--header end-->
<div id="main2">
<div class="content-wrap w-artical">
<h1>Free YouTube Downloader for Android</h1>
<div class="block-content android">
<p>Forget about annoying issues like connectivity, coverage related,
data streaming or low Internet speed from now on. Download
YouTube videos to view offline anywhere.</p>
<p><div class="btn"><a href="http://download.wontube.com/wontube-free-youtube-downloader-android.apk" onClick="_gaq.push(['_trackEvent', 'YTD Android', 'Download', document.location.pathname]);"><img src="images/tools/btn_andriod.png" width="168" height="52" alt="Free YouTube Downloader for Android" /></a>
<div class="plusbtn">
<div id="fb-root"></div>
<script>(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) return;
js = d.createElement(s); js.id = id;
js.src = "//connect.facebook.net/en_GB/all.js#xfbml=1";
fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));</script>
<div class="fb-like" style="float:left;" data-href="http://www.facebook.com/wontube" data-send="false" data-layout="button_count" data-width="95" data-show-faces="false"></div>
<!-- AddThis Button BEGIN -->
<div class="addthis_toolbox addthis_default_style " style="float:left; width:300px;"> <a class="addthis_button_tweet"></a> <a class="addthis_button_google_plusone" g:plusone:size="medium"></a> </div>
<script type="text/javascript" src="http://s7.addthis.com/js/250/addthis_widget.js#pubid=xa-4f0e74ae40eeca21"></script>
<!-- AddThis Button END -->
</div>
</div></p>
<div class="clear"></div>
</div>
<div class="left">
<div class="block-content">
<div class="float-right-img"><img src="images/tools/Free_androd.png" width="257" height="170" alt="Free YouTube Download" /></div>
<h3>Free for 100% Sure </h3>
<p>Free YouTube Downloader for Android users. It is 100% reliable and of course Free. Just have a try now. </p>
<div class="clear"></div>
</div>
<div class="block-content">
<div class="float-left-img"><img src="images/tools/Free_androd.png" width="257" height="170" alt="Free YouTube Download" /></div>
<h3>Download YouTube Video</h3>
<p>The best way to watch YouTube Video is to download it. With this simple and trouble-free application, never mind about buffering issues and your favorite video is deleted by the author.</p>
<div class="clear"></div>
</div>
</div>
<div class="right social_">
<div class="block-content social_">
<div class="social">
<div class="social_top"></div>
<div class="social">
<div class="social_top"></div>
<div class="social_tit">
<h3>Social Connection</h3>
</div>
<div class="social_bg"></div>
<div class="social_cont">
<div id="fb-root2"></div>
<script>(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) return;
js = d.createElement(s); js.id = id;
js.src = "//connect.facebook.net/en_US/all.js#xfbml=1";
fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));</script>
<div class="fb-like-box" data-href="http://www.facebook.com/WonTube" data-width="217" data-show-faces="true" data-border-color="#FFFFFF" data-stream="false" data-header="false"></div>
<p style="padding:10px 0px;"><a class="addthis_button_twitter_follow_native" tf:screen_name="WonTube"></a></p>
<p class="google" style="padding-top:15px;"></p>
<div style="float:left; line-height:40px;">Circle us on Google+: </div>
<div style=" float:left; padding:5px 0px;"><a href="https://plus.google.com/109284886880937561295" style="text-decoration: none;"><img src="https://ssl.gstatic.com/images/icons/gplus-32.png" width="32" height="32" style="border: 0;"/></a></div>
<p></p>
<div class="clear"></div>
<!-- AddThis Button BEGIN -->
<div class="addthis_toolbox addthis_default_style " style="padding-top:10px;"> <a class="addthis_button_google_plusone" g:plusone:size="Medium"></a> <a class="addthis_counter addthis_pill_style"></a></div>
<script type="text/javascript" src="http://s7.addthis.com/js/250/addthis_widget.js#pubid=ra-4edc321f02b434d3"></script>
<!-- AddThis Button END -->
</div>
<div class="social_btm"></div>
</div>
</div>
</div>
</div>
<div class="clear"></div>
</div>
</div>
<!--main end--><!-- #BeginLibraryItem "/static/library/footer.lbi" -->
<div class="clear"></div>
<div id="footer">
<div id="footer_copy">
<div id="f1_div"><a href="http://www.wontube.com/about">About Us</a> | <a href="http://www.wontube.com/tools">Tools</a> | </a><a href="http://www.wontube.com/blog">Blog</a> | <a href="http://www.wontube.com/term">Terms of Service</a> | <a href="http://www.wontube.com/feedback">Feedback</a> | <a href="http://www.wontube.com/sitemap">Sitemap</a> <span>WonTube Studio. © 2012</span></div>
<div id="f2_div" style="display:none"><a href="http://www.wontube.com/world/about">About Us</a> | <a href="http://www.wontube.com/world/tools">Tools</a> | <a href="http://www.wontube.com/world/term/">Terms of Service</a> | <a href="http://www.wontube.com/world/feedback/">Feedback</a> | <a href="http://www.wontube.com/world/sitemap/">Sitemap</a> <span>WonTube Studio. © 2012</span>
</div>
</div>
</div><!-- #EndLibraryItem --><!--footer end-->
</body>
</html>
|
README.html | gitpan/Debug-Fork-Tmux | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>
Debug::Fork::Tmux
</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body class='pod'>
<!--
If you want to change this HTML document, you probably shouldn't do that
by changing it directly. Instead, see about changing the calling options
to Pod::Simple::HTML, and/or subclassing Pod::Simple::HTML,
then reconverting this document from the Pod source.
When in doubt, email the author of Pod::Simple::HTML for advice.
See 'perldoc Pod::Simple::HTML' for more info.
-->
<!-- start doc -->
<a name='___top' class='dummyTopAnchor'></a>
<h1>
Debug::Fork::Tmux
</h1>
<p>
Makes fork() in debugger to open a new Tmux window
</p>
<div class='indexgroup'>
<ul class='indexList indexList1'>
<li class='indexItem indexItem1'>
<a href='#NAME'>NAME</a>
</li>
<li class='indexItem indexItem1'>
<a href='#VERSION'>VERSION</a>
</li>
<li class='indexItem indexItem1'>
<a href='#SYNOPSIS'>SYNOPSIS</a>
</li>
<li class='indexItem indexItem1'>
<a href='#DESCRIPTION'>DESCRIPTION</a>
</li>
<li class='indexItem indexItem1'>
<a href='#SUBROUTINES%2FMETHODS'>SUBROUTINES/METHODS</a>
<ul class='indexList indexList2'>
<li class='indexItem indexItem2'>
<a href='#PUBLIC'>PUBLIC</a>
<ul class='indexList indexList3'>
<li class='indexItem indexItem3'>
<a href='#DB%3A%3Aget_fork_TTY()'>DB::get_fork_TTY()</a>
</li>
</ul>
</li>
<li class='indexItem indexItem2'>
<a href='#PRIVATE'>PRIVATE</a>
<ul class='indexList indexList3'>
<li class='indexItem indexItem3'>
<a href='#_spawn_tty()'>_spawn_tty()</a>
</li>
<li class='indexItem indexItem3'>
<a href='#_tmux_new_window()'>_tmux_new_window()</a>
</li>
<li class='indexItem indexItem3'>
<a href=
'#_tmux_window_tty(_%24window_id_)'>_tmux_window_tty(
$window_id )</a>
</li>
<li class='indexItem indexItem3'>
<a href=
'#_read_from_cmd(_%24cmd_%3D%3E_%40args_)'>_read_from_cmd(
$cmd => @args )</a>
</li>
<li class='indexItem indexItem3'>
<a href=
'#_croak_on_cmd(_%24cmd_%3D%3E_%40args%2C_%24happen_)'>_croak_on_cmd(
$cmd => @args, $happen )</a>
</li>
</ul>
</li>
</ul>
</li>
<li class='indexItem indexItem1'>
<a href='#CONFIGURATION_AND_ENVIRONMENT'>CONFIGURATION AND
ENVIRONMENT</a>
<ul class='indexList indexList2'>
<li class='indexItem indexItem2'>
<a href='#DFTMUX_FQFN'>DFTMUX_FQFN</a>
</li>
<li class='indexItem indexItem2'>
<a href='#DFTMUX_CMD_NEWW'>DFTMUX_CMD_NEWW</a>
</li>
<li class='indexItem indexItem2'>
<a href='#DFTMUX_CMD_NEWW_EXEC'>DFTMUX_CMD_NEWW_EXEC</a>
</li>
<li class='indexItem indexItem2'>
<a href='#DFTMUX_CMD_TTY'>DFTMUX_CMD_TTY</a>
</li>
<li class='indexItem indexItem2'>
<a href=
'#Earlier_versions%27_SPUNGE_*_environment_variables'>Earlier
versions' SPUNGE_* environment variables</a>
</li>
<li class='indexItem indexItem2'>
<a href='#Attaching_to_the_other_Tmux_session'>Attaching to
the other Tmux session</a>
</li>
</ul>
</li>
<li class='indexItem indexItem1'>
<a href='#DIAGNOSTICS'>DIAGNOSTICS</a>
</li>
<li class='indexItem indexItem1'>
<a href='#DEPENDENCIES'>DEPENDENCIES</a>
</li>
<li class='indexItem indexItem1'>
<a href='#BUGS_AND_LIMITATIONS'>BUGS AND LIMITATIONS</a>
</li>
<li class='indexItem indexItem1'>
<a href='#WEB_SITE'>WEB SITE</a>
</li>
<li class='indexItem indexItem1'>
<a href='#SUPPORT'>SUPPORT</a>
<ul class='indexList indexList2'>
<li class='indexItem indexItem2'>
<a href='#Perldoc'>Perldoc</a>
</li>
<li class='indexItem indexItem2'>
<a href='#Websites'>Websites</a>
</li>
<li class='indexItem indexItem2'>
<a href='#Email'>Email</a>
</li>
<li class='indexItem indexItem2'>
<a href='#Bugs_%2F_Feature_Requests'>Bugs / Feature
Requests</a>
</li>
<li class='indexItem indexItem2'>
<a href='#Source_Code'>Source Code</a>
</li>
</ul>
</li>
<li class='indexItem indexItem1'>
<a href='#AUTHOR'>AUTHOR</a>
</li>
<li class='indexItem indexItem1'>
<a href='#COPYRIGHT_AND_LICENSE'>COPYRIGHT AND LICENSE</a>
</li>
<li class='indexItem indexItem1'>
<a href='#SEE_ALSO'>SEE ALSO</a>
</li>
<li class='indexItem indexItem1'>
<a href='#DISCLAIMER_OF_WARRANTY'>DISCLAIMER OF WARRANTY</a>
</li>
</ul>
</div>
<h2>
<a class='u' href='#___top' title='click to go to top of document'
name="VERSION" id="VERSION">VERSION</a>
</h2>
<p>
This documentation refers to the module contained in the distribution
<code>Debug-Fork-Tmux</code> version 1.000012.
</p>
<h2>
<a class='u' href='#___top' title='click to go to top of document'
name="SYNOPSIS" id="SYNOPSIS">SYNOPSIS</a>
</h2>
<pre>
#!/usr/bin/perl -d
#
# ABSTRACT: Debug the fork()-contained code in this file
#
## Works only under Tmux: http://tmux.sf.net
#
# Make fork()s debuggable with Tmux
use Debug::Fork::Tmux;
# See what happens in your debugger then...
fork;
</pre>
<h2>
<a class='u' href='#___top' title='click to go to top of document'
name="DESCRIPTION" id="DESCRIPTION">DESCRIPTION</a>
</h2>
<p>
Make sure you have the running <code>Tmux</code> window manager:
</p>
<pre>
$ tmux
</pre>
<ul>
<li>Only <code>Tmux</code> version 1.6 and higher works with
<code>Debug::Fork::Tmux</code>. See <a href="#DEPENDENCIES" class=
"podlinkpod">"DEPENDENCIES"</a>.
</li>
<li>It is not necessary to run this under <code>Tmux</code>, see
<a href="#Attaching_to_the_other_Tmux_session" class=
"podlinkpod">"Attaching to the other <code>Tmux</code> session"</a>.
</li>
</ul>
<p>
Then the real usage example of this module is:
</p>
<pre>
$ perl -MDebug::Fork::Tmux -d your_script.pl
</pre>
<p>
As Perl's standard debugger requires additional code to be written
and used when the debugged Perl program use the <a href=
"http://search.cpan.org/perldoc?perlfunc#fork" class=
"podlinkpod">fork()</a> built-in.
</p>
<p>
This module is about to solve the trouble which is used to be
observed like this:
</p>
<pre>
######### Forked, but do not know how to create a new TTY. #########
Since two debuggers fight for the same TTY, input is severely entangled.
I know how to switch the output to a different window in xterms, OS/2
consoles, and Mac OS X Terminal.app only. For a manual switch, put the
name of the created TTY in $DB::fork_TTY, or define a function
DB::get_fork_TTY() returning this.
On UNIX-like systems one can get the name of a TTY for the given window
by typing tty, and disconnect the shell from TTY by sleep 1000000.
</pre>
<p>
All of that is about getting the pseudo-terminal device for another
part of user interface. This is probably why only the
<code>GUI</code>s are mentioned here: <code>OS/2</code> 'Command
Prompt', <code>Mac OS X</code>'s <code>Terminal.app</code> and an
<code>xterm</code>. For those of you who develop server-side stuff it
should be known that keeping <code>GUI</code> on the server is far
from always to be available as an option no matter if it's a
production or a development environment.
</p>
<p>
The most ridiculous for every <code>TUI</code> (the <code>ssh</code>
particularly) user is that the pseudo-terminal device isn't that much
about <code>GUI</code>s by its nature so the problem behind the bars
of the <a href="http://search.cpan.org/perldoc?perl5db.pl" class=
"podlinkpod">perl5db.pl</a> report (see more detailed problem
description at the <a href="http://perlmonks.org/?node_id=128283"
class="podlinkurl">PerlMonks thread</a>) is the consoles management.
It's a kind of a tricky, for example, to start the next
<code>ssh</code> session initiated from the machine serving as an
<code>sshd</code> server for the existing session.
</p>
<p>
Thus we kind of have to give a chance to the consoles management with
a software capable to run on a server machine without as much
dependencies as an <code>xterm</code>. This module is a try to pick
the <a href="http://tmux.sf.net" class="podlinkurl">Tmux</a> windows
manager for such a task.
</p>
<p>
Because of highly-developed scripting capabilities of
<code>Tmux</code> any user can supply the 'window' or a 'pane' to
Perl's debugger making it suitable to debug the separate process in a
different <code>UI</code> instance. Also this adds the features like
<code>groupware</code>: imagine that your mate can debug the process
you've just <code>fork()ed</code> by mean of attaching the same
<code>tmux</code> you are running on a server. While you keep working
on a process that called a <code>fork()</code>.
</p>
<h2>
<a class='u' href='#___top' title='click to go to top of document'
name="SUBROUTINES/METHODS">SUBROUTINES/METHODS</a>
</h2>
<p>
All of the following are functions:
</p>
<h3>
<a class='u' href='#___top' title='click to go to top of document'
name="PUBLIC" id="PUBLIC">PUBLIC</a>
</h3>
<h4>
<a class='u' href='#___top' title='click to go to top of document'
name="DB::get_fork_TTY()"><code>DB::get_fork_TTY()</code></a>
</h4>
<p>
Finds new <code>TTY</code> for the <code>fork()</code>ed process.
</p>
<p>
Takes no arguments. Returns <code>Str</code> name of the
<code>tty</code> device of the <tmux>'s new window created for
the debugger's new process.
</p>
<p>
Sets the <code>$DB::fork_TTY</code> to the same <code>Str</code>
value.
</p>
<h3>
<a class='u' href='#___top' title='click to go to top of document'
name="PRIVATE" id="PRIVATE">PRIVATE</a>
</h3>
<h4>
<a class='u' href='#___top' title='click to go to top of document'
name="_spawn_tty()"><code>_spawn_tty()</code></a>
</h4>
<p>
Creates a <code>TTY</code> device and returns <code>Str</code> its
name.
</p>
<h4>
<a class='u' href='#___top' title='click to go to top of document'
name="_tmux_new_window()"><code>_tmux_new_window()</code></a>
</h4>
<p>
Creates a given <code>tmux</code> window and returns <code>Str</code>
its id/number.
</p>
<h4>
<a class='u' href='#___top' title='click to go to top of document'
name="_tmux_window_tty(_$window_id_)"><code>_tmux_window_tty(
$window_id )</code></a>
</h4>
<p>
Finds a given <code>tmux</code> window's tty name and returns its
<code>Str</code> name based on a given window id/number typically
from <a href="#_tmux_new_window()" class=
"podlinkpod">"_tmux_new_window()"</a>.
</p>
<h4>
<a class='u' href='#___top' title='click to go to top of document'
name="_read_from_cmd(_$cmd_=>_@args_)"><code>_read_from_cmd( $cmd
=> @args )</code></a>
</h4>
<p>
Takes the list containing the <code>Str</code> <a href=
"http://search.cpan.org/perldoc?perlfunc#system" class=
"podlinkpod">system()</a> command and <code>Array</code> its
arguments and executes it. Reads <code>Str</code> the output and
returns it. Throws if no output or if the command failed.
</p>
<h4>
<a class='u' href='#___top' title='click to go to top of document'
name=
"_croak_on_cmd(_$cmd_=>_@args,_$happen_)"><code>_croak_on_cmd(
$cmd => @args, $happen )</code></a>
</h4>
<p>
Takes the <code>Str</code> command, <code>Array</code> its arguments
and <code>Str</code> the reason of its failure, examines the
<code>$?</code> and dies with explanation on the <a href=
"http://search.cpan.org/perldoc?perlfunc#system" class=
"podlinkpod">system()</a> command failure.
</p>
<h2>
<a class='u' href='#___top' title='click to go to top of document'
name="CONFIGURATION_AND_ENVIRONMENT" id=
"CONFIGURATION_AND_ENVIRONMENT">CONFIGURATION AND ENVIRONMENT</a>
</h2>
<p>
The module requires the <a href="http://tmux.sf.net" class=
"podlinkurl">Tmux</a> window manager for the console to be present in
the system.
</p>
<p>
This means that it requires the <code>Unix</code>-like operating
system not only to have a <a href=
"http://search.cpan.org/perldoc?fork" class="podlinkpod">fork</a>
implemented and a <code>TTY</code> device name supplement but the
system should have Tmux up and running.
</p>
<p>
Therefore <code>Cygwin</code> for example isn't in at this moment,
see the <a href=
"http://permalink.gmane.org/gmane.comp.terminal-emulators.tmux.user/1354"
class="podlinkurl">explanation</a> why.
</p>
<p>
Configuration is made via environment variables, the default is taken
for each of them with no such variable is set in the environment:
</p>
<h3>
<a class='u' href='#___top' title='click to go to top of document'
name="DFTMUX_FQFN" id="DFTMUX_FQFN"><code>DFTMUX_FQFN</code></a>
</h3>
<p>
The <code>tmux</code> binary name with the full path.
</p>
<p>
Default : The first of those for executable to exist:
</p>
<dl>
<dt>
<a name="PATH_environment_variable_contents" id=
"PATH_environment_variable_contents"><code>PATH</code> environment
variable contents</a>
</dt>
<dt>
<a name="Path_to_the_Perl_binary_interpreter" id=
"Path_to_the_Perl_binary_interpreter">Path to the Perl binary
interpreter</a>
</dt>
<dt>
<a name="Current_directory" id="Current_directory">Current
directory</a>
</dt>
</dl>
<p>
and just the <code>tmux</code> as a fallback if none of above is the
location of the <code>tmux</code> executable file.
</p>
<h3>
<a class='u' href='#___top' title='click to go to top of document'
name="DFTMUX_CMD_NEWW" id=
"DFTMUX_CMD_NEWW"><code>DFTMUX_CMD_NEWW</code></a>
</h3>
<p>
The <a href="http://search.cpan.org/perldoc?perlfunc#system" class=
"podlinkpod">system()</a> arguments for a <code>tmux</code> command
for opening a new window and with output of a window address from
<code>tmux</code>. String is sliced by spaces to be a list of
parameters.
</p>
<p>
Default : <code>neww -P</code>
</p>
<h3>
<a class='u' href='#___top' title='click to go to top of document'
name="DFTMUX_CMD_NEWW_EXEC" id=
"DFTMUX_CMD_NEWW_EXEC"><code>DFTMUX_CMD_NEWW_EXEC</code></a>
</h3>
<p>
The <a href="http://search.cpan.org/perldoc?perlfunc#system" class=
"podlinkpod">system()</a> or a shell command to be given to the
<code>DFTMUX_CMD_NEWW</code> command to be executed in a brand new
created window. It should wait unexpectedly and do nothing till the
debugger catches the device and puts in into the proper use.
</p>
<p>
Default : <code>sleep 1000000</code>
</p>
<h3>
<a class='u' href='#___top' title='click to go to top of document'
name="DFTMUX_CMD_TTY" id=
"DFTMUX_CMD_TTY"><code>DFTMUX_CMD_TTY</code></a>
</h3>
<p>
Command- line parameter(s) for a <code>tmux</code> command to find a
<code>tty</code> name in the output. The string is sliced then by
spaces. The <code>tmux</code>'s window address is added then as the
very last argument.
</p>
<p>
Default : <code>lsp -F #{pane_tty} -t</code>
</p>
<h3>
<a class='u' href='#___top' title='click to go to top of document'
name="Earlier_versions'_SPUNGE_*_environment_variables">Earlier
versions' <code>SPUNGE_*</code> environment variables</a>
</h3>
<p>
Till v1.000009 the module was controlled by the environment variables
like <code>SPUNGE_TMUX_FQDN</code>. Those are deprecated and should
be replaced in your configuration(s) onto the
<code>DFTMUX_</code>-prefixed ones.
</p>
<h3>
<a class='u' href='#___top' title='click to go to top of document'
name="Attaching_to_the_other_Tmux_session" id=
"Attaching_to_the_other_Tmux_session">Attaching to the other
<code>Tmux</code> session</a>
</h3>
<p>
For the case you can not or don't want to use the current
<code>tmux</code> session you are running in, you may want to have
the separate <code>tmux</code> server up and running and use its
windows or panes to be created. This can be done by mean of
prepending the correct <code>-L</code> or <code>-S</code> switch to
the start of the every of the command-line parameters string to be
used, for example:
</p>
<pre>
$ DFTMUX_CMD_NEWW="-L default neww -P" \
> DFTMUX_CMD_TTY="-L default lsp -F #{pane_tty} -t" \
> perl -MDebug::Fork::Tmux -d your_script.pl
</pre>
<h2>
<a class='u' href='#___top' title='click to go to top of document'
name="DIAGNOSTICS" id="DIAGNOSTICS">DIAGNOSTICS</a>
</h2>
<ul>
<li>
<code>The command ...</code>
<p>
Typically the error message starts with the command the <a href=
"http://search.cpan.org/perldoc?Debug%3A%3AFork%3A%3ATmux" class=
"podlinkpod">Debug::Fork::Tmux</a> tried to execute, including
the command's arguments.
</p>
</li>
<li>
<code>failed opening command: ...</code>
<p>
The command was not taken by the system as an executable binary
file.
</p>
</li>
<li>
<code>... didn't write a line</code>
</li>
<li>
<code>failed reading command: ...</code>
<p>
Command did not output exactly one line of the text.
</p>
</li>
<li>
<code>... did not finish</code>
<p>
Command outputs more than one line of the text.
</p>
</li>
<li>
<code>provided empty string</code>
<p>
Command outputs exactly one line of the text and the line is
empty.
</p>
</li>
<li>
<code>failed to execute: ...</code>
<p>
There was failure executing the command
</p>
</li>
<li>
<code>child died with(out) signal X, Y coredump</code>
<p>
Command was killed by the signal X and the coredump is (not)
located in Y.
</p>
</li>
<li>
<code>child exited with value X</code>
<p>
Command was not failed but there are reasons to throw an error
like the wrong command's output.
</p>
</li>
</ul>
<h2>
<a class='u' href='#___top' title='click to go to top of document'
name="DEPENDENCIES" id="DEPENDENCIES">DEPENDENCIES</a>
</h2>
<p>
* <code>Perl 5.8.9+</code> is available from <a href=
"http://www.perl.org" class="podlinkurl">The Perl website</a>
</p>
<p>
* <a href="http://search.cpan.org/perldoc?Config" class=
"podlinkpod">Config</a>, <a href="http://search.cpan.org/perldoc?Cwd"
class="podlinkpod">Cwd</a>, <a href=
"http://search.cpan.org/perldoc?DB" class="podlinkpod">DB</a>,
<a href="http://search.cpan.org/perldoc?ExtUtils%3A%3AMakeMaker"
class="podlinkpod">ExtUtils::MakeMaker</a>, <a href=
"http://search.cpan.org/perldoc?File%3A%3AFind" class=
"podlinkpod">File::Find</a>, <a href=
"http://search.cpan.org/perldoc?File%3A%3ASpec" class=
"podlinkpod">File::Spec</a>, <a href=
"http://search.cpan.org/perldoc?File%3A%3ABasename" class=
"podlinkpod">File::Basename</a>, <a href=
"http://search.cpan.org/perldoc?Scalar%3A%3AUtil" class=
"podlinkpod">Scalar::Util</a>, <a href=
"http://search.cpan.org/perldoc?Test%3A%3AMore" class=
"podlinkpod">Test::More</a> are available in core <code>Perl</code>
distribution version 5.8.9 and later
</p>
<p>
* <a href="http://search.cpan.org/perldoc?Const%3A%3AFast" class=
"podlinkpod">Const::Fast</a> is available from <code>CPAN</code>
</p>
<p>
* <a href="http://search.cpan.org/perldoc?Module%3A%3ABuild" class=
"podlinkpod">Module::Build</a> is available in core <code>Perl</code>
distribution since version 5.9.4
</p>
<p>
* <a href="http://search.cpan.org/perldoc?Sort%3A%3AVersions" class=
"podlinkpod">Sort::Versions</a> is available from <code>CPAN</code>
</p>
<p>
* <a href="http://search.cpan.org/perldoc?Test%3A%3AException" class=
"podlinkpod">Test::Exception</a> is available from <code>CPAN</code>
</p>
<p>
* <a href="http://search.cpan.org/perldoc?Test%3A%3AMost" class=
"podlinkpod">Test::Most</a> is available from <code>CPAN</code>
</p>
<p>
* <a href="http://search.cpan.org/perldoc?Test%3A%3AStrict" class=
"podlinkpod">Test::Strict</a> is available from <code>CPAN</code>
</p>
<p>
* <a href="http://search.cpan.org/perldoc?Env%3A%3APath" class=
"podlinkpod">Env::Path</a> is available from <code>CPAN</code>
</p>
<p>
* <a href="http://search.cpan.org/perldoc?autodie" class=
"podlinkpod">autodie</a> is available in core <code>Perl</code>
distribution since version 5.10.1
</p>
<p>
* <code>Tmux</code> v1.6+ is available from <a href=
"http://tmux.sourceforge.net" class="podlinkurl">The Tmux website</a>
</p>
<p>
Most of them can easily be found in your operating system
distribution/repository.
</p>
<h2>
<a class='u' href='#___top' title='click to go to top of document'
name="BUGS_AND_LIMITATIONS" id="BUGS_AND_LIMITATIONS">BUGS AND
LIMITATIONS</a>
</h2>
<p>
You can make new bug reports, and view existing ones, through the web
interface at <a href=
"http://bugs.vereshagin.org/product/Debug-Fork-Tmux" class=
"podlinkurl">http://bugs.vereshagin.org/product/Debug-Fork-Tmux</a>.
</p>
<h2>
<a class='u' href='#___top' title='click to go to top of document'
name="WEB_SITE" id="WEB_SITE">WEB SITE</a>
</h2>
<p>
The web site of <a href=
"http://gitweb.vereshagin.org/Debug-Fork-Tmux/README.html" class=
"podlinkurl">Debug::Fork::Tmux</a> currently consists of only one
page cause it's a very small module.
</p>
<p>
You may want to visit a <a href=
"https://github.com/petr999/Debug-Fork-Tmux" class=
"podlinkurl">GitHub page</a>, too.
</p>
<h2>
<a class='u' href='#___top' title='click to go to top of document'
name="SUPPORT" id="SUPPORT">SUPPORT</a>
</h2>
<h3>
<a class='u' href='#___top' title='click to go to top of document'
name="Perldoc" id="Perldoc">Perldoc</a>
</h3>
<p>
You can find documentation for this module with the perldoc command.
</p>
<pre>
perldoc Debug::Fork::Tmux
</pre>
<h3>
<a class='u' href='#___top' title='click to go to top of document'
name="Websites" id="Websites">Websites</a>
</h3>
<p>
The following websites have more information about this module, and
may be of help to you. As always, in addition to those websites
please use your favorite search engine to discover more resources.
</p>
<ul>
<li>MetaCPAN
<p>
A modern, open-source CPAN search engine, useful to view POD in
HTML format.
</p>
<p>
<a href="http://metacpan.org/release/Debug-Fork-Tmux" class=
"podlinkurl">http://metacpan.org/release/Debug-Fork-Tmux</a>
</p>
</li>
<li>Search CPAN
<p>
The default CPAN search engine, useful to view POD in HTML
format.
</p>
<p>
<a href="http://search.cpan.org/dist/Debug-Fork-Tmux" class=
"podlinkurl">http://search.cpan.org/dist/Debug-Fork-Tmux</a>
</p>
</li>
<li>RT: CPAN's Bug Tracker
<p>
The RT ( Request Tracker ) website is the default bug/issue
tracking system for CPAN.
</p>
<p>
<a href=
"http://rt.cpan.org/NoAuth/Bugs.html?Dist=Debug-Fork-Tmux" class=
"podlinkurl">http://rt.cpan.org/NoAuth/Bugs.html?Dist=Debug-Fork-Tmux</a>
</p>
</li>
<li>AnnoCPAN
<p>
The AnnoCPAN is a website that allows community annotations of
Perl module documentation.
</p>
<p>
<a href="http://annocpan.org/dist/Debug-Fork-Tmux" class=
"podlinkurl">http://annocpan.org/dist/Debug-Fork-Tmux</a>
</p>
</li>
<li>CPAN Ratings
<p>
The CPAN Ratings is a website that allows community ratings and
reviews of Perl modules.
</p>
<p>
<a href="http://cpanratings.perl.org/d/Debug-Fork-Tmux" class=
"podlinkurl">http://cpanratings.perl.org/d/Debug-Fork-Tmux</a>
</p>
</li>
<li>CPAN Forum
<p>
The CPAN Forum is a web forum for discussing Perl modules.
</p>
<p>
<a href="http://cpanforum.com/dist/Debug-Fork-Tmux" class=
"podlinkurl">http://cpanforum.com/dist/Debug-Fork-Tmux</a>
</p>
</li>
<li>CPANTS
<p>
The CPANTS is a website that analyzes the Kwalitee ( code metrics
) of a distribution.
</p>
<p>
<a href="http://cpants.perl.org/dist/overview/Debug-Fork-Tmux"
class=
"podlinkurl">http://cpants.perl.org/dist/overview/Debug-Fork-Tmux</a>
</p>
</li>
<li>CPAN Testers
<p>
The CPAN Testers is a network of smokers who run automated tests
on uploaded CPAN distributions.
</p>
<p>
<a href="http://www.cpantesters.org/distro/D/Debug-Fork-Tmux"
class=
"podlinkurl">http://www.cpantesters.org/distro/D/Debug-Fork-Tmux</a>
</p>
</li>
<li>CPAN Testers Matrix
<p>
The CPAN Testers Matrix is a website that provides a visual
overview of the test results for a distribution on various
Perls/platforms.
</p>
<p>
<a href="http://matrix.cpantesters.org/?dist=Debug-Fork-Tmux"
class=
"podlinkurl">http://matrix.cpantesters.org/?dist=Debug-Fork-Tmux</a>
</p>
</li>
<li>CPAN Testers Dependencies
<p>
The CPAN Testers Dependencies is a website that shows a chart of
the test results of all dependencies for a distribution.
</p>
<p>
<a href="http://deps.cpantesters.org/?module=Debug::Fork::Tmux"
class=
"podlinkurl">http://deps.cpantesters.org/?module=Debug::Fork::Tmux</a>
</p>
</li>
</ul>
<h3>
<a class='u' href='#___top' title='click to go to top of document'
name="Email" id="Email">Email</a>
</h3>
<p>
You can email the author of this module at
<code>peter@vereshagin.org</code> asking for help with any problems
you have.
</p>
<h3>
<a class='u' href='#___top' title='click to go to top of document'
name="Bugs_/_Feature_Requests">Bugs / Feature Requests</a>
</h3>
<p>
Please report any bugs or feature requests by email to
<code>peter@vereshagin.org</code>, or through the web interface at
<a href="http://bugs.vereshagin.org/product/Debug-Fork-Tmux" class=
"podlinkurl">http://bugs.vereshagin.org/product/Debug-Fork-Tmux</a>.
You will be automatically notified of any progress on the request by
the system.
</p>
<h3>
<a class='u' href='#___top' title='click to go to top of document'
name="Source_Code" id="Source_Code">Source Code</a>
</h3>
<p>
The code is open to the world, and available for you to hack on.
Please feel free to browse it and play with it, or whatever. If you
want to contribute patches, please send me a diff or prod me to pull
from your repository :)
</p>
<p>
<a href="http://gitweb.vereshagin.org/Debug-Fork-Tmux" class=
"podlinkurl">http://gitweb.vereshagin.org/Debug-Fork-Tmux</a>
</p>
<pre>
git clone https://github.com/petr999/Debug-Fork-Tmux.git
</pre>
<h2>
<a class='u' href='#___top' title='click to go to top of document'
name="AUTHOR" id="AUTHOR">AUTHOR</a>
</h2>
<p>
<a href="http://vereshagin.org" class="podlinkurl">Peter
Vereshagin</a> <peter@vereshagin.org>
</p>
<h2>
<a class='u' href='#___top' title='click to go to top of document'
name="COPYRIGHT_AND_LICENSE" id="COPYRIGHT_AND_LICENSE">COPYRIGHT AND
LICENSE</a>
</h2>
<p>
This software is Copyright (c) 2013 by Peter Vereshagin.
</p>
<p>
This is free software, licensed under:
</p>
<pre>
The (three-clause) BSD License
</pre>
<h2>
<a class='u' href='#___top' title='click to go to top of document'
name="SEE_ALSO" id="SEE_ALSO">SEE ALSO</a>
</h2>
<p>
Please see those modules/websites for more information related to
this module.
</p>
<ul>
<li>
<a href=
"http://search.cpan.org/perldoc?Debug%3A%3AFork%3A%3ATmux%3A%3AConfig"
class="podlinkpod">Debug::Fork::Tmux::Config</a>
</li>
<li>
<a href="http://perlmonks.org/?node_id=128283" class=
"podlinkurl">http://perlmonks.org/?node_id=128283</a>
</li>
<li>
<a href="nntp://nntp.perl.org/perl.debugger" class=
"podlinkurl">nntp://nntp.perl.org/perl.debugger</a>
</li>
<li>
<a href="http://debugger.perl.org/" class=
"podlinkurl">http://debugger.perl.org/</a>
</li>
</ul>
<h2>
<a class='u' href='#___top' title='click to go to top of document'
name="DISCLAIMER_OF_WARRANTY" id="DISCLAIMER_OF_WARRANTY">DISCLAIMER
OF WARRANTY</a>
</h2>
<p>
BECAUSE THIS SOFTWARE IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE SOFTWARE, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE SOFTWARE "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
SOFTWARE IS WITH YOU. SHOULD THE SOFTWARE PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR, OR CORRECTION.
</p>
<p>
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE SOFTWARE AS PERMITTED BY THE ABOVE LICENCE, BE
LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR
INABILITY TO USE THE SOFTWARE (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR
THIRD PARTIES OR A FAILURE OF THE SOFTWARE TO OPERATE WITH ANY OTHER
SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
</p><!-- end doc -->
</body>
</html> |
web/admin/css/common.css | hiscaler/mts | input[type=text].disabled, select.disabled, input[type=password].disabled, input.disabled, textarea.disabled {
background: #F5F5F5;
}
.g-text {
background: url(../images/input-bg.png) repeat-x scroll 0 -130px #fff;
border: 1px solid #AAAAAA;
height: 14px;
padding: 5px 5px 6px;
width: 180px;
}
.g-text-username {
width: 80px;
}
.g-text-tel {
width: 80px;
}
.g-text:focus {
border-color: #999;
}
.g-text-area {
background: url(../images/input-bg.png) repeat-x scroll 0 -130px #fff;
border: 1px solid #AAAAAA;
width: 604px;
height: 120px;
max-height: 450px;
font-size: 12px;
line-height: 24px;
padding: 5px 5px 6px;
resize: none;
}
.g-text-area:focus {
border-color: #999;
}
.g-editor {
background-color: #ccc;
width: 600px;
height: 200px;
}
.icon-date-picker {
width: 100px;
background: #FFF url(../images/calendar.png) no-repeat 90px 50%!important;
}
.icon-datetime-picker {
width: 140px;
background: #FFF url(../images/calendar.png) no-repeat 120px 50%!important;
}
.button {
border: #ccc solid 1px;
border-radius: 3px;
background: #F5F5F5;
display: inline-block;
padding: 3px 5px;
cursor: pointer;
color: #4362BF;
}
.large-button {
padding: 5px 10px;
}
.button:hover {
border-color: #3b7fc4;
}
.loading, .processing, .running, .running-c-c {
background: url(../images/loading.gif) no-repeat;
}
.running-c-c {
background-position: center center;
}
.lock-ui {
background: url(../images/lock-ui-running.gif) no-repeat center center;
}
#infscr-loading {
border: #ccc solid 1px;
border-radius: 3px;
background-color: #F5F5F5;
display: block;
text-align: center;
padding: 0 10px;
width: 300px;
margin: 0 auto;
}
/*******************************************************************************
* 通用 Tabs 样式
******************************************************************************/
.tabs-common {
margin: 0;
}
.tabs-common {
display: block;
height: 25px;
border-bottom: 1px solid #E9E9E9;
}
.tabs-common li {
float: left;
list-style: none outside none;
margin: 0 6px;
}
.tabs-common li.active a {
background: none repeat scroll 0 0 #F5F5F5;
border-top: #DD4B39 solid 2px;
border-bottom: 1px solid #F8F8F8;
color: #4362BF;
font-weight: bold;
}
.tabs-common a:hover {
background: none repeat scroll 0 0 #F5F5F5;
}
.tabs-common a {
-moz-border-bottom-colors: none;
-moz-border-image: none;
-moz-border-left-colors: none;
-moz-border-right-colors: none;
-moz-border-top-colors: none;
background: none repeat scroll 0 0 #FFF;
border-color: #E9E9E9;
border-style: solid solid none;
border-top-left-radius: 3px;
border-top-right-radius: 3px;
border-width: 1px 1px medium;
color: #666677;
display: block;
padding: 0.25em 1em;
text-decoration: none;
}
.tabs-common li .badges {
margin-left: 5px;
}
.panels {
border: 1px solid #E9E9E9;
border-top: none;
padding: 10px;
border-radius: 0 0 5px 5px
}
/*******************************************************************************
* label
******************************************************************************/
.label {
display: inline-block;
float: left;
padding: 3px 5px;
}
.label-active, .label:hover {
border-bottom: #205081 solid 2px;
}
.label:hover {
text-decoration: none;
}
/*******************************************************************************
* Site error
******************************************************************************/
.site-error {
padding: 50px 140px;
}
.site-error h1 {
background: url(../images/error-message.png) no-repeat left center;
padding-left: 40px;
}
.site-error .message {
color: #e4393c;
}
/*******************************************************************************
* Message box
******************************************************************************/
.alert, .notice, .success, .info {
padding: 0.8em;
margin: 10px;
border: 1px solid #ddd;
}
.alert a, .notice a, .success a, .info a {
color: #4362BF;
}
.alert {
background: #fbe3e4;
color: #8a1f11;
border-color: #fbc2c4;
}
.notice {
background: #fff6bf;
color: #514721;
border-color: #ffd324;
}
.success {
background: #e6efc2;
color: #264409;
border-color: #c6d880;
}
.info {
background: #d5edf8;
color: #205791;
border-color: #92cae4;
}
/*******************************************************************************
* Badges
******************************************************************************/
.badges {
border-radius: 3px;
padding: 0 4px;
}
.badges:hover {
color: #FFF;
}
.badges-blue {
background-color: #4362BF;
color: #FFF;
}
.badges-bright-blue {
background-color: #3b73af;
color: #FFF;
}
.badges-gray {
background-color: #CCCCCC;
color: #333333;
}
.badges-light-gray {
background-color: #3b73af;
color: #f5f5f5;
}
.badges-red {
background-color: #d04437;
color: #FFF;
}
/*******************************************************************************
* List view
******************************************************************************/
.list-view-loading {
background:url(../images/loading.gif) no-repeat center center;
}
.list-view .summary {
margin: 0 0 5px 0;
text-align: right;
}
.list-view .sorter {
margin: 0 0 5px 0;
text-align: right;
}
.list-view .sorter {
font-size: 0.9em;
}
.list-view .sorter ul {
display: inline;
list-style-image:none;
list-style-position:outside;
list-style-type:none;
margin:0;
padding:0;
}
.list-view .sorter li {
display: inline;
margin: 0 0 0 5px;
padding: 0;
}
.list-view .sorter a.asc {
background: url(../images/up.gif) right center no-repeat;
padding-right: 10px;
}
.list-view .sorter a.desc {
background: url(../images/down.gif) right center no-repeat;
padding-right: 10px;
}
.list-view span.empty {
display: block;
background: #fff6bf url(../images/notice.png) no-repeat 10px 50%;
color: #514721;
padding: 10px 10px 10px 30px;
margin: 10px;
border: 1px solid #ffd324;
}
/*******************************************************************************
* Pagination
******************************************************************************/
ul.pagination {
height: 30px;
line-height: 30px;
padding: 0;
margin: 5px 0;
}
ul.pagination li {
display: inline;
margin: 0;
float: left;
}
ul.pagination a,
ul.pagination span {
padding: 0 10px;
font-size: 13px;
display: inline;
color: #487BB7;
margin: 0;
text-decoration: none;
font-weight: normal;
border: solid 1px #E9E9E9;
border-right: none;
float: left;
}
ul.pagination li.prev a,
ul.pagination li.prev span {
border-radius: 3px 0 0 3px;
}
ul.pagination li.next a,
ul.pagination li.next span {
border-right: solid 1px #E9E9E9;
border-radius: 0 3px 3px 0;
}
ul.pagination a:hover,
ul.pagination li.active {
background: #EEE;
color: #4362BF;
}
ul.pagination li.disabled span {
color: #E9E9E9;
}
/*******************************************************************************
* Message box
******************************************************************************/
.message-box {
padding: 5px 10px;
margin-bottom: 10px;
border: 1px solid #FFD324;
background: #FFF6BF;
}
.message-box .hd {
height: 30px;
line-height: 30px;
background: url(../images/notice.png) no-repeat left center;
border-bottom: 1px solid #FFD324;
padding-left: 25px;
margin-bottom: 6px;
font-size: 16px;
font-weight: bold;
color: #487BB7;
}
.message-box .hd em {
float: right;
font-size: 12px;
}
.message-box .hd em a.close-button {
border: #FFD324 solid 1px;
padding: 0 5px;
color: #FFD324;
font-weight: bold;
text-decoration: none;
}
.message-box .hd em a.close-button:hover {
color: #6C7B81;
border: #6C7B81 solid 1px;
}
.message-box .bd {
padding: 5px 25px;
}
.message-box .bd li {
line-height: 24px;
background: url(../images/bullet-blue.png) no-repeat 0 9px ;
padding-left: 12px;
}
.message-box .bd li.warning {
color: #d04437;
}
.message-box .bd li.bold {
font-weight: bold;
}
/*******************************************************************************
* Error message
******************************************************************************/
.message-error {
background: #F5F5F5;
margin-bottom: -10px;
}
.message-error .inner {
width: 600px;
margin: 0 auto;
padding: 100px 0;
}
.message-error h2 {
background: url(../images/error-message.png) no-repeat left center;
padding: 0 0 0 40px;
height: 40px;
line-height: 40px;
margin: 0;
}
.message-error .content {
border: #B7320F solid 1px;
padding: 15px 10px;
background-color: #fbc2c4;
}
/*******************************************************************************
* 水平垂直居中
******************************************************************************/
#hv-center-outer {
height: 100%;
overflow: hidden;
position: relative;
width: 100%;
display: table;
}
#hv-center-outer[id] {
display: table;
position: static;
*position: relative;
_position: static;
}
#hv-center-middle {
position: absolute;
top: 50%;
left: 0;
vertical-align: middle;
display: table-cell;
width: 100%;
*vertical-align: middle;
*display: table-cell;
*width: 100%;
_vertical-align:;
_display:;
_width:;
}
#hv-center-middle[id] {
display: table-cell;
vertical-align: middle;
position: static;
top: 50%;
left: 0;
width: 100%;
*position: absolute;
_position: ;
}
#hv-center-inner {
position: relative;
top: -50%;
margin: 0 auto;
text-align: center;
}
#hv-center-content{
margin: 0 auto;
text-align:left;
}
#hv-center-content #login {
width: 500px;
height: 320px;
}
/*******************************************************************************
* Smart text input
******************************************************************************/
.smart-edit input {
border: #ccc solid 1px;
width: 60%;
padding: 3px;
}
.icon {
display: inline-block !important;
width: 16px;
height: 16px;
overflow: hidden;
vertical-align: middle;
background-image: url(../images/icons.png);
background-repeat: no-repeat;
font-size: 0;
}
/* glyphicon */
.glyphicon {
position: relative;
top: 1px;
display: inline-block;
width: 16px;
height: 16px;
font-family: 'Glyphicons Halflings';
font-style: normal;
font-weight: normal;
line-height: 1;
-webkit-font-smoothing: antialiased;
-moz-osx-font-smoothing: grayscale;
background-image: url(../images/icons.png);
background-repeat: no-repeat;
}
.glyphicon-eye-open {
background-position: -1904px -16px;
}
.glyphicon-pencil {
background-position: -1166px -16px;
}
.glyphicon-trash {
background-position: -816px -16px;
} |
doc/brown/tracingplane/atomlayer/TestOverflowMarker.html | tracingplane/tracingplane-java | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<!-- NewPage -->
<html lang="en">
<head>
<!-- Generated by javadoc (1.8.0_112) on Thu May 18 12:33:07 EDT 2017 -->
<title>TestOverflowMarker</title>
<meta name="date" content="2017-05-18">
<link rel="stylesheet" type="text/css" href="../../../javadoc-stylesheet.css" title="Style">
<script type="text/javascript" src="../../../script.js"></script>
</head>
<body>
<script type="text/javascript"><!--
try {
if (location.href.indexOf('is-external=true') == -1) {
parent.document.title="TestOverflowMarker";
}
}
catch(err) {
}
//-->
var methods = {"i0":10,"i1":10,"i2":10};
var tabs = {65535:["t0","All Methods"],2:["t2","Instance Methods"],8:["t4","Concrete Methods"]};
var altColor = "altColor";
var rowColor = "rowColor";
var tableTab = "tableTab";
var activeTableTab = "activeTableTab";
</script>
<noscript>
<div>JavaScript is disabled on your browser.</div>
</noscript>
<!-- ========= START OF TOP NAVBAR ======= -->
<div class="topNav"><a name="navbar.top">
<!-- -->
</a>
<div class="skipNav"><a href="#skip.navbar.top" title="Skip navigation links">Skip navigation links</a></div>
<a name="navbar.top.firstrow">
<!-- -->
</a>
<ul class="navList" title="Navigation">
<li><a href="../../../overview-summary.html">Overview</a></li>
<li><a href="package-summary.html">Package</a></li>
<li class="navBarCell1Rev">Class</li>
<li><a href="class-use/TestOverflowMarker.html">Use</a></li>
<li><a href="package-tree.html">Tree</a></li>
<li><a href="../../../deprecated-list.html">Deprecated</a></li>
<li><a href="../../../index-files/index-1.html">Index</a></li>
<li><a href="../../../help-doc.html">Help</a></li>
</ul>
</div>
<div class="subNav">
<ul class="navList">
<li><a href="../../../brown/tracingplane/atomlayer/TestMergeTwoIterator.html" title="class in brown.tracingplane.atomlayer"><span class="typeNameLink">Prev Class</span></a></li>
<li><a href="../../../brown/tracingplane/atomlayer/TestProtobufVarint.html" title="class in brown.tracingplane.atomlayer"><span class="typeNameLink">Next Class</span></a></li>
</ul>
<ul class="navList">
<li><a href="../../../index.html?brown/tracingplane/atomlayer/TestOverflowMarker.html" target="_top">Frames</a></li>
<li><a href="TestOverflowMarker.html" target="_top">No Frames</a></li>
</ul>
<ul class="navList" id="allclasses_navbar_top">
<li><a href="../../../allclasses-noframe.html">All Classes</a></li>
</ul>
<div>
<script type="text/javascript"><!--
allClassesLink = document.getElementById("allclasses_navbar_top");
if(window==top) {
allClassesLink.style.display = "block";
}
else {
allClassesLink.style.display = "none";
}
//-->
</script>
</div>
<div>
<ul class="subNavList">
<li>Summary: </li>
<li>Nested | </li>
<li>Field | </li>
<li><a href="#constructor.summary">Constr</a> | </li>
<li><a href="#method.summary">Method</a></li>
</ul>
<ul class="subNavList">
<li>Detail: </li>
<li>Field | </li>
<li><a href="#constructor.detail">Constr</a> | </li>
<li><a href="#method.detail">Method</a></li>
</ul>
</div>
<a name="skip.navbar.top">
<!-- -->
</a></div>
<!-- ========= END OF TOP NAVBAR ========= -->
<!-- ======== START OF CLASS DATA ======== -->
<div class="header">
<div class="subTitle">brown.tracingplane.atomlayer</div>
<h2 title="Class TestOverflowMarker" class="title">Class TestOverflowMarker</h2>
</div>
<div class="contentContainer">
<ul class="inheritance">
<li>java.lang.Object</li>
<li>
<ul class="inheritance">
<li>brown.tracingplane.atomlayer.TestOverflowMarker</li>
</ul>
</li>
</ul>
<div class="description">
<ul class="blockList">
<li class="blockList">
<hr>
<br>
<pre>public class <span class="typeNameLabel">TestOverflowMarker</span>
extends java.lang.Object</pre>
</li>
</ul>
</div>
<div class="summary">
<ul class="blockList">
<li class="blockList">
<!-- ======== CONSTRUCTOR SUMMARY ======== -->
<ul class="blockList">
<li class="blockList"><a name="constructor.summary">
<!-- -->
</a>
<h3>Constructor Summary</h3>
<table class="memberSummary" border="0" cellpadding="3" cellspacing="0" summary="Constructor Summary table, listing constructors, and an explanation">
<caption><span>Constructors</span><span class="tabEnd"> </span></caption>
<tr>
<th class="colOne" scope="col">Constructor and Description</th>
</tr>
<tr class="altColor">
<td class="colOne"><code><span class="memberNameLink"><a href="../../../brown/tracingplane/atomlayer/TestOverflowMarker.html#TestOverflowMarker--">TestOverflowMarker</a></span>()</code> </td>
</tr>
</table>
</li>
</ul>
<!-- ========== METHOD SUMMARY =========== -->
<ul class="blockList">
<li class="blockList"><a name="method.summary">
<!-- -->
</a>
<h3>Method Summary</h3>
<table class="memberSummary" border="0" cellpadding="3" cellspacing="0" summary="Method Summary table, listing methods, and an explanation">
<caption><span id="t0" class="activeTableTab"><span>All Methods</span><span class="tabEnd"> </span></span><span id="t2" class="tableTab"><span><a href="javascript:show(2);">Instance Methods</a></span><span class="tabEnd"> </span></span><span id="t4" class="tableTab"><span><a href="javascript:show(8);">Concrete Methods</a></span><span class="tabEnd"> </span></span></caption>
<tr>
<th class="colFirst" scope="col">Modifier and Type</th>
<th class="colLast" scope="col">Method and Description</th>
</tr>
<tr id="i0" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../brown/tracingplane/atomlayer/TestOverflowMarker.html#testMergeOverflowAtoms--">testMergeOverflowAtoms</a></span>()</code> </td>
</tr>
<tr id="i1" class="rowColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../brown/tracingplane/atomlayer/TestOverflowMarker.html#testSerializedOverflowMarker--">testSerializedOverflowMarker</a></span>()</code> </td>
</tr>
<tr id="i2" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../brown/tracingplane/atomlayer/TestOverflowMarker.html#testTrimByteBuffer--">testTrimByteBuffer</a></span>()</code> </td>
</tr>
</table>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
<!-- -->
</a>
<h3>Methods inherited from class java.lang.Object</h3>
<code>equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait</code></li>
</ul>
</li>
</ul>
</li>
</ul>
</div>
<div class="details">
<ul class="blockList">
<li class="blockList">
<!-- ========= CONSTRUCTOR DETAIL ======== -->
<ul class="blockList">
<li class="blockList"><a name="constructor.detail">
<!-- -->
</a>
<h3>Constructor Detail</h3>
<a name="TestOverflowMarker--">
<!-- -->
</a>
<ul class="blockListLast">
<li class="blockList">
<h4>TestOverflowMarker</h4>
<pre>public TestOverflowMarker()</pre>
</li>
</ul>
</li>
</ul>
<!-- ============ METHOD DETAIL ========== -->
<ul class="blockList">
<li class="blockList"><a name="method.detail">
<!-- -->
</a>
<h3>Method Detail</h3>
<a name="testSerializedOverflowMarker--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>testSerializedOverflowMarker</h4>
<pre>public void testSerializedOverflowMarker()</pre>
</li>
</ul>
<a name="testTrimByteBuffer--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>testTrimByteBuffer</h4>
<pre>public void testTrimByteBuffer()</pre>
</li>
</ul>
<a name="testMergeOverflowAtoms--">
<!-- -->
</a>
<ul class="blockListLast">
<li class="blockList">
<h4>testMergeOverflowAtoms</h4>
<pre>public void testMergeOverflowAtoms()</pre>
</li>
</ul>
</li>
</ul>
</li>
</ul>
</div>
</div>
<!-- ========= END OF CLASS DATA ========= -->
<!-- ======= START OF BOTTOM NAVBAR ====== -->
<div class="bottomNav"><a name="navbar.bottom">
<!-- -->
</a>
<div class="skipNav"><a href="#skip.navbar.bottom" title="Skip navigation links">Skip navigation links</a></div>
<a name="navbar.bottom.firstrow">
<!-- -->
</a>
<ul class="navList" title="Navigation">
<li><a href="../../../overview-summary.html">Overview</a></li>
<li><a href="package-summary.html">Package</a></li>
<li class="navBarCell1Rev">Class</li>
<li><a href="class-use/TestOverflowMarker.html">Use</a></li>
<li><a href="package-tree.html">Tree</a></li>
<li><a href="../../../deprecated-list.html">Deprecated</a></li>
<li><a href="../../../index-files/index-1.html">Index</a></li>
<li><a href="../../../help-doc.html">Help</a></li>
</ul>
</div>
<div class="subNav">
<ul class="navList">
<li><a href="../../../brown/tracingplane/atomlayer/TestMergeTwoIterator.html" title="class in brown.tracingplane.atomlayer"><span class="typeNameLink">Prev Class</span></a></li>
<li><a href="../../../brown/tracingplane/atomlayer/TestProtobufVarint.html" title="class in brown.tracingplane.atomlayer"><span class="typeNameLink">Next Class</span></a></li>
</ul>
<ul class="navList">
<li><a href="../../../index.html?brown/tracingplane/atomlayer/TestOverflowMarker.html" target="_top">Frames</a></li>
<li><a href="TestOverflowMarker.html" target="_top">No Frames</a></li>
</ul>
<ul class="navList" id="allclasses_navbar_bottom">
<li><a href="../../../allclasses-noframe.html">All Classes</a></li>
</ul>
<div>
<script type="text/javascript"><!--
allClassesLink = document.getElementById("allclasses_navbar_bottom");
if(window==top) {
allClassesLink.style.display = "block";
}
else {
allClassesLink.style.display = "none";
}
//-->
</script>
</div>
<div>
<ul class="subNavList">
<li>Summary: </li>
<li>Nested | </li>
<li>Field | </li>
<li><a href="#constructor.summary">Constr</a> | </li>
<li><a href="#method.summary">Method</a></li>
</ul>
<ul class="subNavList">
<li>Detail: </li>
<li>Field | </li>
<li><a href="#constructor.detail">Constr</a> | </li>
<li><a href="#method.detail">Method</a></li>
</ul>
</div>
<a name="skip.navbar.bottom">
<!-- -->
</a></div>
<!-- ======== END OF BOTTOM NAVBAR ======= -->
</body>
</html>
|
measurer/hotspot-measurer/jdk1.6.0_45/db/docs/html/getstart/cgsquck13780.html | armoredsoftware/protocol | <!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
<meta name="copyright" content="(C) Copyright 2005" />
<meta name="DC.rights.owner" content="(C) Copyright 2005" />
<meta content="public" name="security" />
<meta content="index,follow" name="Robots" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta content="concept" name="DC.Type" />
<meta name="DC.Title" content="Client/server environment" />
<meta name="abstract" content="A client/server environment is an environment in which multiple applications connect to Derby over the network." />
<meta name="description" content="A client/server environment is an environment in which multiple applications connect to Derby over the network." />
<meta content="client/server environment, environment, client/server" name="DC.subject" />
<meta content="client/server environment, environment, client/server" name="keywords" />
<meta scheme="URI" name="DC.Relation" content="cgsquck70629.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="cgsquck13780" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
<link href="commonltr.css" type="text/css" rel="stylesheet" />
<title>Client/server environment</title>
</head>
<body id="cgsquck13780"><a name="cgsquck13780"><!-- --></a>
<h1 class="topictitle1">Client/server environment</h1>
<div><p>A client/server environment is an environment in which multiple
applications connect to <span>Derby</span> over
the network.</p>
<p><span>Derby</span> runs embedded in
a server framework that allows multiple network connections. (The framework
itself starts an instance of <span>Derby</span> and
runs in an embedded environment. However, the client applications do not run
in the embedded environment.)</p>
<p>You can also embed <span>Derby</span> in
any Java server framework. </p>
<p>See the <cite><span><em>Java DB Server and Administration Guide</em></span></cite> for
more information on how to run <span>Derby</span> on
a server.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cgsquck70629.html" title="Before you configure your system to run Derby, it is useful to understand something about the different environments in which Derby can run, because these environments affect the classpath, driver name, and database connection URL.">Environments in which Derby can run</a></div>
</div>
</div>
</body>
</html> |
measurer/hotspot-measurer/jdk1.6.0_45/db/docs/html/devguide/cdevdeploy15325.html | armoredsoftware/protocol | <!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
<meta name="copyright" content="(C) Copyright 2005" />
<meta name="DC.rights.owner" content="(C) Copyright 2005" />
<meta content="public" name="security" />
<meta content="index,follow" name="Robots" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta content="concept" name="DC.Type" />
<meta name="DC.Title" content="Creating Derby databases for read-only use" />
<meta name="abstract" content="You can create Derby databases for use on read-only media such as CD-ROMs." />
<meta name="description" content="You can create Derby databases for use on read-only media such as CD-ROMs." />
<meta content="Read-only databases, working with" name="DC.subject" />
<meta content="Read-only databases, working with" name="keywords" />
<meta scheme="URI" name="DC.Relation" content="cdevdeploy30736.html" />
<meta scheme="URI" name="DC.Relation" content="cdevdeploy18639.html" />
<meta scheme="URI" name="DC.Relation" content="cdevdeploy32171.html" />
<meta scheme="URI" name="DC.Relation" content="tdevdeploy26887.html" />
<meta scheme="URI" name="DC.Relation" content="tdevdeploy19136.html" />
<meta scheme="URI" name="DC.Relation" content="tdevdeploy33704.html" />
<meta scheme="URI" name="DC.Relation" content="cdevdeploy11201.html" />
<meta scheme="URI" name="DC.Relation" content="tdevdeploy39856.html" />
<meta scheme="URI" name="DC.Relation" content="cdevdeploy82529.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="cdevdeploy15325" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
<link href="commonltr.css" type="text/css" rel="stylesheet" />
<title>Creating Derby databases for read-only use</title>
</head>
<body id="cdevdeploy15325"><a name="cdevdeploy15325"><!-- --></a>
<h1 class="topictitle1">Creating Derby databases for read-only use</h1>
<div><p>You can create <span>Derby</span> databases for use on read-only media such as
CD-ROMs.</p>
<p><span>Derby</span> databases in zip or jar files are also read-only databases.
Typically, read-only databases are deployed with an application in an embedded
environment.</p>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="tdevdeploy26887.html">Creating and preparing the database for read-only use</a></strong><br />
To create databases for use on read-only media, perform these steps.</li>
<li class="ulchildlink"><strong><a href="tdevdeploy19136.html">Deploying the database on the read-only media</a></strong><br />
To deploy the database on read-only media, perform the following steps.</li>
<li class="ulchildlink"><strong><a href="tdevdeploy33704.html">Transferring read-only databases to archive (jar or zip) files</a></strong><br />
Once a database has been created in Derby, it can be stored in a jar or zip file and continue to be accessed by Derby in read-only mode.</li>
<li class="ulchildlink"><strong><a href="cdevdeploy11201.html">Accessing a read-only database in a zip/jar file</a></strong><br />
To access a database in a zip/jar, you specify the jar in the subsubprotocol.</li>
<li class="ulchildlink"><strong><a href="tdevdeploy39856.html">Accessing databases within a jar file using the classpath</a></strong><br />
Once an archive containing one or more Derby databases has been created it can be placed in the classpath. This allows access to a database from within an application without the application's knowing the path of the archive.</li>
<li class="ulchildlink"><strong><a href="cdevdeploy82529.html">Databases on read-only media and DatabaseMetaData</a></strong><br />
Databases on read-only media return true for DatabaseMetaData.isReadOnly.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cdevdeploy32171.html" title="Typically, once you have developed a Derby application and database, you package up the application, the Derby libraries, and the database in some means for distribution to your users. This process is called deployment.">Deploying Derby applications</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="cdevdeploy30736.html" title="You can store application logic in a database and then load classes from the database.">Loading classes from a database</a></div>
<div><a href="cdevdeploy18639.html" title="Database-wide properties are stored in the database and are simpler for deployment, while system-wide parameters might be easier for development.">Embedded systems and properties</a></div>
</div>
</div>
</body>
</html> |
urdl/doc/html/urdl/reference/core/istream/open.html | mapbox/jit_datasource | <html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>istream::open</title>
<link rel="stylesheet" href="../../../../boostbook.css" type="text/css">
<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
<link rel="start" href="../../../../index.html" title="Urdl">
<link rel="up" href="../istream.html" title="istream">
<link rel="prev" href="istream/overload3.html" title="istream::istream (3 of 3 overloads)">
<link rel="next" href="open_timeout.html" title="istream::open_timeout">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table cellpadding="2" width="100%"><tr><td valign="top"><img alt="Urdl C++ Library" width="160" height="60" src="../../../../urdl.png"></td></tr></table>
<hr>
<div class="spirit-nav">
<a accesskey="p" href="istream/overload3.html"><img src="../../../../prev.png" alt="Prev"></a><a accesskey="u" href="../istream.html"><img src="../../../../up.png" alt="Up"></a><a accesskey="h" href="../../../../index.html"><img src="../../../../home.png" alt="Home"></a><a accesskey="n" href="open_timeout.html"><img src="../../../../next.png" alt="Next"></a>
</div>
<div class="section" lang="en">
<div class="titlepage"><div><div><h5 class="title">
<a name="urdl.reference.core.istream.open"></a><a class="link" href="open.html" title="istream::open"> istream::open</a>
</h5></div></div></div>
<p>
<a class="indexterm" name="id606541"></a>
Opens the specified URL.
</p>
<pre class="programlisting"><span class="keyword">void</span> <span class="identifier">open</span><span class="special">(</span>
<span class="keyword">const</span> <span class="identifier">url</span> <span class="special">&</span> <span class="identifier">u</span><span class="special">);</span>
</pre>
<p>
<span class="emphasis"><em><span class="bold"><strong>Parameters</strong></span></em></span>
</p>
<div class="variablelist">
<p class="title"><b></b></p>
<dl>
<dt><span class="term">u</span></dt>
<dd><p>
The URL to open.
</p></dd>
</dl>
</div>
<p>
<span class="emphasis"><em><span class="bold"><strong>Remarks</strong></span></em></span>
</p>
<p>
Calls <code class="computeroutput"><span class="identifier">rdbuf</span><span class="special">()-></span><span class="identifier">open</span><span class="special">(</span><span class="identifier">u</span><span class="special">)</span></code>.
If that function does not return a null pointer, calls <code class="computeroutput"><span class="identifier">clear</span><span class="special">()</span></code>.
Otherwise calls <code class="computeroutput"><span class="identifier">setstate</span><span class="special">(</span><span class="identifier">failbit</span><span class="special">)</span></code> (which may throw <code class="computeroutput"><span class="identifier">ios_base</span><span class="special">::</span><span class="identifier">failure</span></code>).
</p>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
<td align="right"><div class="copyright-footer">Copyright © 2009 Christopher M. Kohlhoff<p>
Distributed under the Boost Software License, Version 1.0. (See accompanying
file LICENSE_1_0.txt or copy at <a href="http://www.boost.org/LICENSE_1_0.txt" target="_top">http://www.boost.org/LICENSE_1_0.txt</a>)
</p>
</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
<a accesskey="p" href="istream/overload3.html"><img src="../../../../prev.png" alt="Prev"></a><a accesskey="u" href="../istream.html"><img src="../../../../up.png" alt="Up"></a><a accesskey="h" href="../../../../index.html"><img src="../../../../home.png" alt="Home"></a><a accesskey="n" href="open_timeout.html"><img src="../../../../next.png" alt="Next"></a>
</div>
</body>
</html>
|
vendor/assets/stylesheets/jquery.modal.css | KirubanP/kanban | .modal {
display: none;
background: #fff;
-webkit-box-shadow: 5px 5px 5px rgba(50, 50, 50, 0.6);
-moz-box-shadow: 5px 5px 5px rgba(50, 50, 50, 0.6);
box-shadow: 5px 5px 5px rgba(50, 50, 50, 0.6);
/* custom */
width: 420px;
padding: 25px;
margin-top: 40px !important;
margin-bottom: 25px !important;
top: 0 !important;
position: absolute !important;
-webkit-border-radius: 3px;
-moz-border-radius: 3px;
-o-border-radius: 3px;
-ms-border-radius: 3px;
border-radius: 3px;
}
.modal a.close-modal {
display: none;
}
.modal a.close-modal-custom {
position: absolute;
top: -12.5px;
right: -12.5px;
display: block;
width: 26px;
height: 26px;
text-indent: -9999px;
top: 9px;
right: 9px;
background: url("/assets/close_squared.png") no-repeat 0 0;
opacity: .75;
-webkit-transition: .2s;
-moz-transition: .2s;
transition: .2s;
}
.modal a.close-modal-custom:hover {
opacity: 1;
}
.modal-spinner {
display: none;
width: 64px;
height: 64px;
position: fixed;
top: 50%;
left: 50%;
margin-right: -32px;
margin-top: -32px;
background: url(spinner.gif) #111 no-repeat center center;
-webkit-border-radius: 8px;
-moz-border-radius: 8px;
-o-border-radius: 8px;
-ms-border-radius: 8px;
border-radius: 8px;
} |
lib/angular-1.3.10/docs/examples/example-example37/index-production.html | apulll/angular_study | <!doctype html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Example - example-example37-production</title>
<script src="//ajax.googleapis.com/ajax/libs/angularjs/1.3.9/angular.min.js"></script>
<script src="script.js"></script>
</head>
<body ng-app="form-example-modify-validators">
<form name="form" class="css-form" novalidate>
<div>
Overwritten Email:
<input type="email" ng-model="myEmail" overwrite-email name="overwrittenEmail" />
<span ng-show="form.overwrittenEmail.$error.email">This email format is invalid!</span><br>
Model: {{myEmail}}
</div>
</form>
</body>
</html> |
example.html | ibheem/CSSJSON | <body>
<style>
body {
font-family: arial, sans-serif;
font-size: 18px;
}
pre {
background: #eee;
padding: 10px;
width: 800px;
white-space: pre-wrap;
word-break: break-all;
}
</style>
<!-- Add this if you're supporting IE 7, 8 -->
<script type="text/javascript" src="json2.js"></script>
<script type="text/javascript" src="cssjson.js"></script>
<script type="text/javascript">
// Dummy CSS
var css = '\
@media (max-width: 800px) {\n\
#main #comments {\n\
margin: 0px;\n\
width: auto;\n\
background: red;\n\
background: img("example.png");\n\
}\n\
#main #buttons {\n\
padding: 5px 10px;\n\
color: blue;\n\
}\n\
}\n\
\n\
#main #content {\n\
margin: 0 7.6%;\n\
width: auto;\n\
}\n\
#nav-below {\n\
border-bottom: 1px solid #ddd;\n\
margin-bottom: 1.625em;\n\
background-image: url(http://www.example.com/images/im.jpg);\n\
}\n\
';
exampleCSSJSON(css);
function exampleCSSJSON(cssString) {
var json = CSSJSON.toJSON(cssString);
if (typeof console != 'undefined') {
console.log('JSON:\n');
console.dir(json);
console.log('\n\n');
}
document.write('<strong>JSON</strong><br/><pre>'+JSON.stringify(json, undefined, 2)+'</pre>');
var css = CSSJSON.toCSS(json);
if (typeof console != 'undefined') {
console.log('CSS:\n');
console.log(css + '\n\n');
}
document.write('<br/><strong>CSS</strong><br/><pre>'+css+'</pre>');
}
</script>
</body> |
src/3rdparty/tbb/doc/html/a00085.html | GraphicsEmpire/tetcutter | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=9"/>
<meta name="generator" content="Doxygen 1.8.4"/>
<title>tbb::flow::interface7::join_node< OutputTuple, queueing > Class Template Reference</title>
<link href="tabs.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="jquery.js"></script>
<script type="text/javascript" src="dynsections.js"></script>
<link href="doxygen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="top"><!-- do not remove this div, it is closed by doxygen! -->
<!-- end header part -->
<!-- Generated by Doxygen 1.8.4 -->
<div id="navrow1" class="tabs">
<ul class="tablist">
<li><a href="index.html"><span>Main Page</span></a></li>
<li><a href="pages.html"><span>Related Pages</span></a></li>
<li><a href="modules.html"><span>Modules</span></a></li>
<li><a href="namespaces.html"><span>Namespaces</span></a></li>
<li class="current"><a href="annotated.html"><span>Classes</span></a></li>
<li><a href="files.html"><span>Files</span></a></li>
</ul>
</div>
<div id="navrow2" class="tabs2">
<ul class="tablist">
<li><a href="annotated.html"><span>Class List</span></a></li>
<li><a href="hierarchy.html"><span>Class Hierarchy</span></a></li>
<li><a href="functions.html"><span>Class Members</span></a></li>
</ul>
</div>
<div id="nav-path" class="navpath">
<ul>
<li class="navelem"><a class="el" href="a00237.html">tbb</a></li><li class="navelem"><b>flow</b></li><li class="navelem"><b>interface7</b></li><li class="navelem"><a class="el" href="a00085.html">join_node< OutputTuple, queueing ></a></li> </ul>
</div>
</div><!-- top -->
<div class="header">
<div class="summary">
<a href="#pub-types">Public Types</a> |
<a href="#pub-methods">Public Member Functions</a> |
<a href="a00348.html">List of all members</a> </div>
<div class="headertitle">
<div class="title">tbb::flow::interface7::join_node< OutputTuple, queueing > Class Template Reference</div> </div>
</div><!--header-->
<div class="contents">
<div class="dynheader">
Inheritance diagram for tbb::flow::interface7::join_node< OutputTuple, queueing >:</div>
<div class="dyncontent">
<div class="center">
<img src="a00085.png" usemap="#tbb::flow::interface7::join_node< OutputTuple, queueing >_map" alt=""/>
<map id="tbb::flow::interface7::join_node< OutputTuple, queueing >_map" name="tbb::flow::interface7::join_node< OutputTuple, queueing >_map">
</map>
</div></div>
<table class="memberdecls">
<tr class="heading"><td colspan="2"><h2 class="groupheader"><a name="pub-types"></a>
Public Types</h2></td></tr>
<tr class="memitem:a68f4d59b0d31a9f13e53f75fe3ded700"><td class="memItemLeft" align="right" valign="top"><a class="anchor" id="a68f4d59b0d31a9f13e53f75fe3ded700"></a>
typedef OutputTuple </td><td class="memItemRight" valign="bottom"><b>output_type</b></td></tr>
<tr class="separator:a68f4d59b0d31a9f13e53f75fe3ded700"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:a7ac9b6f2600b75143ff1dea1e3786b04"><td class="memItemLeft" align="right" valign="top"><a class="anchor" id="a7ac9b6f2600b75143ff1dea1e3786b04"></a>
typedef <br class="typebreak"/>
unfolded_type::input_ports_type </td><td class="memItemRight" valign="bottom"><b>input_ports_type</b></td></tr>
<tr class="separator:a7ac9b6f2600b75143ff1dea1e3786b04"><td class="memSeparator" colspan="2"> </td></tr>
</table><table class="memberdecls">
<tr class="heading"><td colspan="2"><h2 class="groupheader"><a name="pub-methods"></a>
Public Member Functions</h2></td></tr>
<tr class="memitem:ab1c49eff4420fd53b80b4425117ddb36"><td class="memItemLeft" align="right" valign="top"><a class="anchor" id="ab1c49eff4420fd53b80b4425117ddb36"></a>
 </td><td class="memItemRight" valign="bottom"><b>join_node</b> (<a class="el" href="a00067.html">graph</a> &g)</td></tr>
<tr class="separator:ab1c49eff4420fd53b80b4425117ddb36"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:a33ff02c356a0f2f590323177e9314ccd"><td class="memItemLeft" align="right" valign="top"><a class="anchor" id="a33ff02c356a0f2f590323177e9314ccd"></a>
 </td><td class="memItemRight" valign="bottom"><b>join_node</b> (const <a class="el" href="a00084.html">join_node</a> &other)</td></tr>
<tr class="separator:a33ff02c356a0f2f590323177e9314ccd"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:a7615ce374a3ec504ed196b7babbf1e04"><td class="memItemLeft" align="right" valign="top"><a class="anchor" id="a7615ce374a3ec504ed196b7babbf1e04"></a>
void </td><td class="memItemRight" valign="bottom"><b>set_name</b> (const char *name)</td></tr>
<tr class="separator:a7615ce374a3ec504ed196b7babbf1e04"><td class="memSeparator" colspan="2"> </td></tr>
</table>
<hr/>The documentation for this class was generated from the following file:<ul>
<li><a class="el" href="a00194.html">flow_graph.h</a></li>
</ul>
</div><!-- contents -->
<hr>
<p></p>
Copyright © 2005-2015 Intel Corporation. All Rights Reserved.
<p></p>
Intel, Pentium, Intel Xeon, Itanium, Intel XScale and VTune are
registered trademarks or trademarks of Intel Corporation or its
subsidiaries in the United States and other countries.
<p></p>
* Other names and brands may be claimed as the property of others.
|
api/v0.6.5/utility/input/Keyboard.F16.html | Circular-Studios/Dash-Docs |
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8"/><!-- using block title in layout.dt--><!-- using block ddox.defs in ddox.layout.dt--><!-- using block ddox.title in ddox.layout.dt-->
<title>Field Keyboard.F16</title>
<link rel="stylesheet" type="text/css" href="../../styles/ddox.css"/>
<link rel="stylesheet" href="../../prettify/prettify.css" type="text/css"/>
<script type="text/javascript" src="../../scripts/jquery.js">/**/</script>
<script type="text/javascript" src="../../prettify/prettify.js">/**/</script>
<script type="text/javascript" src="../../scripts/ddox.js">/**/</script>
</head>
<body onload="prettyPrint(); setupDdox();">
<nav id="main-nav"><!-- using block navigation in layout.dt-->
<ul class="tree-view">
<li class="collapsed tree-view">
<a href="#" class="package">components</a>
<ul class="tree-view">
<li>
<a href="../../components/animation.html" class=" module">animation</a>
</li>
<li>
<a href="../../components/assetanimation.html" class=" module">assetanimation</a>
</li>
<li>
<a href="../../components/assets.html" class=" module">assets</a>
</li>
<li>
<a href="../../components/camera.html" class=" module">camera</a>
</li>
<li>
<a href="../../components/icomponent.html" class=" module">icomponent</a>
</li>
<li>
<a href="../../components/lights.html" class=" module">lights</a>
</li>
<li>
<a href="../../components/material.html" class=" module">material</a>
</li>
<li>
<a href="../../components/mesh.html" class=" module">mesh</a>
</li>
<li>
<a href="../../components/userinterface.html" class=" module">userinterface</a>
</li>
</ul>
</li>
<li class="collapsed tree-view">
<a href="#" class="package">core</a>
<ul class="tree-view">
<li>
<a href="../../core/dgame.html" class=" module">dgame</a>
</li>
<li>
<a href="../../core/gameobject.html" class=" module">gameobject</a>
</li>
<li>
<a href="../../core/prefabs.html" class=" module">prefabs</a>
</li>
<li>
<a href="../../core/properties.html" class=" module">properties</a>
</li>
<li>
<a href="../../core/reflection.html" class=" module">reflection</a>
</li>
<li>
<a href="../../core/scene.html" class=" module">scene</a>
</li>
</ul>
</li>
<li class="collapsed tree-view">
<a href="#" class="package">graphics</a>
<ul class="tree-view">
<li class="collapsed tree-view">
<a href="#" class="package">adapters</a>
<ul class="tree-view">
<li>
<a href="../../graphics/adapters/adapter.html" class=" module">adapter</a>
</li>
<li>
<a href="../../graphics/adapters/linux.html" class=" module">linux</a>
</li>
<li>
<a href="../../graphics/adapters/mac.html" class=" module">mac</a>
</li>
<li>
<a href="../../graphics/adapters/win32.html" class=" module">win32</a>
</li>
</ul>
</li>
<li class="collapsed tree-view">
<a href="#" class="package">shaders</a>
<ul class="tree-view">
<li class="collapsed tree-view">
<a href="#" class="package">glsl</a>
<ul class="tree-view">
<li>
<a href="../../graphics/shaders/glsl/ambientlight.html" class=" module">ambientlight</a>
</li>
<li>
<a href="../../graphics/shaders/glsl/animatedgeometry.html" class=" module">animatedgeometry</a>
</li>
<li>
<a href="../../graphics/shaders/glsl/directionallight.html" class=" module">directionallight</a>
</li>
<li>
<a href="../../graphics/shaders/glsl/geometry.html" class=" module">geometry</a>
</li>
<li>
<a href="../../graphics/shaders/glsl/pointlight.html" class=" module">pointlight</a>
</li>
<li>
<a href="../../graphics/shaders/glsl/userinterface.html" class=" module">userinterface</a>
</li>
</ul>
</li>
<li>
<a href="../../graphics/shaders/glsl.html" class=" module">glsl</a>
</li>
<li>
<a href="../../graphics/shaders/shaders.html" class=" module">shaders</a>
</li>
</ul>
</li>
<li>
<a href="../../graphics/adapters.html" class=" module">adapters</a>
</li>
<li>
<a href="../../graphics/graphics.html" class=" module">graphics</a>
</li>
<li>
<a href="../../graphics/shaders.html" class=" module">shaders</a>
</li>
</ul>
</li>
<li class=" tree-view">
<a href="#" class="package">utility</a>
<ul class="tree-view">
<li>
<a href="../../utility/awesomium.html" class=" module">awesomium</a>
</li>
<li>
<a href="../../utility/concurrency.html" class=" module">concurrency</a>
</li>
<li>
<a href="../../utility/config.html" class=" module">config</a>
</li>
<li>
<a href="../../utility/filepath.html" class=" module">filepath</a>
</li>
<li>
<a href="../../utility/input.html" class="selected module">input</a>
</li>
<li>
<a href="../../utility/output.html" class=" module">output</a>
</li>
<li>
<a href="../../utility/string.html" class=" module">string</a>
</li>
<li>
<a href="../../utility/tasks.html" class=" module">tasks</a>
</li>
<li>
<a href="../../utility/time.html" class=" module">time</a>
</li>
</ul>
</li>
<li>
<a href="../../components.html" class=" module">components</a>
</li>
<li>
<a href="../../core.html" class=" module">core</a>
</li>
<li>
<a href="../../graphics.html" class=" module">graphics</a>
</li>
<li>
<a href="../../utility.html" class=" module">utility</a>
</li>
</ul>
<noscript>
<p style="color: red">The search functionality needs JavaScript enabled</p>
</noscript>
<div id="symbolSearchPane" style="display: none">
<p>
<input id="symbolSearch" type="text" placeholder="Search for symbols" onchange="performSymbolSearch(24);" onkeypress="this.onchange();" onpaste="this.onchange();" oninput="this.onchange();"/>
</p>
<ul id="symbolSearchResults" style="display: none"></ul>
<script type="application/javascript" src="../../symbols.js"></script>
<script type="application/javascript">
//<![CDATA[
var symbolSearchRootDir = "../../"; $('#symbolSearchPane').show();
//]]>
</script>
</div>
</nav>
<div id="main-contents">
<h1>Field Keyboard.F16</h1><!-- using block body in layout.dt--><!-- using block ddox.description in ddox.layout.dt-->
<p> Function 16 key
</p>
<section>
<h2>Declaration</h2>
<pre class="code prettyprint lang-d prototype">
enum <a href="../../utility/input/Keyboard.html">Keyboard</a>
{
// ...
F16,
// ...
}</pre>
</section><!-- using block ddox.sections in ddox.layout.dt-->
<!-- Default block ddox.members in ddox.layout.dt-->
<section>
<h2>Authors</h2><!-- using block ddox.authors in ddox.layout.dt-->
</section>
<section>
<h2>Copyright</h2><!-- using block ddox.copyright in ddox.layout.dt-->
</section>
<section>
<h2>License</h2><!-- using block ddox.license in ddox.layout.dt-->
</section>
</div>
</body>
</html> |
_includes/post-list.html | Lukasa/lukasa.github.io | <li>{% if post.date %}<span>{{ post.date | date: "%B %d, %Y" }}</span> » {% endif %}<a href="{{ post.url }}">{{ post.title }}</a></li> |
publish/blog/2014/06/26/arduino-workshop/index.html | agocs/agocs.org |
<!DOCTYPE HTML>
<html>
<head>
<script data-cfasync="false" type="text/javascript" src="//use.typekit.net/axj3cfp.js"></script>
<script data-cfasync="false" type="text/javascript">try{Typekit.load();}catch(e){}</script>
<meta charset="utf-8">
<title>Arduino Workshop | Agocs</title>
<meta name="author" content="Christopher Agocs">
<meta name="description" content="Sometimes I blog stuff"> <meta name="keywords" content="">
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">
<link href="/atom.xml" rel="alternate" title="Agocs" type="application/atom+xml">
<link rel="canonical" href="">
<link href="/favicon.png" rel="shortcut icon">
<link href="/stylesheets/screen.css" media="screen, projection" rel="stylesheet" type="text/css">
<!--[if lt IE 9]><script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
<script src="//ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js"></script>
<script type="text/javascript" src="/javascripts/jquery.fancybox.pack.js"></script>
<script language="Javascript" type="text/javascript">
$(document).ready(
function() {
(function($) {
$(".fancybox[data-content-id]").each(function() {
this.href = $(this).data('content-id');
});
$(".fancybox").fancybox({
beforeLoad: function() {
var el,
id = $(this.element).data('title-id');
if (id) {
el = $('#' + id);
if (el.length) {
this.title = el.html();
}
}
if ($(this).data('content')) {
this.content = $(this).data('content');
}
},
helpers: {
title: {
type: 'inside'
}
}
});
})(jQuery);
}
);
</script>
</head>
<body>
<header id="header" class="inner"><h1><a href="/">Agocs</a></h1>
<h4>Christopher Agocs</h4>
<nav id="main-nav"><ul>
<li><a href="/">Blog</a></li>
<li><a href="/social-media">Contact + Social Media</a></li>
<li><a href="/resume">Resume</a></li>
<li><a href="/projects">Projects</a></li>
<li><a href="/archives">Archive</a></li>
<li><a href="/robotfindskitten/non-kitten-item/">Robot Finds Kitten</a></li>
</ul>
</nav>
<nav id="mobile-nav">
<div class="alignleft menu">
<a class="button">Menu</a>
<div class="container"><ul>
<li><a href="/">Blog</a></li>
<li><a href="/social-media">Contact + Social Media</a></li>
<li><a href="/resume">Resume</a></li>
<li><a href="/projects">Projects</a></li>
<li><a href="/archives">Archive</a></li>
<li><a href="/robotfindskitten/non-kitten-item/">Robot Finds Kitten</a></li>
</ul>
</div>
</div>
<div class="alignright search">
<a class="button"></a>
<div class="container">
<form action="http://google.com/search" method="get">
<input type="text" name="q" results="0">
<input type="hidden" name="q" value="site:agocs.org">
</form>
</div>
</div>
</nav>
</header>
<div id="content" class="inner"><article class="post">
<h2 class="title">Arduino Workshop</h2>
<div class="entry-content"><p>Sometimes, shit doesn’t work out. For example: Mike’s Hard Lemonade contacted me at the <a href="http://sshchicago.org">Southside Hackerspace</a>, wanting us to modify a golf cart as part of their “Mike’s Hacks” summer ad campaign. I dumped a lot of time (and just a little money) into the project, but everything went south at the last minute.</p>
<p>But this isn’t about that.</p>
<p>At the same time, <a href="http://www.pinterest.com/r4v5/">Mason Donahue</a> put me in touch with <a href="https://www.facebook.com/ChicagoGirlsInComputing">Chicago Girls in Computing</a>. I put together a lesson plan, put together Arduino kits, made a powerpoint, and taught a class. It went awesome.</p>
<p>I had them assemble and program basic nightlights (LEDs turn on when the ambient light drops). They took that idea and ran with it.</p>
<p>The kits:</p>
<ul>
<li><a href="http://www.amazon.com/gp/product/B00761NDHI/ref=oh_details_o01_s00_i00?ie=UTF8&psc=1">Sainsmart Nano V3</a> — $14</li>
<li><a href="https://www.adafruit.com/products/64">Half-size breadboard</a> — $5</li>
<li><a href="https://www.adafruit.com/products/161">Photoresistor</a> — $1</li>
<li>10Kohm resistor</li>
<li>9v battery</li>
<li>9v battery leads</li>
<li>bunches of LEDs</li>
</ul>
<p>The total cost per student came out to about $27. I was able to pick up a bunch of plastic containers from the grocery store for $0.10 each, and the kits fit into the containers.</p>
<iframe src="http://www.slideshare.net/slideshow/embed_code/36339800" width="476" height="400" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe>
<p>They seemed to like it.</p>
<p><a href="http://agocs.smugmug.com/Other/misc/29939745_7n8ptc#!i=3343759361&k=5fwQCB6&lb=1&s=A" title="Photo & Video Sharing by SmugMug"><img src="http://agocs.smugmug.com/Other/misc/i-5fwQCB6/0/L/20140621151638-L.jpg" title="Photo & Video Sharing by SmugMug" alt="Photo & Video Sharing by SmugMug"></a></p>
<p><a href="http://agocs.smugmug.com/Other/misc/29939745_7n8ptc#!i=3343759349&k=hKHRThm&lb=1&s=A" title="Photo & Video Sharing by SmugMug"><img src="http://agocs.smugmug.com/Other/misc/i-hKHRThm/0/L/20140621151700-L.jpg" title="Photo & Video Sharing by SmugMug" alt="Photo & Video Sharing by SmugMug"></a></p>
<p><a href="http://agocs.smugmug.com/Other/misc/29939745_7n8ptc#!i=3343759469&k=3W5HDLF&lb=1&s=A" title=""><img src="http://agocs.smugmug.com/Other/misc/i-3W5HDLF/0/L/20140621151538-L.jpg" title="" alt=""></a></p>
<p><a href="http://agocs.smugmug.com/Other/misc/29939745_7n8ptc#!i=3343759220&k=9WTNCvh&lb=1&s=A" title=""><img src="http://agocs.smugmug.com/Other/misc/i-9WTNCvh/0/L/20140621151415-L.jpg" title="" alt=""></a></p>
<p>Major props go to Backstop, Stack Overflow, and DigitalOcean. I wrote them at the last minute saying it would sure be neat if I could give out some stickers at the workshop. Backstop gave me pads and pens, Stack Overflow sent stickers and markers, and DigitalOcean sent me a bunch of stickers (and chocolates).</p>
</div>
<div class="meta">
<div class="date">
<time datetime="2014-06-26T10:33:30-04:00" pubdate data-updated="true">Jun 26<span>th</span>, 2014</time></div>
</div></article>
<div class="share">
<div class="addthis_toolbox addthis_default_style ">
<a class="addthis_button_tweet"></a>
<!--- <a class="addthis_counter addthis_pill_style"></a> --->
</div>
<script type="text/javascript" src="http://s7.addthis.com/js/250/addthis_widget.js#pubid="></script>
</div>
<section id="comment">
<h2 class="title">Comments</h2>
<div id="disqus_thread" aria-live="polite"><noscript>Please enable JavaScript to view the <a href="http://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>
</div>
</section>
</div>
<footer id="footer" class="inner">Copyright © 2016
Christopher Agocs
<br>
Powered by Octopress.
</footer>
<script src="/javascripts/slash.js"></script>
<script src="/javascripts/jquery.fancybox.pack.js"></script>
<script type="text/javascript">
(function($){
$('.fancybox').fancybox();
})(jQuery);
</script> <!-- Delete or comment this line to disable Fancybox -->
<script type="text/javascript">
var disqus_shortname = 'agocs';
// var disqus_developer = 1;
var disqus_identifier = 'http://agocs.org/blog/2014/06/26/arduino-workshop/';
var disqus_url = 'http://agocs.org/blog/2014/06/26/arduino-workshop/';
var disqus_script = 'embed.js';
(function () {
var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
dsq.src = '//' + disqus_shortname + '.disqus.com/' + disqus_script;
(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
}());
</script>
</body>
</html>
|
doc/lib/opentok_rb.html | stijnster/opentok | <?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
<title>File: opentok.rb [RDoc Documentation]</title>
<link type="text/css" media="screen" href="../rdoc.css" rel="stylesheet" />
<script src="../js/jquery.js" type="text/javascript"
charset="utf-8"></script>
<script src="../js/thickbox-compressed.js" type="text/javascript"
charset="utf-8"></script>
<script src="../js/quicksearch.js" type="text/javascript"
charset="utf-8"></script>
<script src="../js/darkfish.js" type="text/javascript"
charset="utf-8"></script>
</head>
<body class="file file-popup">
<div id="metadata">
<dl>
<dt class="modified-date">Last Modified</dt>
<dd class="modified-date">Mon Apr 11 12:03:48 +0200 2011</dd>
<dt class="requires">Requires</dt>
<dd class="requires">
<ul>
<li>rubygems</li>
<li>net/http</li>
<li>uri</li>
<li>digest/md5</li>
<li>cgi</li>
<li>monkey_patches</li>
<li>open_tok/exceptions</li>
<li>open_tok/open_tok_sdk</li>
<li>open_tok/session</li>
</ul>
</dd>
</dl>
</div>
<div id="documentation">
<div class="description">
<h2>Description</h2>
</div>
</div>
</body>
</html>
|
appsensor-dot-org/site-contents/docs/v2.3.1/javadoc/org/owasp/appsensor/block/store/resources/package-use.html | ProZachJ/appsensor | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<!-- NewPage -->
<html lang="en">
<head>
<!-- Generated by javadoc (1.8.0) on Thu Jan 05 01:03:33 EST 2017 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Package org.owasp.appsensor.block.store.resources (appsensor-parent 2.3.1 API)</title>
<meta name="date" content="2017-01-05">
<link rel="stylesheet" type="text/css" href="../../../../../../stylesheet.css" title="Style">
<script type="text/javascript" src="../../../../../../script.js"></script>
</head>
<body>
<script type="text/javascript"><!--
try {
if (location.href.indexOf('is-external=true') == -1) {
parent.document.title="Uses of Package org.owasp.appsensor.block.store.resources (appsensor-parent 2.3.1 API)";
}
}
catch(err) {
}
//-->
</script>
<noscript>
<div>JavaScript is disabled on your browser.</div>
</noscript>
<div class="header">
<h1 title="Uses of Package org.owasp.appsensor.block.store.resources" class="title">Uses of Package<br>org.owasp.appsensor.block.store.resources</h1>
</div>
<div class="contentContainer">No usage of org.owasp.appsensor.block.store.resources</div>
<p class="legalCopy"><small>Copyright © 2017 <a href="http://www.owasp.org">The Open Web Application Security Project (OWASP)</a>. All rights reserved.</small></p>
</body>
</html>
|
app/views/Group/snippets/deleteGroupModal.scala.html | socia-platform/socia | @(group: Group)
@import helper._
@import models.enums.GroupType
<div class="modal-dialog">
<div class="modal-content">
<div class="modal-header">
<button type="button" class="close" data-dismiss="modal" aria-hidden="true">×</button>
<h4 class="modal-title hp-truncate" id="confirmModalLabel">
@if(group.groupType == GroupType.close) {
<span class="glyphicon glyphicon-lock"></span>
}
@if(group.groupType == GroupType.open) {
<span class="glyphicon glyphicon-globe"></span>
}
@if(group.groupType == GroupType.course) {
<span class="glyphicon glyphicon-briefcase"></span>
}
Gruppe löschen
</h4>
</div>
<div class="modal-body">
Möchtest Du <b>@truncate(group.title,30)</b> wirklich löschen?<br />
Alle dazugehörigen Post, Kommentare, Mitglieder, Medien werden ebenfalls gelöscht!
</div>
<div class="modal-footer">
<a type="button" class="btn btn-warning" href="@routes.GroupController.delete(group.id)">Ja</a>
<a type="button" class="btn btn-default" data-dismiss="modal">Nein</a>
</div>
</div>
</div> |
ext/c++/thirdpart/c++/boost/doc/html/boost/program_options/parse_config_f_idp16825440.html | yinchunlong/abelkhan-1 | <!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=US-ASCII">
<title>Function template parse_config_file</title>
<link rel="stylesheet" href="../../../../doc/src/boostbook.css" type="text/css">
<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
<link rel="home" href="../../index.html" title="The Boost C++ Libraries BoostBook Documentation Subset">
<link rel="up" href="../../program_options/reference.html#header.boost.program_options.parsers_hpp" title="Header <boost/program_options/parsers.hpp>">
<link rel="prev" href="parse_config__idp131600080.html" title="Function template parse_config_file">
<link rel="next" href="collect_unrecognized.html" title="Function template collect_unrecognized">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../boost.png"></td>
<td align="center"><a href="../../../../index.html">Home</a></td>
<td align="center"><a href="../../../../libs/libraries.htm">Libraries</a></td>
<td align="center"><a href="http://www.boost.org/users/people.html">People</a></td>
<td align="center"><a href="http://www.boost.org/users/faq.html">FAQ</a></td>
<td align="center"><a href="../../../../more/index.htm">More</a></td>
</tr></table>
<hr>
<div class="spirit-nav">
<a accesskey="p" href="parse_config__idp131600080.html"><img src="../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../../program_options/reference.html#header.boost.program_options.parsers_hpp"><img src="../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="collect_unrecognized.html"><img src="../../../../doc/src/images/next.png" alt="Next"></a>
</div>
<div class="refentry">
<a name="boost.program_options.parse_config_f_idp16825440"></a><div class="titlepage"></div>
<div class="refnamediv">
<h2><span class="refentrytitle">Function template parse_config_file</span></h2>
<p>boost::program_options::parse_config_file</p>
</div>
<h2 xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="refsynopsisdiv-title">Synopsis</h2>
<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="refsynopsisdiv"><pre class="synopsis"><span class="comment">// In header: <<a class="link" href="../../program_options/reference.html#header.boost.program_options.parsers_hpp" title="Header <boost/program_options/parsers.hpp>">boost/program_options/parsers.hpp</a>>
</span>
<span class="keyword">template</span><span class="special"><</span><span class="keyword">typename</span> charT<span class="special">></span>
<span class="identifier">BOOST_PROGRAM_OPTIONS_DECL</span> <a class="link" href="basic_parsed_options.html" title="Class template basic_parsed_options">basic_parsed_options</a><span class="special"><</span> <span class="identifier">charT</span> <span class="special">></span>
<span class="identifier">parse_config_file</span><span class="special">(</span><span class="keyword">const</span> <span class="keyword">char</span> <span class="special">*</span> filename<span class="special">,</span> <span class="keyword">const</span> <a class="link" href="options_description.html" title="Class options_description">options_description</a> <span class="special">&</span><span class="special">,</span>
<span class="keyword">bool</span> allow_unregistered <span class="special">=</span> <span class="keyword">false</span><span class="special">)</span><span class="special">;</span></pre></div>
<div class="refsect1">
<a name="idp369413184"></a><h2>Description</h2>
<p>Parse a config file.</p>
<p>Read from file with the given name. The character type is passed to the file stream. </p>
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
<td align="right"><div class="copyright-footer">Copyright © 2002-2004 Vladimir Prus<p>Distributed under the Boost Software License, Version 1.0.
(See accompanying file <code class="filename">LICENSE_1_0.txt</code> or copy at
<a href="http://www.boost.org/LICENSE_1_0.txt" target="_top">http://www.boost.org/LICENSE_1_0.txt</a>)
</p>
</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
<a accesskey="p" href="parse_config__idp131600080.html"><img src="../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../../program_options/reference.html#header.boost.program_options.parsers_hpp"><img src="../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="collect_unrecognized.html"><img src="../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>
|
api/v0.6.2/core/scene/Scene.loadObjects.html | Circular-Studios/Dash-Docs |
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8"/><!-- using block title in layout.dt--><!-- using block ddox.defs in ddox.layout.dt--><!-- using block ddox.title in ddox.layout.dt-->
<title>Method Scene.loadObjects</title>
<link rel="stylesheet" type="text/css" href="../../styles/ddox.css"/>
<link rel="stylesheet" href="../../prettify/prettify.css" type="text/css"/>
<script type="text/javascript" src="../../scripts/jquery.js">/**/</script>
<script type="text/javascript" src="../../prettify/prettify.js">/**/</script>
<script type="text/javascript" src="../../scripts/ddox.js">/**/</script>
</head>
<body onload="prettyPrint(); setupDdox();">
<nav id="main-nav"><!-- using block navigation in layout.dt-->
<ul class="tree-view">
<li class="collapsed tree-view">
<a href="#" class="package">components</a>
<ul class="tree-view">
<li>
<a href="../../components/animation.html" class=" module">animation</a>
</li>
<li>
<a href="../../components/assetanimation.html" class=" module">assetanimation</a>
</li>
<li>
<a href="../../components/assets.html" class=" module">assets</a>
</li>
<li>
<a href="../../components/camera.html" class=" module">camera</a>
</li>
<li>
<a href="../../components/icomponent.html" class=" module">icomponent</a>
</li>
<li>
<a href="../../components/lights.html" class=" module">lights</a>
</li>
<li>
<a href="../../components/material.html" class=" module">material</a>
</li>
<li>
<a href="../../components/mesh.html" class=" module">mesh</a>
</li>
<li>
<a href="../../components/userinterface.html" class=" module">userinterface</a>
</li>
</ul>
</li>
<li class=" tree-view">
<a href="#" class="package">core</a>
<ul class="tree-view">
<li>
<a href="../../core/dgame.html" class=" module">dgame</a>
</li>
<li>
<a href="../../core/gameobject.html" class=" module">gameobject</a>
</li>
<li>
<a href="../../core/gameobjectcollection.html" class=" module">gameobjectcollection</a>
</li>
<li>
<a href="../../core/prefabs.html" class=" module">prefabs</a>
</li>
<li>
<a href="../../core/properties.html" class=" module">properties</a>
</li>
<li>
<a href="../../core/reflection.html" class=" module">reflection</a>
</li>
<li>
<a href="../../core/scene.html" class="selected module">scene</a>
</li>
</ul>
</li>
<li class="collapsed tree-view">
<a href="#" class="package">graphics</a>
<ul class="tree-view">
<li class="collapsed tree-view">
<a href="#" class="package">adapters</a>
<ul class="tree-view">
<li>
<a href="../../graphics/adapters/adapter.html" class=" module">adapter</a>
</li>
<li>
<a href="../../graphics/adapters/linux.html" class=" module">linux</a>
</li>
<li>
<a href="../../graphics/adapters/mac.html" class=" module">mac</a>
</li>
<li>
<a href="../../graphics/adapters/win32.html" class=" module">win32</a>
</li>
</ul>
</li>
<li class="collapsed tree-view">
<a href="#" class="package">shaders</a>
<ul class="tree-view">
<li class="collapsed tree-view">
<a href="#" class="package">glsl</a>
<ul class="tree-view">
<li>
<a href="../../graphics/shaders/glsl/ambientlight.html" class=" module">ambientlight</a>
</li>
<li>
<a href="../../graphics/shaders/glsl/animatedgeometry.html" class=" module">animatedgeometry</a>
</li>
<li>
<a href="../../graphics/shaders/glsl/directionallight.html" class=" module">directionallight</a>
</li>
<li>
<a href="../../graphics/shaders/glsl/geometry.html" class=" module">geometry</a>
</li>
<li>
<a href="../../graphics/shaders/glsl/pointlight.html" class=" module">pointlight</a>
</li>
<li>
<a href="../../graphics/shaders/glsl/userinterface.html" class=" module">userinterface</a>
</li>
</ul>
</li>
<li>
<a href="../../graphics/shaders/glsl.html" class=" module">glsl</a>
</li>
<li>
<a href="../../graphics/shaders/shaders.html" class=" module">shaders</a>
</li>
</ul>
</li>
<li>
<a href="../../graphics/adapters.html" class=" module">adapters</a>
</li>
<li>
<a href="../../graphics/graphics.html" class=" module">graphics</a>
</li>
<li>
<a href="../../graphics/shaders.html" class=" module">shaders</a>
</li>
</ul>
</li>
<li class="collapsed tree-view">
<a href="#" class="package">utility</a>
<ul class="tree-view">
<li>
<a href="../../utility/awesomium.html" class=" module">awesomium</a>
</li>
<li>
<a href="../../utility/concurrency.html" class=" module">concurrency</a>
</li>
<li>
<a href="../../utility/config.html" class=" module">config</a>
</li>
<li>
<a href="../../utility/filepath.html" class=" module">filepath</a>
</li>
<li>
<a href="../../utility/input.html" class=" module">input</a>
</li>
<li>
<a href="../../utility/output.html" class=" module">output</a>
</li>
<li>
<a href="../../utility/string.html" class=" module">string</a>
</li>
<li>
<a href="../../utility/time.html" class=" module">time</a>
</li>
</ul>
</li>
<li>
<a href="../../components.html" class=" module">components</a>
</li>
<li>
<a href="../../core.html" class=" module">core</a>
</li>
<li>
<a href="../../graphics.html" class=" module">graphics</a>
</li>
<li>
<a href="../../utility.html" class=" module">utility</a>
</li>
</ul>
<noscript>
<p style="color: red">The search functionality needs JavaScript enabled</p>
</noscript>
<div id="symbolSearchPane" style="display: none">
<p>
<input id="symbolSearch" type="text" placeholder="Search for symbols" onchange="performSymbolSearch(24);" onkeypress="this.onchange();" onpaste="this.onchange();" oninput="this.onchange();"/>
</p>
<ul id="symbolSearchResults" style="display: none"></ul>
<script type="application/javascript" src="../../symbols.js"></script>
<script type="application/javascript">
//<![CDATA[
var symbolSearchRootDir = "../../"; $('#symbolSearchPane').show();
//]]>
</script>
</div>
</nav>
<div id="main-contents">
<h1>Method Scene.loadObjects</h1><!-- using block body in layout.dt--><!-- Default block ddox.description in ddox.layout.dt--><!-- Default block ddox.sections in ddox.layout.dt--><!-- using block ddox.members in ddox.layout.dt-->
<p> Load all <a href="../../core/scene/Scene.objects.html"><code class="prettyprint lang-d">objects</code></a> inside the specified folder in FilePath.Objects.
</p>
<section></section>
<section>
<h2>Prototype</h2>
<pre class="code prettyprint lang-d prototype">
void loadObjects(
string objectPath
) shared final;</pre>
</section>
<section><h2>Parameters</h2>
<table><col class="caption"><tr><th>Name</th><th>Description</th></tr>
<tr><td id="objectPath">objectPath</td><td> The folder location inside of /Objects to look for <a href="../../core/scene/Scene.objects.html"><code class="prettyprint lang-d">objects</code></a> in.
</td></tr>
</table>
</section>
<section>
<h2>Authors</h2><!-- using block ddox.authors in ddox.layout.dt-->
</section>
<section>
<h2>Copyright</h2><!-- using block ddox.copyright in ddox.layout.dt-->
</section>
<section>
<h2>License</h2><!-- using block ddox.license in ddox.layout.dt-->
</section>
</div>
</body>
</html> |
app/perf.html | relateiq/popular | <!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<title>popgun demo</title>
<link rel="stylesheet" type="text/css" href="app.css">
</head>
<body>
<h2>Popgun Perf</h2>
<form id="perfGeneratorForm">
<input name="numberInput" type="number"/>
<button>Generate!</button>
</form>
<div id="popgunPerfSection"></div>
<script src="app.js"></script>
</body>
</html>
|
test/cases/hmr/expected/webpack-5/main.css | faceyspacey/extract-css-chunks-webpack-plugin | @import url(https://some/other/external/css);
@import url(https://some/external/css);
body {
background: red;
}
.c {
background: red;
}
.c {
color: yellow;
}
.b {
background: red;
}
.b {
color: yellow;
}
|
doc/html/aabbtree_8cpp.html | Playermet/gbmath | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=9"/>
<meta name="generator" content="Doxygen 1.8.4"/>
<title>gbmath: aabbtree.cpp File Reference</title>
<link href="tabs.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="jquery.js"></script>
<script type="text/javascript" src="dynsections.js"></script>
<link href="doxygen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="top"><!-- do not remove this div, it is closed by doxygen! -->
<div id="titlearea">
<table cellspacing="0" cellpadding="0">
<tbody>
<tr style="height: 56px;">
<td id="projectlogo"><img alt="Logo" src="logo.jpg"/></td>
<td style="padding-left: 0.5em;">
<div id="projectname">gbmath
 <span id="projectnumber">v0.05</span>
</div>
<div id="projectbrief">c++ math library</div>
</td>
</tr>
</tbody>
</table>
</div>
<!-- end header part -->
<!-- Generated by Doxygen 1.8.4 -->
<div id="navrow1" class="tabs">
<ul class="tablist">
<li><a href="index.html"><span>Main Page</span></a></li>
<li><a href="pages.html"><span>Related Pages</span></a></li>
<li><a href="namespaces.html"><span>Namespaces</span></a></li>
<li><a href="annotated.html"><span>Classes</span></a></li>
<li class="current"><a href="files.html"><span>Files</span></a></li>
</ul>
</div>
<div id="navrow2" class="tabs2">
<ul class="tablist">
<li><a href="files.html"><span>File List</span></a></li>
<li><a href="globals.html"><span>File Members</span></a></li>
</ul>
</div>
</div><!-- top -->
<div class="header">
<div class="summary">
<a href="#namespaces">Namespaces</a> |
<a href="#namespaces">Constant Groups</a> </div>
<div class="headertitle">
<div class="title">aabbtree.cpp File Reference</div> </div>
</div><!--header-->
<div class="contents">
<div class="textblock"><code>#include "<a class="el" href="__gbmath_8h_source.html">_gbmath.h</a>"</code><br/>
</div>
<p><a href="aabbtree_8cpp_source.html">Go to the source code of this file.</a></p>
<table class="memberdecls">
<tr class="heading"><td colspan="2"><h2 class="groupheader"><a name="namespaces"></a>
Namespaces</h2></td></tr>
<tr class="memitem:namespacegbmath"><td class="memItemLeft" align="right" valign="top"> </td><td class="memItemRight" valign="bottom"><a class="el" href="namespacegbmath.html">gbmath</a></td></tr>
<tr class="memdesc:namespacegbmath"><td class="mdescLeft"> </td><td class="mdescRight">math operations and structures . <br/></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
</table><table class="memberdecls">
<tr class="heading"><td colspan="2"><h2 class="groupheader"><a name="namespaces"></a>
Constant Groups</h2></td></tr>
<tr class="memitem:namespacegbmath"><td class="memItemLeft" align="right" valign="top"> </td><td class="memItemRight" valign="bottom"><a class="el" href="namespacegbmath.html">gbmath</a></td></tr>
<tr class="memdesc:namespacegbmath"><td class="mdescLeft"> </td><td class="mdescRight">math operations and structures . <br/></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
</table>
</div><!-- contents -->
<hr class="footer"/>
<!--address class="footer"-->
<!--small-->
<br>
<b>Project page:</b> <a target="_blank" href="https://code.google.com/p/gbmath/">https://code.google.com/p/gbmath/</a> <br>
<b>Doc page:</b> <a target="_blank" href="http://www.it.ks777.ru/docs">http://www.it.ks777.ru/docs</a> <br>
<br>
Generated on Sat Jul 27 2013 08:09:04 for gbmath by  
<a href="http://www.doxygen.org/index.html">
<img class="footer" src="doxygen.png" alt="doxygen"/>
</a> 1.8.4
|
examples/cra-ts-kitchen-sink/public/index.html | storybooks/storybook | <!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<link rel="icon" href="%PUBLIC_URL%/favicon.ico" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<meta name="theme-color" content="#000000" />
<meta name="description" content="Web site created using create-react-app" />
<link rel="apple-touch-icon" href="logo192.png" />
<!--
manifest.json provides metadata used when your web app is installed on a
user's mobile device or desktop. See https://developers.google.com/web/fundamentals/web-app-manifest/
-->
<link rel="manifest" href="%PUBLIC_URL%/manifest.json" />
<!--
Notice the use of %PUBLIC_URL% in the tags above.
It will be replaced with the URL of the `public` folder during the build.
Only files inside the `public` folder can be referenced from the HTML.
Unlike "/favicon.ico" or "favicon.ico", "%PUBLIC_URL%/favicon.ico" will
work correctly both with client-side routing and a non-root public URL.
Learn how to configure a non-root public URL by running `npm run build`.
-->
<title>React App</title>
</head>
<body>
<noscript>You need to enable JavaScript to run this app.</noscript>
<div id="root"></div>
<!--
This HTML file is a template.
If you open it directly in the browser, you will see an empty page.
You can add webfonts, meta tags, or analytics to this file.
The build step will place the bundled scripts into the <body> tag.
To begin the development, run `npm start` or `yarn start`.
To create a production bundle, use `npm run build` or `yarn build`.
-->
</body>
</html>
|
public/stylesheets/manual.oldie.css | shunjikonishi/jquery-formbuilder | @charset "utf-8";
body {
overflow:auto;
}
.copy-right {
margin-top:20px;
width: 100%;
}
|
src/frontend/dev_puzzles/coevoludens/partials/trendspyramid.component.tpl.html | Cha-OS/KnAllEdge | <div class="brainstorming brainstorming-form" id="popupContainer">
<md-dialog #brainstormingFormDialog class="brainstormingFormDialog">
<md-dialog-title>Brainstorming</md-dialog-title>
<div class="md-inline-form">
<form *ngIf="brainstormingFormActive" (ngSubmit)="onSubmit(brainstormingFormTabs.selectedIndex)" #brainstormingForm="ngForm" layout="column" class="inline-form">
<!-- {{brainstormingForm.valid}}<br/>
{{brainstormingForm.form.valid}}<br/> -->
<!-- {{JSON.stringify(brainstormingForm)}}<br/>
{{JSON.stringify(brainstormingForm.form)}}<br/> -->
<!-- {{diagnostic}} -->
<md-tab-group #brainstormingFormTabs (focusChange) = "focusChanged(brainstormingFormTabs.selectedIndex)" [selectedIndex] = "selectedIndex()" (selectChange) = "selectedChanged(brainstormingFormTabs.selectedIndex)">
<md-tab [disabled]="isDisabled(0)">
<template md-tab-label>{{getTitle(0)}}</template>
<template md-tab-content>
<md-content class="md-padding">
</md-content>
</template>
</md-tab>
<md-tab [disabled]="isDisabled(1)">
<!-- <md-tab ng-disabled="true" [ng-disabled]="true" disabled="true" [disabled]="true"> -->
<template md-tab-label>{{getTitle(1)}}</template>
<template md-tab-content>
<md-content class="md-padding">
</md-content>
</template>
</md-tab>
</md-tab-group>
<div layout="row">
<!-- type="button" is required or otherwise button reacts as type="submit", like it is default type-->
<button md-button type="button" (click)="close(false)">Cancel</button>
<!-- <button md-button type="button" (click)="nextPhase()">Next Phase</button> -->
</div>
</form>
</div>
<!-- <md-dialog-actions>
<button md-button (click)="close(false)">Cancel</button>
<button md-button (click)="close(true)">Create</button>
</md-dialog-actions> -->
</md-dialog>
</div>
|
components/x-tags/index.html | gnomeontherun/web-components-today | <!DOCTYPE html>
<html>
<head>
<script src="../bower_components/platform/platform.js"></script>
<link rel="import" href="github-buttons.html">
</head>
<body>
<github-buttons user="w3c" repo="webcomponents" size="large"></github-buttons>
</body>
</html>
|
main/libc/unix/linux_like/linux/constant.RTF_XRESOLVE.html | malept/guardhaus | <!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="refresh" content="0;URL=../../../../libc/constant.RTF_XRESOLVE.html">
</head>
<body>
<p>Redirecting to <a href="../../../../libc/constant.RTF_XRESOLVE.html">../../../../libc/constant.RTF_XRESOLVE.html</a>...</p>
<script>location.replace("../../../../libc/constant.RTF_XRESOLVE.html" + location.search + location.hash);</script>
</body>
</html> |
_posts/2012/05/2012-05-02-the-good-and-the-bad-of-it.html | FranciscoCanas/website | ---
layout: post
date: 2012-05-02
time: "09:00:00"
author: "Neil Chue Hong"
title: The Good and the Bad of It
category: ["Assessment", "University College London"]
---
<p>We've come to the end of a hot, slightly sweaty, two days of learning in UCL and have just done a straw poll of participants of the good and bad points of this bootcamp. Something that was trialled at UCL was asking participants to sign up in small (3-4 people) teams drawn from their local research group. In total, we had a little over 40 learners and 10 helpers. We also taught the version control portion using EasyMercurial (thanks to Chris Cannam from SoundSoftware).</p>
<p>Here's what we learned...</p>
<h3>Good</h3>
<ul>
<li>Beginner friendly</li>
<li>Easy learning curve</li>
<li>Now know how to use SQL</li>
<li>Doesn't matter what programming language I used in the first place</li>
<li>Version control for the win</li>
<li>Taught functional programming rather than object-oriented</li>
<li>Material backed up by anecdotes and evidence</li>
<li>Good at giving thoughts rather than skills</li>
<li>Can go back and share with other members of the group</li>
<li>Killed my fear of version control</li>
<li>Give tips on good programming practices</li>
<li>Anything new was given with the why as well as the what</li>
<li>Introduction to systematic testing</li>
<li>Best balance of typing, testing and listening</li>
<li>Good ratio of helpers to students</li>
<li>Greg's digressions keep your mind active</li>
<li>Learned feedback technique of using coloured sticky notes</li>
<li>Test driven development</li>
<li>Quoted Alan Turing (programs are just a type of data)</li>
<li>Working in pairs</li>
<li>Live coding (realtime typing)</li>
<li>Being forced to use python</li>
<li>Psychological aspects, and how it relates to programming</li>
<li>Always good to reinforce the learning of things you've heard before</li>
<li>Interaction with participants at workshops — both in workshop and in pub</li>
<li>Website is a good resource</li>
<li>Insight (for a sysadmin) of how the researchers I support work</li>
</ul>
<h3>Bad</h3>
<ul>
<li>Can't afford to buy all the books referenced</li>
<li>Too early a start [9am start both days in central London]</li>
<li>Too much to take in</li>
<li>Not enough functional programming</li>
<li>Lower level than group is used to</li>
<li>Need coffee at the start of the morning [which we didn't have on day 2]</li>
<li>Problems with the wireless network</li>
<li>Need biscuits in the afternoon</li>
<li>No handouts [though SWC does this because best practice suggests you shouldn't give out handouts at the start]</li>
<li>Lack of air conditioning</li>
<li>Too short (not enough days) [SWC experience shows that 5 days F2F didn't work, will have online followups]</li>
<li>Not clear when you should be furiously catching up on typing</li>
<li>Greg's too fast</li>
<li>Helpers not physically interspersed amongst tutors</li>
<li>Room too small</li>
<li>Not enough desks / table arrangements</li>
<li>Couldn't find nose on list of required software</li>
<li>No documentation on how to get nose running on a windows system</li>
<li>No toilets / running water on the same floor [we broke the toilets and the lift!]</li>
<li>Microphone would have been good</li>
<li>Recommending Cygwin rather than VMware or Virtualbox [but people want to come out with a working setup...]</li>
<li>Implied endorsement of bittorrent for illegal activities (plus smartass comments)</li>
</ul>
<p>What does this tell us? Probably that the teaching environment has a much bigger impact than you might expect, and that we should do all we can to fix it upstream. Also that Greg talks and types too fast!</p>
<p>We're going to have plenty of chances to see how these good and bad points change as we go on to the next workshops — collecting the evidence so that we can understand how to teach people better.</p>
|
templates/index.ejs.html | kengz/lomath | <!DOCTYPE html>
<html lang="en" id="docs">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<title><%= title %></title>
<link rel="stylesheet" href="styles.css" media="all">
<link rel="stylesheet" href="//cdnjs.cloudflare.com/ajax/libs/highlight.js/8.6/styles/default.min.css">
</head>
<body>
<div class="toc-container">
<h2><code><a href="http://kengz.github.io/lomath/"><%= title %></a></code></h2>
<ul>
<li><a href="#">Introduction</a></li>
<li><a href="https://github.com/kengz/lomath">Github Repository</a></li>
<li><a href="tests.html">Test suite</a></li>
<li><a href="annotated/index.html">Annotated Source</a></li>
</ul>
<%- apiToc %>
</div>
<div class="doc-container">
<div>
<%- readme %>
<h2>API documentation</h2>
<%- apiDoc %>
</div>
</div>
<script src="//cdnjs.cloudflare.com/ajax/libs/highlight.js/8.6/highlight.min.js"></script>
</body>
</html>
|
client/components/search/resultCard.html | Epotignano/MEAN-architecture-setup | <div class="row">
<div class="col-md-12">
<div class="row">
<div class="col-md-12">
<h4>
<a href="{{ card.element.url }}" target="_blank">
<p ng-bind-html="card.element.title"></p>
</a>
</h4>
</div>
</div>
<div class="row">
<div class="col-md-12">
<p ng-bind-html="card.element.abstract">
</p>
</div>
</div>
</div>
</div>
|
less/libs/prism.css | jacobshafi/jacobshafi.github.io | /* http://prismjs.com/download.html?themes=prism&languages=markup+css+clike+javascript+applescript+aspnet+c+csharp+cpp+coffeescript+css-extras+git+haml+handlebars+jade+java+less+markdown+objectivec+perl+php+php-extras+python+jsx+ruby+scss+scheme+smarty+sql+stylus+swift+typescript&plugins=line-numbers */
/**
* prism.js default theme for JavaScript, CSS and HTML
* Based on dabblet (http://dabblet.com)
* @author Lea Verou
*/
code[class*="language-"],
pre[class*="language-"] {
color: #333;
text-shadow: 0 1px white;
font-family: Consolas, Monaco, 'Andale Mono', monospace;
direction: ltr;
text-align: left;
white-space: pre;
word-spacing: normal;
word-break: normal;
line-height: 1.5;
-moz-tab-size: 4;
-o-tab-size: 4;
tab-size: 4;
-webkit-hyphens: none;
-moz-hyphens: none;
-ms-hyphens: none;
hyphens: none;
}
pre[class*="language-"]::-moz-selection, pre[class*="language-"] ::-moz-selection,
code[class*="language-"]::-moz-selection, code[class*="language-"] ::-moz-selection {
text-shadow: none;
background: #b3d4fc;
}
pre[class*="language-"]::selection, pre[class*="language-"] ::selection,
code[class*="language-"]::selection, code[class*="language-"] ::selection {
text-shadow: none;
background: #b3d4fc;
}
@media print {
code[class*="language-"],
pre[class*="language-"] {
text-shadow: none;
}
}
/* Code blocks */
pre[class*="language-"] {
padding: 1em;
margin: .5em 0;
overflow: auto;
}
:not(pre) > code[class*="language-"],
pre[class*="language-"] {
background: #f5f2f0;
}
/* Inline code */
:not(pre) > code[class*="language-"] {
padding: .1em;
border-radius: .3em;
}
.token.comment,
.token.prolog,
.token.doctype,
.token.cdata {
color: slategray;
}
.token.punctuation {
color: #999;
}
.namespace {
opacity: .7;
}
.token.property,
.token.tag,
.token.boolean,
.token.number,
.token.constant,
.token.symbol,
.token.deleted {
color: #905;
}
.token.selector,
.token.attr-name,
.token.string,
.token.char,
.token.builtin,
.token.inserted {
color: #690;
}
.token.operator,
.token.entity,
.token.url,
.language-css .token.string,
.style .token.string {
color: #a67f59;
background: hsla(0, 0%, 100%, .5);
}
.token.atrule,
.token.attr-value,
.token.keyword {
color: #07a;
}
.token.function {
color: #DD4A68;
}
.token.regex,
.token.important,
.token.variable {
color: #e90;
}
.token.important,
.token.bold {
font-weight: bold;
}
.token.italic {
font-style: italic;
}
.token.entity {
cursor: help;
}
pre.line-numbers {
position: relative;
padding-left: 3.8em;
counter-reset: linenumber;
}
pre.line-numbers > code {
position: relative;
}
.line-numbers .line-numbers-rows {
position: absolute;
pointer-events: none;
top: 0;
font-size: 100%;
left: -3.8em;
width: 3em; /* works for line-numbers below 1000 lines */
letter-spacing: -1px;
border-right: 1px solid #999;
-webkit-user-select: none;
-moz-user-select: none;
-ms-user-select: none;
user-select: none;
}
.line-numbers-rows > span {
pointer-events: none;
display: block;
counter-increment: linenumber;
}
.line-numbers-rows > span:before {
content: counter(linenumber);
color: #999;
display: block;
padding-right: 0.8em;
text-align: right;
}
|
tag/帶球/json/index.html | sunnyKiwi/JustCopy | {
"posts": [
{
"url": "/sport/baseball/2018/01/02/BaseballM.1514901366.A.7D8.html",
"title": "巧遇野生陳冠宇",
"image": "https://i.imgur.com/kYrqzl4.jpg",
"push": "23",
"boo": "2",
"date": "2018-01-02 21:56:04 +0800",
"boardName": "棒球",
"boardLink": "/category/baseball"
}
]
}
|
lit2go.ok/107/the-hunchback-of-notre-dame/1994/book-eleventh-chapter-3/index.html | adrianosb/HtmlToText | <!DOCTYPE html>
<html>
<head>
<title>Book Eleventh, Chapter 3 | The Hunchback of Notre Dame | Victor Hugo | Lit2Go ETC</title>
<link rel="stylesheet" href="http://etc.usf.edu/lit2go/css/screenless.css" type="text/css" media="screen" title="no title" charset="utf-8">
<link rel="stylesheet" href="http://etc.usf.edu/lit2go/css/printless.css" type="text/css" media="print" title="no title" charset="utf-8">
<!--[if lt IE 9]>
<script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
<script type="text/javascript" src="//ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js"></script>
<script type="text/javascript" defer src="http://etc.usf.edu/lit2go/js/js.min.js"></script>
<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-5574891-1']);
_gaq.push(['_trackPageview']);
(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();
$(document).ready(function() {
$('img').unveil();
$('#contactable').contactable({
url: 'http://etc.usf.edu/lit2go/welcome/feedback/',
subject: 'Lit2Go Feedback — Book Eleventh, Chapter 3 | The Hunchback of Notre Dame | Victor Hugo — http://etc.usf.edu/lit2go/107/the-hunchback-of-notre-dame/1994/book-eleventh-chapter-3/'
});
});
</script>
</head>
<body>
<div class="page"> <header>
<h1>
<a href="http://etc.usf.edu/lit2go/">Lit<span class="blue">2</span>Go</a>
</h1>
<ul>
<li id="search"><form action="http://etc.usf.edu/lit2go/search/"><input type="text" name="q" placeholder="Search" value=""></form></li>
</ul>
</header>
<nav id="shell">
<ul>
<li><a href="http://etc.usf.edu/lit2go/authors/" class="">Authors</a></li>
<li><a href="http://etc.usf.edu/lit2go/books/" class="selected">Books</a></li>
<li><a href="http://etc.usf.edu/lit2go/genres/" class="">Genres</a></li>
<li><a href="http://etc.usf.edu/lit2go/collections/" class="">Collections</a></li>
<li><a href="http://etc.usf.edu/lit2go/readability/" class="">Readability</a></li>
</ul>
</nav>
<section id="content">
<div id="contactable"><!-- contactable html placeholder --></div>
<div id="page_content">
<header>
<h2>
<a href="http://etc.usf.edu/lit2go/107/the-hunchback-of-notre-dame/">The Hunchback of Notre Dame</a>
</h2>
<h3>
by <a href="http://etc.usf.edu/lit2go/authors/116/victor-hugo/">Victor Hugo</a>
</h3>
<h4>
Book Eleventh, Chapter 3 </h4>
</header>
<div id="default">
<details open>
<summary>
Additional Information
</summary>
<div id="columns">
<ul>
<li>
<strong>Year Published:</strong>
1831 </li>
<li>
<strong>Language:</strong>
English </li>
<li>
<strong>Country of Origin:</strong>
France </li>
<li>
<strong>Source:</strong>
Hapsgood, I., trans. (1831). <em>The Hunchback of Notre Dame</em>. New York: Carey, Lea, and Blanchard. </li>
</ul>
</div>
<div id="columns">
<ul>
<li>
<strong>Readability:</strong>
<ul>
<li>
Flesch–Kincaid Level:
<a href="http://etc.usf.edu/lit2go/readability/flesch_kincaid_grade_level/12/" title="Flesch–Kincaid Grade Level 12.0">12.0</a>
</li>
</ul>
</li>
<li>
<strong>Word Count:</strong>
273 </li>
</ul>
</div>
<div id="columns">
<ul>
<li>
<strong>Genre:</strong>
<a href="http://etc.usf.edu/lit2go/genres/9/romance/">Romance</a>
</li>
<li>
<strong>Keywords:</strong>
culture, fate, love, loyalty </li>
<li>
<a class="btn" data-toggle="modal" href="#cite_this" >✎ Cite This</a>
</li>
<li>
<!-- AddThis Button BEGIN -->
<div class="addthis_toolbox addthis_default_style ">
<a addthis:ui_delay="500" href="http://www.addthis.com/bookmark.php?v=250&pub=roywinkelman" class="addthis_button_compact">Share</a>
<span class="addthis_separator">|</span>
<a class="addthis_button_preferred_1"></a>
<a class="addthis_button_preferred_2"></a>
<a class="addthis_button_preferred_3"></a>
<a class="addthis_button_preferred_4"></a>
</div>
<script type="text/javascript">$($.getScript("http://s7.addthis.com/js/250/addthis_widget.js?pub=roywinkelman"))</script>
<!-- <script type="text/javascript" src="http://s7.addthis.com/js/250/addthis_widget.js?pub=roywinkelman"></script> -->
<!-- AddThis Button END -->
</li>
</ul>
</div>
<h4>Downloads</h4>
<ul id="downloads">
<li>
<a href="http://etc.usf.edu/lit2go/audio/mp3/the-hunchback-of-notre-dame-059-book-eleventh-chapter-3.1994.mp3">Audio</a>
</li>
</ul>
<hr>
</details>
<div class="modal hide" id="cite_this">
<script>
$($('#myTab a').click(function (e) {e.preventDefault();$('#myTab a[href="#apa"]').tab('show');}));
</script>
<nav>
<ul id="myTab">
<li class="active">
<a href="#apa" data-toggle="tab">APA</a>
</li>
<li>
<a href="#mla" data-toggle="tab">MLA</a>
</li>
<li>
<a href="#chicago" data-toggle="tab">Chicago</a>
</li>
</ul>
</nav>
<div class="tab-content">
<div class="content tab-pane hide active" id="apa">
<p class="citation">
Hugo, V. (1831). Book Eleventh, Chapter 3. <em>The Hunchback of Notre Dame</em> (Lit2Go Edition). Retrieved February 15, 2016, from <span class="faux_link">http://etc.usf.edu/lit2go/107/the-hunchback-of-notre-dame/1994/book-eleventh-chapter-3/</span>
</p>
</div>
<div class="content tab-pane" id="mla">
<p class="citation">
Hugo, Victor. "Book Eleventh, Chapter 3." <em>The Hunchback of Notre Dame</em>. Lit2Go Edition. 1831. Web. <<span class="faux_link">http://etc.usf.edu/lit2go/107/the-hunchback-of-notre-dame/1994/book-eleventh-chapter-3/</span>>. February 15, 2016.
</p>
</div>
<div class="content tab-pane" id="chicago">
<p class="citation">
Victor Hugo, "Book Eleventh, Chapter 3," <em>The Hunchback of Notre Dame</em>, Lit2Go Edition, (1831), accessed February 15, 2016, <span class="faux_link">http://etc.usf.edu/lit2go/107/the-hunchback-of-notre-dame/1994/book-eleventh-chapter-3/</span>.
</p>
</div>
</div>
</div>
<span class="top"> <nav class="passage">
<ul>
<li><a href="http://etc.usf.edu/lit2go/107/the-hunchback-of-notre-dame/1991/book-eleventh-chapter-2/" title="Book Eleventh, Chapter 2" class="back">Back</a></li>
<li><a href="http://etc.usf.edu/lit2go/107/the-hunchback-of-notre-dame/1995/book-eleventh-chapter-4/" title="Book Eleventh, Chapter 4" class="next">Next</a></li>
</ul>
</nav>
</span>
<div id="shrink_wrap">
<div id="i_apologize_for_the_soup">
<audio controls style="width:99%;">
<source src="http://etc.usf.edu/lit2go/audio/mp3/the-hunchback-of-notre-dame-059-book-eleventh-chapter-3.1994.mp3" type="audio/mpeg" />
<source src="http://etc.usf.edu/lit2go/audio/ogg/the-hunchback-of-notre-dame-059-book-eleventh-chapter-3.1994.ogg" type="audio/ogg" />
The embedded audio player requires a modern internet browser. You should visit <a href="http://browsehappy.com/">Browse Happy</a> and update your internet browser today!
</audio>
<p>
Towards evening on that day, when the judiciary officers of the bishop came to pick up from the pavement of the Parvis the dislocated corpse of the archdeacon, Quasimodo had disappeared.</p>
<p>
A great many rumors were in circulation with regard to this adventure. No one doubted but that the day had come when, in accordance with their compact, Quasimodo, that is to say, the devil, was to carry off Claude Frollo, that is to say, the sorcerer. It was presumed that he had broken the body when taking the soul, like monkeys who break the shell to get at the nut.</p>
<p>
This is why the archdeacon was not interred in consecrated earth.</p>
<p>
Louis XI. died a year later, in the month of August, 1483.</p>
<p>
As for Pierre Gringoire, he succeeded in saving the goat, and he won success in tragedy. It appears that, after having tasted astrology, philosophy, architecture, hermetics,—all vanities, he returned to tragedy, vainest pursuit of all. This is what he called "coming to a tragic end." This is what is to be read, on the subject of his dramatic triumphs, in 1483, in the accounts of the "Ordinary:" "To Jehan Marchand and Pierre Gringoire, carpenter and composer, who have made and composed the mystery made at the Chatelet of Paris, at the entry of Monsieur the Legate, and have ordered the personages, clothed and dressed the same, as in the said mystery was required; and likewise, for having made the scaffoldings thereto necessary; and for this deed,—one hundred livres."</p>
<p>
Phoebus de Châteaupers also came to a tragic end. He married.</p>
</div>
</div>
<span class="bottom"> <nav class="passage">
<ul>
<li><a href="http://etc.usf.edu/lit2go/107/the-hunchback-of-notre-dame/1991/book-eleventh-chapter-2/" title="Book Eleventh, Chapter 2" class="back">Back</a></li>
<li><a href="http://etc.usf.edu/lit2go/107/the-hunchback-of-notre-dame/1995/book-eleventh-chapter-4/" title="Book Eleventh, Chapter 4" class="next">Next</a></li>
</ul>
</nav>
</span>
</div>
</div>
</section>
<footer screen>
<div id="footer-text">
<p>
This collection of children's literature is a part of the <a href="http://etc.usf.edu/">Educational Technology Clearinghouse</a> and is funded by various <a href="http://etc.usf.edu/lit2go/welcome/funding/">grants</a>.
</p>
<p>
Copyright © 2006—2016 by the <a href="http://fcit.usf.edu/">Florida Center for Instructional Technology</a>, <a href="http://www.coedu.usf.edu/">College of Education</a>, <a href="http://www.usf.edu/">University of South Florida</a>.
</p>
</div>
<ul id="footer-links">
<li><a href="http://etc.usf.edu/lit2go/welcome/license/">License</a></li>
<li><a href="http://etc.usf.edu/lit2go/welcome/credits/">Credits</a></li>
<li><a href="http://etc.usf.edu/lit2go/welcome/faq/">FAQ</a></li>
<li><a href="http://etc.usf.edu/lit2go/giving/">Giving</a></li>
</ul>
</footer>
<footer print>
<div id="footer-text">
<p>This document was downloaded from <a href="http://etc.usf.edu/lit2go/">Lit2Go</a>, a free online collection of stories and poems in Mp3 (audiobook) format published by the <a href="http://fcit.usf.edu/">Florida Center for Instructional Technology</a>. For more information, including classroom activities, readability data, and original sources, please visit <a href="http://etc.usf.edu/lit2go/107/the-hunchback-of-notre-dame/1994/book-eleventh-chapter-3/">http://etc.usf.edu/lit2go/107/the-hunchback-of-notre-dame/1994/book-eleventh-chapter-3/</a>.</p>
</div>
<div id="book-footer">
<p>Lit2Go: <em>The Hunchback of Notre Dame</em></p>
<p>Book Eleventh, Chapter 3</p>
</div>
</footer>
<script type="text/javascript" defer src="http://etc.usf.edu/lit2go/js/details.js"></script>
</div>
</body>
</html>
|
lit2go.ok/114/the-poems-of-emily-dickinson-series-one/2625/nature-poem-22-a-day/index.html | adrianosb/HtmlToText | <!DOCTYPE html>
<html>
<head>
<title>Nature, Poem 22: A Day | The Poems of Emily Dickinson: Series One | Emily Dickinson | Lit2Go ETC</title>
<link rel="stylesheet" href="http://etc.usf.edu/lit2go/css/screenless.css" type="text/css" media="screen" title="no title" charset="utf-8">
<link rel="stylesheet" href="http://etc.usf.edu/lit2go/css/printless.css" type="text/css" media="print" title="no title" charset="utf-8">
<!--[if lt IE 9]>
<script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
<script type="text/javascript" src="//ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js"></script>
<script type="text/javascript" defer src="http://etc.usf.edu/lit2go/js/js.min.js"></script>
<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-5574891-1']);
_gaq.push(['_trackPageview']);
(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();
$(document).ready(function() {
$('img').unveil();
$('#contactable').contactable({
url: 'http://etc.usf.edu/lit2go/welcome/feedback/',
subject: 'Lit2Go Feedback — Nature, Poem 22: A Day | The Poems of Emily Dickinson: Series One | Emily Dickinson — http://etc.usf.edu/lit2go/114/the-poems-of-emily-dickinson-series-one/2625/nature-poem-22-a-day/'
});
});
</script>
</head>
<body>
<div class="page"> <header>
<h1>
<a href="http://etc.usf.edu/lit2go/">Lit<span class="blue">2</span>Go</a>
</h1>
<ul>
<li id="search"><form action="http://etc.usf.edu/lit2go/search/"><input type="text" name="q" placeholder="Search" value=""></form></li>
</ul>
</header>
<nav id="shell">
<ul>
<li><a href="http://etc.usf.edu/lit2go/authors/" class="">Authors</a></li>
<li><a href="http://etc.usf.edu/lit2go/books/" class="selected">Books</a></li>
<li><a href="http://etc.usf.edu/lit2go/genres/" class="">Genres</a></li>
<li><a href="http://etc.usf.edu/lit2go/collections/" class="">Collections</a></li>
<li><a href="http://etc.usf.edu/lit2go/readability/" class="">Readability</a></li>
</ul>
</nav>
<section id="content">
<div id="contactable"><!-- contactable html placeholder --></div>
<div id="page_content">
<header>
<h2>
<a href="http://etc.usf.edu/lit2go/114/the-poems-of-emily-dickinson-series-one/">The Poems of Emily Dickinson: Series One</a>
</h2>
<h3>
by <a href="http://etc.usf.edu/lit2go/authors/165/emily-dickinson/">Emily Dickinson</a>
</h3>
<h4>
Nature, Poem 22: A Day </h4>
</header>
<div id="poem">
<details open>
<summary>
Additional Information
</summary>
<div id="columns">
<ul>
<li>
<strong>Year Published:</strong>
1896 </li>
<li>
<strong>Language:</strong>
English </li>
<li>
<strong>Country of Origin:</strong>
United States of America </li>
<li>
<strong>Source:</strong>
Dickenson, E. (1896). <em>The Poems of Emily Dickinson: Series One.</em>Boston, MA: Roberts Brothers. </li>
</ul>
</div>
<div id="columns">
<ul>
<li>
<strong>Readability:</strong>
<ul>
<li>
Flesch–Kincaid Level:
<a href="http://etc.usf.edu/lit2go/readability/flesch_kincaid_grade_level/6/" title="Flesch–Kincaid Grade Level 6.6">6.6</a>
</li>
</ul>
</li>
<li>
<strong>Word Count:</strong>
91 </li>
</ul>
</div>
<div id="columns">
<ul>
<li>
<strong>Genre:</strong>
<a href="http://etc.usf.edu/lit2go/genres/24/poetry/">Poetry</a>
</li>
<li>
<strong>Keywords:</strong>
19th century literature, american literature, emily dickinson, poems, poetry, series 1 </li>
<li>
<a class="btn" data-toggle="modal" href="#cite_this" >✎ Cite This</a>
</li>
<li>
<!-- AddThis Button BEGIN -->
<div class="addthis_toolbox addthis_default_style ">
<a addthis:ui_delay="500" href="http://www.addthis.com/bookmark.php?v=250&pub=roywinkelman" class="addthis_button_compact">Share</a>
<span class="addthis_separator">|</span>
<a class="addthis_button_preferred_1"></a>
<a class="addthis_button_preferred_2"></a>
<a class="addthis_button_preferred_3"></a>
<a class="addthis_button_preferred_4"></a>
</div>
<script type="text/javascript">$($.getScript("http://s7.addthis.com/js/250/addthis_widget.js?pub=roywinkelman"))</script>
<!-- <script type="text/javascript" src="http://s7.addthis.com/js/250/addthis_widget.js?pub=roywinkelman"></script> -->
<!-- AddThis Button END -->
</li>
</ul>
</div>
<h4>Downloads</h4>
<ul id="downloads">
<li>
<a href="http://etc.usf.edu/lit2go/audio/mp3/the-poems-of-emily-dickinson-series-one-065-nature-poem-22-a-day.2625.mp3">Audio</a>
</li>
</ul>
<hr>
</details>
<div class="modal hide" id="cite_this">
<script>
$($('#myTab a').click(function (e) {e.preventDefault();$('#myTab a[href="#apa"]').tab('show');}));
</script>
<nav>
<ul id="myTab">
<li class="active">
<a href="#apa" data-toggle="tab">APA</a>
</li>
<li>
<a href="#mla" data-toggle="tab">MLA</a>
</li>
<li>
<a href="#chicago" data-toggle="tab">Chicago</a>
</li>
</ul>
</nav>
<div class="tab-content">
<div class="content tab-pane hide active" id="apa">
<p class="citation">
Dickinson, E. (1896). Nature, Poem 22: A Day. <em>The Poems of Emily Dickinson: Series One</em> (Lit2Go Edition). Retrieved February 15, 2016, from <span class="faux_link">http://etc.usf.edu/lit2go/114/the-poems-of-emily-dickinson-series-one/2625/nature-poem-22-a-day/</span>
</p>
</div>
<div class="content tab-pane" id="mla">
<p class="citation">
Dickinson, Emily. "Nature, Poem 22: A Day." <em>The Poems of Emily Dickinson: Series One</em>. Lit2Go Edition. 1896. Web. <<span class="faux_link">http://etc.usf.edu/lit2go/114/the-poems-of-emily-dickinson-series-one/2625/nature-poem-22-a-day/</span>>. February 15, 2016.
</p>
</div>
<div class="content tab-pane" id="chicago">
<p class="citation">
Emily Dickinson, "Nature, Poem 22: A Day," <em>The Poems of Emily Dickinson: Series One</em>, Lit2Go Edition, (1896), accessed February 15, 2016, <span class="faux_link">http://etc.usf.edu/lit2go/114/the-poems-of-emily-dickinson-series-one/2625/nature-poem-22-a-day/</span>.
</p>
</div>
</div>
</div>
<span class="top"> <nav class="passage">
<ul>
<li><a href="http://etc.usf.edu/lit2go/114/the-poems-of-emily-dickinson-series-one/2624/nature-poem-21-the-mountain/" title="Nature, Poem 21: The Mountain" class="back">Back</a></li>
<li><a href="http://etc.usf.edu/lit2go/114/the-poems-of-emily-dickinson-series-one/2626/nature-poem-23/" title="Nature, Poem 23" class="next">Next</a></li>
</ul>
</nav>
</span>
<div id="shrink_wrap">
<div id="i_apologize_for_the_soup">
<audio controls style="width:99%;">
<source src="http://etc.usf.edu/lit2go/audio/mp3/the-poems-of-emily-dickinson-series-one-065-nature-poem-22-a-day.2625.mp3" type="audio/mpeg" />
<source src="http://etc.usf.edu/lit2go/audio/ogg/the-poems-of-emily-dickinson-series-one-065-nature-poem-22-a-day.2625.ogg" type="audio/ogg" />
The embedded audio player requires a modern internet browser. You should visit <a href="http://browsehappy.com/">Browse Happy</a> and update your internet browser today!
</audio>
<p>
I'll tell you how the sun rose, —<br />
A ribbon at a time.<br />
The steeples swam in amethyst,<br />
The news like squirrels ran.</p>
<p>
The hills untied their bonnets,<br />
The bobolinks begun.<br />
Then I said softly to myself,<br />
"That must have been the sun!"</p>
<p>
* * *</p>
<p>
But how he set, I know not.<br />
There seemed a purple stile<br />
Which little yellow boys and girls<br />
Were climbing all the while</p>
<p>
Till when they reached the other side,<br />
A dominie in gray<br />
Put gently up the evening bars,<br />
And led the flock away.</p>
</div>
</div>
<span class="bottom"> <nav class="passage">
<ul>
<li><a href="http://etc.usf.edu/lit2go/114/the-poems-of-emily-dickinson-series-one/2624/nature-poem-21-the-mountain/" title="Nature, Poem 21: The Mountain" class="back">Back</a></li>
<li><a href="http://etc.usf.edu/lit2go/114/the-poems-of-emily-dickinson-series-one/2626/nature-poem-23/" title="Nature, Poem 23" class="next">Next</a></li>
</ul>
</nav>
</span>
</div>
</div>
</section>
<footer screen>
<div id="footer-text">
<p>
This collection of children's literature is a part of the <a href="http://etc.usf.edu/">Educational Technology Clearinghouse</a> and is funded by various <a href="http://etc.usf.edu/lit2go/welcome/funding/">grants</a>.
</p>
<p>
Copyright © 2006—2016 by the <a href="http://fcit.usf.edu/">Florida Center for Instructional Technology</a>, <a href="http://www.coedu.usf.edu/">College of Education</a>, <a href="http://www.usf.edu/">University of South Florida</a>.
</p>
</div>
<ul id="footer-links">
<li><a href="http://etc.usf.edu/lit2go/welcome/license/">License</a></li>
<li><a href="http://etc.usf.edu/lit2go/welcome/credits/">Credits</a></li>
<li><a href="http://etc.usf.edu/lit2go/welcome/faq/">FAQ</a></li>
<li><a href="http://etc.usf.edu/lit2go/giving/">Giving</a></li>
</ul>
</footer>
<footer print>
<div id="footer-text">
<p>This document was downloaded from <a href="http://etc.usf.edu/lit2go/">Lit2Go</a>, a free online collection of stories and poems in Mp3 (audiobook) format published by the <a href="http://fcit.usf.edu/">Florida Center for Instructional Technology</a>. For more information, including classroom activities, readability data, and original sources, please visit <a href="http://etc.usf.edu/lit2go/114/the-poems-of-emily-dickinson-series-one/2625/nature-poem-22-a-day/">http://etc.usf.edu/lit2go/114/the-poems-of-emily-dickinson-series-one/2625/nature-poem-22-a-day/</a>.</p>
</div>
<div id="book-footer">
<p>Lit2Go: <em>The Poems of Emily Dickinson: Series One</em></p>
<p>Nature, Poem 22: A Day</p>
</div>
</footer>
<script type="text/javascript" defer src="http://etc.usf.edu/lit2go/js/details.js"></script>
</div>
</body>
</html>
|
_attachments/2011-06-14-3723429927_87a667cc96_z-2.html | poojaadani/carlvlewis-theme | ---
layout: attachment
title: 3723429927_87a667cc96_z
date: 2011-06-14 20:25:02.000000000 +05:30
categories: []
tags: []
status: inherit
type: attachment
published: false
meta:
_wp_attached_file: 2011/06/3723429927_87a667cc96_z1.jpg
_wp_attachment_metadata: a:6:{s:5:"width";s:3:"640";s:6:"height";s:3:"449";s:14:"hwstring_small";s:23:"height='89'
width='128'";s:4:"file";s:36:"2011/06/3723429927_87a667cc96_z1.jpg";s:5:"sizes";a:2:{s:9:"thumbnail";a:3:{s:4:"file";s:36:"3723429927_87a667cc96_z1-150x150.jpg";s:5:"width";s:3:"150";s:6:"height";s:3:"150";}s:6:"medium";a:3:{s:4:"file";s:36:"3723429927_87a667cc96_z1-300x210.jpg";s:5:"width";s:3:"300";s:6:"height";s:3:"210";}}s:10:"image_meta";a:10:{s:8:"aperture";s:1:"0";s:6:"credit";s:0:"";s:6:"camera";s:0:"";s:7:"caption";s:0:"";s:17:"created_timestamp";s:1:"0";s:9:"copyright";s:0:"";s:12:"focal_length";s:1:"0";s:3:"iso";s:1:"0";s:13:"shutter_speed";s:1:"0";s:5:"title";s:0:"";}}
pvc_views: '13'
_jetpack_related_posts_cache: a:0:{}
author:
login: cvlewis
email: carl@carlvlewis.net
display_name: Carl V. Lewis
first_name: Carl V.
last_name: Lewis
excerpt: !ruby/object:Hpricot::Doc
options: {}
---
|
test/index.html | kyroskoh/plasio | <!DOCTYPE HTML>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Jasmine Spec Runner v2.0.3</title>
<link rel="shortcut icon" type="image/png" href="lib/jasmine-2.0.3/jasmine_favicon.png">
<link rel="stylesheet" type="text/css" href="lib/jasmine-2.0.3/jasmine.css">
<script type="text/javascript" src="lib/jasmine-2.0.3/jasmine.js"></script>
<script type="text/javascript" src="lib/jasmine-2.0.3/jasmine-html.js"></script>
<script type="text/javascript" src="lib/jasmine-2.0.3/boot.js"></script>
<!-- include source files here... -->
<script type="text/javascript" src="build/specs.js"></script>
</head>
<body>
</body>
</html>
|
examples/tween1.html | quark-dev-team/quarkjs | <!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="viewport" content="user-scalable=no, width=device-width, height=device-height, initial-scale=1.0, minimum-scale=1, maximum-scale=1" />
<title>Quark Framework Example - Tween</title>
<style type="text/css">
body{margin:0;padding:0;font-size:12px;background-color:#eee;}
</style>
<script type="text/javascript" src="../js/quark.base-1.0.0.js"></script>
</head>
<body>
<div id="container" style="position:absolute;left:0;top:0;width:480px;height:320px;background:#fff;"></div>
<div id="fps" style="position:absolute;left:0;top:0;"></div>
<img id="girl" src="images/girl.png" style="display:none;" />
<img id="boy" src="images/boy.png" style="display:none;" />
<div id="box1" style="position:absolute; width:50px; height:50px; border:solid 1px #000; background:#000;"></div>
<div id="box2" style="position:absolute; width:50px; height:50px; left:200px; top:120px; border:solid 1px #f00; background:#f00;"></div>
<script type="text/javascript">
window.onload = init;
var timer,
box1 = document.getElementById("box1"),
box2 = document.getElementById("box2"),
container = Q.getDOM("container");
function init()
{
timer = new Q.Timer(60);
timer.addListener(Q.Tween);
timer.start();
testTween();
}
function testTween()
{
var obj1 = {x:0, y:0}, obj2 = {alpha:1};
var tween1 = new Q.Tween(obj2, {alpha:0}, {time:1000,
onUpdate:function(tween)
{
var t = tween.target;
box2.style.opacity = t.alpha;
}});
Q.Tween.to(obj1, {x:200, y:120}, {time:1000, delay:0, paused:false, reverse:true, loop:false, next:tween1,
onStart:function(tween)
{
//nothing to do
},
onUpdate:function(tween, elapsed)
{
var t = tween.target;
box1.style.left = t.x + "px";
box1.style.top = t.y + "px";
},
onComplete:function(tween)
{
trace("complete:", Date.now());
}
});
}
var frames = 0, fpsContainer = Quark.getDOM("fps");
setInterval(function()
{
//fpsContainer.innerHTML = "FPS:" + frames;
frames = 0;
}, 1000);
</script>
</body>
</html> |
test/renders/component-semantic-time-string-value3.html | formio/formio.js | 23:59 |
examples/05-unbundled-batch-builds/src/dep.css | popeindustries/buddy | main {
color: red;
margin: 10px;
} |
data/president/n706000200000000/20160116153128/page.html | gugod/vote-watch-2016 | <!DOCTYPE html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Expires" content="-1">
<meta http-equiv="Pragma" content="no-cache">
<meta http-equiv="Cache-Control" content="no-cache">
<title>105年第十四任總統副總統及第九屆立法委員選舉</title>
<link href="../css/style.css" rel="stylesheet" type="text/css">
<link href="../css/style2.css" rel="stylesheet" type="text/css">
<script type="text/javascript" src="../js/ftiens4.js"></script>
<script type="text/javascript" src="../js/ua.js"></script>
<script type="text/javascript" src="../js/func.js"></script>
<script type="text/javascript" src="../js/treeP1.js"></script>
<script type="text/javascript" src="../js/refresh.js"></script>
</head>
<body id="main-body">
<div id="main-header">
<div id="main-top">
<a class="main-top-logo" href="#">中央選舉委員會</a>
<ul class="main-top-list">
<li class="main-top-item"><a class="main-top-link main-top-link-home" href="../index.html">回首頁</a></li>
<li class="main-top-item"><a class="main-top-link main-top-link-cec" href="http://2016.cec.gov.tw">中選會網站</a></li>
<li class="main-top-item"><a class="main-top-link main-top-link-english" href="../../en/index.html">English</a></li>
</ul>
</div>
</div>
<div id="main-wrap">
<div id="main-banner">
<div class="slideshow">
<img src="../img/main_bg_1.jpg" width="1024" height="300" alt="background" title="background">
</div>
<div class="main-deco"></div>
<div class="main-title"></div>
<a class="main-pvpe main-pvpe-current" href="../IDX/indexP1.html">總統副總統選舉</a>
<a class="main-le" href="../IDX/indexT.html">立法委員選舉</a>
</div>
<div id="main-container">
<div id="main-content">
<table width="1024" border="1" cellpadding="0" cellspacing="0">
<tr>
<td width="180" valign="top">
<div id="divMenu">
<table border="0">
<tr>
<td><a style="text-decoration:none;color:silver" href="http://www.treemenu.net/" target=_blank></a></td>
</tr>
</table>
<span class="TreeviewSpanArea">
<script>initializeDocument()</script>
<noscript>請開啟Javascript功能</noscript>
</span>
</div>
</td>
<td width="796" valign="top">
<div id="divContent">
<!-- 修改區塊 -->
<table width="100%" border="0" cellpadding="0" cellspacing="4">
<tr>
<td><img src="../images/search.png" alt="候選人得票數" title="候選人得票數"> <b>總統副總統選舉 候選人在 嘉義縣 東石鄉得票數 </b></td>
</tr>
<tr valign="bottom">
<td>
<table width="100%" border="0" cellpadding="0" cellspacing="0">
<tr valign="bottom">
<td class="fontNumber"> <img src="../images/nav.gif" alt="候選組數" title="候選組數"> <img src="../images/nav.gif" alt="候選組數" title="候選組數"> 候選組數：3 <img src="../images/nav.gif" alt="應選組數" title="應選組數"> <img src="../images/nav.gif" alt="應選組數" title="應選組數"> 應選組數：1</td>
<td align="right">
<select name="selector_order" class="selectC" tabindex="1" id="orderBy" onChange="changeOrder();">
<option value="n">依號次排序</option>
<option value="s">依得票排序</option>
</select>
</td>
</tr>
</table>
</td>
</tr>
<tr valign="top">
<td>
<table width="100%" border="0" cellpadding="6" cellspacing="1" class="tableT">
<tr class="trHeaderT">
<td>註記</td>
<td>號次</td>
<td><table><tr><td>總統</td><td rowspan=2> 候選人姓名</td></tr><td>副總統</td></table></td>
<td>性別</td>
<td>得票數</td>
<td>得票率%</td>
<td>登記方式</td>
</tr>
<tr class="trT">
<td> </td>
<td>1</td>
<td>朱立倫<br>王如玄</td>
<td>男<br>女</td>
<td class="tdAlignRight">3,839</td>
<td class="tdAlignRight">25.2799</td>
<td>中國國民黨 推薦</td>
</tr>
<tr class="trT">
<td>◎</td>
<td>2</td>
<td>蔡英文<br>陳建仁</td>
<td>女<br>男</td>
<td class="tdAlignRight">9,252</td>
<td class="tdAlignRight">60.9245</td>
<td>民主進步黨 推薦</td>
</tr>
<tr class="trT">
<td> </td>
<td>3</td>
<td>宋楚瑜<br>徐欣瑩</td>
<td>男<br>女</td>
<td class="tdAlignRight">2,095</td>
<td class="tdAlignRight">13.7956</td>
<td>親民黨 推薦</td>
</tr>
<tr class="trFooterT">
<td colspan="7" align="right">投開票所數 已送/應送: 27/27 </td>
</tr>
</table>
</td>
</tr>
<tr valign="top">
<td>
<table width="100%" border="0" cellpadding="0" cellspacing="0">
<tr>
<td width="10"></td>
<td valign="top" class="fontNote">
<table>
<tr>
<td>註記說明：</td>
<td align="center">◎</td>
<td>自然當選</td>
</tr>
<tr>
<td></td>
<td align="center">？</td>
<td>同票待抽籤</td>
</tr>
</table>
</td>
<td valign="top" class="fontTimer"><img src="../images/clock2.png" alt="Sat, 16 Jan 2016 23:15:12 +0800" title="Sat, 16 Jan 2016 23:15:12 +0800"> 資料更新時間： 01/16 23:15:06 <br>(網頁每3分鐘自動更新一次)</td>
</tr>
<tr>
<td colspan="3" class="fontNote"></td>
</tr>
</table>
</td>
</tr>
</table>
<!-- 修改區塊 -->
</div>
</td>
</tr>
</table>
</div>
<div class="main-footer"></div>
<div id="divFooter" align=center>[中央選舉委員會] </div>
<!--main-content-->
</div><!--main-container-->
</div><!--END main-wrap-->
<script>setOrder();</script>
<script>setMenuScrollPosY();</script>
</body>
</html>
|
resources/apache-jena/javadoc-sdb/com/hp/hpl/jena/sdb/exprmatch/class-use/FunctionAction.html | vuk/Clojure-Movies | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<!-- NewPage -->
<html lang="en">
<head>
<!-- Generated by javadoc (version 1.7.0_25) on Thu Sep 12 11:01:01 BST 2013 -->
<meta http-equiv="Content-Type" content="text/html" charset="UTF-8">
<title>Uses of Interface com.hp.hpl.jena.sdb.exprmatch.FunctionAction (Apache Jena SDB)</title>
<meta name="date" content="2013-09-12">
<link rel="stylesheet" type="text/css" href="../../../../../../../stylesheet.css" title="Style">
</head>
<body>
<script type="text/javascript"><!--
if (location.href.indexOf('is-external=true') == -1) {
parent.document.title="Uses of Interface com.hp.hpl.jena.sdb.exprmatch.FunctionAction (Apache Jena SDB)";
}
//-->
</script>
<noscript>
<div>JavaScript is disabled on your browser.</div>
</noscript>
<!-- ========= START OF TOP NAVBAR ======= -->
<div class="topNav"><a name="navbar_top">
<!-- -->
</a><a href="#skip-navbar_top" title="Skip navigation links"></a><a name="navbar_top_firstrow">
<!-- -->
</a>
<ul class="navList" title="Navigation">
<li><a href="../../../../../../../overview-summary.html">Overview</a></li>
<li><a href="../package-summary.html">Package</a></li>
<li><a href="../../../../../../../com/hp/hpl/jena/sdb/exprmatch/FunctionAction.html" title="interface in com.hp.hpl.jena.sdb.exprmatch">Class</a></li>
<li class="navBarCell1Rev">Use</li>
<li><a href="../package-tree.html">Tree</a></li>
<li><a href="../../../../../../../deprecated-list.html">Deprecated</a></li>
<li><a href="../../../../../../../index-all.html">Index</a></li>
<li><a href="../../../../../../../help-doc.html">Help</a></li>
</ul>
</div>
<div class="subNav">
<ul class="navList">
<li>Prev</li>
<li>Next</li>
</ul>
<ul class="navList">
<li><a href="../../../../../../../index.html?com/hp/hpl/jena/sdb/exprmatch/class-use/FunctionAction.html" target="_top">Frames</a></li>
<li><a href="FunctionAction.html" target="_top">No Frames</a></li>
</ul>
<ul class="navList" id="allclasses_navbar_top">
<li><a href="../../../../../../../allclasses-noframe.html">All Classes</a></li>
</ul>
<div>
<script type="text/javascript"><!--
allClassesLink = document.getElementById("allclasses_navbar_top");
if(window==top) {
allClassesLink.style.display = "block";
}
else {
allClassesLink.style.display = "none";
}
//-->
</script>
</div>
<a name="skip-navbar_top">
<!-- -->
</a></div>
<!-- ========= END OF TOP NAVBAR ========= -->
<div class="header">
<h2 title="Uses of Interface com.hp.hpl.jena.sdb.exprmatch.FunctionAction" class="title">Uses of Interface<br>com.hp.hpl.jena.sdb.exprmatch.FunctionAction</h2>
</div>
<div class="classUseContainer">No usage of com.hp.hpl.jena.sdb.exprmatch.FunctionAction</div>
<!-- ======= START OF BOTTOM NAVBAR ====== -->
<div class="bottomNav"><a name="navbar_bottom">
<!-- -->
</a><a href="#skip-navbar_bottom" title="Skip navigation links"></a><a name="navbar_bottom_firstrow">
<!-- -->
</a>
<ul class="navList" title="Navigation">
<li><a href="../../../../../../../overview-summary.html">Overview</a></li>
<li><a href="../package-summary.html">Package</a></li>
<li><a href="../../../../../../../com/hp/hpl/jena/sdb/exprmatch/FunctionAction.html" title="interface in com.hp.hpl.jena.sdb.exprmatch">Class</a></li>
<li class="navBarCell1Rev">Use</li>
<li><a href="../package-tree.html">Tree</a></li>
<li><a href="../../../../../../../deprecated-list.html">Deprecated</a></li>
<li><a href="../../../../../../../index-all.html">Index</a></li>
<li><a href="../../../../../../../help-doc.html">Help</a></li>
</ul>
</div>
<div class="subNav">
<ul class="navList">
<li>Prev</li>
<li>Next</li>
</ul>
<ul class="navList">
<li><a href="../../../../../../../index.html?com/hp/hpl/jena/sdb/exprmatch/class-use/FunctionAction.html" target="_top">Frames</a></li>
<li><a href="FunctionAction.html" target="_top">No Frames</a></li>
</ul>
<ul class="navList" id="allclasses_navbar_bottom">
<li><a href="../../../../../../../allclasses-noframe.html">All Classes</a></li>
</ul>
<div>
<script type="text/javascript"><!--
allClassesLink = document.getElementById("allclasses_navbar_bottom");
if(window==top) {
allClassesLink.style.display = "block";
}
else {
allClassesLink.style.display = "none";
}
//-->
</script>
</div>
<a name="skip-navbar_bottom">
<!-- -->
</a></div>
<!-- ======== END OF BOTTOM NAVBAR ======= -->
<p class="legalCopy"><small>Licenced under the Apache License, Version 2.0</small></p>
</body>
</html>
|
administrator/components/com_rokgallery/assets/styles/uploader.css | smetal/gvdd | /**
* @author RocketTheme http://www.rockettheme.com
* @copyright Copyright (C) 2007 - 2013 RocketTheme, LLC
* @license http://www.gnu.org/licenses/gpl-2.0.html GNU/GPLv2 only
*/
#popup .topbar .counter{color:#999;float:right;font-size:12px;font-weight:normal;text-transform:none;line-height:17px;margin-right:5px}#popup .topbar .counter span{font-weight:bold}
#files-status,#files-list{display:none}#files-status{float:left;background:url(../images/images.png) top center no-repeat;padding-top:40px;width:75px;font-size:10px;line-height:13px}
#files-list{float:right;width:300px;max-height:145px;overflow:hidden;margin:0;padding:0;list-style:none}#files-clear{color:#aaa;font-size:12px;line-height:29px;margin-left:5px;text-shadow:0 1px 0 #fff;cursor:pointer;display:none}
#files-list .file-1{background:url(../images/image-red.png) 0 2px no-repeat}#files-list .file-2{background:url(../images/image-green.png) 0 2px no-repeat}
#files-list .file-3{background:url(../images/image-blue.png) 0 2px no-repeat}#files-list .file-success{background:url(../images/file-success.png) 0 2px no-repeat}
#files-list .file-failed{background:url(../images/file-fail.png) 0 2px no-repeat}#files-list .file-uploading{background:transparent}#files-list .file{padding-left:20px;padding-bottom:5px;margin:0 10px 10px 0;float:left;width:120px;font-size:11px;line-height:13px;position:relative;z-index:10;border-bottom:1px solid #eee}
#files-list .file:hover{z-index:20}#files-list .file-name,#files-list .file-size{display:block}#files-list .file-name{color:#555;overflow:hidden;white-space:nowrap;text-overflow:ellipsis;-o-text-overflow:ellipsis;-icab-text-overflow:ellipsis;-khtml-text-overflow:ellipsis;-moz-text-overflow:ellipsis;-webkit-text-overflow:ellipsis;margin-bottom:2px;line-height:17px}
#files-list .file-name:hover{overflow:visible;text-shadow:0 0 5px #0074eb}#files-list .file-success .file-name{color:#457e17}#files-list .file-failed .file-name{color:#a40303}
#files-list .file-uploading .file-name{color:#ee7600}#files-list .file-info{clear:both;float:left;margin-top:5px;color:#a40303}#files-list .file-size{color:#999;float:left}
#files-list .file-remove{float:left;background:url(../images/icons.png) -16px -240px;width:12px;height:12px;display:block;opacity:0;position:absolute;left:2px;top:20px}
#files-list .file:hover .file-remove{opacity:.8}#files-list .file.file-success .file-name:hover,#files-list .file.file-failed .file-name:hover,#files-list .file.file-uploading .file-name:hover{text-shadow:0 1px 0 #fff}
#files-list .file-remove:hover{opacity:1}#files-list .file.file-success .file-remove,#files-list .file.file-failed .file-remove,#files-list .file.file-uploading .file-remove{display:none}
#files-list .file-remove span{display:none}#files-list .file-canvas-wrapper{left:0;position:absolute;top:2px;display:none}#files-list .file-canvas,#files-list .file-canvas-bg{position:absolute;z-index:5}
#files-list .file-canvas{z-index:10}#files-list .file-uploading .file-canvas-wrapper{display:block}#files-list .file-success .file-canvas-wrapper{display:none}
#files-list .validation-error{background:#ec4343;border-radius:8px;color:#fff;font-size:11px;line-height:13px;margin:0 3px 5px 0;padding:5px 8px 8px;box-shadow:0 -4px 0 rgba(0,0,0,0.1) inset;cursor:pointer}
.statusbar .job-canvas-wrapper{position:absolute;left:10px;top:10px}.statusbar .job-canvas-wrapper canvas{left:0;position:absolute;top:0;z-index:5}.statusbar .job-canvas-wrapper canvas.job-canvas{z-index:10}
#files-status .overall-title{margin-top:5px;text-align:center}#files-status .current-text{text-align:center}#files-status .total-progress{position:relative;width:25px;height:25px;margin:0 auto}
#files-status .total-progress-bg{z-index:5}#files-status canvas{left:0;position:absolute;top:0;z-index:5}#files-status .overall-progress{z-index:10}#files-status .progress-bg{background:url(../images/progress-bg.png) no-repeat;display:block;height:40px;left:0;position:absolute;top:0;width:40px;z-index:1}
#files-status .button{float:left}#files-status #files-success{width:100%;height:100%;background:url(../images/files-success.png) center center no-repeat;display:none;z-index:15}
#files-form{position:relative}#files-form div.scrollbar{width:4px;border-radius:4px;background:#333;position:absolute;top:0;right:-4px;display:block}#files-empty-desc .drop-info{margin:10px;padding:40px 20px;text-align:center;text-align:center;text-transform:uppercase;color:#ddd;border:4px dashed #eee;border-radius:6px;-webkit-border-radius:12px;-moz-border-radius:12px;font-size:16px}
#files-empty-desc .drop-info.drag-over{color:#91ce84;border-color:#91ce84}.job-info,.jobs-info,.galleries-info,.gallery-info,.tags-info{color:#888;float:left;font-size:12px;line-height:28px;margin-left:30px}
.jobs-info,.galleries-info,.tags-info{margin-left:0}.drop-info,#files-list .file-remove,#files-list .file-name{-webkit-transition:all .3s ease-in-out;-moz-transition:all .3s ease-in-out;-o-transition:all .3s ease-in-out;-webkit-transition:all .3s ease-in-out;transition:all .3s ease-in-out} |
toolchains/gcc-linaro-7.3.1-2018.05-x86_64_arm-linux-gnueabihf/share/doc/gcc/Nvidia-PTX-Function-Attributes.html | BPI-SINOVOIP/BPI-Mainline-kernel | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Copyright (C) 1988-2017 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with the
Invariant Sections being "Funding Free Software", the Front-Cover
Texts being (a) (see below), and with the Back-Cover Texts being (b)
(see below). A copy of the license is included in the section entitled
"GNU Free Documentation License".
(a) The FSF's Front-Cover Text is:
A GNU Manual
(b) The FSF's Back-Cover Text is:
You have freedom to copy and modify this GNU Manual, like GNU
software. Copies published by the Free Software Foundation raise
funds for GNU development. -->
<!-- Created by GNU Texinfo 5.2, http://www.gnu.org/software/texinfo/ -->
<head>
<title>Using the GNU Compiler Collection (GCC): Nvidia PTX Function Attributes</title>
<meta name="description" content="Using the GNU Compiler Collection (GCC): Nvidia PTX Function Attributes">
<meta name="keywords" content="Using the GNU Compiler Collection (GCC): Nvidia PTX Function Attributes">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link href="index.html#Top" rel="start" title="Top">
<link href="Option-Index.html#Option-Index" rel="index" title="Option Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Function-Attributes.html#Function-Attributes" rel="up" title="Function Attributes">
<link href="PowerPC-Function-Attributes.html#PowerPC-Function-Attributes" rel="next" title="PowerPC Function Attributes">
<link href="Nios-II-Function-Attributes.html#Nios-II-Function-Attributes" rel="prev" title="Nios II Function Attributes">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.indentedblock {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
div.smalllisp {margin-left: 3.2em}
kbd {font-style:oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: inherit; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: inherit; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.nocodebreak {white-space:nowrap}
span.nolinebreak {white-space:nowrap}
span.roman {font-family:serif; font-weight:normal}
span.sansserif {font-family:sans-serif; font-weight:normal}
ul.no-bullet {list-style: none}
-->
</style>
</head>
<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
<a name="Nvidia-PTX-Function-Attributes"></a>
<div class="header">
<p>
Next: <a href="PowerPC-Function-Attributes.html#PowerPC-Function-Attributes" accesskey="n" rel="next">PowerPC Function Attributes</a>, Previous: <a href="Nios-II-Function-Attributes.html#Nios-II-Function-Attributes" accesskey="p" rel="prev">Nios II Function Attributes</a>, Up: <a href="Function-Attributes.html#Function-Attributes" accesskey="u" rel="up">Function Attributes</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Option-Index.html#Option-Index" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<a name="Nvidia-PTX-Function-Attributes-1"></a>
<h4 class="subsection">6.31.22 Nvidia PTX Function Attributes</h4>
<p>These function attributes are supported by the Nvidia PTX back end:
</p>
<dl compact="compact">
<dt><code>kernel</code></dt>
<dd><a name="index-kernel-attribute_002c-Nvidia-PTX"></a>
<p>This attribute indicates that the corresponding function should be compiled
as a kernel function, which can be invoked from the host via the CUDA RT
library.
By default functions are only callable only from other PTX functions.
</p>
<p>Kernel functions must have <code>void</code> return type.
</p></dd>
</dl>
</body>
</html>
|
Schrodinger/Schrodinger_2012_docs/maestro/help_Maestro91/primex/water_placement_panel.html | platinhom/ManualHom | <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<link rel="stylesheet" href="../support/help.css" charset="ISO-8859-1" type="text/css" />
<meta name="categories" content="primex tasks_menu ">
<meta name="product" content="PrimeX">
<title>PrimeX — Water Placement Panel</title>
</head>
<script type="text/javascript">
function setTitle()
{
top.document.title = document.title + " - " + parent.parent.WINDOW_TITLE;
}
</script>
<body onload="setTitle();">
<table border=0 cellspacing=0 bgcolor=#dcdcdc width=100%>
<tr><td>
<p><img src="../support/schrodinger_logo.gif" border=0 alt="" align="left"
vspace=5 hspace=5 /></p>
</td></tr>
<tr><td>
<h1 class="title"><span class="primex">PrimeX — Water Placement Panel</span></h1>
</td></tr>
</table>
<ul>
<li><a href="#summary">Summary</a></li>
<li><a href="#opening">Opening the <span class="GUI">Water Placement</span> Panel</a></li>
<li><a href="#using">Using the <span class="GUI">Water Placement</span> Panel</a></li>
<li><a href="#features"><span class="GUI">Water Placement</span> Panel Features</a></li>
<li><a href="#links">Related Topics</a></li>
</ul>
<a name="summary"></a>
<h2>Summary</h2>
<p>
In this panel you set options and run a job to place water molecules. The
options in this panel ensure that water molecules are placed in reasonable locations.
</p>
<a name="opening"></a>
<h2>Opening the Water Placement Panel</h2>
<p>To open the <span class="GUI">Water Placement</span> panel,
do one of the following:</p>
<ul>
<li><p>Choose <span class="GUI">Applications → PrimeX → Task →
Water Placement</span></p></li>
<li><p>Choose <span class="GUI">Tasks → Protein X-Ray Refinement →
Task →
Water Placement</span></p></li>
<li><p>Choose <span class="GUI">Water Placement</span> from the
<span class="GUI">Task</span> button menu on the PrimeX toolbar.</p>
<p><img src="../images/MaestroToolbarIcons/primex_task.png" /></p>
</li>
</ul>
<a name="using"></a>
<h2>Using the Water Placement Panel</h2>
<p>To place water molecules, you must first have a difference density map. Water
molecules are placed in all locations that match the criteria specified in the
text boxes. When you have set these values, click <span class="GUI">Start</span>
to open the <span class="GUI">Start</span> dialog
box, in which you can make job settings and run the water placement job.</p>
<p>Once the job is run, it is a good idea to check the placements using the
<a href="density_fit_panel.html"><span class="GUI">Density Fit</span> panel</a>.
</p>
<p>To center the view on a particular part of a density map, right-click on one
of the displayed vertices of the map.
</p>
<a name="features"></a>
<h2>Water Placement Panel Features</h2>
<ul>
<li><a href="#feature1"><span class="GUI">Minimum peak height (Fo-Fc)</span> text box</a></li>
<li><a href="#feature2"><span class="GUI">Maximum B-factor</span> text box</a></li>
<li><a href="#feature3"><span class="GUI">Minimum hydrogen-bonding distance</span> text box</a></li>
<li><a href="#feature4"><span class="GUI">Minimum distance to other atoms</span> text box</a></li>
<li><a href="#feature5"><span class="GUI">Maximum distance to other atoms</span> text box</a></li>
<li><a href="#feature6"><span class="GUI">Calculation Settings</span> button</a></li>
</ul>
<dl>
<a name="feature1"></a>
<dt><span class="GUI">Minimum peak height (Fo-Fc)</span> text box</dt>
<dd><p>Specify the minimum height of any peak that will be used to place a water
molecule.
</p></dd>
<a name="feature2"></a>
<dt><span class="GUI">Maximum B-factor</span> text box</dt>
<dd><p>Specify the maximum B-factor for any water molecule to be accepted as
placed. Water molecules with larger B-factors are rejected as "noise".
</p></dd>
<a name="feature3"></a>
<dt><span class="GUI">Minimum hydrogen-bonding distance</span> text box</dt>
<dd><p>Specify the minimum distance between the oxygen atom and a hydrogen-bond
donor or acceptor. Water molecules will not be placed in locations where this
distance is less than the value specified.
</p></dd>
<a name="feature4"></a>
<dt><span class="GUI">Minimum distance to other atoms</span> text box</dt>
<dd><p>Specify the minimum distance between the oxygen atom and any other atom.
Water molecules will not be placed in locations where this distance is less than
the value specified.
</p></dd>
<a name="feature5"></a>
<dt><span class="GUI">Maximum distance to other atoms</span> text box</dt>
<dd><p>Specify the maximum distance between the oxygen atom and any other atom.
Water molecules will not be placed in locations where this distance is greater than
the value specified.
</p></dd>
<a name="feature6"></a>
<dt><span class="GUI">Calculation Settings</span> button</dt>
<dd><p>This button opens the
<a href="calculation_settings_db.html"><span class="GUI">Calculation
Settings</span> dialog box</a>, in which you can set the resolution limits and
limits for rejecting reflections; choose an overall B-factor scaling and a bulk
solvent correction; choose whether to use implicit solvation, include
hydrogen atoms in the output, restrain planar groups, set B-factors for the
duration of the job, use phased reflections for the map, and change the relative
weight of the force-field and X-ray terms.
</p></dd>
</dl>
<a name="links"></a>
<h2>Related Topics</h2>
<ul>
<li><a href="ligand_solvent_placement_panel.html">Ligand/Solvent Placement Panel</a></li>
</ul>
<hr />
<table width="100%">
<td><p class="small"><a href="../support/legal_notice.html" target="LegalNoticeWindow">Legal Notice</a></p></td>
<td>
<table align="right">
<td><p class="small">
File: primex/water_placement_panel.html<br />
Last updated: 11 Jan 2012
</p></td>
</table>
</td>
</table>
</body>
</html>
|
engines/bastion_katello/app/assets/javascripts/bastion_katello/subscriptions/details/views/subscription-info.html | cfouant/katello | <div data-extend-template="layouts/two-column-details.html">
<div data-block="left-column">
<h4 translate>Subscription Info</h4>
<dl class="dl-horizontal dl-horizontal-left">
<dt translate>Name</dt>
<dd>{{ subscription.name }}</dd>
<dt translate>Description</dt>
<dd>{{ subscription.description }}</dd>
<dt>
<span translate>Virt-Who Usage Required</span>
<i class="pf pficon-info"
tooltip-html-unsafe="{{ virtWhoToolTip }}"
tooltip-trigger="click"
tooltip-animation="false"
tooltip-placement="right"
tooltip-close-popup-delay="5"
tooltip-append-to-body="true">
</i>
</dt>
<dd>{{ subscription.virt_who | booleanToYesNo }}</dd>
<dt translate>Consumed</dt>
<dd>{{ subscription | subscriptionConsumedFilter }}</dd>
<dt translate>Starts</dt>
<dd><short-date-time date="subscription.start_date" /></dd>
<dt translate>Ends</dt>
<dd><short-date-time date="subscription.end_date" /></dd>
<dt translate>Product ID</dt>
<dd>{{ subscription.product_id }}</dd>
<dt translate>Contract Number</dt>
<dd>{{ subscription.contract_number }}</dd>
<dt translate>Account Number</dt>
<dd>{{ subscription.account_number }}</dd>
<dt translate>Support Level</dt>
<dd>{{ subscription.support_level }}</dd>
<dt translate>Support Type</dt>
<dd>{{ subscription.support_type }}</dd>
<dt translate>Architecture(s)</dt>
<dd>{{ subscription.arch }}</dd>
<dt translate>Type</dt>
<dd>{{ subscription.type }}</dd>
<dt translate>Limits</dt>
<dd>{{ subscriptionLimits(subscription) }}</dd>
<dt translate>Multi-entitlement</dt>
<dd>{{ subscription.multi_entitlement | booleanToYesNo }}</dd>
<dt translate>Instance-based</dt>
<dd>{{ formatInstanceBased(subscription) }}</dd>
<dt ng-hide="subscription.stacking_id == ''" translate>Stacking ID</dt>
<dd ng-hide="subscription.stacking_id == ''">{{ subscription.stacking_id }}</dd>
<dt ng-hide="subscription.source_pool_id == undefined || subscription.source_pool_id == ''" translate>Virtual Guest From</dt>
<dd ng-hide="subscription.source_pool_id == undefined || subscription.source_pool_id == ''">{{ subscription.name }}</dd>
<dt ng-hide="subscription.host_id == undefined || subscription.host_id == ''" translate>Required Host</dt>
<dd ng-hide="subscription.host_id == undefined || subscription.host_id == ''">{{ subscription.host.name }}</dd>
</dl>
</div>
<div data-block="right-column">
<h4 translate>Associations</h4>
<section>
<table class="table table-striped table-bordered">
<thead>
<tr>
<th translate>Resource</th>
<th translate>Quantity</th>
</tr>
</thead>
<tbody>
<tr>
<td>Content Hosts</td>
<td>
<a ng-href="/content_hosts?search={{searchQuery(subscription)}}">
{{ subscription.host_count }}
</a>
</td>
</tr>
<tr>
<td>Activation Keys</td>
<td>
<a ng-href="/activation_keys?search={{searchQuery(subscription)}}">
{{ subscription.activation_keys.length }}
</a>
</td>
</tr>
</tbody>
</table>
</section>
<h4 translate>Provided Products</h4>
<ul>
<li ng-repeat="product in subscription.provided_products">
{{ product.name }}
</li>
</ul>
<p ng-show="subscription.provided_products.length === 0" translate>
No Products are provided by this Subscription.
</p>
</div>
</div>
|
phpsecinfo/docs/PhpSecInfo/PhpSecInfo_Test_Core_Gid.html | sonha/codetor | <?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<!-- template designed by Marco Von Ballmoos -->
<title>Docs For Class PhpSecInfo_Test_Core_Gid</title>
<link rel="stylesheet" href="../media/stylesheet.css" />
<meta http-equiv='Content-Type' content='text/html; charset=iso-8859-1'/>
</head>
<body>
<div class="page-body">
<h2 class="class-name">Class PhpSecInfo_Test_Core_Gid</h2>
<a name="sec-description"></a>
<div class="info-box">
<div class="info-box-title">Description</div>
<div class="nav-bar">
<span class="disabled">Description</span> |
<a href="#sec-var-summary">Vars</a> (<a href="#sec-vars">details</a>)
| <a href="#sec-method-summary">Methods</a> (<a href="#sec-methods">details</a>)
</div>
<div class="info-box-body">
<!-- ========== Info from phpDoc block ========= -->
<p class="short-description">Test class for GID</p>
<p class="notes">
Located in <a class="field" href="_PhpSecInfo_Test_Core_gid_php.html">/PhpSecInfo/Test/Core/gid.php</a> (line <span class="field"><a href="..//__filesource/fsource_PhpSecInfo__PhpSecInfoTestCoregid.php.html#a28">28</a></span>)
</p>
<pre><a href="../PhpSecInfo/PhpSecInfo_Test.html">PhpSecInfo_Test</a>
|
--<a href="../PhpSecInfo/PhpSecInfo_Test_Core.html">PhpSecInfo_Test_Core</a>
|
--PhpSecInfo_Test_Core_Gid</pre>
</div>
</div>
<a name="sec-var-summary"></a>
<div class="info-box">
<div class="info-box-title">Variable Summary</span></div>
<div class="nav-bar">
<a href="#sec-description">Description</a> |
<span class="disabled">Vars</span> (<a href="#sec-vars">details</a>)
|
<a href="#sec-method-summary">Methods</a> (<a href="#sec-methods">details</a>)
</div>
<div class="info-box-body">
<div class="var-summary">
<div class="var-title">
<span class="var-type">mixed</span>
<a href="#$recommended_value" title="details" class="var-name">$recommended_value</a>
</div>
<div class="var-title">
<span class="var-type">string</span>
<a href="#$test_name" title="details" class="var-name">$test_name</a>
</div>
</div>
</div>
</div>
<a name="sec-method-summary"></a>
<div class="info-box">
<div class="info-box-title">Method Summary</span></div>
<div class="nav-bar">
<a href="#sec-description">Description</a> |
<a href="#sec-var-summary">Vars</a> (<a href="#sec-vars">details</a>)
|
<span class="disabled">Methods</span> (<a href="#sec-methods">details</a>)
</div>
<div class="info-box-body">
<div class="method-summary">
<div class="method-definition">
<span class="method-result">boolean</span>
<a href="#isTestable" title="details" class="method-name">isTestable</a>
()
</div>
<div class="method-definition">
<span class="method-result">void</span>
<a href="#_execTest" title="details" class="method-name">_execTest</a>
()
</div>
<div class="method-definition">
<span class="method-result">void</span>
<a href="#_retrieveCurrentValue" title="details" class="method-name">_retrieveCurrentValue</a>
()
</div>
<div class="method-definition">
<span class="method-result">void</span>
<a href="#_setMessages" title="details" class="method-name">_setMessages</a>
()
</div>
</div>
</div>
</div>
<a name="sec-vars"></a>
<div class="info-box">
<div class="info-box-title">Variables</div>
<div class="nav-bar">
<a href="#sec-description">Description</a> |
<a href="#sec-var-summary">Vars</a> (<span class="disabled">details</span>)
|
<a href="#sec-method-summary">Methods</a> (<a href="#sec-methods">details</a>)
</div>
<div class="info-box-body">
<a name="var$recommended_value" id="$recommended_value"><!-- --></A>
<div class="oddrow">
<div class="var-header">
<span class="var-title">
<span class="var-type">mixed</span>
<span class="var-name">$recommended_value</span>
= <span class="var-default"> PHPSECINFO_MIN_SAFE_GID</span> (line <span class="line-number"><a href="..//__filesource/fsource_PhpSecInfo__PhpSecInfoTestCoregid.php.html#a38">38</a></span>)
</span>
</div>
<!-- ========== Info from phpDoc block ========= -->
<hr class="separator" />
<div class="notes">Redefinition of:</div>
<dl>
<dt><a href="../PhpSecInfo/PhpSecInfo_Test.html#var$recommended_value">PhpSecInfo_Test::$recommended_value</a></dt>
<dd>This is the recommended value the test will be looking for</dd>
</dl>
</div>
<a name="var$test_name" id="$test_name"><!-- --></A>
<div class="evenrow">
<div class="var-header">
<span class="var-title">
<span class="var-type">string</span>
<span class="var-name">$test_name</span>
= <span class="var-default"> "group_id"</span> (line <span class="line-number"><a href="..//__filesource/fsource_PhpSecInfo__PhpSecInfoTestCoregid.php.html#a36">36</a></span>)
</span>
</div>
<!-- ========== Info from phpDoc block ========= -->
<p class="short-description">This should be a <strong>unique</strong>, human-readable identifier for this test</p>
<hr class="separator" />
<div class="notes">Redefinition of:</div>
<dl>
<dt><a href="../PhpSecInfo/PhpSecInfo_Test.html#var$test_name">PhpSecInfo_Test::$test_name</a></dt>
<dd>This should be a <strong>unique</strong>, human-readable identifier for this test</dd>
</dl>
</div>
<h4>Inherited Variables</h4>
<A NAME='inherited_vars'><!-- --></A>
<p>Inherited from <span class="classname"><a href="../PhpSecInfo/PhpSecInfo_Test_Core.html">PhpSecInfo_Test_Core</a></span></p>
<blockquote>
<span class="var-title">
<span class="var-name"><a href="../PhpSecInfo/PhpSecInfo_Test_Core.html#var$test_group">PhpSecInfo_Test_Core::$test_group</a></span><br>
</span>
</blockquote>
<p>Inherited from <span class="classname"><a href="../PhpSecInfo/PhpSecInfo_Test.html">PhpSecInfo_Test</a></span></p>
<blockquote>
<span class="var-title">
<span class="var-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#var$current_value">PhpSecInfo_Test::$current_value</a></span><br>
</span>
<span class="var-title">
<span class="var-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#var$_language">PhpSecInfo_Test::$_language</a></span><br>
</span>
<span class="var-title">
<span class="var-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#var$_message">PhpSecInfo_Test::$_message</a></span><br>
</span>
<span class="var-title">
<span class="var-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#var$_messages">PhpSecInfo_Test::$_messages</a></span><br>
</span>
<span class="var-title">
<span class="var-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#var$_result">PhpSecInfo_Test::$_result</a></span><br>
</span>
</blockquote>
</div>
</div>
<a name="sec-methods"></a>
<div class="info-box">
<div class="info-box-title">Methods</div>
<div class="nav-bar">
<a href="#sec-description">Description</a> |
<a href="#sec-var-summary">Vars</a> (<a href="#sec-vars">details</a>)
<a href="#sec-method-summary">Methods</a> (<span class="disabled">details</span>)
</div>
<div class="info-box-body">
<A NAME='method_detail'></A>
<a name="methodisTestable" id="isTestable"><!-- --></a>
<div class="oddrow">
<div class="method-header">
<span class="method-title">isTestable</span> (line <span class="line-number"><a href="..//__filesource/fsource_PhpSecInfo__PhpSecInfoTestCoregid.php.html#a46">46</a></span>)
</div>
<!-- ========== Info from phpDoc block ========= -->
<p class="short-description">This test only works under Unix OSes</p>
<div class="method-signature">
<span class="method-result">boolean</span>
<span class="method-name">
isTestable
</span>
()
</div>
<hr class="separator" />
<div class="notes">Redefinition of:</div>
<dl>
<dt><a href="../PhpSecInfo/PhpSecInfo_Test_Core.html#methodisTestable">PhpSecInfo_Test_Core::isTestable()</a></dt>
<dd>"Core" tests should pretty much be always testable, so the default is just to return true</dd>
</dl>
</div>
<a name="method_execTest" id="_execTest"><!-- --></a>
<div class="evenrow">
<div class="method-header">
<span class="method-title">_execTest</span> (line <span class="line-number"><a href="..//__filesource/fsource_PhpSecInfo__PhpSecInfoTestCoregid.php.html#a71">71</a></span>)
</div>
<!-- ========== Info from phpDoc block ========= -->
<p class="short-description">Checks the GID of the PHP process to make sure it is above PHPSECINFO_MIN_SAFE_GID</p>
<ul class="tags">
<li><span class="field">see:</span> <a href="../PhpSecInfo/_PhpSecInfo_Test_Core_gid_php.html#definePHPSECINFO_MIN_SAFE_GID">PHPSECINFO_MIN_SAFE_GID</a></li>
</ul>
<div class="method-signature">
<span class="method-result">void</span>
<span class="method-name">
_execTest
</span>
()
</div>
<hr class="separator" />
<div class="notes">Redefinition of:</div>
<dl>
<dt><a href="../PhpSecInfo/PhpSecInfo_Test.html#method_execTest">PhpSecInfo_Test::_execTest()</a></dt>
<dd>The "meat" of the test. This is where the real test code goes. You should override this when extending</dd>
</dl>
</div>
<a name="method_retrieveCurrentValue" id="_retrieveCurrentValue"><!-- --></a>
<div class="oddrow">
<div class="method-header">
<span class="method-title">_retrieveCurrentValue</span> (line <span class="line-number"><a href="..//__filesource/fsource_PhpSecInfo__PhpSecInfoTestCoregid.php.html#a56">56</a></span>)
</div>
<!-- ========== Info from phpDoc block ========= -->
<div class="method-signature">
<span class="method-result">void</span>
<span class="method-name">
_retrieveCurrentValue
</span>
()
</div>
<hr class="separator" />
<div class="notes">Redefinition of:</div>
<dl>
<dt><a href="../PhpSecInfo/PhpSecInfo_Test.html#method_retrieveCurrentValue">PhpSecInfo_Test::_retrieveCurrentValue()</a></dt>
<dd>Placeholder - extend for tests</dd>
</dl>
</div>
<a name="method_setMessages" id="_setMessages"><!-- --></a>
<div class="evenrow">
<div class="method-header">
<span class="method-title">_setMessages</span> (line <span class="line-number"><a href="..//__filesource/fsource_PhpSecInfo__PhpSecInfoTestCoregid.php.html#a84">84</a></span>)
</div>
<!-- ========== Info from phpDoc block ========= -->
<p class="short-description">Set the messages specific to this test</p>
<div class="method-signature">
<span class="method-result">void</span>
<span class="method-name">
_setMessages
</span>
()
</div>
<hr class="separator" />
<div class="notes">Redefinition of:</div>
<dl>
<dt><a href="../PhpSecInfo/PhpSecInfo_Test.html#method_setMessages">PhpSecInfo_Test::_setMessages()</a></dt>
<dd>This function loads up result messages into the $this->_messages array.</dd>
</dl>
</div>
<h4>Inherited Methods</h4>
<a name='inherited_methods'><!-- --></a>
<!-- =========== Summary =========== -->
<p>Inherited From <span class="classname"><a href="../PhpSecInfo/PhpSecInfo_Test_Core.html">PhpSecInfo_Test_Core</a></span></p>
<blockquote>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test_Core.html#methodisTestable">PhpSecInfo_Test_Core::isTestable()</a></span><br>
</blockquote>
<!-- =========== Summary =========== -->
<p>Inherited From <span class="classname"><a href="../PhpSecInfo/PhpSecInfo_Test.html">PhpSecInfo_Test</a></span></p>
<blockquote>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#methodPhpSecInfo_Test">PhpSecInfo_Test::PhpSecInfo_Test()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#methodgetBooleanIniValue">PhpSecInfo_Test::getBooleanIniValue()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#methodgetCurrentTestValue">PhpSecInfo_Test::getCurrentTestValue()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#methodgetMessage">PhpSecInfo_Test::getMessage()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#methodgetMoreInfoURL">PhpSecInfo_Test::getMoreInfoURL()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#methodgetRecommendedTestValue">PhpSecInfo_Test::getRecommendedTestValue()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#methodgetResult">PhpSecInfo_Test::getResult()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#methodgetStringValue">PhpSecInfo_Test::getStringValue()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#methodgetTestGroup">PhpSecInfo_Test::getTestGroup()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#methodgetTestName">PhpSecInfo_Test::getTestName()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#methodgetUnixId">PhpSecInfo_Test::getUnixId()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#methodisTestable">PhpSecInfo_Test::isTestable()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#methodosIsWindows">PhpSecInfo_Test::osIsWindows()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#methodreturnBytes">PhpSecInfo_Test::returnBytes()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#methodsetMessageForResult">PhpSecInfo_Test::setMessageForResult()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#methodsetTestGroup">PhpSecInfo_Test::setTestGroup()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#methodsetTestName">PhpSecInfo_Test::setTestName()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#methodsys_get_temp_dir">PhpSecInfo_Test::sys_get_temp_dir()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#methodtest">PhpSecInfo_Test::test()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#method_execTest">PhpSecInfo_Test::_execTest()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#method_retrieveCurrentValue">PhpSecInfo_Test::_retrieveCurrentValue()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#method_setMessage">PhpSecInfo_Test::_setMessage()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#method_setMessages">PhpSecInfo_Test::_setMessages()</a></span><br>
<span class="method-name"><a href="../PhpSecInfo/PhpSecInfo_Test.html#method_setResult">PhpSecInfo_Test::_setResult()</a></span><br>
</blockquote>
</div>
</div>
<p class="notes" id="credit">
Documentation generated on Fri, 06 Apr 2007 13:32:13 -0400 by <a href="http://www.phpdoc.org" target="_blank">phpDocumentor 1.3.0RC3</a>
</p>
</div></body>
</html> |
wp-content/themes/zbench/editor-style.css | ashray-velapanur/grind-members | /*
Theme Name: zBench
Used to style the TinyMCE editor.
*/
html .mceContentBody{max-width:620px;font-size:13px;font-family:Tahoma,Arial,Helvetica,sans-serif;color:#333;background:#f7f7f7;}
* {margin:0;padding:0;}
h1,h2,h3,h4,h5,h6{font-weight:bold;}
h1{font-size:24px;line-height:30px;}
h2{font-size:20px;line-height:26px;}
h3{font-size:16px;line-height:24px;}
h4{font-size:14px;line-height:20px;}
h5{font-size:14px;line-height:20px;}
h6{font-size:14px;line-height:20px;}
small{font-size:10px;line-height:16px;}
dl{font-size:12px;}
dt{font-weight:bold;}
a{color:#047;text-decoration:none;outline:none;}
a:hover{color:#4a630f;text-decoration:none;}
fieldset,img{border:none;}
hr{color:#ddd;background-color:#ddd;height:1px;border:0px;}
ul,ol{margin:0 30px 18px;}
li{line-height:18px;}
hr{display:block;}
p{line-height:18px;margin:0 0 18px 0;}
h1,h2,h3,h4,h5,h6{margin:0 0 18px 0;color:#555;}
a{color:#333;text-decoration:underline;}
a:hover{color:#4a630f;text-decoration:none;}
img{max-width:610px;height:auto;margin:10px 0;padding:4px;background:#fff;border:1px solid #ddd;}
img.wp-smiley{background:#fff;border:none;padding:0;}
.alignleft,img.alignleft{display:inline;float:left;margin:10px 10px 10px 0;}
.alignright,img.alignright{display:inline;float:right;margin:10px 0 10px 10px;}
.aligncenter,img.aligncenter{clear:both;display:block;margin:10px auto;}
table{background:#fff;border:1px solid #ccc;border-width:2px;border-collapse:collapse;margin:5px 0 10px;}
th,td{border:1px solid #ccc;padding:3px 10px;text-align:left;vertical-align:top;}
tr.even td{background:#f7f7f7;}
th{background:#edeff0;}
blockquote{color:#555;padding:10px;margin:0 0 20px;border:1px solid #ddd;background:#eee;}
code{background:#333;color:#ddd;}
pre{overflow:auto;width:95%;line-height:16px;margin:0 0 20px;padding:0 5px 16px;color:#555;font-family:"Courier New",FixedSys;font-size:12px;background:#fafafa;border:1px solid #ccc;border-left:15px solid #ccc;}
p.read-more a,p a.more-link{display:inline;font-weight:bold;color:#4a630f;text-decoration:none;background-position:0 -20px;}
p a.more-link{display:block;margin-top:18px;}
p.read-more a:hover,p a.more-link:hover{color:#345;}
.wp-caption{text-align:center;margin-top:10px;margin-bottom:10px;padding:4px;border-radius:3px;background:#fff;border:1px solid #ddd;}
.wp-caption img{margin:0;padding:0;background:none;}
.wp-caption-dd,.wp-caption p.wp-caption-text{font-size:12px;line-height:20px;padding:4px 0 0;margin:0;} |
Library/init/zsh/man/html/prompt_kerbaugh_setup.html | jaredbonobos/zsh-templates-osx | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content=
"HTML Tidy for Mac OS X (vers 1st December 2004), see www.w3.org" />
<meta http-equiv="Content-Type" content=
"text/html; charset=us-ascii" />
<title>Manual Page for prompt_kerbaugh_setup</title>
<style type="text/css">
/*<![CDATA[*/
<!--.red {color: #CC0000}-->
/*]]>*/
</style>
<style type="text/css">
/*<![CDATA[*/
<!--.hed {color: #000000; font-weight: bold; font-size: larger;}-->
/*]]>*/
</style>
</head>
<body>
<pre>
<a href=
"http://sage.ucsc.edu/Library/init/zsh/man/html/prompt_kerbaugh_setup.html">prompt_kerbaugh_setup(7)</a> Mac OS X Darwin ZSH customization <a href="http://sage.ucsc.edu/Library/init/zsh/man/html/prompt_kerbaugh_setup.html">prompt_kerbaugh_setup(7)</a>
<span class="hed">NAME</span>
<span class=
"red">prompt_kerbaugh_setup</span> - function defining Gary Kerbaugh's colorful and
highly functional prompt
<span class="hed">SYNOPSIS</span>
prompt_kerbaugh_setup
<span class="hed">AUTHOR</span>
William Scott
<span class="hed">MAINTAINER</span>
W. G. Scott <a href=
"mailto:wgscott@users.sourceforge.net">wgscott@users.sourceforge.net</a>
Mac OS X August 5, 2005 <a href=
"http://sage.ucsc.edu/Library/init/zsh/man/html/prompt_kerbaugh_setup.html">prompt_kerbaugh_setup(7)</a>
</pre>
</body>
</html>
|
resource/tools/ArduinoUploader/Arduino/hardware/tools/avr/doc/binutils/as.html/PJ_002dDependent.html | Alexia23/MindPlus | <html lang="en">
<head>
<title>PJ-Dependent - Using as</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="Using as">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Machine-Dependencies.html#Machine-Dependencies" title="Machine Dependencies">
<link rel="prev" href="PDP_002d11_002dDependent.html#PDP_002d11_002dDependent" title="PDP-11-Dependent">
<link rel="next" href="PPC_002dDependent.html#PPC_002dDependent" title="PPC-Dependent">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
This file documents the GNU Assembler "as".
Copyright (C) 1991, 92, 93, 94, 95, 96, 97, 98, 99, 2000, 2001, 2002,
2006, 2007 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.1
or any later version published by the Free Software Foundation;
with no Invariant Sections, with no Front-Cover Texts, and with no
Back-Cover Texts. A copy of the license is included in the
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="PJ_002dDependent"></a>Next: <a rel="next" accesskey="n" href="PPC_002dDependent.html#PPC_002dDependent">PPC-Dependent</a>,
Previous: <a rel="previous" accesskey="p" href="PDP_002d11_002dDependent.html#PDP_002d11_002dDependent">PDP-11-Dependent</a>,
Up: <a rel="up" accesskey="u" href="Machine-Dependencies.html#Machine-Dependencies">Machine Dependencies</a>
<hr><br>
</div>
<h3 class="section">9.26 picoJava Dependent Features</h3>
<p><a name="index-PJ-support-1426"></a>
<ul class="menu">
<li><a accesskey="1" href="PJ-Options.html#PJ-Options">PJ Options</a>: Options
</ul>
</body></html>
|
core/templates/hubbasic2012/css/mobile.css | kevinwojo/hubzero-cms | /* Mobile Top */
.mobile-top #nav {
display: none;
}
.mobile-top #mobile-nav {
position: absolute;
right: 40px;
top: 40px;
}
/* Mobile Search */
.mobile-search #searchform {
float: left;
margin: 35px 0 0 20px;
}
.mobile-search #searchform #searchword {
float: none;
padding: 8px;
border: 1px solid #dadada;
background: #f9f9f9;
color: #555;
}
/* Mobile Wrap */
.mobile-wrap #content .inner {
margin: 0 !important;
}
.mobile-wrap #content #features {
margin: 0 !important;
}
/* Mobile Footer */
.mobile-footer {
text-align: center;
padding: 40px 0 0 0 !important;
height: 30px;
min-height: inherit !important;
} |
site/css/portal.css | salesagility/SuiteCRM-Portal-Joomla | .case_update{
-webkit-border-radius: 5px;
-moz-border-radius: 5px;
border-radius: 5px;
border: solid 1px;
margin-top: 5px;
padding: 5px;
}
.case_description{
-webkit-border-radius: 5px;
-moz-border-radius: 5px;
border-radius: 5px;
border: solid 1px;
margin-top: 5px;
padding: 5px;
min-height: 50px;
}
.user_update{
margin-right: 50px;
}
.contact_update{
margin-left: 50px;
}
.show_case_table{
width: 100%;
}
#case_table{
width: 100%;
}
.portal_form textarea {
height: 125px;
width: 375px;
}
h2 span{
font-size: 0.7em;
}
/*
* List view
*
*/
.paginate_enabled_previous{
text-decoration: underline;
}
.paginate_enabled_next{
text-decoration: underline;
margin-left: 10px;
}
.paginate_disabled_previous{
display: none;
}
.paginate_disabled_next{
display: none;
}
#case_table_info{
text-align: center;
}
#case_table_paginate{
text-align: center;
}
.table_controls{
display: inline;
}
#case_table_filter{
display: inline;
}
#case_table_filter label{
display: inline;
}
#case_table_length{
display: inline;
}
#case_table_length label{
display: inline;
}
#select_controls{
display: inline;
}
#select_controls label{
display: inline;
} |
profiles/cod/themes/cod/pisces/css/panels/cygnus/cygnus.css | DavidHernandez/DrupalCampEs | .site-branding__name {
font-size: 1.6em;
margin-bottom: 40px; }
p.button {
border-bottom: solid 3px #25496e;
-moz-border-radius: 2px;
-webkit-border-radius: 2px;
-o-border-radius: 2px;
-ms-border-radius: 2px;
-khtml-border-radius: 2px;
border-radius: 2px;
background-color: #326294;
font-size: 0.88em;
height: 40px;
padding: 10px 20px; }
p.button a:link, p.button a:visited, p.button a.active-trail, p.button a:hover, p.button a:active {
color: #fff;
text-decoration: none; }
p.button:hover {
background-color: #386fa7;
border-bottom: solid 3px #2f5d8c; }
body {
background: url(../images/white_wave.png) #f0f1f4 repeat; }
body a {
color: #326294;
text-decoration: none; }
body a:hover, body a:active {
text-decoration: underline; }
.l-header {
padding-top: 18px; }
.l-navigation {
background-color: #326294;
color: #fff;
margin-bottom: 1em; }
.l-navigation a {
color: #fff; }
.l-navigation a:hover {
color: #aec8e4; }
.l-highlighted-wrapper {
background: url(../images/highlighted.png) #4d5770 top left repeat-x;
height: 300px; }
.l-region--highlighted {
color: #fff;
padding: 30px; }
.l-region--highlighted h2 {
font-size: 2em;
margin-bottom: 1.5em;
text-align: center; }
.l-region--highlighted p a {
color: #fff;
text-decoration: none; }
.front .l-main-wrapper {
background-color: #fff; }
.not-front .l-content, .not-front .l-region--sidebar .block {
background-color: #fff; }
menu, ol, ul {
padding-left: 18px; }
img, media {
max-width: 100%; }
.l-region--sidebar .block img {
width: 100%; }
table {
border-collapse: collapse;
margin: 0 0 30px 0;
width: 100%; }
table td {
padding: 10px 10px; }
table td:first-child {
padding-right: 10px;
width: 130px; }
table tr:nth-child(even) {
background: #f1f2f5; }
body {
color: #494747;
font-size: 16px;
font-family: "PT Sans", sans-serif; }
.front .l-region--footer h2 {
font-size: 2.25em;
font-weight: normal;
line-height: 1.8em;
margin: 0;
text-align: center; }
.l-region--sidebar .block h2 {
font-size: 0.9em;
margin-top: 0;
text-transform: uppercase; }
p.button {
text-align: center;
max-width: 180px; }
.triptych img {
width: 32.6%; }
.l-region--footer .block h3 {
font-size: 1.5em;
text-align: center; }
.l-region--footer .block img {
width: 100%; }
.l-region--footer .block p {
line-height: 1.5em; }
@media (min-width: 768px) {
.l-region--footer .block {
float: left;
width: 28%;
margin: 2%; }
.l-region--footer .block:first-child {
width: 100%; }
.l-region--footer .block img {
width: 100%; } }
p.button {
border-bottom: solid 3px #25496e;
-moz-border-radius: 2px;
-webkit-border-radius: 2px;
-o-border-radius: 2px;
-ms-border-radius: 2px;
-khtml-border-radius: 2px;
border-radius: 2px;
background-color: #326294;
font-size: 0.88em;
height: 40px;
padding: 10px 20px; }
p.button a:link, p.button a:visited, p.button a.active-trail, p.button a:hover, p.button a:active {
color: #fff;
text-decoration: none; }
p.button:hover {
background-color: #386fa7;
border-bottom: solid 3px #2f5d8c; }
.l-region--navigation .menu {
padding-left: 0; }
.l-region--navigation .menu a {
text-decoration: none; }
.l-region--navigation .menu li {
display: inline;
font-size: 0.88em;
list-style-image: none;
padding: 8px 12px;
white-space: nowrap; }
.l-region--navigation .menu .expanded .menu {
display: none; }
.mean-container .mean-bar {
background: #615f5e 20px 11px no-repeat;
float: left;
min-height: 40px;
padding: 6px 0 0 0;
position: absolute;
width: 100%;
z-index: 999999; }
.mean-container .mean-nav {
background: none repeat scroll 0 0 #fff;
float: left;
margin-top: 40px;
width: 100%; }
.mean-container .mean-nav ul li a {
border-bottom: 1px solid #f0f1f4;
color: #615f5e;
display: block;
float: left;
margin: 0;
padding: 1em 5%;
text-align: left;
text-decoration: none;
text-transform: none;
width: 90%; }
.mean-container .mean-nav ul li a.mean-expand {
background: url(../images/expand.gif) transparent center center no-repeat; }
.mean-container .mean-nav ul li a.mean-expand:hover {
background: url(../images/expand.gif) transparent center center no-repeat; }
.mean-container .mean-nav ul li a.mean-expand.mean-clicked {
background: url(../images/collapse.gif) transparent center center no-repeat; }
.mean-container .mean-nav ul li li {
background-color: #f0f1f4; }
.mean-container .mean-nav ul li li:first-child {
border-top: 1px solid #d3d6de; }
.mean-container .mean-nav ul li li a {
border-bottom: 1px solid #d3d6de;
padding: 1em 7%;
width: 86%; }
.mean-nav > ul > li:last-child {
background-color: #326294; }
.mean-nav > ul > li:last-child a {
color: #fff;
text-align: center; }
.mean-container .l-region--preface .menu {
display: none; }
.l-region--preface .menu {
padding-left: 0; }
.l-region--preface .menu li {
background-color: #f0f1f4;
display: inline;
font-size: 0.84em;
list-style-image: none;
list-style: none;
padding: 10px 12px; }
.l-region--preface .menu li:hover {
background-color: #326294; }
.l-region--preface .menu li:hover a:link, .l-region--preface .menu li:hover a:visited {
color: #fff; }
.l-region--preface .menu li a {
text-decoration: none; }
.l-region--preface .menu li a:link, .l-region--preface .menu li a:visited {
color: #615f5e; }
.tabs--primary {
border-bottom: none;
margin-bottom: 0; }
.tabs--primary li {
float: left;
margin-right: 0; }
.tabs--primary a {
-moz-border-radius: 6px 6px 0 0;
-webkit-border-radius: 6px 6px 0 0;
-o-border-radius: 6px 6px 0 0;
-ms-border-radius: 6px 6px 0 0;
-khtml-border-radius: 6px 6px 0 0;
border-radius: 6px 6px 0 0;
background-color: #dbdee7; }
.tabs--primary a:hover {
background-color: #c8cddb;
text-decoration: none; }
.tabs--primary .active {
color: #000000; }
.tabs--primary a.active {
background-color: #fff;
-moz-border-radius: 6px 6px 0 0;
-webkit-border-radius: 6px 6px 0 0;
-o-border-radius: 6px 6px 0 0;
-ms-border-radius: 6px 6px 0 0;
-khtml-border-radius: 6px 6px 0 0;
border-radius: 6px 6px 0 0; }
/* Schedule */
.view-cod-session-schedule ul.quicktabs-tabs.quicktabs-style-zen, .view-cod-bof-schedule ul.quicktabs-tabs.quicktabs-style-zen, .view-cod-schedule ul.quicktabs-tabs.quicktabs-style-zen {
background: none; }
.view-cod-session-schedule ul.quicktabs-tabs.quicktabs-style-zen li, .view-cod-bof-schedule ul.quicktabs-tabs.quicktabs-style-zen li, .view-cod-schedule ul.quicktabs-tabs.quicktabs-style-zen li {
background: #494747;
border-radius: 6px;
margin-bottom: 20px; }
.view-cod-session-schedule ul.quicktabs-tabs.quicktabs-style-zen li.active, .view-cod-bof-schedule ul.quicktabs-tabs.quicktabs-style-zen li.active, .view-cod-schedule ul.quicktabs-tabs.quicktabs-style-zen li.active {
background: #615f5e; }
.view-cod-session-schedule ul.quicktabs-tabs.quicktabs-style-zen li.active a, .view-cod-bof-schedule ul.quicktabs-tabs.quicktabs-style-zen li.active a, .view-cod-schedule ul.quicktabs-tabs.quicktabs-style-zen li.active a {
background: none;
color: #fff;
padding-bottom: 4px; }
.view-cod-session-schedule ul.quicktabs-tabs.quicktabs-style-zen li a, .view-cod-bof-schedule ul.quicktabs-tabs.quicktabs-style-zen li a, .view-cod-schedule ul.quicktabs-tabs.quicktabs-style-zen li a {
background: none;
color: #fff;
padding-bottom: 4px; }
.view-cod-session-schedule .views-field-field-slot-datetime-1, .view-cod-session-schedule .views-field-field-evttime-date-1, .view-cod-bof-schedule .views-field-field-slot-datetime-1, .view-cod-bof-schedule .views-field-field-evttime-date-1, .view-cod-schedule .views-field-field-slot-datetime-1, .view-cod-schedule .views-field-field-evttime-date-1 {
background: #326294;
clear: both;
color: #fff;
padding: 15px;
font-weight: bold;
text-align: center;
border-radius: 6px; }
.view-cod-session-schedule .views-row, .view-cod-bof-schedule .views-row, .view-cod-schedule .views-row {
border-bottom: 1px solid #CCCCCC;
clear: both;
float: left;
padding-bottom: 20px;
padding-top: 24px;
width: 100%; }
.view-cod-session-schedule .views-row.views-row-last, .view-cod-bof-schedule .views-row.views-row-last, .view-cod-schedule .views-row.views-row-last {
border-bottom: none; }
.view-cod-session-schedule .views-field-field-experience, .view-cod-bof-schedule .views-field-field-experience, .view-cod-schedule .views-field-field-experience {
float: right; }
.view-cod-session-schedule .views-field-title, .view-cod-bof-schedule .views-field-title, .view-cod-schedule .views-field-title {
font-weight: bold;
font-size: 1.2em;
margin-bottom: 20px; }
.view-cod-session-schedule .views-field-title a, .view-cod-bof-schedule .views-field-title a, .view-cod-schedule .views-field-title a {
text-decoration: none; }
.view-cod-session-schedule .views-field-room, .view-cod-session-schedule .views-field-name, .view-cod-session-schedule .views-field-field-speakers, .view-cod-session-schedule .views-field-field-session-track, .view-cod-bof-schedule .views-field-room, .view-cod-bof-schedule .views-field-name, .view-cod-bof-schedule .views-field-field-speakers, .view-cod-bof-schedule .views-field-field-session-track, .view-cod-schedule .views-field-room, .view-cod-schedule .views-field-name, .view-cod-schedule .views-field-field-speakers, .view-cod-schedule .views-field-field-session-track {
float: left;
height: 28px;
margin: 0 20px 10px 0;
padding-top: 4px;
padding-left: 30px; }
.view-cod-session-schedule .views-field-room, .view-cod-session-schedule .views-field-name, .view-cod-bof-schedule .views-field-room, .view-cod-bof-schedule .views-field-name, .view-cod-schedule .views-field-room, .view-cod-schedule .views-field-name {
background: url(../images/location.png) transparent center left no-repeat; }
.view-cod-session-schedule .views-field-field-speakers, .view-cod-bof-schedule .views-field-field-speakers, .view-cod-schedule .views-field-field-speakers {
background: url(../images/speaker.png) transparent center left no-repeat; }
.view-cod-session-schedule .views-field-field-session-track, .view-cod-bof-schedule .views-field-field-session-track, .view-cod-schedule .views-field-field-session-track {
background: url(../images/track.png) transparent center left no-repeat; }
.view-cod-sponsors .level {
clear: both; }
.view-cod-sponsors .sponsor {
display: inline-block;
padding: 20px;
vertical-align: middle; }
.user-profile h2 {
margin-bottom: 0; }
.user-profile h3 {
margin-top: 0; }
.user-profile .user-picture {
float: right; }
.user-profile .user-picture img {
border: 1px solid #c4c8d4;
margin: 0.83em 0 12px 12px; }
.l-page .img-float img {
float: left;
margin-right: 15px; }
.pane-content.img-sm img,
.img-sm img {
max-width: 100%;
width: 125px; }
.pane-content.img-md img,
.img-md img {
max-width: 100%;
width: 320px; }
.pane-content.img-lg img,
.img-lg img {
max-width: 100%;
width: 485px; }
.pane-content.img-xl img,
.img-xl img {
max-width: 100%;
width: 650px; }
#panels-dnd-main .grid-4 .width-25, #panels-dnd-main .grid-4 .width-33, #panels-dnd-main .grid-4 .width-50, #panels-dnd-main .grid-3 .width-25, #panels-dnd-main .grid-3 .width-33, #panels-dnd-main .grid-3 .width-50, #panels-dnd-main .grid-3 .width-66, #panels-dnd-main .grid-3 .width-75 {
background: #85231B; }
#page #panels-dnd-main .changed .grabber,
#page #panels-dnd-main .ajax-changed .grabber {
background: #C56827; }
#page #panels-dnd-main .hidden .grabber {
background: #dedede; }
.page-admin-structure-mini-panels form:before,
.page-manager-wrapper form:before {
content: "Fixed width regions are yellow, absolutely positioned regions are blue. You do not need to use every region in a panel. Unused panel regions will disappear.";
font-weight: bold;
color: blue; }
.page-admin-structure-mini-panels form:before {
content: "Fixed width regions are yellow, absolutely positioned regions are blue. You do not need to use every region in a panel. Unused panel regions will disappear.";
font-weight: bold;
color: blue; }
.page-admin-structure-mini-panels .wizard-trail,
#panels-choose-layout .wizard-trail {
padding-top: 20px; }
#panels-dnd-main *, #panels-dnd-main *:after, #panels-dnd-main *:before {
-webkit-box-sizing: border-box;
-moz-box-sizing: border-box;
box-sizing: border-box; }
#panels-dnd-main .panel-pane {
vertical-align: top;
min-width: 90px;
float: none !important;
display: inline-block;
padding: 0 !important;
border: 1px solid #777;
margin: 0 !important; }
#panels-dnd-main .panel-pane.width-25 {
width: 25% !important; }
#panels-dnd-main .panel-pane.width-33 {
width: 33% !important; }
#panels-dnd-main .panel-pane.width-50 {
width: 50% !important; }
#panels-dnd-main .panel-pane.width-66 {
width: 66% !important; }
#panels-dnd-main .panel-pane.width-75 {
width: 75% !important; }
#panels-dnd-main .panel-pane.width-100 {
width: 100% !important; }
#panels-dnd-main .panel-pane .pane-title:after {
height: 13px;
display: inline-block;
width: 100%;
content: ".";
color: white !important;
text-indent: 21px; }
#panels-dnd-main .panel-pane.changed .pane-title:after {
font-size: 0.8em;
color: crimson !important;
letter-spacing: normal;
line-height: 1;
background: #FFF;
display: inline-block;
text-indent: 0;
padding-left: 5px; }
.page-manager-ajax-pad {
background: #DFDFDF; }
#page-manager-edit .clearfix,
#page-manager-edit .page-manager-tabs,
#page-manager-edit .page-manager-wrapper,
#page-manager-edit .panel-panel,
#page-manager-edit .panel-display {
overflow: visible !important; }
#page #panels-dnd-main .panel-pane {
position: relative;
float: left;
width: 100%; }
#page #panels-dnd-main .panel-pane.width-25 {
width: 25%;
float: left; }
#page #panels-dnd-main .panel-pane.width-33 {
width: 33.33%;
float: left; }
#page #panels-dnd-main .panel-pane.width-50 {
width: 50%;
float: left; }
#page #panels-dnd-main .panel-pane.width-66 {
width: 66%;
float: left; }
#page #panels-dnd-main .panel-pane.width-75 {
width: 75%;
float: left; }
#page #panels-dnd-main .panel-pane.width-100 {
width: 100%;
float: left; }
#page #panels-dnd-main .panel-pane .pane-content {
margin: 0 10px;
position: relative; }
#page #panels-dnd-main .panel-pane {
margin: 0; }
#page #panels-dnd-main .panel-region {
padding: 5px;
margin: 0;
border: white 2px dashed;
overflow: hidden;
*zoom: 1;
overflow: visible;
background: rgba(248, 248, 248, 0.4);
float: left;
width: 100%;
line-height: 0; }
#page #panels-dnd-main .panel-region h2.label {
line-height: 1.5;
font-size: 1.3em;
color: black; }
#page #panels-dnd-main .panel-region .panel-pane {
line-height: 1.2;
max-width: 100%; }
#page #panels-dnd-main div.ctools-dropdown div.ctools-dropdown-container ul {
line-height: 1.3; }
#page #panels-dnd-main .container-inner.grid-12 {
float: left;
width: 100%; }
#page #panels-dnd-main .panel-region:after,
#page #panels-dnd-main .container-inner:after,
#page #panels-dnd-main .column-content-region:after {
content: ".";
font-size: 0;
clear: both; }
.grid-3,
.width-25 {
width: 25%;
float: left; }
.grid-4,
.width-33 {
width: 33.33%;
float: left; }
.grid-6,
.width-50 {
width: 50%;
float: left; }
.grid-8,
.width-66 {
width: 66%;
float: left; }
.grid-9,
.width-75 {
width: 75%;
float: left; }
.grid-12,
.width-100 {
width: 100%;
float: left; }
.panel-display .float-right {
float: right; }
.panel-display .float-left {
float: left; }
.panel-display .clear-left {
clear: left; }
.panel-display .clear-right {
clear: right; }
.panel-display .clear-both {
clear: both; }
body #page .panel-display .clear-left,
body #page .panel-display .grid-12,
body #page .panel-display .width-100 {
padding-left: 0; }
.panel-layout {
margin: 0;
max-width: 1200px; }
.panel-layout .container {
float: left;
clear: left;
width: 100%; }
.panel-layout .panel-pane {
position: relative; }
.panel-layout .panel-pane.width-25 {
width: 25%;
float: left; }
.panel-layout .panel-pane.width-33 {
width: 33.33%;
float: left; }
.panel-layout .panel-pane.width-50 {
width: 50%;
float: left; }
.panel-layout .panel-pane.width-66 {
width: 66%;
float: left; }
.panel-layout .panel-pane.width-75 {
width: 75%;
float: left; }
.panel-layout .panel-pane.width-100 {
width: 100%;
float: left; }
.panel-layout .panel-pane .pane-content {
padding: 0 10px;
position: relative;
overflow: hidden;
*zoom: 1; }
.panel-layout .container {
position: relative; }
@media (max-width: 750px) {
.panel-layout .container .panel-pane.width-25 {
width: 50%; } }
@media (max-width: 550px) {
.panel-layout .container .panel-pane.width-33 {
width: 100%; } }
@media (max-width: 480px) {
.panel-layout .container .panel-pane.width-25 {
width: 100%; } }
@media screen and (min-width: 1075px) and (max-width: 5000px) {
.panel-layout .preface .width-25 .img-sm img, .panel-layout .footer .width-25 .img-sm img, .panel-layout .content .width-25 .img-sm img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 1855px) and (max-width: 5000px) {
.panel-layout .preface .width-25 .img-md img, .panel-layout .footer .width-25 .img-md img, .panel-layout .content .width-25 .img-md img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 2515px) and (max-width: 5000px) {
.panel-layout .preface .width-25 .img-lg img, .panel-layout .footer .width-25 .img-lg img, .panel-layout .content .width-25 .img-lg img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 3175px) and (max-width: 5000px) {
.panel-layout .preface .width-25 .img-xl img, .panel-layout .footer .width-25 .img-xl img, .panel-layout .content .width-25 .img-xl img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 820px) and (max-width: 5000px) {
.panel-layout .preface .width-33 .img-sm img, .panel-layout .footer .width-33 .img-sm img, .panel-layout .content .width-33 .img-sm img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 1405px) and (max-width: 5000px) {
.panel-layout .preface .width-33 .img-md img, .panel-layout .footer .width-33 .img-md img, .panel-layout .content .width-33 .img-md img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 1900px) and (max-width: 5000px) {
.panel-layout .preface .width-33 .img-lg img, .panel-layout .footer .width-33 .img-lg img, .panel-layout .content .width-33 .img-lg img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 2395px) and (max-width: 5000px) {
.panel-layout .preface .width-33 .img-xl img, .panel-layout .footer .width-33 .img-xl img, .panel-layout .content .width-33 .img-xl img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 565px) and (max-width: 5000px) {
.panel-layout .preface .width-50 .img-sm img, .panel-layout .footer .width-50 .img-sm img, .panel-layout .content .width-50 .img-sm img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 955px) and (max-width: 5000px) {
.panel-layout .preface .width-50 .img-md img, .panel-layout .footer .width-50 .img-md img, .panel-layout .content .width-50 .img-md img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 1285px) and (max-width: 5000px) {
.panel-layout .preface .width-50 .img-lg img, .panel-layout .footer .width-50 .img-lg img, .panel-layout .content .width-50 .img-lg img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 1615px) and (max-width: 5000px) {
.panel-layout .preface .width-50 .img-xl img, .panel-layout .footer .width-50 .img-xl img, .panel-layout .content .width-50 .img-xl img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 437.5px) and (max-width: 5000px) {
.panel-layout .preface .width-66 .img-sm img, .panel-layout .footer .width-66 .img-sm img, .panel-layout .content .width-66 .img-sm img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 730px) and (max-width: 5000px) {
.panel-layout .preface .width-66 .img-md img, .panel-layout .footer .width-66 .img-md img, .panel-layout .content .width-66 .img-md img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 977.5px) and (max-width: 5000px) {
.panel-layout .preface .width-66 .img-lg img, .panel-layout .footer .width-66 .img-lg img, .panel-layout .content .width-66 .img-lg img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 1225px) and (max-width: 5000px) {
.panel-layout .preface .width-66 .img-xl img, .panel-layout .footer .width-66 .img-xl img, .panel-layout .content .width-66 .img-xl img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 394.15px) and (max-width: 5000px) {
.panel-layout .preface .width-75 .img-sm img, .panel-layout .footer .width-75 .img-sm img, .panel-layout .content .width-75 .img-sm img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 653.5px) and (max-width: 5000px) {
.panel-layout .preface .width-75 .img-md img, .panel-layout .footer .width-75 .img-md img, .panel-layout .content .width-75 .img-md img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 872.95px) and (max-width: 5000px) {
.panel-layout .preface .width-75 .img-lg img, .panel-layout .footer .width-75 .img-lg img, .panel-layout .content .width-75 .img-lg img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 1092.4px) and (max-width: 5000px) {
.panel-layout .preface .width-75 .img-xl img, .panel-layout .footer .width-75 .img-xl img, .panel-layout .content .width-75 .img-xl img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 310px) and (max-width: 5000px) {
.panel-layout .preface .width-100 .img-sm img, .panel-layout .footer .width-100 .img-sm img, .panel-layout .content .width-100 .img-sm img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 505px) and (max-width: 5000px) {
.panel-layout .preface .width-100 .img-md img, .panel-layout .footer .width-100 .img-md img, .panel-layout .content .width-100 .img-md img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 670px) and (max-width: 5000px) {
.panel-layout .preface .width-100 .img-lg img, .panel-layout .footer .width-100 .img-lg img, .panel-layout .content .width-100 .img-lg img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
@media screen and (min-width: 835px) and (max-width: 5000px) {
.panel-layout .preface .width-100 .img-xl img, .panel-layout .footer .width-100 .img-xl img, .panel-layout .content .width-100 .img-xl img {
float: left;
margin-right: 15px;
margin-bottom: 10px; } }
|
web/public/java.css | severinh/java-gnome | /*
* java.css
*
* Copyright (c) 2008-2010 Operational Dynamics Consulting, Pty Ltd
*
* This file comprises part of the infrastructure and content of the
* java-gnome project website. As such, it is conveyed alongside the source
* code and is made available to you by its authors under the terms of the
* "GNU General Public Licence, version 2". See the LICENCE file for the terms
* governing usage, copying and redistribution.
*
* CSS properties for syntax highlighting Java source files, as formatted in
* HTML with the GNU source-highlight program.
*/
.preproc {
color: #7F0055;
font-weight: bold;
}
.keyword {
color: #7F0055;
font-weight: bold;
}
.comment {
color: #296F4C;
}
.type {
color: #7F0055;
font-weight: bold;
}
.string {
color: #2A00FF;
font-weight: bold;
}
/*
* Custom; not in 2.5 output, and manually hacked into example.
*/
.javadoc {
color: #3F5FBF;
}
.tag {
color: #7F7F9F;
}
/*
* Hide line numbers
*/
.linenum {
display: none;
}
|
doc/processors.html | dineshram2010/Enhanced-Heat-Exchanger-Design-using-Constructal-Networks | <HTML>
<CENTER><A HREF = "http://www.cfdem.com">LIGGGHTS(R)-PUBLIC WWW Site</A> - <A HREF = "Manual.html">LIGGGHTS(R)-PUBLIC Documentation</A> - <A HREF = "Section_commands.html#comm">LIGGGHTS(R)-PUBLIC Commands</A>
</CENTER>
<HR>
<H3>processors command
</H3>
<P><B>Syntax:</B>
</P>
<PRE>processors Px Py Pz keyword args ...
</PRE>
<UL><LI>Px,Py,Pz = # of processors in each dimension of 3d grid overlaying the simulation domain
<LI>zero or more keyword/arg pairs may be appended
<LI>keyword = <I>grid</I> or <I>map</I> or <I>part</I> or <I>file</I>
<PRE> <I>grid</I> arg = gstyle params ...
gstyle = <I>onelevel</I> or <I>twolevel</I> or <I>numa</I> or <I>custom</I>
onelevel params = none
twolevel params = Nc Cx Cy Cz
Nc = number of cores per node
Cx,Cy,Cz = # of cores in each dimension of 3d sub-grid assigned to each node
numa params = none
custom params = infile
infile = file containing grid layout
<I>map</I> arg = <I>cart</I> or <I>cart/reorder</I> or <I>xyz</I> or <I>xzy</I> or <I>yxz</I> or <I>yzx</I> or <I>zxy</I> or <I>zyx</I>
cart = use MPI_Cart() methods to map processors to 3d grid with reorder = 0
cart/reorder = use MPI_Cart() methods to map processors to 3d grid with reorder = 1
xyz,xzy,yxz,yzx,zxy,zyx = map procesors to 3d grid in IJK ordering
<I>numa</I> arg = none
<I>part</I> args = Psend Precv cstyle
Psend = partition # (1 to Np) which will send its processor layout
Precv = partition # (1 to Np) which will recv the processor layout
cstyle = <I>multiple</I>
<I>multiple</I> = Psend grid will be multiple of Precv grid in each dimension
<I>file</I> arg = outfile
outfile = name of file to write 3d grid of processors to
</PRE>
</UL>
<P><B>Examples:</B>
</P>
<PRE>processors * * 5
processors 2 4 4
processors * * 8 map xyz
processors * * * grid numa
processors * * * grid twolevel 4 * * 1
processors 4 8 16 grid custom myfile
processors * * * part 1 2 multiple
</PRE>
<P><B>Description:</B>
</P>
<P>Specify how processors are mapped as a 3d logical grid to the global
simulation box. This involves 2 steps. First if there are P
processors it means choosing a factorization P = Px by Py by Pz so
that there are Px processors in the x dimension, and similarly for the
y and z dimensions. Second, the P processors are mapped to the
logical 3d grid. The arguments to this command control each of these
2 steps.
</P>
<P>The Px, Py, Pz parameters affect the factorization. Any of the 3
parameters can be specified with an asterisk "*", which means LIGGGHTS(R)-PUBLIC
will choose the number of processors in that dimension of the grid.
It will do this based on the size and shape of the global simulation
box so as to minimize the surface-to-volume ratio of each processor's
sub-domain.
</P>
<P>Since LIGGGHTS(R)-PUBLIC does not load-balance by changing the grid of 3d
processors on-the-fly, choosing explicit values for Px or Py or Pz can
be used to override the LIGGGHTS(R)-PUBLIC default if it is known to be
sub-optimal for a particular problem. E.g. a problem where the extent
of atoms will change dramatically in a particular dimension over the
course of the simulation.
</P>
<P>The product of Px, Py, Pz must equal P, the total # of processors
LIGGGHTS(R)-PUBLIC is running on. For a <A HREF = "dimension.html">2d simulation</A>, Pz must
equal 1.
</P>
<P>Note that if you run on a prime number of processors P, then a grid
such as 1 x P x 1 will be required, which may incur extra
communication costs due to the high surface area of each processor's
sub-domain.
</P>
<P>Also note that if multiple partitions are being used then P is the
number of processors in this partition; see <A HREF = "Section_start.html#start_7">this
section</A> for an explanation of the
-partition command-line switch. Also note that you can prefix the
processors command with the <A HREF = "partition.html">partition</A> command to
easily specify different Px,Py,Pz values for different partitions.
</P>
<P>You can use the <A HREF = "partition.html">partition</A> command to specify
different processor grids for different partitions, e.g.
</P>
<PRE>partition yes 1 processors 4 4 4
partition yes 2 processors 2 3 2
</PRE>
<HR>
<P>The <I>grid</I> keyword affects the factorization of P into Px,Py,Pz and it
can also affect how the P processor IDs are mapped to the 3d grid of
processors.
</P>
<P>The <I>onelevel</I> style creates a 3d grid that is compatible with the
Px,Py,Pz settings, and which minimizes the surface-to-volume ratio of
each processor's sub-domain, as described above. The mapping of
processors to the grid is determined by the <I>map</I> keyword setting.
</P>
<P>The <I>twolevel</I> style can be used on machines with multicore nodes to
minimize off-node communication. It insures that contiguous
sub-sections of the 3d grid are assigned to all the cores of a node.
For example if <I>Nc</I> is 4, then 2x2x1 or 2x1x2 or 1x2x2 sub-sections of
the 3d grid will correspond to the cores of each node. This affects
both the factorization and mapping steps.
</P>
<P>The <I>Cx</I>, <I>Cy</I>, <I>Cz</I> settings are similar to the <I>Px</I>, <I>Py</I>, <I>Pz</I>
settings, only their product should equal <I>Nc</I>. Any of the 3
parameters can be specified with an asterisk "*", which means LIGGGHTS(R)-PUBLIC
will choose the number of cores in that dimension of the node's
sub-grid. As with Px,Py,Pz, it will do this based on the size and
shape of the global simulation box so as to minimize the
surface-to-volume ratio of each processor's sub-domain.
</P>
<P>IMPORTANT NOTE: For the <I>twolevel</I> style to work correctly, it
assumes the MPI ranks of processors LIGGGHTS(R)-PUBLIC is running on are ordered
by core and then by node. E.g. if you are running on 2 quad-core
nodes, for a total of 8 processors, then it assumes processors 0,1,2,3
are on node 1, and processors 4,5,6,7 are on node 2. This is the
default rank ordering for most MPI implementations, but some MPIs
provide options for this ordering, e.g. via environment variable
settings.
</P>
<P>The <I>numa</I> style operates similar to the <I>twolevel</I> keyword except
that it auto-detects which cores are running on which nodes.
Currently, it does this in only 2 levels, but it may be extended in
the future to account for socket topology and other non-uniform memory
access (NUMA) costs. It also uses a different algorithm than the
<I>twolevel</I> keyword for doing the two-level factorization of the
simulation box into a 3d processor grid to minimize off-node
communication, and it does its own MPI-based mapping of nodes and
cores to the logical 3d grid. Thus it may produce a different layout
of the processors than the <I>twolevel</I> options.
</P>
<P>The <I>numa</I> style will give an error if the number of MPI processes is
not divisible by the number of cores used per node, or any of the Px
or Py of Pz values is greater than 1.
</P>
<P>IMPORTANT NOTE: Unlike the <I>twolevel</I> style, the <I>numa</I> style does not
require any particular ordering of MPI ranks i norder to work
correctly. This is because it auto-detects which processes are
running on which nodes.
</P>
<P>The <I>custom</I> style uses the file <I>infile</I> to define both the 3d
factorization and the mapping of processors to the grid.
</P>
<P>The file should have the following format. Any number of initial
blank or comment lines (starting with a "#" character) can be present.
The first non-blank, non-comment line should have
3 values:
</P>
<PRE>Px Py Py
</PRE>
<P>These must be compatible with the total number of processors
and the Px, Py, Pz settings of the processors commmand.
</P>
<P>This line should be immediately followed by
P = Px*Py*Pz lines of the form:
</P>
<PRE>ID I J K
</PRE>
<P>where ID is a processor ID (from 0 to P-1) and I,J,K are the
processors location in the 3d grid. I must be a number from 1 to Px
(inclusive) and similarly for J and K. The P lines can be listed in
any order, but no processor ID should appear more than once.
</P>
<HR>
<P>The <I>map</I> keyword affects how the P processor IDs (from 0 to P-1) are
mapped to the 3d grid of processors. It is only used by the
<I>onelevel</I> and <I>twolevel</I> grid settings.
</P>
<P>The <I>cart</I> style uses the family of MPI Cartesian functions to perform
the mapping, namely MPI_Cart_create(), MPI_Cart_get(),
MPI_Cart_shift(), and MPI_Cart_rank(). It invokes the
MPI_Cart_create() function with its reorder flag = 0, so that MPI is
not free to reorder the processors.
</P>
<P>The <I>cart/reorder</I> style does the same thing as the <I>cart</I> style
except it sets the reorder flag to 1, so that MPI can reorder
processors if it desires.
</P>
<P>The <I>xyz</I>, <I>xzy</I>, <I>yxz</I>, <I>yzx</I>, <I>zxy</I>, and <I>zyx</I> styles are all
similar. If the style is IJK, then it maps the P processors to the
grid so that the processor ID in the I direction varies fastest, the
processor ID in the J direction varies next fastest, and the processor
ID in the K direction varies slowest. For example, if you select
style <I>xyz</I> and you have a 2x2x2 grid of 8 processors, the assignments
of the 8 octants of the simulation domain will be:
</P>
<PRE>proc 0 = lo x, lo y, lo z octant
proc 1 = hi x, lo y, lo z octant
proc 2 = lo x, hi y, lo z octant
proc 3 = hi x, hi y, lo z octant
proc 4 = lo x, lo y, hi z octant
proc 5 = hi x, lo y, hi z octant
proc 6 = lo x, hi y, hi z octant
proc 7 = hi x, hi y, hi z octant
</PRE>
<P>Note that, in principle, an MPI implementation on a particular machine
should be aware of both the machine's network topology and the
specific subset of processors and nodes that were assigned to your
simulation. Thus its MPI_Cart calls can optimize the assignment of
MPI processes to the 3d grid to minimize communication costs. In
practice, however, few if any MPI implementations actually do this.
So it is likely that the <I>cart</I> and <I>cart/reorder</I> styles simply give
the same result as one of the IJK styles.
</P>
<P>Also note, that for the <I>twolevel</I> grid style, the <I>map</I> setting is
used to first map the nodes to the 3d grid, then again to the cores
within each node. For the latter step, the <I>cart</I> and <I>cart/reorder</I>
styles are not supported, so an <I>xyz</I> style is used in their place.
</P>
<HR>
<P>The <I>part</I> keyword affects the factorization of P into Px,Py,Pz.
</P>
<P>It can be useful when running in multi-partition mode, e.g. with the
<A HREF = "run_style.html">run_style verlet/split</A> command. It specifies a
dependency bewteen a sending partition <I>Psend</I> and a receiving
partition <I>Precv</I> which is enforced when each is setting up their own
mapping of their processors to the simulation box. Each of <I>Psend</I>
and <I>Precv</I> must be integers from 1 to Np, where Np is the number of
partitions you have defined via the <A HREF = "Section_start.html#start_7">-partition command-line
switch</A>.
</P>
<P>A "dependency" means that the sending partition will create its 3d
logical grid as Px by Py by Pz and after it has done this, it will
send the Px,Py,Pz values to the receiving partition. The receiving
partition will wait to receive these values before creating its own 3d
logical grid and will use the sender's Px,Py,Pz values as a
constraint. The nature of the constraint is determined by the
<I>cstyle</I> argument.
</P>
<P>For a <I>cstyle</I> of <I>multiple</I>, each dimension of the sender's processor
grid is required to be an integer multiple of the corresponding
dimension in the receiver's processor grid. This is a requirement of
the <A HREF = "run_style.html">run_style verlet/split</A> command.
</P>
<P>For example, assume the sending partition creates a 4x6x10 grid = 240
processor grid. If the receiving partition is running on 80
processors, it could create a 4x2x10 grid, but it will not create a
2x4x10 grid, since in the y-dimension, 6 is not an integer multiple of
4.
</P>
<P>IMPORTANT NOTE: If you use the <A HREF = "partition.html">partition</A> command to
invoke different "processsors" commands on different partitions, and
you also use the <I>part</I> keyword, then you must insure that both the
sending and receiving partitions invoke the "processors" command that
connects the 2 partitions via the <I>part</I> keyword. LIGGGHTS(R)-PUBLIC cannot
easily check for this, but your simulation will likely hang in its
setup phase if this error has been made.
</P>
<HR>
<P>The <I>file</I> keyword writes the mapping of the factorization of P
processors and their mapping to the 3d grid to the specified file
<I>outfile</I>. This is useful to check that you assigned physical
processors in the manner you desired, which can be tricky to figure
out, especially when running on multiple partitions or on, a multicore
machine or when the processor ranks were reordered by use of the
<A HREF = "Section_start.html#start_7">-reorder command-line switch</A> or due to
use of MPI-specific launch options such as a config file.
</P>
<P>If you have multiple partitions you should insure that each one writes
to a different file, e.g. using a <A HREF = "variable.html">world-style variable</A>
for the filename. The file has a self-explanatory header, followed by
one-line per processor in this format:
</P>
<P>world-ID universe-ID original-ID: I J K: name
</P>
<P>The IDs are the processor's rank in this simulation (the world), the
universe (of multiple simulations), and the original MPI communicator
used to instantiate LIGGGHTS(R)-PUBLIC, respectively. The world and universe IDs
will only be different if you are running on more than one partition;
see the <A HREF = "Section_start.html#start_7">-partition command-line switch</A>.
The universe and original IDs will only be different if you used the
<A HREF = "Section_start.html#start_7">-reorder command-line switch</A> to reorder
the processors differently than their rank in the original
communicator LIGGGHTS(R)-PUBLIC was instantiated with.
</P>
<P>I,J,K are the indices of the processor in the 3d logical grid, each
from 1 to Nd, where Nd is the number of processors in that dimension
of the grid.
</P>
<P>The <I>name</I> is what is returned by a call to MPI_Get_processor_name()
and should represent an identifier relevant to the physical processors
in your machine. Note that depending on the MPI implementation,
multiple cores can have the same <I>name</I>.
</P>
<HR>
<P><B>Restrictions:</B>
</P>
<P>This command cannot be used after the simulation box is defined by a
<A HREF = "read_data.html">read_data</A> or <A HREF = "create_box.html">create_box</A> command.
It can be used before a restart file is read to change the 3d
processor grid from what is specified in the restart file.
</P>
<P>The <I>grid numa</I> keyword only currently works with the <I>map cart</I>
option.
</P>
<P>The <I>part</I> keyword (for the receiving partition) only works with the
<I>grid onelevel</I> or <I>grid twolevel</I> options.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "partition.html">partition</A>, <A HREF = "Section_start.html#start_7">-reorder command-line
switch</A>
</P>
<P><B>Default:</B>
</P>
<P>The option defaults are Px Py Pz = * * *, grid = onelevel, and map =
cart.
</P>
</HTML>
|
wp-content/themes/sg-window/inc/css/list.css | maskweb/maskconcursos | .column-4 .element-list {
-webkit-column-count: 2;
-moz-column-count: 2;
column-count: 2;
}
@media screen and (min-width: 500px) {
.column-2 .element-list {
-webkit-column-count: 2;
-moz-column-count: 2;
column-count: 2;
}
.column-3 .element-list {
-webkit-column-count: 3;
-moz-column-count: 3;
column-count: 3;
}
.column-4 .element-list {
-webkit-column-count: 4;
-moz-column-count: 4;
column-count: 4;
}
} |
php/5.5/function.runkit-import.html | rafaelgou/the-phpjs-local-docs-collection | <!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=UTF-8">
<title>Process a PHP file importing function and class definitions, overwriting where appropriate</title>
</head>
<body><div class="manualnavbar" style="text-align: center;">
<div class="prev" style="text-align: left; float: left;"><a href="function.runkit-function-rename.html">runkit_function_rename</a></div>
<div class="next" style="text-align: right; float: right;"><a href="function.runkit-lint-file.html">runkit_lint_file</a></div>
<div class="up"><a href="ref.runkit.html">runkit Functions</a></div>
<div class="home"><a href="index.html">PHP Manual</a></div>
</div><hr /><div id="function.runkit-import" class="refentry">
<div class="refnamediv">
<h1 class="refname">runkit_import</h1>
<p class="verinfo">(PECL runkit >= 0.7.0)</p><p class="refpurpose"><span class="refname">runkit_import</span> — <span class="dc-title">
Process a PHP file importing function and class definitions, overwriting where appropriate
</span></p>
</div>
<div class="refsect1 description" id="refsect1-function.runkit-import-description">
<h3 class="title">Description</h3>
<div class="methodsynopsis dc-description">
<span class="type">bool</span> <span class="methodname"><strong>runkit_import</strong></span>
( <span class="methodparam"><span class="type">string</span> <code class="parameter">$filename</code></span>
[, <span class="methodparam"><span class="type">int</span> <code class="parameter">$flags</code><span class="initializer"> = RUNKIT_IMPORT_CLASS_METHODS</span></span>
] )</div>
<p class="para rdfs-comment">
Similar to <span class="function"><a href="function.include.html" class="function">include</a></span> however any code residing outside
of a function or class is simply ignored.
Additionally, depending on the value of <code class="parameter">flags</code>,
any functions or classes which already exist in the currently running environment
will be automatically overwritten by their new definitions.
</p>
</div>
<div class="refsect1 parameters" id="refsect1-function.runkit-import-parameters">
<h3 class="title">Parameters</h3>
<p class="para">
<dl>
<dt>
<code class="parameter">filename</code></dt>
<dd>
<p class="para">
Filename to import function and class definitions from
</p>
</dd>
<dt>
<code class="parameter">flags</code></dt>
<dd>
<p class="para">
Bitwise OR of the <strong><code>RUNKIT_IMPORT_*</code></strong> family of constants.
</p>
</dd>
</dl>
</p>
</div>
<div class="refsect1 returnvalues" id="refsect1-function.runkit-import-returnvalues">
<h3 class="title">Return Values</h3>
<p class="para">
Returns <strong><code>TRUE</code></strong> on success or <strong><code>FALSE</code></strong> on failure.
</p>
</div>
</div><hr /><div class="manualnavbar" style="text-align: center;">
<div class="prev" style="text-align: left; float: left;"><a href="function.runkit-function-rename.html">runkit_function_rename</a></div>
<div class="next" style="text-align: right; float: right;"><a href="function.runkit-lint-file.html">runkit_lint_file</a></div>
<div class="up"><a href="ref.runkit.html">runkit Functions</a></div>
<div class="home"><a href="index.html">PHP Manual</a></div>
</div></body></html>
|
texi2html/test/encodings/res/nodetest_use_nodes_no_unidecode/c.html | cgwalters/texinfo-git-mirror | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
<head>
<title>Untitled Document: 7.1 ç</title>
<meta name="description" content="Untitled Document: 7.1 ç">
<meta name="keywords" content="Untitled Document: 7.1 ç">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="texi2html">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
div.smalllisp {margin-left: 3.2em}
pre.display {font-family: serif}
pre.format {font-family: serif}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: serif; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: serif; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.nocodebreak {white-space:pre}
span.nolinebreak {white-space:pre}
span.roman {font-family:serif; font-weight:normal}
span.sansserif {font-family:sans-serif; font-weight:normal}
ul.no-bullet {list-style: none}
-->
</style>
</head>
<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
<a name="g_t_00e7"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="cedilla-accent.html#cedilla-accent" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="cedilla-accent.html#cedilla-accent" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="cedilla-accent.html#cedilla-accent" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="C.html#g_t_00c7" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="rest.html#rest" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="nodetest_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[Index]</td>
<td valign="middle" align="left">[<a href="nodetest_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<hr>
<a name="c"></a>
<h2 class="section">7.1 ç</h2>
<hr>
<p>
<font size="-1">
This document was generated on <em>a sunny day</em> using <a href="http://www.gnu.org/software/texinfo/"><em>texi2html</em></a>.
</font>
<br>
</p>
</body>
</html>
|
game/data/scripts/ai/npc/Trainers/HealerTrainer/cleanse-no.html | karolusw/l2j | <html><body>
To reset the skill link requires 10 million Adena. In addition, your class must corresponding to the skill.
</body></html> |
game/data/scripts/quests/Q00016_TheComingDarkness/31517-05.html | karolusw/l2j | <html><body>Hierarch:<br>
We've spent much time together, dear brother, but I regret to tell you that you're not yet ready! Try again when your faith and conviction are more firmly established.<br>
(Only characters of level 62 and above may undertake this quest.)
</body></html> |
CSE167X/hw2-windows_VS2012/hw2-windows/glm-0.9.2.7/doc/api-0.9.2/a00056_source.html | wessamfathi/GFX | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<title>half_float.hpp Source File</title>
<link href="tabs.css" rel="stylesheet" type="text/css"/>
<link href="doxygen.css" rel="stylesheet" type="text/css"/>
</head>
<body>
<!-- Generated by Doxygen 1.7.4 -->
<div id="top">
<div id="titlearea">
<table cellspacing="0" cellpadding="0">
<tbody>
<tr style="height: 56px;">
<td id="projectlogo"><img alt="Logo" src="logo-mini.png"/></td>
</tr>
</tbody>
</table>
</div>
<div id="navrow1" class="tabs">
<ul class="tablist">
<li><a href="index.html"><span>Main Page</span></a></li>
<li><a href="modules.html"><span>Modules</span></a></li>
<li><a href="namespaces.html"><span>Namespaces</span></a></li>
<li><a href="annotated.html"><span>Classes</span></a></li>
<li class="current"><a href="files.html"><span>Files</span></a></li>
</ul>
</div>
<div id="navrow2" class="tabs2">
<ul class="tablist">
<li><a href="files.html"><span>File List</span></a></li>
</ul>
</div>
<div class="header">
<div class="headertitle">
<div class="title">half_float.hpp</div> </div>
</div>
<div class="contents">
<div class="fragment"><pre class="fragment"><a name="l00001"></a>00001
<a name="l00002"></a>00002 <span class="comment">// OpenGL Mathematics Copyright (c) 2005 - 2011 G-Truc Creation (www.g-truc.net)</span>
<a name="l00004"></a>00004 <span class="comment"></span><span class="comment">// Created : 2009-04-29</span>
<a name="l00005"></a>00005 <span class="comment">// Updated : 2010-02-07</span>
<a name="l00006"></a>00006 <span class="comment">// Licence : This source is under MIT License</span>
<a name="l00007"></a>00007 <span class="comment">// File : glm/gtc/half_float.hpp</span>
<a name="l00009"></a>00009 <span class="comment"></span>
<a name="l00010"></a>00010 <span class="preprocessor">#ifndef glm_gtc_half_float</span>
<a name="l00011"></a>00011 <span class="preprocessor"></span><span class="preprocessor">#define glm_gtc_half_float</span>
<a name="l00012"></a>00012 <span class="preprocessor"></span>
<a name="l00013"></a>00013 <span class="comment">// Dependency:</span>
<a name="l00014"></a>00014 <span class="preprocessor">#include "../glm.hpp"</span>
<a name="l00015"></a>00015
<a name="l00016"></a>00016 <span class="preprocessor">#if(defined(GLM_MESSAGES) && !defined(glm_ext))</span>
<a name="l00017"></a>00017 <span class="preprocessor"></span><span class="preprocessor"># pragma message("GLM: GLM_GTC_half_float extension included")</span>
<a name="l00018"></a>00018 <span class="preprocessor"></span><span class="preprocessor">#endif</span>
<a name="l00019"></a>00019 <span class="preprocessor"></span>
<a name="l00020"></a>00020 <span class="keyword">namespace </span>glm{
<a name="l00021"></a>00021 <span class="keyword">namespace </span>detail
<a name="l00022"></a>00022 {
<a name="l00023"></a>00023 <span class="preprocessor">#ifndef _MSC_EXTENSIONS</span>
<a name="l00024"></a>00024 <span class="preprocessor"></span> <span class="keyword">template</span> <>
<a name="l00025"></a>00025 <span class="keyword">struct </span>tvec2<thalf>
<a name="l00026"></a>00026 {
<a name="l00027"></a>00027 <span class="keyword">enum</span> ctor{null};
<a name="l00028"></a>00028 <span class="keyword">typedef</span> thalf value_type;
<a name="l00029"></a>00029 <span class="keyword">typedef</span> std::size_t size_type;
<a name="l00030"></a>00030 <span class="keyword">static</span> size_type value_size();
<a name="l00031"></a>00031 GLM_FUNC_DECL size_type length() <span class="keyword">const</span>;
<a name="l00032"></a>00032
<a name="l00033"></a>00033 <span class="keyword">typedef</span> tvec2<thalf> type;
<a name="l00034"></a>00034 <span class="keyword">typedef</span> tvec2<bool> bool_type;
<a name="l00035"></a>00035
<a name="l00037"></a>00037 <span class="comment">// Data</span>
<a name="l00038"></a>00038
<a name="l00039"></a>00039 thalf x, y;
<a name="l00040"></a>00040
<a name="l00042"></a>00042 <span class="comment">// Accesses</span>
<a name="l00043"></a>00043
<a name="l00044"></a>00044 thalf & operator[](size_type i);
<a name="l00045"></a>00045 thalf <span class="keyword">const</span> & operator[](size_type i) <span class="keyword">const</span>;
<a name="l00046"></a>00046
<a name="l00048"></a>00048 <span class="comment">// Implicit basic constructors</span>
<a name="l00049"></a>00049
<a name="l00050"></a>00050 tvec2();
<a name="l00051"></a>00051 tvec2(tvec2<thalf> <span class="keyword">const</span> & v);
<a name="l00052"></a>00052
<a name="l00054"></a>00054 <span class="comment">// Explicit basic constructors</span>
<a name="l00055"></a>00055
<a name="l00056"></a>00056 <span class="keyword">explicit</span> tvec2(ctor);
<a name="l00057"></a>00057 <span class="keyword">explicit</span> tvec2(
<a name="l00058"></a>00058 thalf <span class="keyword">const</span> & s);
<a name="l00059"></a>00059 <span class="keyword">explicit</span> tvec2(
<a name="l00060"></a>00060 thalf <span class="keyword">const</span> & s1,
<a name="l00061"></a>00061 thalf <span class="keyword">const</span> & s2);
<a name="l00062"></a>00062
<a name="l00064"></a>00064 <span class="comment">// Swizzle constructors</span>
<a name="l00065"></a>00065
<a name="l00066"></a>00066 tvec2(tref2<thalf> <span class="keyword">const</span> & r);
<a name="l00067"></a>00067
<a name="l00069"></a>00069 <span class="comment">// Convertion scalar constructors</span>
<a name="l00070"></a>00070
<a name="l00072"></a>00072 <span class="keyword">template</span> <<span class="keyword">typename</span> U>
<a name="l00073"></a>00073 <span class="keyword">explicit</span> tvec2(U <span class="keyword">const</span> & x);
<a name="l00075"></a>00075 <span class="keyword">template</span> <<span class="keyword">typename</span> U, <span class="keyword">typename</span> V>
<a name="l00076"></a>00076 <span class="keyword">explicit</span> tvec2(U <span class="keyword">const</span> & x, V <span class="keyword">const</span> & y);
<a name="l00077"></a>00077
<a name="l00079"></a>00079 <span class="comment">// Convertion vector constructors</span>
<a name="l00080"></a>00080
<a name="l00082"></a>00082 <span class="keyword">template</span> <<span class="keyword">typename</span> U>
<a name="l00083"></a>00083 <span class="keyword">explicit</span> tvec2(tvec2<U> <span class="keyword">const</span> & v);
<a name="l00085"></a>00085 <span class="keyword">template</span> <<span class="keyword">typename</span> U>
<a name="l00086"></a>00086 <span class="keyword">explicit</span> tvec2(tvec3<U> <span class="keyword">const</span> & v);
<a name="l00088"></a>00088 <span class="keyword">template</span> <<span class="keyword">typename</span> U>
<a name="l00089"></a>00089 <span class="keyword">explicit</span> tvec2(tvec4<U> <span class="keyword">const</span> & v);
<a name="l00090"></a>00090
<a name="l00092"></a>00092 <span class="comment">// Unary arithmetic operators</span>
<a name="l00093"></a>00093
<a name="l00094"></a>00094 tvec2<thalf>& operator= (tvec2<thalf> <span class="keyword">const</span> & v);
<a name="l00095"></a>00095
<a name="l00096"></a>00096 tvec2<thalf>& operator+=(thalf <span class="keyword">const</span> & s);
<a name="l00097"></a>00097 tvec2<thalf>& operator+=(tvec2<thalf> <span class="keyword">const</span> & v);
<a name="l00098"></a>00098 tvec2<thalf>& operator-=(thalf <span class="keyword">const</span> & s);
<a name="l00099"></a>00099 tvec2<thalf>& operator-=(tvec2<thalf> <span class="keyword">const</span> & v);
<a name="l00100"></a>00100 tvec2<thalf>& operator*=(thalf <span class="keyword">const</span> & s);
<a name="l00101"></a>00101 tvec2<thalf>& operator*=(tvec2<thalf> <span class="keyword">const</span> & v);
<a name="l00102"></a>00102 tvec2<thalf>& operator/=(thalf <span class="keyword">const</span> & s);
<a name="l00103"></a>00103 tvec2<thalf>& operator/=(tvec2<thalf> <span class="keyword">const</span> & v);
<a name="l00104"></a>00104 tvec2<thalf>& operator++();
<a name="l00105"></a>00105 tvec2<thalf>& operator--();
<a name="l00106"></a>00106
<a name="l00108"></a>00108 <span class="comment">// Swizzle operators</span>
<a name="l00109"></a>00109
<a name="l00110"></a>00110 thalf swizzle(comp X) <span class="keyword">const</span>;
<a name="l00111"></a>00111 tvec2<thalf> swizzle(comp X, comp Y) <span class="keyword">const</span>;
<a name="l00112"></a>00112 tvec3<thalf> swizzle(comp X, comp Y, comp Z) <span class="keyword">const</span>;
<a name="l00113"></a>00113 tvec4<thalf> swizzle(comp X, comp Y, comp Z, comp W) <span class="keyword">const</span>;
<a name="l00114"></a>00114 tref2<thalf> swizzle(comp X, comp Y);
<a name="l00115"></a>00115 };
<a name="l00116"></a>00116
<a name="l00117"></a>00117 <span class="keyword">template</span> <>
<a name="l00118"></a>00118 <span class="keyword">struct </span>tvec3<thalf>
<a name="l00119"></a>00119 {
<a name="l00120"></a>00120 <span class="keyword">enum</span> ctor{null};
<a name="l00121"></a>00121 <span class="keyword">typedef</span> thalf value_type;
<a name="l00122"></a>00122 <span class="keyword">typedef</span> std::size_t size_type;
<a name="l00123"></a>00123 <span class="keyword">static</span> size_type value_size();
<a name="l00124"></a>00124 GLM_FUNC_DECL size_type length() <span class="keyword">const</span>;
<a name="l00125"></a>00125
<a name="l00126"></a>00126 <span class="keyword">typedef</span> tvec3<thalf> type;
<a name="l00127"></a>00127 <span class="keyword">typedef</span> tvec3<bool> bool_type;
<a name="l00128"></a>00128
<a name="l00130"></a>00130 <span class="comment">// Data</span>
<a name="l00131"></a>00131
<a name="l00132"></a>00132 thalf x, y, z;
<a name="l00133"></a>00133
<a name="l00135"></a>00135 <span class="comment">// Accesses</span>
<a name="l00136"></a>00136
<a name="l00137"></a>00137 thalf & operator[](size_type i);
<a name="l00138"></a>00138 thalf <span class="keyword">const</span> & operator[](size_type i) <span class="keyword">const</span>;
<a name="l00139"></a>00139
<a name="l00141"></a>00141 <span class="comment">// Implicit basic constructors</span>
<a name="l00142"></a>00142
<a name="l00143"></a>00143 tvec3();
<a name="l00144"></a>00144 tvec3(tvec3<thalf> <span class="keyword">const</span> & v);
<a name="l00145"></a>00145
<a name="l00147"></a>00147 <span class="comment">// Explicit basic constructors</span>
<a name="l00148"></a>00148
<a name="l00149"></a>00149 <span class="keyword">explicit</span> tvec3(ctor);
<a name="l00150"></a>00150 <span class="keyword">explicit</span> tvec3(
<a name="l00151"></a>00151 thalf <span class="keyword">const</span> & s);
<a name="l00152"></a>00152 <span class="keyword">explicit</span> tvec3(
<a name="l00153"></a>00153 thalf <span class="keyword">const</span> & s1,
<a name="l00154"></a>00154 thalf <span class="keyword">const</span> & s2,
<a name="l00155"></a>00155 thalf <span class="keyword">const</span> & s3);
<a name="l00156"></a>00156
<a name="l00158"></a>00158 <span class="comment">// Swizzle constructors</span>
<a name="l00159"></a>00159
<a name="l00160"></a>00160 tvec3(tref3<thalf> <span class="keyword">const</span> & r);
<a name="l00161"></a>00161
<a name="l00163"></a>00163 <span class="comment">// Convertion scalar constructors</span>
<a name="l00164"></a>00164
<a name="l00166"></a>00166 <span class="keyword">template</span> <<span class="keyword">typename</span> U>
<a name="l00167"></a>00167 <span class="keyword">explicit</span> tvec3(U <span class="keyword">const</span> & x);
<a name="l00169"></a>00169 <span class="keyword">template</span> <<span class="keyword">typename</span> U, <span class="keyword">typename</span> V, <span class="keyword">typename</span> W>
<a name="l00170"></a>00170 <span class="keyword">explicit</span> tvec3(U <span class="keyword">const</span> & x, V <span class="keyword">const</span> & y, W <span class="keyword">const</span> & z);
<a name="l00171"></a>00171
<a name="l00173"></a>00173 <span class="comment">// Convertion vector constructors</span>
<a name="l00174"></a>00174
<a name="l00176"></a>00176 <span class="keyword">template</span> <<span class="keyword">typename</span> A, <span class="keyword">typename</span> B>
<a name="l00177"></a>00177 <span class="keyword">explicit</span> tvec3(tvec2<A> <span class="keyword">const</span> & v, B <span class="keyword">const</span> & s);
<a name="l00179"></a>00179 <span class="keyword">template</span> <<span class="keyword">typename</span> A, <span class="keyword">typename</span> B>
<a name="l00180"></a>00180 <span class="keyword">explicit</span> tvec3(A <span class="keyword">const</span> & s, tvec2<B> <span class="keyword">const</span> & v);
<a name="l00182"></a>00182 <span class="keyword">template</span> <<span class="keyword">typename</span> U>
<a name="l00183"></a>00183 <span class="keyword">explicit</span> tvec3(tvec3<U> <span class="keyword">const</span> & v);
<a name="l00185"></a>00185 <span class="keyword">template</span> <<span class="keyword">typename</span> U>
<a name="l00186"></a>00186 <span class="keyword">explicit</span> tvec3(tvec4<U> <span class="keyword">const</span> & v);
<a name="l00187"></a>00187
<a name="l00189"></a>00189 <span class="comment">// Unary arithmetic operators</span>
<a name="l00190"></a>00190
<a name="l00191"></a>00191 tvec3<thalf>& operator= (tvec3<thalf> <span class="keyword">const</span> & v);
<a name="l00192"></a>00192
<a name="l00193"></a>00193 tvec3<thalf>& operator+=(thalf <span class="keyword">const</span> & s);
<a name="l00194"></a>00194 tvec3<thalf>& operator+=(tvec3<thalf> <span class="keyword">const</span> & v);
<a name="l00195"></a>00195 tvec3<thalf>& operator-=(thalf <span class="keyword">const</span> & s);
<a name="l00196"></a>00196 tvec3<thalf>& operator-=(tvec3<thalf> <span class="keyword">const</span> & v);
<a name="l00197"></a>00197 tvec3<thalf>& operator*=(thalf <span class="keyword">const</span> & s);
<a name="l00198"></a>00198 tvec3<thalf>& operator*=(tvec3<thalf> <span class="keyword">const</span> & v);
<a name="l00199"></a>00199 tvec3<thalf>& operator/=(thalf <span class="keyword">const</span> & s);
<a name="l00200"></a>00200 tvec3<thalf>& operator/=(tvec3<thalf> <span class="keyword">const</span> & v);
<a name="l00201"></a>00201 tvec3<thalf>& operator++();
<a name="l00202"></a>00202 tvec3<thalf>& operator--();
<a name="l00203"></a>00203
<a name="l00205"></a>00205 <span class="comment">// Swizzle operators</span>
<a name="l00206"></a>00206
<a name="l00207"></a>00207 thalf swizzle(comp X) <span class="keyword">const</span>;
<a name="l00208"></a>00208 tvec2<thalf> swizzle(comp X, comp Y) <span class="keyword">const</span>;
<a name="l00209"></a>00209 tvec3<thalf> swizzle(comp X, comp Y, comp Z) <span class="keyword">const</span>;
<a name="l00210"></a>00210 tvec4<thalf> swizzle(comp X, comp Y, comp Z, comp W) <span class="keyword">const</span>;
<a name="l00211"></a>00211 tref3<thalf> swizzle(comp X, comp Y, comp Z);
<a name="l00212"></a>00212 };
<a name="l00213"></a>00213
<a name="l00214"></a>00214 <span class="keyword">template</span> <>
<a name="l00215"></a>00215 <span class="keyword">struct </span>tvec4<thalf>
<a name="l00216"></a>00216 {
<a name="l00217"></a>00217 <span class="keyword">enum</span> ctor{null};
<a name="l00218"></a>00218 <span class="keyword">typedef</span> thalf value_type;
<a name="l00219"></a>00219 <span class="keyword">typedef</span> std::size_t size_type;
<a name="l00220"></a>00220 <span class="keyword">static</span> size_type value_size();
<a name="l00221"></a>00221 GLM_FUNC_DECL size_type length() <span class="keyword">const</span>;
<a name="l00222"></a>00222
<a name="l00223"></a>00223 <span class="keyword">typedef</span> tvec4<thalf> type;
<a name="l00224"></a>00224 <span class="keyword">typedef</span> tvec4<bool> bool_type;
<a name="l00225"></a>00225
<a name="l00227"></a>00227 <span class="comment">// Data</span>
<a name="l00228"></a>00228
<a name="l00229"></a>00229 thalf x, y, z, w;
<a name="l00230"></a>00230
<a name="l00232"></a>00232 <span class="comment">// Accesses</span>
<a name="l00233"></a>00233
<a name="l00234"></a>00234 thalf & operator[](size_type i);
<a name="l00235"></a>00235 thalf <span class="keyword">const</span> & operator[](size_type i) <span class="keyword">const</span>;
<a name="l00236"></a>00236
<a name="l00238"></a>00238 <span class="comment">// Implicit basic constructors</span>
<a name="l00239"></a>00239
<a name="l00240"></a>00240 tvec4();
<a name="l00241"></a>00241 tvec4(tvec4<thalf> <span class="keyword">const</span> & v);
<a name="l00242"></a>00242
<a name="l00244"></a>00244 <span class="comment">// Explicit basic constructors</span>
<a name="l00245"></a>00245
<a name="l00246"></a>00246 <span class="keyword">explicit</span> tvec4(ctor);
<a name="l00247"></a>00247 <span class="keyword">explicit</span> tvec4(
<a name="l00248"></a>00248 thalf <span class="keyword">const</span> & s);
<a name="l00249"></a>00249 <span class="keyword">explicit</span> tvec4(
<a name="l00250"></a>00250 thalf <span class="keyword">const</span> & s0,
<a name="l00251"></a>00251 thalf <span class="keyword">const</span> & s1,
<a name="l00252"></a>00252 thalf <span class="keyword">const</span> & s2,
<a name="l00253"></a>00253 thalf <span class="keyword">const</span> & s3);
<a name="l00254"></a>00254
<a name="l00256"></a>00256 <span class="comment">// Swizzle constructors</span>
<a name="l00257"></a>00257
<a name="l00258"></a>00258 tvec4(tref4<thalf> <span class="keyword">const</span> & r);
<a name="l00259"></a>00259
<a name="l00261"></a>00261 <span class="comment">// Convertion scalar constructors</span>
<a name="l00262"></a>00262
<a name="l00264"></a>00264 <span class="keyword">template</span> <<span class="keyword">typename</span> U>
<a name="l00265"></a>00265 <span class="keyword">explicit</span> tvec4(U <span class="keyword">const</span> & x);
<a name="l00267"></a>00267 <span class="keyword">template</span> <<span class="keyword">typename</span> A, <span class="keyword">typename</span> B, <span class="keyword">typename</span> C, <span class="keyword">typename</span> D>
<a name="l00268"></a>00268 <span class="keyword">explicit</span> tvec4(A <span class="keyword">const</span> & x, B <span class="keyword">const</span> & y, C <span class="keyword">const</span> & z, D <span class="keyword">const</span> & w);
<a name="l00269"></a>00269
<a name="l00271"></a>00271 <span class="comment">// Convertion vector constructors</span>
<a name="l00272"></a>00272
<a name="l00274"></a>00274 <span class="keyword">template</span> <<span class="keyword">typename</span> A, <span class="keyword">typename</span> B, <span class="keyword">typename</span> C>
<a name="l00275"></a>00275 <span class="keyword">explicit</span> tvec4(tvec2<A> <span class="keyword">const</span> & v, B <span class="keyword">const</span> & s1, C <span class="keyword">const</span> & s2);
<a name="l00277"></a>00277 <span class="keyword">template</span> <<span class="keyword">typename</span> A, <span class="keyword">typename</span> B, <span class="keyword">typename</span> C>
<a name="l00278"></a>00278 <span class="keyword">explicit</span> tvec4(A <span class="keyword">const</span> & s1, tvec2<B> <span class="keyword">const</span> & v, C <span class="keyword">const</span> & s2);
<a name="l00280"></a>00280 <span class="keyword">template</span> <<span class="keyword">typename</span> A, <span class="keyword">typename</span> B, <span class="keyword">typename</span> C>
<a name="l00281"></a>00281 <span class="keyword">explicit</span> tvec4(A <span class="keyword">const</span> & s1, B <span class="keyword">const</span> & s2, tvec2<C> <span class="keyword">const</span> & v);
<a name="l00283"></a>00283 <span class="keyword">template</span> <<span class="keyword">typename</span> A, <span class="keyword">typename</span> B>
<a name="l00284"></a>00284 <span class="keyword">explicit</span> tvec4(tvec3<A> <span class="keyword">const</span> & v, B <span class="keyword">const</span> & s);
<a name="l00286"></a>00286 <span class="keyword">template</span> <<span class="keyword">typename</span> A, <span class="keyword">typename</span> B>
<a name="l00287"></a>00287 <span class="keyword">explicit</span> tvec4(A <span class="keyword">const</span> & s, tvec3<B> <span class="keyword">const</span> & v);
<a name="l00289"></a>00289 <span class="keyword">template</span> <<span class="keyword">typename</span> A, <span class="keyword">typename</span> B>
<a name="l00290"></a>00290 <span class="keyword">explicit</span> tvec4(tvec2<A> <span class="keyword">const</span> & v1, tvec2<B> <span class="keyword">const</span> & v2);
<a name="l00292"></a>00292 <span class="keyword">template</span> <<span class="keyword">typename</span> U>
<a name="l00293"></a>00293 <span class="keyword">explicit</span> tvec4(tvec4<U> <span class="keyword">const</span> & v);
<a name="l00294"></a>00294
<a name="l00296"></a>00296 <span class="comment">// Unary arithmetic operators</span>
<a name="l00297"></a>00297
<a name="l00298"></a>00298 tvec4<thalf>& operator= (tvec4<thalf> <span class="keyword">const</span> & v);
<a name="l00299"></a>00299
<a name="l00300"></a>00300 tvec4<thalf>& operator+=(thalf <span class="keyword">const</span> & s);
<a name="l00301"></a>00301 tvec4<thalf>& operator+=(tvec4<thalf> <span class="keyword">const</span> & v);
<a name="l00302"></a>00302 tvec4<thalf>& operator-=(thalf <span class="keyword">const</span> & s);
<a name="l00303"></a>00303 tvec4<thalf>& operator-=(tvec4<thalf> <span class="keyword">const</span> & v);
<a name="l00304"></a>00304 tvec4<thalf>& operator*=(thalf <span class="keyword">const</span> & s);
<a name="l00305"></a>00305 tvec4<thalf>& operator*=(tvec4<thalf> <span class="keyword">const</span> & v);
<a name="l00306"></a>00306 tvec4<thalf>& operator/=(thalf <span class="keyword">const</span> & s);
<a name="l00307"></a>00307 tvec4<thalf>& operator/=(tvec4<thalf> <span class="keyword">const</span> & v);
<a name="l00308"></a>00308 tvec4<thalf>& operator++();
<a name="l00309"></a>00309 tvec4<thalf>& operator--();
<a name="l00310"></a>00310
<a name="l00312"></a>00312 <span class="comment">// Swizzle operators</span>
<a name="l00313"></a>00313
<a name="l00314"></a>00314 thalf swizzle(comp X) <span class="keyword">const</span>;
<a name="l00315"></a>00315 tvec2<thalf> swizzle(comp X, comp Y) <span class="keyword">const</span>;
<a name="l00316"></a>00316 tvec3<thalf> swizzle(comp X, comp Y, comp Z) <span class="keyword">const</span>;
<a name="l00317"></a>00317 tvec4<thalf> swizzle(comp X, comp Y, comp Z, comp W) <span class="keyword">const</span>;
<a name="l00318"></a>00318 tref4<thalf> swizzle(comp X, comp Y, comp Z, comp W);
<a name="l00319"></a>00319 };
<a name="l00320"></a>00320 <span class="preprocessor">#endif//_MSC_EXTENSIONS</span>
<a name="l00321"></a>00321 <span class="preprocessor"></span>}
<a name="l00322"></a>00322 <span class="comment">//namespace detail</span>
<a name="l00323"></a>00323
<a name="l00324"></a>00324 <span class="keyword">namespace </span>gtc{
<a name="l00325"></a><a class="code" href="a00159.html">00325</a> <span class="keyword">namespace </span>half_float
<a name="l00326"></a>00326 {
<a name="l00329"></a>00329
<a name="l00332"></a><a class="code" href="a00240.html#ga256188598ace9135605a8ac8fc158654">00332</a> <span class="keyword">typedef</span> <a class="code" href="a00009.html" title="16-bit floating point type.">detail::thalf</a> <a class="code" href="a00240.html#ga256188598ace9135605a8ac8fc158654" title="Type for half-precision floating-point numbers.">half</a>;
<a name="l00333"></a>00333
<a name="l00336"></a><a class="code" href="a00240.html#ga2cd0b3fe113dc1aa2ee750a85f77c50a">00336</a> <span class="keyword">typedef</span> <a class="code" href="a00020.html" title="The basic 2D vector type.">detail::tvec2<detail::thalf></a> <a class="code" href="a00240.html#ga2cd0b3fe113dc1aa2ee750a85f77c50a" title="Vector of 2 half-precision floating-point numbers.">hvec2</a>;
<a name="l00337"></a>00337
<a name="l00340"></a><a class="code" href="a00240.html#gab708ed615526a03ec26e3b614bea2b7b">00340</a> <span class="keyword">typedef</span> <a class="code" href="a00021.html" title="Basic 3D vector type.">detail::tvec3<detail::thalf></a> <a class="code" href="a00240.html#gab708ed615526a03ec26e3b614bea2b7b" title="Vector of 3 half-precision floating-point numbers.">hvec3</a>;
<a name="l00341"></a>00341
<a name="l00344"></a><a class="code" href="a00240.html#ga912913b034fea8952fcfc129a633c667">00344</a> <span class="keyword">typedef</span> <a class="code" href="a00022.html" title="Basic 4D vector type.">detail::tvec4<detail::thalf></a> <a class="code" href="a00240.html#ga912913b034fea8952fcfc129a633c667" title="Vector of 4 half-precision floating-point numbers.">hvec4</a>;
<a name="l00345"></a>00345
<a name="l00348"></a><a class="code" href="a00240.html#ga784f92f5a36fd8e23a69119eb6a80eb8">00348</a> <span class="keyword">typedef</span> <a class="code" href="a00010.html" title="Template for 2 * 2 matrix of floating-point numbers.">detail::tmat2x2<detail::thalf></a> <a class="code" href="a00240.html#ga784f92f5a36fd8e23a69119eb6a80eb8" title="2 * 2 matrix of half-precision floating-point numbers.">hmat2</a>;
<a name="l00349"></a>00349
<a name="l00352"></a><a class="code" href="a00240.html#ga97a57670730ece7f6b904d6dcce5bd7a">00352</a> <span class="keyword">typedef</span> <a class="code" href="a00014.html" title="Template for 3 * 3 matrix of floating-point numbers.">detail::tmat3x3<detail::thalf></a> <a class="code" href="a00240.html#ga97a57670730ece7f6b904d6dcce5bd7a" title="3 * 3 matrix of half-precision floating-point numbers.">hmat3</a>;
<a name="l00353"></a>00353
<a name="l00356"></a><a class="code" href="a00240.html#gaffa8b541819e978ede6129703be94285">00356</a> <span class="keyword">typedef</span> <a class="code" href="a00018.html" title="Template for 4 * 4 matrix of floating-point numbers.">detail::tmat4x4<detail::thalf></a> <a class="code" href="a00240.html#gaffa8b541819e978ede6129703be94285" title="4 * 4 matrix of half-precision floating-point numbers.">hmat4</a>;
<a name="l00357"></a>00357
<a name="l00360"></a><a class="code" href="a00240.html#gaef5a99a975d1df44e43f3662d84d24e2">00360</a> <span class="keyword">typedef</span> <a class="code" href="a00010.html" title="Template for 2 * 2 matrix of floating-point numbers.">detail::tmat2x2<detail::thalf></a> <a class="code" href="a00240.html#gaef5a99a975d1df44e43f3662d84d24e2" title="2 * 2 matrix of half-precision floating-point numbers.">hmat2x2</a>;
<a name="l00361"></a>00361
<a name="l00364"></a><a class="code" href="a00240.html#ga55c96491b1d2508504b7fad8f31fdd47">00364</a> <span class="keyword">typedef</span> <a class="code" href="a00011.html" title="Template for 2 columns and 3 rows matrix of floating-point numbers.">detail::tmat2x3<detail::thalf></a> <a class="code" href="a00240.html#ga55c96491b1d2508504b7fad8f31fdd47" title="2 * 3 matrix of half-precision floating-point numbers.">hmat2x3</a>;
<a name="l00365"></a>00365
<a name="l00368"></a><a class="code" href="a00240.html#ga43a7d1bfd8945398effa19eb66ce304a">00368</a> <span class="keyword">typedef</span> <a class="code" href="a00012.html" title="Template for 2 columns and 4 rows matrix of floating-point numbers.">detail::tmat2x4<detail::thalf></a> <a class="code" href="a00240.html#ga43a7d1bfd8945398effa19eb66ce304a" title="2 * 4 matrix of half-precision floating-point numbers.">hmat2x4</a>;
<a name="l00369"></a>00369
<a name="l00372"></a><a class="code" href="a00240.html#gaf89371358a1d90a224c72795d25a4f3e">00372</a> <span class="keyword">typedef</span> <a class="code" href="a00013.html" title="Template for 3 columns and 2 rows matrix of floating-point numbers.">detail::tmat3x2<detail::thalf></a> <a class="code" href="a00240.html#gaf89371358a1d90a224c72795d25a4f3e" title="3 * 2 matrix of half-precision floating-point numbers.">hmat3x2</a>;
<a name="l00373"></a>00373
<a name="l00376"></a><a class="code" href="a00240.html#ga3b23962a795f1f157242859c1a35dec0">00376</a> <span class="keyword">typedef</span> <a class="code" href="a00014.html" title="Template for 3 * 3 matrix of floating-point numbers.">detail::tmat3x3<detail::thalf></a> <a class="code" href="a00240.html#ga3b23962a795f1f157242859c1a35dec0" title="3 * 3 matrix of half-precision floating-point numbers.">hmat3x3</a>;
<a name="l00377"></a>00377
<a name="l00380"></a><a class="code" href="a00240.html#ga8eeb3d8c00910f5497117d1749b6550f">00380</a> <span class="keyword">typedef</span> <a class="code" href="a00015.html" title="Template for 3 columns and 4 rows matrix of floating-point numbers.">detail::tmat3x4<detail::thalf></a> <a class="code" href="a00240.html#ga8eeb3d8c00910f5497117d1749b6550f" title="3 * 4 matrix of half-precision floating-point numbers.">hmat3x4</a>;
<a name="l00381"></a>00381
<a name="l00384"></a><a class="code" href="a00240.html#ga370098417bb96d7796b11a4611bf67ac">00384</a> <span class="keyword">typedef</span> <a class="code" href="a00016.html" title="Template for 4 columns and 2 rows matrix of floating-point numbers.">detail::tmat4x2<detail::thalf></a> <a class="code" href="a00240.html#ga370098417bb96d7796b11a4611bf67ac" title="4 * 2 matrix of half-precision floating-point numbers.">hmat4x2</a>;
<a name="l00385"></a>00385
<a name="l00388"></a><a class="code" href="a00240.html#ga8248b190b2f9a4ff3f2aadf865f72b84">00388</a> <span class="keyword">typedef</span> <a class="code" href="a00017.html" title="Template for 4 columns and 3 rows matrix of floating-point numbers.">detail::tmat4x3<detail::thalf></a> <a class="code" href="a00240.html#ga8248b190b2f9a4ff3f2aadf865f72b84" title="4 * 3 matrix of half-precision floating-point numbers.">hmat4x3</a>;
<a name="l00389"></a>00389
<a name="l00392"></a><a class="code" href="a00240.html#ga66a4356be6f3c7a1e5cb944657917002">00392</a> <span class="keyword">typedef</span> <a class="code" href="a00018.html" title="Template for 4 * 4 matrix of floating-point numbers.">detail::tmat4x4<detail::thalf></a> <a class="code" href="a00240.html#ga66a4356be6f3c7a1e5cb944657917002" title="4 * 4 matrix of half-precision floating-point numbers.">hmat4x4</a>;
<a name="l00393"></a>00393
<a name="l00395"></a>00395
<a name="l00396"></a>00396 }<span class="comment">// namespace half_float</span>
<a name="l00397"></a>00397 }<span class="comment">// namespace gtc</span>
<a name="l00398"></a>00398 }<span class="comment">// namespace glm</span>
<a name="l00399"></a>00399
<a name="l00400"></a>00400 <span class="preprocessor">#include "half_float.inl"</span>
<a name="l00401"></a>00401
<a name="l00402"></a>00402 <span class="keyword">namespace </span>glm{<span class="keyword">using namespace </span>gtc::half_float;}
<a name="l00403"></a>00403
<a name="l00404"></a>00404 <span class="preprocessor">#endif//glm_gtc_half_float</span>
</pre></div></div>
</div>
<hr class="footer"/><address class="footer"><small>Generated by 
<a href="http://www.doxygen.org/index.html">
<img class="footer" src="doxygen.png" alt="doxygen"/></a> 1.7.4 </small></address>
</body>
</html>
|
libraries_diagram/RGraph/demos/bar12.html | Simon90/Semvis-Air | <!DOCTYPE html >
<html>
<head>
<link rel="stylesheet" href="demos.css" type="text/css" media="screen" />
<script src="../libraries/RGraph.common.core.js" ></script>
<script src="../libraries/RGraph.bar.js" ></script>
<script src="../libraries/RGraph.line.js" ></script>
<!--[if lt IE 9]><script src="../excanvas/excanvas.js"></script><![endif]-->
<title>A combined bar/line chart</title>
</head>
<body>
<h1>A combined bar/line chart</h1>
<p>
</p>
<canvas id="cvs" width="1000" height="350">[No canvas support]</canvas>
<script>
window.onload = function ()
{
/**
* Create the data and colors
*/
var barData = [];
var lineData = [];
var colors = [];
for (var i=0; i<60; ++i) {
if (i < 30) {
barData[i] = RGraph.random(-100, 0);
colors[i] = '#318CBD';
} else {
barData[i] = RGraph.random(0, 100);
colors[i] = '#BD3929';
}
lineData[i] = (((i/60) * 200) - 100) * RGraph.random(0, 10);
}
var bar = new RGraph.Bar('cvs', barData)
bar.Set('hmargin', 1);
bar.Set('colors', colors);
bar.Set('colors.sequential', true);
bar.Set('xaxispos', 'center');
bar.Set('background.grid.autofit.numhlines', 10);
bar.Set('ymax', 100);
bar.Set('gutter.bottom', 50);
bar.Set('labels', ['1997', '1998','1999','2000','2001','2002','2003','2004','2005','2006','2007','2008','2009','2010','2011']);
/**
* Now add the line chart
*/
var line = new RGraph.Line('cvs', lineData);
line.Set('colors', ['#FFD600']);
line.Set('xaxispos', 'center');
line.Set('linewidth', 2);
line.Set('shadow', true);
line.Set('shadow.offsetx', 0);
line.Set('shadow.offsety', 0);
line.Set('shadow.blur', 5);
/**
* Create the combined class
*/
combo = new RGraph.CombinedChart(bar, line);
combo.Draw();
}
</script>
<p>
<a href="./">« Back</a>
</p>
</body>
</html> |
php/5.5/function.fbsql-get-autostart-info.html | rafaelgou/the-phpjs-local-docs-collection | <!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=UTF-8">
<title>Description</title>
</head>
<body><div class="manualnavbar" style="text-align: center;">
<div class="prev" style="text-align: left; float: left;"><a href="function.fbsql-free-result.html">fbsql_free_result</a></div>
<div class="next" style="text-align: right; float: right;"><a href="function.fbsql-hostname.html">fbsql_hostname</a></div>
<div class="up"><a href="ref.fbsql.html">FrontBase Functions</a></div>
<div class="home"><a href="index.html">PHP Manual</a></div>
</div><hr /><div id="function.fbsql-get-autostart-info" class="refentry">
<div class="refnamediv">
<h1 class="refname">fbsql_get_autostart_info</h1>
<p class="verinfo">(PHP 4 >= 4.0.7, PHP 5)</p><p class="refpurpose"><span class="refname">fbsql_get_autostart_info</span> — <span class="dc-title">
</div>
<div class="refsect1 description" id="refsect1-function.fbsql-get-autostart-info-description">
<h3 class="title">Description</h3>
<div class="methodsynopsis dc-description">
<span class="type">array</span> <span class="methodname"><strong>fbsql_get_autostart_info</strong></span>
([ <span class="methodparam"><span class="type">resource</span> <code class="parameter">$link_identifier</code></span>
] )</div>
<div class="warning"><strong class="warning">Warning</strong><p class="simpara">This function is
currently not documented; only its argument list is available.
</p></div>
</div>
<div class="refsect1 parameters" id="refsect1-function.fbsql-get-autostart-info-parameters">
<h3 class="title">Parameters</h3>
<p class="para">
<dl>
<dt>
<code class="parameter">
link_identifier</code></dt>
<dd>
<p class="para">A FrontBase link identifier
returned by <span class="function"><a href="function.fbsql-connect.html" class="function">fbsql_connect()</a></span> or
<span class="function"><a href="function.fbsql-pconnect.html" class="function">fbsql_pconnect()</a></span>.</p><p class="para">If optional and not specified,
the function will try to find an open link to the FrontBase server and if no
such link is found it will try to create one as if
<span class="function"><a href="function.fbsql-connect.html" class="function">fbsql_connect()</a></span> was called with no arguments.</p>
</dd>
</dl>
</p>
</div>
</div><hr /><div class="manualnavbar" style="text-align: center;">
<div class="prev" style="text-align: left; float: left;"><a href="function.fbsql-free-result.html">fbsql_free_result</a></div>
<div class="next" style="text-align: right; float: right;"><a href="function.fbsql-hostname.html">fbsql_hostname</a></div>
<div class="up"><a href="ref.fbsql.html">FrontBase Functions</a></div>
<div class="home"><a href="index.html">PHP Manual</a></div>
</div></body></html>
|
templates/expandableListWithAutocomplete.html | jfly/ccm | <template name="expandableListWithAutocomplete">
<div class="panel panel-default">
<div class="panel-heading">
<h3 class="panel-title text-capitalize">
{{title}}
</h3>
{{> Template.contentBlock}}
</div>
<ul class="list-group">
{{#each matchingDocs}}
<li class="list-group-item">
{{> Template.dynamic template=../settings.pillTemplateName}}
{{#if isDeletable}}
<button type="button" name="buttonRemoveDoc" class="btn btn-default btn-xs pull-right">
<span class="glyphicon glyphicon-remove"></span>
</button>
{{/if}}
</li>
{{else}}
<li class="list-group-item">
No one yet! Add people below.
</li>
{{/each}}
<div class="panel-footer">
<form class="form-horizontal" role="form" name="newDocForm">
<div class="input-group">
{{> inputAutocomplete name="name" settings=autocompleteSettings class="form-control input-xlarge" placeholder="Enter name..."}}
<span class="input-group-btn">
<button type="submit" name="buttonAddDoc" class="btn btn-default" disabled={{not newDocSelected}}>
<span class="glyphicon glyphicon-plus"></span>
</button>
</span>
</div>
</form>
</div>
</ul>
</div>
</template>
|
php/5.5/function.cubrid-set-query-timeout.html | rafaelgou/the-phpjs-local-docs-collection | <!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=UTF-8">
<title>Set the timeout time of query execution</title>
</head>
<body><div class="manualnavbar" style="text-align: center;">
<div class="prev" style="text-align: left; float: left;"><a href="function.cubrid-set-drop.html">cubrid_set_drop</a></div>
<div class="next" style="text-align: right; float: right;"><a href="function.cubrid-version.html">cubrid_version</a></div>
<div class="up"><a href="ref.cubrid.html">CUBRID Functions</a></div>
<div class="home"><a href="index.html">PHP Manual</a></div>
</div><hr /><div id="function.cubrid-set-query-timeout" class="refentry">
<div class="refnamediv">
<h1 class="refname">cubrid_set_query_timeout</h1>
<p class="verinfo">(PECL CUBRID >= 8.4.1)</p><p class="refpurpose"><span class="refname">cubrid_set_query_timeout</span> — <span class="dc-title">Set the timeout time of query execution</span></p>
</div>
<div class="refsect1 description" id="refsect1-function.cubrid-set-query-timeout-description">
<h3 class="title">Description</h3>
<div class="methodsynopsis dc-description">
<span class="type">bool</span> <span class="methodname"><strong>cubrid_set_query_timeout</strong></span>
( <span class="methodparam"><span class="type">resource</span> <code class="parameter">$req_identifier</code></span>
, <span class="methodparam"><span class="type">int</span> <code class="parameter">$timeout</code></span>
)</div>
<p class="para rdfs-comment">
The <span class="function"><strong>cubrid_set_query_timeout()</strong></span> function is used to set
the timeout time of query execution.
</p>
</div>
<div class="refsect1 parameters" id="refsect1-function.cubrid-set-query-timeout-parameters">
<h3 class="title">Parameters</h3>
<p class="para">
<dl>
<dt>
<code class="parameter">req_identifier</code></dt>
<dd>
<p class="para">Request identifier.</p></dd>
<dt>
<code class="parameter">timeout</code></dt>
<dd>
<p class="para">Timeout time, unit of msec.</p>
</dd>
</dl>
</p>
</div>
<div class="refsect1 returnvalues" id="refsect1-function.cubrid-set-query-timeout-returnvalues">
<h3 class="title">Return Values</h3>
<p class="para">
<strong><code>TRUE</code></strong>, when process is successful.
</p>
<p class="para">
<strong><code>FALSE</code></strong>, when process is unsuccessful.
</p>
</div>
<div class="refsect1 seealso" id="refsect1-function.cubrid-set-query-timeout-seealso">
<h3 class="title">See Also</h3>
<p class="para">
<ul class="simplelist">
<li class="member"><span class="function"><a href="function.cubrid-get-query-timeout.html" class="function" rel="rdfs-seeAlso">cubrid_get_query_timeout()</a> - Get the query timeout value of the request</span></li>
</ul>
</p>
</div>
</div><hr /><div class="manualnavbar" style="text-align: center;">
<div class="prev" style="text-align: left; float: left;"><a href="function.cubrid-set-drop.html">cubrid_set_drop</a></div>
<div class="next" style="text-align: right; float: right;"><a href="function.cubrid-version.html">cubrid_version</a></div>
<div class="up"><a href="ref.cubrid.html">CUBRID Functions</a></div>
<div class="home"><a href="index.html">PHP Manual</a></div>
</div></body></html>
|
php/5.5/iconv.resources.html | rafaelgou/the-phpjs-local-docs-collection | <!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=UTF-8">
<title>Resource Types</title>
</head>
<body><div class="manualnavbar" style="text-align: center;">
<div class="prev" style="text-align: left; float: left;"><a href="iconv.configuration.html">Runtime Configuration</a></div>
<div class="next" style="text-align: right; float: right;"><a href="iconv.constants.html">Predefined Constants</a></div>
<div class="up"><a href="iconv.setup.html">Installing/Configuring</a></div>
<div class="home"><a href="index.html">PHP Manual</a></div>
</div><hr /><div id="iconv.resources" class="section">
<h2 class="title">Resource Types</h2>
<p class="para">This extension has no resource types defined.</p>
</div><hr /><div class="manualnavbar" style="text-align: center;">
<div class="prev" style="text-align: left; float: left;"><a href="iconv.configuration.html">Runtime Configuration</a></div>
<div class="next" style="text-align: right; float: right;"><a href="iconv.constants.html">Predefined Constants</a></div>
<div class="up"><a href="iconv.setup.html">Installing/Configuring</a></div>
<div class="home"><a href="index.html">PHP Manual</a></div>
</div></body></html>
|
pelican/tests/output/basic/category/bar.html | getpelican/pelican | <!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="generator" content="Pelican" />
<title>A Pelican Blog - bar</title>
<link rel="stylesheet" href="/theme/css/main.css" />
<link href="/feeds/all.atom.xml" type="application/atom+xml" rel="alternate" title="A Pelican Blog Atom Feed" />
</head>
<body id="index" class="home">
<header id="banner" class="body">
<h1><a href="/">A Pelican Blog</a></h1>
<nav><ul>
<li><a href="/tag/oh.html">Oh Oh Oh</a></li>
<li><a href="/override/">Override url/save_as</a></li>
<li><a href="/pages/this-is-a-test-page.html">This is a test page</a></li>
<li class="active"><a href="/category/bar.html">bar</a></li>
<li><a href="/category/cat1.html">cat1</a></li>
<li><a href="/category/misc.html">misc</a></li>
<li><a href="/category/yeah.html">yeah</a></li>
</ul></nav>
</header><!-- /#banner -->
<aside id="featured" class="body">
<article>
<h1 class="entry-title"><a href="/oh-yeah.html">Oh yeah !</a></h1>
<footer class="post-info">
<abbr class="published" title="2010-10-20T10:14:00+00:00">
Published: Wed 20 October 2010
</abbr>
<address class="vcard author">
By <a class="url fn" href="/author/alexis-metaireau.html">Alexis Métaireau</a>
</address>
<p>In <a href="/category/bar.html">bar</a>.</p>
<p>tags: <a href="/tag/oh.html">oh</a> <a href="/tag/bar.html">bar</a> <a href="/tag/yeah.html">yeah</a> </p>Translations:
<a href="/oh-yeah-fr.html" hreflang="fr">fr</a>
</footer><!-- /.post-info --><div class="section" id="why-not">
<h2>Why not ?</h2>
<p>After all, why not ? It's pretty simple to do it, and it will allow me to write my blogposts in rst !
YEAH !</p>
<img alt="alternate text" src="/pictures/Sushi.jpg" style="width: 600px; height: 450px;" />
</div>
</article>
</aside><!-- /#featured -->
<section id="extras" class="body">
<div class="social">
<h2>social</h2>
<ul>
<li><a href="/feeds/all.atom.xml" type="application/atom+xml" rel="alternate">atom feed</a></li>
</ul>
</div><!-- /.social -->
</section><!-- /#extras -->
<footer id="contentinfo" class="body">
<address id="about" class="vcard body">
Proudly powered by <a href="https://getpelican.com/">Pelican</a>, which takes great advantage of <a href="https://www.python.org/">Python</a>.
</address><!-- /#about -->
<p>The theme is by <a href="https://www.smashingmagazine.com/2009/08/designing-a-html-5-layout-from-scratch/">Smashing Magazine</a>, thanks!</p>
</footer><!-- /#contentinfo -->
</body>
</html> |
src/joshua/decoder/package.html | gwenniger/joshua | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<html>
<head></head>
<body bgcolor="white">
<!--
##### THIS IS THE TEMPLATE FOR THE PACKAGE DOC COMMENTS. #####
##### TYPE YOUR PACKAGE COMMENTS HERE. BEGIN WITH A #####
##### ONE-SENTENCE SUMMARY STARTING WITH A VERB LIKE: #####
-->
Provides infrastructure and wrapper code used relevant to
hierarchical phrase-based decoding for statistical machine translation.
<p>
This package does not include an implementation of any actual decoding algorithm.
Rather, such code is in child packages of this package.
<!-- Put @see and @since tags down here. -->
</body>
</html> |
cpp_component/3rdparty/boost/libs/icl/doc/html/header/boost/icl/interval_bounds_hpp.html | qianqians/abelkhan | <html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Header <boost/icl/interval_bounds.hpp></title>
<link rel="stylesheet" href="../../../../../../../doc/src/boostbook.css" type="text/css">
<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="../../../index.html" title="Chapter 1. Boost.Icl">
<link rel="up" href="../../../interval_container_library_reference.html" title="Interval Container Library Reference">
<link rel="prev" href="../../../boost/icl/is_set_icl_interv_idm37162.html" title="Struct template is_set<icl::interval_base_set< SubType, DomainT, Compare, Interval, Alloc >>">
<link rel="next" href="../../../boost/icl/bounded_value.html" title="Class template bounded_value">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../../boost.png"></td>
<td align="center"><a href="../../../../../../../index.html">Home</a></td>
<td align="center"><a href="../../../../../../libraries.htm">Libraries</a></td>
<td align="center"><a href="http://www.boost.org/users/people.html">People</a></td>
<td align="center"><a href="http://www.boost.org/users/faq.html">FAQ</a></td>
<td align="center"><a href="../../../../../../../more/index.htm">More</a></td>
</tr></table>
<hr>
<div class="spirit-nav">
<a accesskey="p" href="../../../boost/icl/is_set_icl_interv_idm37162.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../../../interval_container_library_reference.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="../../../boost/icl/bounded_value.html"><img src="../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="header.boost.icl.interval_bounds_hpp"></a>Header <<a href="../../../../../../../boost/icl/interval_bounds.hpp" target="_top">boost/icl/interval_bounds.hpp</a>></h3></div></div></div>
<pre class="synopsis"><span class="keyword">namespace</span> <span class="identifier">boost</span> <span class="special">{</span>
<span class="keyword">namespace</span> <span class="identifier">icl</span> <span class="special">{</span>
<span class="keyword">template</span><span class="special"><</span><span class="keyword">typename</span> DomainT<span class="special">></span> <span class="keyword">class</span> <a class="link" href="../../../boost/icl/bounded_value.html" title="Class template bounded_value">bounded_value</a><span class="special">;</span>
<span class="keyword">class</span> <a class="link" href="../../../boost/icl/interval_bounds.html" title="Class interval_bounds">interval_bounds</a><span class="special">;</span>
<span class="keyword">typedef</span> <span class="keyword">unsigned</span> <span class="keyword">char</span> <a name="boost.icl.bound_type"></a><span class="identifier">bound_type</span><span class="special">;</span>
<span class="special">}</span>
<span class="special">}</span></pre>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
<td align="right"><div class="copyright-footer">Copyright © 2007-2010 Joachim
Faulhaber<br>Copyright © 1999-2006 Cortex Software
GmbH<p>
Distributed under the Boost Software License, Version 1.0. (See accompanying
file LICENSE_1_0.txt or copy at <a href="http://www.boost.org/LICENSE_1_0.txt" target="_top">http://www.boost.org/LICENSE_1_0.txt</a>)
</p>
</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
<a accesskey="p" href="../../../boost/icl/is_set_icl_interv_idm37162.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../../../interval_container_library_reference.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="../../../boost/icl/bounded_value.html"><img src="../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>
|
cpp_component/3rdparty/boost/libs/beast/doc/html/beast/ref/boost__beast__buffers_prefix_view/buffers_prefix_view.html | qianqians/abelkhan | <html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>buffers_prefix_view::buffers_prefix_view</title>
<link rel="stylesheet" href="../../../../../../../doc/src/boostbook.css" type="text/css">
<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="../../../index.html" title="Chapter 1. Boost.Beast">
<link rel="up" href="../boost__beast__buffers_prefix_view.html" title="buffers_prefix_view">
<link rel="prev" href="const_iterator.html" title="buffers_prefix_view::const_iterator">
<link rel="next" href="buffers_prefix_view/overload1.html" title="buffers_prefix_view::buffers_prefix_view (1 of 3 overloads)">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../../boost.png"></td>
<td align="center"><a href="../../../../../../../index.html">Home</a></td>
<td align="center"><a href="../../../../../../../libs/libraries.htm">Libraries</a></td>
<td align="center"><a href="http://www.boost.org/users/people.html">People</a></td>
<td align="center"><a href="http://www.boost.org/users/faq.html">FAQ</a></td>
<td align="center"><a href="../../../../../../../more/index.htm">More</a></td>
</tr></table>
<hr>
<div class="spirit-nav">
<a accesskey="p" href="const_iterator.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../boost__beast__buffers_prefix_view.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="buffers_prefix_view/overload1.html"><img src="../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="beast.ref.boost__beast__buffers_prefix_view.buffers_prefix_view"></a><a class="link" href="buffers_prefix_view.html" title="buffers_prefix_view::buffers_prefix_view">buffers_prefix_view::buffers_prefix_view</a>
</h5></div></div></div>
<p>
<a class="indexterm" name="idm19620"></a>
</p>
<p>
Copy Constructor.
</p>
<pre class="programlisting"><a class="link" href="buffers_prefix_view/overload1.html" title="buffers_prefix_view::buffers_prefix_view (1 of 3 overloads)">buffers_prefix_view</a><span class="special">(</span>
<span class="identifier">buffers_prefix_view</span> <span class="keyword">const</span><span class="special">&);</span>
<span class="emphasis"><em>» <a class="link" href="buffers_prefix_view/overload1.html" title="buffers_prefix_view::buffers_prefix_view (1 of 3 overloads)"><code class="computeroutput"><span class="identifier">more</span><span class="special">...</span></code></a></em></span>
</pre>
<p>
Construct a buffer sequence prefix.
</p>
<pre class="programlisting"><a class="link" href="buffers_prefix_view/overload2.html" title="buffers_prefix_view::buffers_prefix_view (2 of 3 overloads)">buffers_prefix_view</a><span class="special">(</span>
<span class="identifier">std</span><span class="special">::</span><span class="identifier">size_t</span> <span class="identifier">size</span><span class="special">,</span>
<span class="identifier">BufferSequence</span> <span class="keyword">const</span><span class="special">&</span> <span class="identifier">buffers</span><span class="special">);</span>
<span class="emphasis"><em>» <a class="link" href="buffers_prefix_view/overload2.html" title="buffers_prefix_view::buffers_prefix_view (2 of 3 overloads)"><code class="computeroutput"><span class="identifier">more</span><span class="special">...</span></code></a></em></span>
</pre>
<p>
Construct a buffer sequence prefix in-place.
</p>
<pre class="programlisting"><span class="keyword">template</span><span class="special"><</span>
<span class="keyword">class</span><span class="special">...</span> <span class="identifier">Args</span><span class="special">></span>
<a class="link" href="buffers_prefix_view/overload3.html" title="buffers_prefix_view::buffers_prefix_view (3 of 3 overloads)">buffers_prefix_view</a><span class="special">(</span>
<span class="identifier">std</span><span class="special">::</span><span class="identifier">size_t</span> <span class="identifier">size</span><span class="special">,</span>
<span class="identifier">boost</span><span class="special">::</span><span class="identifier">in_place_init_t</span><span class="special">,</span>
<span class="identifier">Args</span><span class="special">&&...</span> <span class="identifier">args</span><span class="special">);</span>
<span class="emphasis"><em>» <a class="link" href="buffers_prefix_view/overload3.html" title="buffers_prefix_view::buffers_prefix_view (3 of 3 overloads)"><code class="computeroutput"><span class="identifier">more</span><span class="special">...</span></code></a></em></span>
</pre>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
<td align="right"><div class="copyright-footer">Copyright © 2016-2019 Vinnie
Falco<p>
Distributed under the Boost Software License, Version 1.0. (See accompanying
file LICENSE_1_0.txt or copy at <a href="http://www.boost.org/LICENSE_1_0.txt" target="_top">http://www.boost.org/LICENSE_1_0.txt</a>)
</p>
</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
<a accesskey="p" href="const_iterator.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../boost__beast__buffers_prefix_view.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="buffers_prefix_view/overload1.html"><img src="../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>
|
wenliandroid/unpacked/assets/www/chapter265.html | yighu/wenli |
<div>
<h3>第二十八章</h3>
<p>1如尔听从尔上帝耶和华之言、遵行其诫、我今日所谕尔者、则尔上帝耶和华必举尔升高、超乎天下万民、</p>
<p>2如尔听从尔上帝耶和华之言、则此诸福、必临及尔、</p>
<p>3在邑获福、在田获福、</p>
<p>4身之所生、土之所产、畜之所出、牛群之犊、羊群之羔、并皆获福、</p>
<p>5盛粮之筐、搏面之器获福、</p>
<p>6尔出获福、尔入获福、</p>
<p>7敌起攻尔、耶和华必使尔击败之、其攻尔也由一途、其逃尔也由七途、</p>
<p>8耶和华必降福于尔仓、及尔手之所为、锡嘏于尔、在尔上帝耶和华所赐之地、</p>
<p>9如尔守尔上帝耶和华之诫、遵行其道、则耶和华必践其所誓、立尔为己之圣民、</p>
<p>10天下亿兆、将见尔称以耶和华名、惟尔是畏、</p>
<p>11耶和华必使尔昌炽、身之所生、畜之所出、土之所产、俱蒙福祉、于耶和华所誓尔祖赐尔之地、</p>
<p>12耶和华必为尔启其宝藏、使天降时雨于尔土、于尔凡百所为、锡嘏于尔、尔贷金于列邦、而不告贷于彼、</p>
<p>13 14如尔听从尔上帝耶和华之诫命、我今日所谕尔者、谨守遵行、不偏左右、离我今日所谕之言、不从他神、而崇事之、则耶和华必以尔为首、不以尔为尾、使尔居上、不居于下、○</p>
<p>15如尔不听尔上帝耶和华之言、不守其诫命典章、我今日所谕尔者、则此诸诅、必临及尔、</p>
<p>16在邑受诅、在田受诅、</p>
<p>17盛粮之筐、搏面之器受诅、</p>
<p>18身之所生、土之所产、畜之所出、牛群之犊、羊群之羔、并皆受诅、</p>
<p>19尔入受诅、尔出受诅、</p>
<p>20耶和华因尔行恶离弃彼、必于凡尔所为、加尔咒诅、扰乱谴责、以致速亡、</p>
<p>21耶和华必使疫疠附于尔身、以至灭尔于尔入据之地、</p>
<p>22耶和华必以痨疾、热疾、炎疾、疟疾、兵革、枯槁、霉烂击尔、此灾必追袭尔、致尔陨没、</p>
<p>23覆尔之天如铜、载尔之地如铁、</p>
<p>24耶和华必以尘沙为雨、自天降于尔土、俾尔灭亡、</p>
<p>25耶和华必使尔为敌所败、尔攻之也由一途、尔逃之也由七途、抛弃于天下万国之中、</p>
<p>26尔尸必为飞禽走兽所食、无人逐之、</p>
<p>27耶和华必以埃及人所患之痈、痔、疥、癣、不治之症、加乎尔身、</p>
<p>28又必使尔颠狂、目瞽心惊、</p>
<p>29虽在日中、犹如瞽者暗中摸索、所行所为、不获亨通、恒遭暴虐劫夺、无人救援、</p>
<p>30聘妻而人与之寝、筑室而己不得居、植葡萄园而不得食其果、</p>
<p>31尔牛被宰、尔目击之、而不得食、尔驴被夺、尔目击之、而不见返、尔羊付于尔敌、无人救尔、</p>
<p>32子女付于异族、尔将终日瞻望、至于目盲、无力拯之、</p>
<p>33尔之土产、及尔劳而得者、将为尔所未识之民吞噬、尔惟受虐见迫、历久如是、</p>
<p>34尔目所见、必致颠狂、</p>
<p>35耶和华必以恶疮、加于尔膝与股、自踵延及于顶、无术以疗、</p>
<p>36耶和华必以尔及尔所立之王、徙至尔与尔祖素所未识之国、在彼奉事木石之神、</p>
<p>37于耶和华徙尔所至之国、必为人所骇异、作谚语及话柄、</p>
<p>38尔之田亩、播种则多、获实则少、蝗食故也、</p>
<p>39植葡萄园而治之、不收其果、不饮其酒、虫食故也、</p>
<p>40四境有橄榄树、不以其油膏身、果陨故也、</p>
<p>41尔生子女、不为尔有、被虏故也、</p>
<p>42尔囿之树、尔地之产、为蝗所食、</p>
<p>43尔中宾旅、必愈升愈高、尔愈降愈卑、</p>
<p>44彼可贷金于尔、尔不贷金于彼、彼为首、尔为尾、</p>
<p>45凡此诸诅、必追袭尔、临及尔、俾尔灭亡、因尔不听尔上帝耶和华所谕之言、守其诫命典章、</p>
<p>46凡此诸诅、必为异迹奇事于尔、爰及子孙、历世靡暨、</p>
<p>47尔当富有之时、不中心欣喜、奉事尔上帝耶和华、</p>
<p>48尔必饥渴、裸裎、匮乏、服役于敌、耶和华所遣攻尔者、彼以铁轭置于尔颈、迨尔灭亡、</p>
<p>49耶和华必使远民、如鹰之飞、来自地极、以攻击尔、其言尔不之识、</p>
<p>50其容强悍、不顾耆老、不恤幼稚、</p>
<p>51尔畜所生、尔土所产、俱为所食、迨尔灭亡、尔谷与酒及油、牛群之犊、羊群之羔、取之无遗、迨尔灭亡、</p>
<p>52尔上帝耶和华所赐尔之全地、其中诸邑、城垣高固、尔所恃也、敌必困尔于中、迨其倾圮、</p>
<p>53被围之时、受敌窘迫、至食子女之肉、尔上帝耶和华所赐者、</p>
<p>54尔中荏弱娇嫩之人、必怒视其兄弟、及怀中之妻室、遗留之子女、</p>
<p>55甚至彼于敌围尔邑、窘迫之际、食其子女之肉、不肯分给亲属、无所遗余故也、</p>
<p>56 57尔中荏弱娇嫩之妇、因其袅娜、以足践地、犹且不屑、必怒视其怀中之夫、与其子女、暨膝间之婴孩、及凡所生、缘敌围邑窘迫、而无所得、则私食之、</p>
<p>58如尔不守此书所载法律之言、不畏尔上帝耶和华尊荣可畏之名、</p>
<p>59则耶和华必使尔遘奇异之灾、至重至久之殃、艰苦缠绵之病、爰及苗裔、</p>
<p>60加以埃及诸疾、尔所畏者、必附尔身、</p>
<p>61更有诸疾诸灾、律书所未载者、耶和华亦以相加、迨尔灭亡、</p>
<p>62昔尔人数、如天星之多、因不听尔上帝耶和华命、致所遗无几、</p>
<p>63昔耶和华以善待尔、昌炽尔为悦、厥后以毁灭尔、歼殄尔为悦、使尔绝于所入而得之地、</p>
<p>64耶和华必散尔于列邦、自地极至天涯、在彼奉事木石之神、尔与尔祖所未识者、</p>
<p>65在此族中、不获绥安、无有驻足之所、耶和华必使尔心栗目盲、精神衰败、</p>
<p>66尔之生命、悬寄危境、昼夜惊惶、料难保全、</p>
<p>67因心所惧、与目所见、朝必曰愿得及暮、暮必曰愿得及朝、</p>
<p>68往埃及之途、我曾谕尔、不复见之、耶和华必使尔驾舟复返、在彼自鬻于敌、为仆为婢、无人市尔、</p>
</div>
|
external/assimp--3.0.1270-sdk/doc/assimp_html/functions_0x6e.html | mangostaniko/cg15-seganku | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=9"/>
<title>Assimp: Class Members</title>
<link href="tabs.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="jquery.js"></script>
<script type="text/javascript" src="dynsections.js"></script>
<link href="doxygen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="top"><!-- do not remove this div, it is closed by doxygen! -->
<div id="titlearea">
<table cellspacing="0" cellpadding="0">
<tbody>
<tr style="height: 56px;">
<td style="padding-left: 0.5em;">
<div id="projectname">Assimp
 <span id="projectnumber">v3.0 (July 2012)</span>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<!-- end header part -->
<!-- Generated by Doxygen 1.8.1.1 -->
<div id="navrow1" class="tabs">
<ul class="tablist">
<li><a href="index.html"><span>Main Page</span></a></li>
<li><a href="pages.html"><span>Related Pages</span></a></li>
<li><a href="namespaces.html"><span>Namespaces</span></a></li>
<li class="current"><a href="annotated.html"><span>Classes</span></a></li>
<li><a href="files.html"><span>Files</span></a></li>
</ul>
</div>
<div id="navrow2" class="tabs2">
<ul class="tablist">
<li><a href="annotated.html"><span>Class List</span></a></li>
<li><a href="classes.html"><span>Class Index</span></a></li>
<li><a href="hierarchy.html"><span>Class Hierarchy</span></a></li>
<li class="current"><a href="functions.html"><span>Class Members</span></a></li>
</ul>
</div>
<div id="navrow3" class="tabs2">
<ul class="tablist">
<li class="current"><a href="functions.html"><span>All</span></a></li>
<li><a href="functions_func.html"><span>Functions</span></a></li>
<li><a href="functions_vars.html"><span>Variables</span></a></li>
<li><a href="functions_type.html"><span>Typedefs</span></a></li>
<li><a href="functions_enum.html"><span>Enumerations</span></a></li>
<li><a href="functions_eval.html"><span>Enumerator</span></a></li>
<li><a href="functions_rela.html"><span>Related Functions</span></a></li>
</ul>
</div>
<div id="navrow4" class="tabs3">
<ul class="tablist">
<li><a href="functions.html#index_a"><span>a</span></a></li>
<li><a href="functions_0x62.html#index_b"><span>b</span></a></li>
<li><a href="functions_0x63.html#index_c"><span>c</span></a></li>
<li><a href="functions_0x64.html#index_d"><span>d</span></a></li>
<li><a href="functions_0x65.html#index_e"><span>e</span></a></li>
<li><a href="functions_0x66.html#index_f"><span>f</span></a></li>
<li><a href="functions_0x67.html#index_g"><span>g</span></a></li>
<li><a href="functions_0x68.html#index_h"><span>h</span></a></li>
<li><a href="functions_0x69.html#index_i"><span>i</span></a></li>
<li><a href="functions_0x6b.html#index_k"><span>k</span></a></li>
<li><a href="functions_0x6c.html#index_l"><span>l</span></a></li>
<li><a href="functions_0x6d.html#index_m"><span>m</span></a></li>
<li class="current"><a href="functions_0x6e.html#index_n"><span>n</span></a></li>
<li><a href="functions_0x6f.html#index_o"><span>o</span></a></li>
<li><a href="functions_0x70.html#index_p"><span>p</span></a></li>
<li><a href="functions_0x72.html#index_r"><span>r</span></a></li>
<li><a href="functions_0x73.html#index_s"><span>s</span></a></li>
<li><a href="functions_0x74.html#index_t"><span>t</span></a></li>
<li><a href="functions_0x75.html#index_u"><span>u</span></a></li>
<li><a href="functions_0x76.html#index_v"><span>v</span></a></li>
<li><a href="functions_0x77.html#index_w"><span>w</span></a></li>
<li><a href="functions_0x78.html#index_x"><span>x</span></a></li>
<li><a href="functions_0x79.html#index_y"><span>y</span></a></li>
<li><a href="functions_0x7a.html#index_z"><span>z</span></a></li>
<li><a href="functions_0x7e.html#index_0x7e"><span>~</span></a></li>
</ul>
</div>
</div><!-- top -->
<div class="contents">
<div class="textblock">Here is a list of all class members with links to the classes they belong to:</div>
<h3><a class="anchor" id="index_n"></a>- n -</h3><ul>
<li>name
: <a class="el" href="structai_export_data_blob.html#a22fbdb28a7ebc30b4d3c3339be18b5f2">aiExportDataBlob</a>
</li>
<li>next
: <a class="el" href="structai_export_data_blob.html#a73baa3d77f95f360540b0b1922075ba5">aiExportDataBlob</a>
</li>
<li>NORMAL
: <a class="el" href="class_assimp_1_1_logger.html#a8b6248a0fd062431e8572556350d29e6a79d16f85dc21486ee489f300027e8eda">Assimp::Logger</a>
</li>
<li>Normalize()
: <a class="el" href="classai_quaterniont.html#a476e48051aee949deeb44a8fd768b019">aiQuaterniont< TReal ></a>
, <a class="el" href="classai_vector2t.html#a6058fe72ac1fffb4993cd003fb0ad177">aiVector2t< TReal ></a>
, <a class="el" href="classai_vector3t.html#ac1c8d0efc1295bc02f2dd56b8abcb9bb">aiVector3t< TReal ></a>
</li>
</ul>
</div><!-- contents -->
<!-- start footer part -->
<hr class="footer"/><address class="footer"><small>
Generated on Tue Jul 10 2012 17:55:53 for Assimp by  <a href="http://www.doxygen.org/index.html">
<img class="footer" src="doxygen.png" alt="doxygen"/>
</a> 1.8.1.1
</small></address>
</body>
</html>
|
Website/Components/pydoc/Kamaelia.Physics.Behaviours.continuousZero.html | bbc/kamaelia | <html><body>
<h1>Kamaelia.Physics.Behaviours.continuousZero</h1>
<h2>class continuousZero(Axon.Component.component)</h2>
<p>continuousZero() -> new continuousZero component</p>
<p>A component that constantly emits the value 0.</p>
<h4>Inboxes</h4>
<ul><li> control : Secondary inbox often used for signals. The closest analogy is unix signals
<li> inbox : Default inbox for bulk data. Used in a pipeline much like stdin
</ul>
<h4>Outboxes</h4>
<ul><li> outbox : Default data out outbox, used in a pipeline much like stdout
<li> signal : The default signal based outbox - kinda like stderr, but more for sending singal type signals
</ul>
<h2>Methods defined here</h2>
[[boxright][[include][file=Components/MethodNote.html][croptop=1][crop
bottom=1] ] ]
<h3>__init__(self)</h3>
<p>x.__init__(...) initializes x; see x.__class__.__doc__ for signature</p>
<h3>main(self)</h3>
<p>Main loop.</p>
<HR>
<h2> Feedback </h2>
<P>Got a problem with the documentation? Something unclear, could
be clearer? Want to help with improving? Constructive criticism,
preferably in the form of suggested rewording is very welcome.
<P>Please leave the feedback
<a href="http://kamaelia.sourceforge.net/cgi-bin/blog/blog.cgi?rm=addpostcomment&postid=1131454685">
here, in reply to the documentation thread in the Kamaelia blog</a>.
</body></html>
|
v0.5.0/nvidia/submission/code/translation/pytorch/cutlass/docs/structcutlass_1_1platform_1_1aligned__storage.html | mlperf/training_results_v0.5 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=9"/>
<meta name="generator" content="Doxygen 1.8.14"/>
<meta name="viewport" content="width=device-width, initial-scale=1"/>
<title>Cutlass: cutlass::platform::aligned_storage< Len, Align > Struct Template Reference</title>
<link href="tabs.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="jquery.js"></script>
<script type="text/javascript" src="dynsections.js"></script>
<link href="search/search.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="search/searchdata.js"></script>
<script type="text/javascript" src="search/search.js"></script>
<script type="text/x-mathjax-config">
MathJax.Hub.Config({
extensions: ["tex2jax.js"],
jax: ["input/TeX","output/HTML-CSS"],
});
</script><script type="text/javascript" async src="http://cdn.mathjax.org/mathjax/latest/MathJax.js"></script>
<link href="doxygen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="top"><!-- do not remove this div, it is closed by doxygen! -->
<div id="titlearea">
<table cellspacing="0" cellpadding="0">
<tbody>
<tr style="height: 56px;">
<td id="projectalign" style="padding-left: 0.5em;">
<div id="projectname">Cutlass
</div>
<div id="projectbrief">CUDA Templates for Linear Algebra Subroutines and Solvers</div>
</td>
</tr>
</tbody>
</table>
</div>
<!-- end header part -->
<!-- Generated by Doxygen 1.8.14 -->
<script type="text/javascript">
/* @license magnet:?xt=urn:btih:cf05388f2679ee054f2beb29a391d25f4e673ac3&dn=gpl-2.0.txt GPL-v2 */
var searchBox = new SearchBox("searchBox", "search",false,'Search');
/* @license-end */
</script>
<script type="text/javascript" src="menudata.js"></script>
<script type="text/javascript" src="menu.js"></script>
<script type="text/javascript">
/* @license magnet:?xt=urn:btih:cf05388f2679ee054f2beb29a391d25f4e673ac3&dn=gpl-2.0.txt GPL-v2 */
$(function() {
initMenu('',true,false,'search.php','Search');
$(document).ready(function() { init_search(); });
});
/* @license-end */</script>
<div id="main-nav"></div>
<!-- window showing the filter options -->
<div id="MSearchSelectWindow"
onmouseover="return searchBox.OnSearchSelectShow()"
onmouseout="return searchBox.OnSearchSelectHide()"
onkeydown="return searchBox.OnSearchSelectKey(event)">
</div>
<!-- iframe showing the search results (closed by default) -->
<div id="MSearchResultsWindow">
<iframe src="javascript:void(0)" frameborder="0"
name="MSearchResults" id="MSearchResults">
</iframe>
</div>
<div id="nav-path" class="navpath">
<ul>
<li class="navelem"><a class="el" href="namespacecutlass.html">cutlass</a></li><li class="navelem"><a class="el" href="namespacecutlass_1_1platform.html">platform</a></li><li class="navelem"><a class="el" href="structcutlass_1_1platform_1_1aligned__storage.html">aligned_storage</a></li> </ul>
</div>
</div><!-- top -->
<div class="header">
<div class="summary">
<a href="#pub-types">Public Types</a> |
<a href="structcutlass_1_1platform_1_1aligned__storage-members.html">List of all members</a> </div>
<div class="headertitle">
<div class="title">cutlass::platform::aligned_storage< Len, Align > Struct Template Reference</div> </div>
</div><!--header-->
<div class="contents">
<p>std::aligned_storage
</p>
<p><code>#include <<a class="el" href="platform_8h_source.html">platform.h</a>></code></p>
<table class="memberdecls">
<tr class="heading"><td colspan="2"><h2 class="groupheader"><a name="pub-types"></a>
Public Types</h2></td></tr>
<tr class="memitem:a9cf0360f335bcd1e9d9e1b266b6dd6c1"><td class="memItemLeft" align="right" valign="top">typedef <a class="el" href="structcutlass_1_1platform_1_1aligned__chunk.html">aligned_chunk</a>< Align > </td><td class="memItemRight" valign="bottom"><a class="el" href="structcutlass_1_1platform_1_1aligned__storage.html#a9cf0360f335bcd1e9d9e1b266b6dd6c1">type</a>[Len/sizeof(<a class="el" href="structcutlass_1_1platform_1_1aligned__chunk.html">aligned_chunk</a>< Align >)]</td></tr>
<tr class="separator:a9cf0360f335bcd1e9d9e1b266b6dd6c1"><td class="memSeparator" colspan="2"> </td></tr>
</table>
<h2 class="groupheader">Member Typedef Documentation</h2>
<a id="a9cf0360f335bcd1e9d9e1b266b6dd6c1"></a>
<h2 class="memtitle"><span class="permalink"><a href="#a9cf0360f335bcd1e9d9e1b266b6dd6c1">◆ </a></span>type</h2>
<div class="memitem">
<div class="memproto">
<div class="memtemplate">
template<size_t Len, size_t Align> </div>
<table class="memname">
<tr>
<td class="memname">typedef <a class="el" href="structcutlass_1_1platform_1_1aligned__chunk.html">aligned_chunk</a><Align> <a class="el" href="structcutlass_1_1platform_1_1aligned__storage.html">cutlass::platform::aligned_storage</a>< Len, Align >::type[Len/sizeof(<a class="el" href="structcutlass_1_1platform_1_1aligned__chunk.html">aligned_chunk</a>< Align >)]</td>
</tr>
</table>
</div><div class="memdoc">
</div>
</div>
<hr/>The documentation for this struct was generated from the following file:<ul>
<li><a class="el" href="platform_8h_source.html">platform.h</a></li>
</ul>
</div><!-- contents -->
<!-- start footer part -->
<hr class="footer"/><address class="footer"><small>
Generated on Fri Oct 26 2018 14:53:40 for Cutlass by  <a href="http://www.doxygen.org/index.html">
<img class="footer" src="doxygen.png" alt="doxygen"/>
</a> 1.8.14
</small></address>
</body>
</html>
|
yourphp/App/Tpl/Admin/Default/Main_top.html | selecterskyphp/framework | {__NOLAYOUT__}<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset={:C('DEFAULT_CHARSET')}" />
<title>{:L('welcome')}</title>
<link rel='stylesheet' type='text/css' href='./Public/Css/style.css'>
<base target="main" />
</head>
<body id="main_top" onLoad="reload()" >
<div id="header" class="header">
<div class="logo"><a href="#" target="_blank"><img src="./Public/Images/sjzm08.png" width=180></a></div>
<div class="nav f_r"> <a href="{:U('Admin/Main/cache')}">{:L('UPDATE_CACHE')}</a> <!-- <i>|</i> <a href="http://www.yourphp.cn" target="_blank">{:L('org_url')}</a> <i>|</i> <a href="http://www.yourphp.cn/license/" target="_blank">{:L('license')}</a> <i>|</i> <a href="http://bbs.yourphp.cn" target="_blank">{:L('org_bbs')}</a> <i>|</i> <a href="http://www.yourphp.cn/help" target="_blank">{:L('help')}</a> <i>|</i> --> </div>
<div class="nav"> {:L('welcome_user')}{$Think.session.username} <i>|</i> [{$usergroup}] <i>|</i> [<a href="{:U('Login/logout')}" target="_top">{:L('logout')}</a>] <i>|</i> <a href="{$site_url}" target="_blank">{:L('home_index')}</a> </div>
<div class="topmenu">
<ul><?php $n=0;?>
<volist name="menuGroupList" id="tag">
<?php if($n==0) $oneurl = U('Main/menu',array(parentid=> $tag[id]));?>
<li><span><a href="#" onClick="sethighlight({$n}); parent.menu.location='{:U('Main/menu',array(parentid=> $tag[id]))}';parent.main.location='{:U($tag['model'].'/'.$tag['action'],$tag['data'])}';return false;">{$tag.name}</a></span></li>
<?php $n++;?>
</volist>
</ul>
</div>
</div>
<script><?php $n=0;?>
function reload(){
parent.menu.location='{$oneurl}';
}
if(self==top){
window.top.location.href = '{:U("Login/index")}';
}
function sethighlight(n) {
var lis = document.getElementsByTagName('span');
for(var i = 0; i < lis.length; i++) {
lis[i].className = '';
}
lis[n].className = 'current';
}
sethighlight(0);
</script>
</body>
</html>
|
dick-ui/nodejs/app/styles/palette.4.css | dick-the-deployer/dick | /*
* Color Scheme
*
*/
/* Body */
body {
background: #006699;
}
/* Selected text */
::-moz-selection {
background: #006699;
color: #ffffff;
text-shadow: none;
}
::selection {
background: #006699;
color: #ffffff;
text-shadow: none;
}
/*********************/
/* Link hover */
a:active,
a:focus,
a:hover {
color: #129cb7;
}
/*********************/
/* Layout top header */
.app > .header {
background-color: #ffffff;
}
.app > .header .brand {
background-color: #006699;
}
.app > .header .brand a,
.app > .header .brand a:hover {
color: rgba(232, 243, 250, 0.9);
}
.app > .header .navbar-toggle {
color: rgba(232, 243, 250, 0.9);
}
.app > .header .nav > li > a,
.app > .header .bg-none {
color: #444444;
}
.app > .header .form-control:-moz-placeholder {
color: #5e5e5e;
}
.app > .header .form-control::-moz-placeholder {
color: #5e5e5e;
}
.app > .header .form-control:-ms-input-placeholder {
color: #5e5e5e;
}
.app > .header .form-control::-webkit-input-placeholder {
color: #5e5e5e;
}
@media screen and (min-width: 768px) {
.horizontal > .header .brand {
background-color: #ffffff;
}
.horizontal > .header .brand a,
.horizontal > .header .brand a:hover {
color: #444444;
}
.header .nav > li > a:hover,
.header .nav > li > a:focus,
.header .nav .open > a,
.header .nav .open > a:hover,
.header .nav .open > a:focus {
background-color: #f5f5f5;
}
}
/*********************/
/* Layout Sidebar */
.sidebar,
.chat-sidebar {
background-color: #006699;
color: #f7fbfe;
}
.sidebar a,
.chat-sidebar a,
.sidebar .nav-title,
.chat-sidebar .nav-title {
color: #f7fbfe;
}
.main-navigation > ul > li > a {
color: #f7fbfe;
}
.app-navigation > ul > li > a {
color: inherit;
}
.app:not(.small-sidebar) .collapsible .main-navigation > ul > li > ul > li > a {
color: #f7fbfe;
}
.app:not(.small-sidebar) .collapsible .main-navigation > ul > li > ul > li.active {
background: #2489cc;
}
.main-navigation:not(.app-navigation) > ul > li.active,
.main-navigation:not(.app-navigation) > ul > li:hover,
.main-navigation:not(.app-navigation) > ul > li.open {
border-radius: 2px;
background: #1177aa;
}
@media screen and (min-width: 768px) {
.small-menu .main-navigation > ul > li.open {
background-color: #2b94d9;
}
}
/*********************/
/* Skin Gallery style */
.spinner-loader {
background: #17c3e5;
background-color: rgba(23, 195, 229, 0.9);
}
.spinner-loader > div {
background-color: #a0e7f5;
}
.loader {
color: #17c3e5;
}
.gallery .overlay {
background-color: #006699;
background-color: rgba(52, 152, 219, 0.9);
}
/*********************/
/* Skin button style */
.btn-color {
color: #ffffff;
background-color: #006699;
border-color: #006699;
}
.btn-color:hover,
.btn-color:focus,
.btn-color:active,
.btn-color.active,
.open .dropdown-toggle.btn-color {
color: #ffffff;
background-color: #258cd1;
border-color: #258cd1;
}
a.btn-color {
color: #ffffff;
}
.btn-color:active,
.btn-color.active,
.open .dropdown-toggle.btn-color {
background-image: none;
}
.btn-color.disabled,
.btn-color[disabled],
fieldset[disabled] .btn-color,
.btn-color.disabled:hover,
.btn-color[disabled]:hover,
fieldset[disabled] .btn-color:hover,
.btn-color.disabled:focus,
.btn-color[disabled]:focus,
fieldset[disabled] .btn-color:focus,
.btn-color.disabled:active,
.btn-color[disabled]:active,
fieldset[disabled] .btn-color:active,
.btn-color.disabled.active,
.btn-color[disabled].active,
fieldset[disabled] .btn-color.active {
background-color: #006699;
border-color: #006699;
}
/*********************/
/* Skin text color style */
.color {
color: #006699;
}
/*********************/
/* Skin nestable style */
#nestable2 .dd-handle {
color: #c2e0f4;
border: 1px solid #006699;
background-color: #006699;
}
#nestable2 .dd-handle:hover {
background-color: #4aa3df;
}
/*********************/
/* Skin slider style */
.slider-color .slider-selection {
background-color: #006699;
}
.slider-color .slider-handle {
box-shadow: rgba(0, 0, 0, 0.2) 0px 2px 5px, #006699 0px 0px 0px 1px;
}
/*********************/
/* Skin panel style */
.panel-color {
border-color: #006699;
}
.panel-color > .panel-heading {
color: #c2e0f4;
background-color: #006699;
border-color: #006699;
}
.panel-color > .panel-heading + .panel-collapse .panel-body {
border-top-color: #006699;
}
.panel-color > .panel-heading a {
color: #c2e0f4;
}
.panel-color > .panel-footer + .panel-collapse .panel-body {
border-bottom-color: #006699;
}
/*********************/
/* Skin label style */
.label-color {
background-color: #006699;
}
.label-color[href]:hover,
.label-color[href]:focus {
background-color: #217dbb;
}
/*********************/
/* Skin background color */
.bg-color {
background-color: #006699;
color: #97caed;
}
.bg-color > a {
color: #97caed;
}
.bg-color > a:active,
.bg-color > a:focus,
.bg-color > a:hover {
color: #89c3ea;
text-decoration: none;
outline: 0;
}
.bg-color .nav > li:hover > a,
.bg-color .nav > li:focus > a,
.bg-color .nav > li:active > a,
.bg-color .nav > li.active > a,
.bg-color .nav > li > a:hover,
.bg-color .nav > li > a:focus {
background-color: #2791d9;
}
/*********************/
/* Skin pagination style */
.pagination > .active > a,
.pagination > .active > span,
.pagination > .active > a:hover,
.pagination > .active > span:hover,
.pagination > .active > a:focus,
.pagination > .active > span:focus {
border-color: #006699;
background-color: #006699;
color: #ffffff;
}
/*********************/
/* Skin progress bar style */
.progress-bar-color {
background-color: #006699;
}
/*********************/
/* Skin chart elements */
.morris-hover.morris-default-style {
border-color: #006699;
background-color: #006699;
background-color: rgba(52, 152, 219, 0.9);
}
.morris-hover.morris-default-style a {
color: #ffffff;
}
#jqstooltip {
background-color: #006699;
border-color: #006699;
}
#tooltip {
background-color: #006699;
color: #ffffff;
}
#tooltip:before {
border-color: transparent #006699 transparent transparent;
}
/*********************/
.jvectormap-label {
border: solid 1px #006699;
background-color: #006699;
color: white;
}
.jvectormap-zoomin,
.jvectormap-zoomout {
background-color: #006699;
color: white;
}
|
docs/html/dir_409f97388efe006bc3438b95e9edef48.html | DallasMuseumArt/OctoberFriends | <!-- HTML header for doxygen 1.8.8-->
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=9"/>
<meta name="generator" content="Doxygen 1.8.9.1"/>
<title>DMA Friends: components Directory Reference</title>
<!--<link href="tabs.css" rel="stylesheet" type="text/css"/>-->
<!--<script type="text/javascript" src="jquery.js"></script>-->
<script type="text/javascript" src="dynsections.js"></script>
<link href="bootstrap3/css/bootstrap.min.css" rel="stylesheet">
<script src="bootstrap3/js/jquery-2.1.1.min.js"></script>
<script src="bootstrap3/js/bootstrap.min.js"></script>
<script type="text/javascript" src="doxy-boot.js"></script>
<link href="search/search.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="search/searchdata.js"></script>
<script type="text/javascript" src="search/search.js"></script>
<script type="text/javascript">
$(document).ready(function() { init_search(); });
</script>
<link href="doxygen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="top"><!-- do not remove this div, it is closed by doxygen! -->
<div id="titlearea">
<table cellspacing="0" cellpadding="0">
<tbody>
<tr style="height: 56px;">
<td style="padding-left: 0.5em;">
<div id="projectname">DMA Friends
 <span id="projectnumber">2.0</span>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<!-- end header part -->
<!-- Generated by Doxygen 1.8.9.1 -->
<script type="text/javascript">
var searchBox = new SearchBox("searchBox", "search",false,'Search');
</script>
<div id="navrow1" class="tabs">
<ul class="tablist">
<li><a href="index.html"><span>Main Page</span></a></li>
<li><a href="pages.html"><span>Related Pages</span></a></li>
<li><a href="namespaces.html"><span>Namespaces</span></a></li>
<li><a href="annotated.html"><span>Classes</span></a></li>
<li>
<div id="MSearchBox" class="MSearchBoxInactive">
<span class="left">
<img id="MSearchSelect" src="search/mag_sel.png"
onmouseover="return searchBox.OnSearchSelectShow()"
onmouseout="return searchBox.OnSearchSelectHide()"
alt=""/>
<input type="text" id="MSearchField" value="Search" accesskey="S"
onfocus="searchBox.OnSearchFieldFocus(true)"
onblur="searchBox.OnSearchFieldFocus(false)"
onkeyup="searchBox.OnSearchFieldChange(event)"/>
</span><span class="right">
<a id="MSearchClose" href="javascript:searchBox.CloseResultsWindow()"><img id="MSearchCloseImg" border="0" src="search/close.png" alt=""/></a>
</span>
</div>
</li>
</ul>
</div>
<!-- window showing the filter options -->
<div id="MSearchSelectWindow"
onmouseover="return searchBox.OnSearchSelectShow()"
onmouseout="return searchBox.OnSearchSelectHide()"
onkeydown="return searchBox.OnSearchSelectKey(event)">
</div>
<!-- iframe showing the search results (closed by default) -->
<div id="MSearchResultsWindow">
<iframe src="javascript:void(0)" frameborder="0"
name="MSearchResults" id="MSearchResults">
</iframe>
</div>
<div id="nav-path" class="navpath">
<ul>
<li class="navelem"><a class="el" href="dir_409f97388efe006bc3438b95e9edef48.html">components</a></li> </ul>
</div>
</div><!-- top -->
<div class="header">
<div class="headertitle">
<div class="title">components Directory Reference</div> </div>
</div><!--header-->
<div class="contents">
<table class="memberdecls">
<tr class="heading"><td colspan="2"><h2 class="groupheader"><a name="files"></a>
Files</h2></td></tr>
<tr class="memitem:d3/dd0/ActivityCatalog_8php"><td class="memItemLeft" align="right" valign="top">file  </td><td class="memItemRight" valign="bottom"><b>ActivityCatalog.php</b></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:d3/dc5/ActivityCodeForm_8php"><td class="memItemLeft" align="right" valign="top">file  </td><td class="memItemRight" valign="bottom"><b>ActivityCodeForm.php</b></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:da/d55/ActivityFilters_8php"><td class="memItemLeft" align="right" valign="top">file  </td><td class="memItemRight" valign="bottom"><b>ActivityFilters.php</b></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:d0/db5/ActivityStream_8php"><td class="memItemLeft" align="right" valign="top">file  </td><td class="memItemRight" valign="bottom"><b>ActivityStream.php</b></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:d1/dd7/GetRewards_8php"><td class="memItemLeft" align="right" valign="top">file  </td><td class="memItemRight" valign="bottom"><b>GetRewards.php</b></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:d2/d0e/GroupFormCreation_8php"><td class="memItemLeft" align="right" valign="top">file  </td><td class="memItemRight" valign="bottom"><b>GroupFormCreation.php</b></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:d1/dc0/GroupJoinCodeForm_8php"><td class="memItemLeft" align="right" valign="top">file  </td><td class="memItemRight" valign="bottom"><b>GroupJoinCodeForm.php</b></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:d7/d02/GroupManager_8php"><td class="memItemLeft" align="right" valign="top">file  </td><td class="memItemRight" valign="bottom"><b>GroupManager.php</b></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:dd/d3a/GroupRequest_8php"><td class="memItemLeft" align="right" valign="top">file  </td><td class="memItemRight" valign="bottom"><b>GroupRequest.php</b></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:df/dbb/Leaderboard_8php"><td class="memItemLeft" align="right" valign="top">file  </td><td class="memItemRight" valign="bottom"><b>Leaderboard.php</b></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:d3/d5f/Modal_8php"><td class="memItemLeft" align="right" valign="top">file  </td><td class="memItemRight" valign="bottom"><b>Modal.php</b></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:df/db1/NotificationCounter_8php"><td class="memItemLeft" align="right" valign="top">file  </td><td class="memItemRight" valign="bottom"><b>NotificationCounter.php</b></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:d2/d24/NotificationList_8php"><td class="memItemLeft" align="right" valign="top">file  </td><td class="memItemRight" valign="bottom"><b>NotificationList.php</b></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:dd/dc6/UserBadges_8php"><td class="memItemLeft" align="right" valign="top">file  </td><td class="memItemRight" valign="bottom"><b>UserBadges.php</b></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:d1/dc7/UserLogin_8php"><td class="memItemLeft" align="right" valign="top">file  </td><td class="memItemRight" valign="bottom"><b>UserLogin.php</b></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:d1/d36/UserMostRecentBadge_8php"><td class="memItemLeft" align="right" valign="top">file  </td><td class="memItemRight" valign="bottom"><b>UserMostRecentBadge.php</b></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:d1/db3/components_2UserProfile_8php"><td class="memItemLeft" align="right" valign="top">file  </td><td class="memItemRight" valign="bottom"><b>UserProfile.php</b></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
<tr class="memitem:d5/dae/UserTimeout_8php"><td class="memItemLeft" align="right" valign="top">file  </td><td class="memItemRight" valign="bottom"><b>UserTimeout.php</b></td></tr>
<tr class="separator:"><td class="memSeparator" colspan="2"> </td></tr>
</table>
</div><!-- contents -->
<!-- HTML footer for doxygen 1.8.8-->
<!-- start footer part -->
<hr class="footer"/><address class="footer"><small>
Generated on Tue Aug 11 2015 18:30:27 for DMA Friends by  <a href="http://www.doxygen.org/index.html">
<img class="footer" src="doxygen.png" alt="doxygen"/>
</a> 1.8.9.1
</small></address>
</body>
</html>
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.