elua/doc/pt/refman.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Strict//EN">
<html><head>
</head>
<h3>The reference manual</h3>
<p>The <b>eLua</b> reference manual presents in details all the modules that can be used from a Lua program running inside <b>eLua</b>. It doesn't cover the
standard Lua libraries, as the <a target="_blank" href="http://www.lua.org/manual/5.1/">Lua reference manual</a> already does a very good job at this. 
Instead, it covers <b>eLua</b>-specific modules (most of which are linked with the <a href="arch_platform.html">platform interface</a>) and some generic
&quot;3rd party&quot; modules that are included in <b>eLua</b> by default. There are two types of modules in <b>eLua</b>, both of which are presented
in this section:
<ul>
  <li><b>generic modules</b>: they are available on all platforms and should behave the same on all platforms.</li>
  <li><b>platform-depedent modules</b>: they can be found only on specific platforms. Using them sacrifices portability, but gives access to platform 
      internals that aren't covered by the generic modules (for example specific hardware features).</b>
</ul></p>
<p>Remember that in order to use a module (generic or not) in <b>eLua</b> you must first include it in your <b>eLua</b> binary image, check 
<a href="building.html#confmodules">here</a> for instructions on how to do this.</p>
<p>
</body></html>
i386 toolchain build tutorial edited to include John Hind fix SConstruct edited just to leave group/files definitions close to the platform/groups. Doc content files mirroed to pt, to ease the portuguese version initial migration 2009-02-21 23:02:39 +00:00			`<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Strict//EN">`
PT_BR content 2009-09-26 17:00:44 +00:00			`<html><head>`
			`</head>`
			`<h3>The reference manual</h3>`
			`<p>The <b>eLua</b> reference manual presents in details all the modules that can be used from a Lua program running inside <b>eLua</b>. It doesn't cover the`
			`standard Lua libraries, as the <a target="_blank" href="http://www.lua.org/manual/5.1/">Lua reference manual</a> already does a very good job at this.`
			`Instead, it covers <b>eLua</b>-specific modules (most of which are linked with the <a href="arch_platform.html">platform interface</a>) and some generic`
			`"3rd party" modules that are included in <b>eLua</b> by default. There are two types of modules in <b>eLua</b>, both of which are presented`
			`in this section:`
			`<ul>`
			`<li><b>generic modules</b>: they are available on all platforms and should behave the same on all platforms.</li>`
			`<li><b>platform-depedent modules</b>: they can be found only on specific platforms. Using them sacrifices portability, but gives access to platform`
			`internals that aren't covered by the generic modules (for example specific hardware features).</b>`
			`</ul></p>`
			`<p>Remember that in order to use a module (generic or not) in <b>eLua</b> you must first include it in your <b>eLua</b> binary image, check`
			`<a href="building.html#confmodules">here</a> for instructions on how to do this.</p>`
			`<p>`
			`</body></html>`