Author: lou
Date: 2008-01-19 03:47:00 -0800 (Sat, 19 Jan 2008)
New Revision: 7860
Modified:
openlaszlo/trunk/docs/src/developers/browser-integration.dbk
openlaszlo/trunk/docs/src/developers/language-preliminaries.dbk
openlaszlo/trunk/docs/src/developers/media-resources.dbk
openlaszlo/trunk/docs/src/developers/methods-events-attributes.dbk
openlaszlo/trunk/docs/src/developers/performance.dbk
openlaszlo/trunk/docs/src/developers/video.dbk
Log:
Change 20080119-lou-4 by [EMAIL PROTECTED] on 2008-01-19 07:37:40 AST
in /Users/lou/src/svn/openlaszlo/trunk
for http://svn.openlaszlo.org/openlaszlo/trunk
Summary: fix typos in the dguide reported by an alert user
Bugs Fixed: LPP-5369
Technical Reviewer: (pending)
QA Reviewer: (pending)
Doc Reviewer: (pending)
Details:
These typos were reported by a user for revision 4.0.8 on an
OpenLaszlo forum: http://forum.openlaszlo.org//showthread.php?t=11411
Most of these typos have already been fixed in the nightly build.
Verified those typos that had already been fixed and fixed those that
hadn't been.
Tests: visual verify
Modified: openlaszlo/trunk/docs/src/developers/browser-integration.dbk
===================================================================
--- openlaszlo/trunk/docs/src/developers/browser-integration.dbk
2008-01-19 11:45:22 UTC (rev 7859)
+++ openlaszlo/trunk/docs/src/developers/browser-integration.dbk
2008-01-19 11:47:00 UTC (rev 7860)
@@ -252,7 +252,7 @@
<programlisting>
lps/includes/source/embednew.js</programlisting>
<para>The source for
- <literal>embednew.js</literal>isshipped compressed as</para>
+ <literal>embednew.js</literal> is shipped compressed as</para>
<programlisting>
lps/includes/embed-compressed.js.</programlisting>
<para>The comments/API documentation are in the source file and
Modified: openlaszlo/trunk/docs/src/developers/language-preliminaries.dbk
===================================================================
--- openlaszlo/trunk/docs/src/developers/language-preliminaries.dbk
2008-01-19 11:45:22 UTC (rev 7859)
+++ openlaszlo/trunk/docs/src/developers/language-preliminaries.dbk
2008-01-19 11:47:00 UTC (rev 7860)
@@ -582,7 +582,7 @@
<para/></section></section>
<!-- add id tag to section so we can link to here. IORIO 22 oct 2007 -->
<section id="combine-tags-script">
-><title>Combining Tags and Script in LZX Programs</title>
+<title>Combining Tags and Script in LZX Programs</title>
<para>As mentioned earlier, virtually all nontrivial LZX programs contain both
(XML) tags and script. Tags are used declaratively, that is, to define objects
and their attributes. Script is used procedurally, that is, to explicitly
define a series of steps. Although the two kinds of code are liberally
intermixed within LZX — for example, script can appear within tags — each
syntax locally maintains its integrity.</para>
Modified: openlaszlo/trunk/docs/src/developers/media-resources.dbk
===================================================================
--- openlaszlo/trunk/docs/src/developers/media-resources.dbk 2008-01-19
11:45:22 UTC (rev 7859)
+++ openlaszlo/trunk/docs/src/developers/media-resources.dbk 2008-01-19
11:47:00 UTC (rev 7860)
@@ -21,11 +21,9 @@
<indexterm>
<primary>videoview</primary>
</indexterm>
- <sgmltag class="element">videoview</sgmltag>s. Please see
- <xref linkend="video" />for a discussion of streaming
+ <sgmltag class="element">videoview</sgmltag>s. See
+ <xref linkend="video" /> for a discussion of streaming
media.</para>
- <para>For a discussion of streaming media, see
- <xref linkend="video" />.</para>
</section>
<section>
<title>Supported media types</title>
Modified: openlaszlo/trunk/docs/src/developers/methods-events-attributes.dbk
===================================================================
--- openlaszlo/trunk/docs/src/developers/methods-events-attributes.dbk
2008-01-19 11:45:22 UTC (rev 7859)
+++ openlaszlo/trunk/docs/src/developers/methods-events-attributes.dbk
2008-01-19 11:47:00 UTC (rev 7860)
@@ -17,7 +17,7 @@
</para>
<para>
In LZX you use attributes, events, and handlers to describe how your
application responds to user input or other changes.
-In general, and to a first approximation, when an<emphasis
role="em">attribute</emphasis> changes value, it can generate an <emphasis
role="em">event </emphasis>. (See below for an qualification of when setting an
attribute's value does and does not cause and event to be sent.) You can
additionally declare events with an
<indexterm><primary>event</primary></indexterm><sgmltag
class="element"><event></sgmltag><remark role="fixme">[unknown
tag]</remark>
+In general, and to a first approximation, when an <emphasis
role="em">attribute</emphasis> changes value, it can generate an <emphasis
role="em">event </emphasis>. (See below for an qualification of when setting an
attribute's value does and does not cause and event to be sent.) You can
additionally declare events with an
<indexterm><primary>event</primary></indexterm><sgmltag
class="element"><event></sgmltag><remark role="fixme">[unknown
tag]</remark>
<!--unknown tag: event-->
tag.
Your application's response to that event is determined by the
associated<glossterm>event handler</glossterm>, which is
@@ -46,7 +46,7 @@
or <indexterm><primary>view</primary></indexterm><sgmltag
class="element"><view></sgmltag><remark role="fixme">[unknown
tag]</remark>
<!--unknown tag: view-->
(or classes derived from them). When defining a method, you must specify
-a value for the <indexterm><primary>name</primary></indexterm><sgmltag
class="attribute">name</sgmltag>attribute. The value of the
+a value for the <indexterm><primary>name</primary></indexterm><sgmltag
class="attribute">name</sgmltag> attribute. The value of the
<indexterm><primary>name</primary></indexterm><sgmltag
class="attribute">name</sgmltag> attribute represents the name by which you
will call this method in script. When you call the method, you use its name
followed by open and close parentheses -- any arguments to the method would be
placed within the parentheses.
</para>
<para>
@@ -386,11 +386,9 @@
</view>
</programlisting>
-<para>Attributes can be an element of a tag or a property of a JavaScript
- class. Attributes that are properties of t
-
-Attributes are usually declared and set in tags, but they can also
- be set and read in script. However, not <emphasis role="em">all</emphasis>
attributes can be set in script,
+<para>An attribute can be an element of a tag or a property of a JavaScript
+ class. Attributes that are properties of tags are usually declared and set
in those tags, but they can also
+ be set and read in script. However, not <emphasis role="em">all</emphasis>
attributes can be set in script,
similarly not all attributes can be in tags. Attributes are
characterized based on this behavior into five categories, as explained
below.</para>
@@ -422,7 +420,7 @@
The <indexterm><primary>attribute</primary></indexterm><sgmltag
class="element"><attribute></sgmltag> tag is useful for writing classes
as well as for performing complicated
constraints of existing attributes.</para>
-<para>In script, the values of most attributes are can be retrieved using
+<para>In script, the values of most attributes can be retrieved using
dot syntax:</para>
<example role="live-example">
Modified: openlaszlo/trunk/docs/src/developers/performance.dbk
===================================================================
--- openlaszlo/trunk/docs/src/developers/performance.dbk 2008-01-19
11:45:22 UTC (rev 7859)
+++ openlaszlo/trunk/docs/src/developers/performance.dbk 2008-01-19
11:47:00 UTC (rev 7860)
@@ -441,7 +441,7 @@
<para>The compiler directive has two forms. The
<indexterm><primary>class</primary></indexterm><sgmltag
class="attribute">class</sgmltag> attribute is a single class. The
<indexterm><primary>classes</primary></indexterm><sgmltag
class="attribute">classes</sgmltag> attribute is a list of class names, so that
this</para>
<programlisting>
<?lzc class="c1" inline-only="true"?>
-<?lzc class="c1" inline-only="true"?></programlisting>
+<?lzc class="c2" inline-only="true"?></programlisting>
<para>can be abbreviated as this:</para>
<programlisting>
<?lzc classes="c1 c2" inline-only="true"?>
Modified: openlaszlo/trunk/docs/src/developers/video.dbk
===================================================================
--- openlaszlo/trunk/docs/src/developers/video.dbk 2008-01-19 11:45:22 UTC
(rev 7859)
+++ openlaszlo/trunk/docs/src/developers/video.dbk 2008-01-19 11:47:00 UTC
(rev 7860)
@@ -11,10 +11,10 @@
s. For discussion of that topic, see <xref linkend="media-resources"/>. The
video APIs described in this chapter work only in OpenLaszlo applications that
are compiled for the Flash runtime target.
</para>
-<para>OpenLaszlo video APIs give you access to the full functionality of media
players such as the <ulink
url="http://www.adobe.com/products/flashmediaserver/";>Flash Media
Server</ulink> and the <ulink url="http://www.osflash.org/red5";>Red5</ulink>
media player. When you OpenLaszlo program is connected to a media server over a
Real Time Media Protocol connection, you can not only receive and play audio
and video (in mp3 and flv formats), you can also record your own audio and
video locally and send it to the server, where it can be stored or shared in
real time with other client programs.
+<para>OpenLaszlo video APIs give you access to the full functionality of media
players such as the <ulink
url="http://www.adobe.com/products/flashmediaserver/";>Flash Media
Server</ulink> and the <ulink url="http://www.osflash.org/red5";>Red5</ulink>
media player. When your OpenLaszlo program is connected to a media server over
a Real Time Media Protocol connection, you can not only receive and play audio
and video (in mp3 and flv formats), you can also record your own audio and
video locally and send it to the server, where it can be stored or shared in
real time with other client programs.
</para>
<para>
-In contrast to RTMP, files that are streamed over an HTTP connection allow
more limited limited functionality.</para>
+In contrast to RTMP, files that are streamed over an HTTP connection allow
more limited functionality.</para>
<para>This chapter explains the concepts of controlling streaming media over
an HTTP connection and and bi-directional communication with a media server
over an RTMP connection. </para>
_______________________________________________
Laszlo-checkins mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-checkins
