[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnash-commit] gnash ChangeLog NEWS README doc/C/actionscript....
|
From: |
Russ Nelson |
|
Subject: |
[Gnash-commit] gnash ChangeLog NEWS README doc/C/actionscript.... |
|
Date: |
Fri, 16 May 2008 13:23:49 +0000 |
CVSROOT: /sources/gnash
Module name: gnash
Changes by: Russ Nelson <nelsonrn> 08/05/16 13:23:45
Modified files:
. : ChangeLog NEWS README
doc/C : actionscript.xml app_authors.xml
conformance.xml gnashref.xml gnashuser.xml
introduction.xml
doc/C/preformatted: gnash.1.in gnash_ref.info.in
gnash_user.info.in gnashref.html.in
gnashuser.html.in
doc/C/refmanual: documentation_dependencies.xml
feature_configuration.xml
testing_dependencies.xml
doc/C/usermanual: usage.xml
macros : boost.m4 docbook.m4
Log message:
NEWS: add notes about this release, make formatting consistent across
all
the release notes.
README: remove first person, update to 0.8.3
doc/C/actionscript.xml: update version number
doc/C/app_authors.xml: add myself as author
doc/C/conformance.xml: add Implements
doc/C/gnashref.xml: update version number
doc/C/gnashuser.xml: update version number
doc/C/introduction.xml: change the tense
doc/C/preformatted/gnash.1.in: regenerate
doc/C/preformatted/gnash_ref.info.in: regenerate
doc/C/preformatted/gnash_user.info.in: regenerate
doc/C/preformatted/gnashref.html.in: regenerate
doc/C/preformatted/gnashuser.html.in: regenerate
doc/C/refmanual/documentation_dependencies.xml: spelling
doc/C/refmanual/feature_configuration.xml: spelling/grammar and note
that
AGG is the default.
doc/C/refmanual/testing_dependencies.xml: spelling
doc/C/usermanual/usage.xml: spelling and add options for dump-gnash.
macros/docbook.m4: improve FOP and jre location code
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnash/ChangeLog?cvsroot=gnash&r1=1.6623&r2=1.6624
http://cvs.savannah.gnu.org/viewcvs/gnash/NEWS?cvsroot=gnash&r1=1.7&r2=1.8
http://cvs.savannah.gnu.org/viewcvs/gnash/README?cvsroot=gnash&r1=1.32&r2=1.33
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/actionscript.xml?cvsroot=gnash&r1=1.3&r2=1.4
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/app_authors.xml?cvsroot=gnash&r1=1.6&r2=1.7
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/conformance.xml?cvsroot=gnash&r1=1.4&r2=1.5
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/gnashref.xml?cvsroot=gnash&r1=1.3&r2=1.4
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/gnashuser.xml?cvsroot=gnash&r1=1.3&r2=1.4
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/introduction.xml?cvsroot=gnash&r1=1.3&r2=1.4
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/preformatted/gnash.1.in?cvsroot=gnash&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/preformatted/gnash_ref.info.in?cvsroot=gnash&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/preformatted/gnash_user.info.in?cvsroot=gnash&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/preformatted/gnashref.html.in?cvsroot=gnash&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/preformatted/gnashuser.html.in?cvsroot=gnash&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/refmanual/documentation_dependencies.xml?cvsroot=gnash&r1=1.3&r2=1.4
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/refmanual/feature_configuration.xml?cvsroot=gnash&r1=1.3&r2=1.4
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/refmanual/testing_dependencies.xml?cvsroot=gnash&r1=1.4&r2=1.5
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/usermanual/usage.xml?cvsroot=gnash&r1=1.13&r2=1.14
http://cvs.savannah.gnu.org/viewcvs/gnash/macros/boost.m4?cvsroot=gnash&r1=1.82&r2=1.83
http://cvs.savannah.gnu.org/viewcvs/gnash/macros/docbook.m4?cvsroot=gnash&r1=1.30&r2=1.31
Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/gnash/gnash/ChangeLog,v
retrieving revision 1.6623
retrieving revision 1.6624
diff -u -b -r1.6623 -r1.6624
--- ChangeLog 16 May 2008 13:10:33 -0000 1.6623
+++ ChangeLog 16 May 2008 13:23:38 -0000 1.6624
@@ -1,3 +1,26 @@
+2008-05-16 Russ Nelson <address@hidden>
+
+ * NEWS: add notes about this release, make formatting consistent
+ across all the release notes.
+ * README: remove first person, update to 0.8.3
+ * doc/C/actionscript.xml: update version number
+ * doc/C/app_authors.xml: add myself as author
+ * doc/C/conformance.xml: add Implements
+ * doc/C/gnashref.xml: update version number
+ * doc/C/gnashuser.xml: update version number
+ * doc/C/introduction.xml: change the tense
+ * doc/C/preformatted/gnash.1.in: regenerate
+ * doc/C/preformatted/gnash_ref.info.in: regenerate
+ * doc/C/preformatted/gnash_user.info.in: regenerate
+ * doc/C/preformatted/gnashref.html.in: regenerate
+ * doc/C/preformatted/gnashuser.html.in: regenerate
+ * doc/C/refmanual/documentation_dependencies.xml: spelling
+ * doc/C/refmanual/feature_configuration.xml: spelling/grammar and note
+ that AGG is the default.
+ * doc/C/refmanual/testing_dependencies.xml: spelling
+ * doc/C/usermanual/usage.xml: spelling and add options for dump-gnash.
+ * macros/docbook.m4: improve FOP and jre location code
+
2008-05-16 Sandro Santilli <address@hidden>
* libmedia/ffmpeg/sound_handler_sdl.h: add an
Index: NEWS
===================================================================
RCS file: /sources/gnash/gnash/NEWS,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- NEWS 16 May 2008 07:45:25 -0000 1.7
+++ NEWS 16 May 2008 13:23:40 -0000 1.8
@@ -86,6 +86,7 @@
Fourth alpha release of Gnash (0.8.1).
Improvements since 0.8.0 release are:
+<<<<<<< NEWS
* Garbage Collector
* Support for device fonts
* Support for dynamic text fields
@@ -100,12 +101,48 @@
* More robust parser
* Better support for flash player detection
* Fix for 'debugLog' directive in gnashrc
+=======
+ * Garbage Collector
+ * Support for device fonts
+ * Support for dynamic text fields
+ * Better key handling
+ * Support for FFMPEG SVN
+ * Support for on-demand install of needed Gstreamer codec plugins.
+ * Debugger off by default (improves performance and memory use)
+ * AGG renderer by default
+ * Support for KDE/AGG combination
+ * Layout change : we'll now build <gui>-gnash and 'gnash' is a shell
+ script with gui selection capabilities (-G)
+ * More robust parser
+ * Better support for flash player detection
+ * Fix for 'debugLog' directive in gnashrc
+>>>>>>> 1.7
2007-06-01 Rob Savoye <address@hidden>
The third alpha release of Gnash. Improvements since the 0.7.2 release
are:
+<<<<<<< NEWS
+ * Streaming video works with YouTube and Lulu.tv! This has been the
+ focus for the majority of the time since the last release.
+ * Many core improvments in the VM as our understanding of Flash
+ improves. These all improve both the correctness of a movie that is
+ being played, but enables more movies to play that used to not work.
+ * New FLTK2 gui.
+ * Simple Flash debugger added.
+ * Improved Darwin support that can use the system OpenGL.
+ * Flash extensions, direct support for file handling, MySQL access,
+ etc.. through plugins to the Gnash VM. Wrappers for any C/C++ API
+ libraries can be exported into ActionScript, and used as native
+ commands in a Flash movie.
+ * Updated manuals.
+ * Many new testcases! Support for testing with ming, swfmill, amd
+ mtasc compilers.
+ * New drawing API for MovieClips..
+
+2006-09-10 Rob Savoye <address@hidden>
+=======
* Streaming video works with YouTube and Lulu.tv! This has been the
focus for the majority of the time since the last release.
* Many core improvments in the VM as our understanding of Flash
@@ -124,6 +161,7 @@
* New drawing API for MovieClips..
2006-09-10 Rob Savoye <address@hidden>
+>>>>>>> 1.7
The second alpha release of Gnash is coming soon. Improvements since
the 0.7.1 alpha release are:
Index: README
===================================================================
RCS file: /sources/gnash/gnash/README,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -b -r1.32 -r1.33
--- README 16 May 2008 07:45:26 -0000 1.32
+++ README 16 May 2008 13:23:40 -0000 1.33
@@ -37,6 +37,22 @@
methods print a warning when using -v with gnash or gprocessor. Using
gprocessor -v is a quick way to see why a movie isn't playing correctly.
+<<<<<<< README
+Currently implemented ActionScript classes are: Array, Boolean, Button,
+Date, Implements, Key, Math, Mouse, NetConnection, NetStream, Number,
+Object, Sound, Stage, String, XML, XMLNode, XMLSocket.
+
+Partially implemented classes are: MovieClipLoader, LocalConnection,
+MovieClip, TextField, TextFormat, System, Function, LoadVars, Video.
+
+Unimplemented classes are: Accessibility, Error, Microphone,
+Selection, SharedObject, Camera, Color, ContextMenu,
+CustomActions.
+
+Unimplemented Opcodes are: MDLength, MDSubstring, MDChr, Throw, Try.
+
+=======
+>>>>>>> 1.32
Currently streaming video for some video sharing sites like Lulu.tv,
or YouTube.com, does work. Your mileage with other sites may vary, but
work continues on improving Gnash.
Index: doc/C/actionscript.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/actionscript.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- doc/C/actionscript.xml 13 Feb 2008 02:30:07 -0000 1.3
+++ doc/C/actionscript.xml 16 May 2008 13:23:41 -0000 1.4
@@ -3,7 +3,7 @@
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"; [
<!ENTITY legal SYSTEM "legal.xml">
<!ENTITY fdl-app SYSTEM "fdl-appendix.xml">
- <!ENTITY appversion "0.8.2">
+ <!ENTITY appversion "0.8.3">
<!ENTITY manrevision "0.2">
<!ENTITY date "Feb 2008">
<!ENTITY app "<application>Gnash</application>">
@@ -11,7 +11,7 @@
<!ENTITY actionscript "ActionScript">
<!ENTITY fn_call "<emphasis>fn_call</emphasis>">
<!ENTITY gen_asclass "<emphasis>gen-asclass.sh</emphasis>">
- <!ENTITY version "0.8.2">
+ <!ENTITY version "0.8.3">
<!ENTITY main SYSTEM "actionscript/main.xml">
<!ENTITY new_as_class SYSTEM "actionscript/new_as_class.xml">
Index: doc/C/app_authors.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/app_authors.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- doc/C/app_authors.xml 20 Feb 2008 11:20:20 -0000 1.6
+++ doc/C/app_authors.xml 16 May 2008 13:23:41 -0000 1.7
@@ -4,10 +4,10 @@
<para>
&app; is maintained by Rob Savoye. Other active developers
are: Sandro Santilli, Bastiaan Jacques, Udo Giacomozzi, Chad
- Musick, Benjamin Wolsey, and Zou Lunkai. Please send all
- comments and suggestions to <email>address@hidden
- </email>. Past and sometimes current developers are Tomas
- Groth and Markus Gothe.
+ Musick, Benjamin Wolsey, Zou Lunkai, and Russ Nelson. Please
+ send all comments and suggestions to
+ <email>address@hidden</email>. Past and sometimes current
+ developers are Tomas Groth and Markus Gothe.
</para>
<para>
Index: doc/C/conformance.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/conformance.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- doc/C/conformance.xml 5 Mar 2008 21:05:55 -0000 1.4
+++ doc/C/conformance.xml 16 May 2008 13:23:41 -0000 1.5
@@ -4,7 +4,7 @@
<para>
Gnash is a capable of reading up to SWF v9 files and opcodes,
but primarily supports SWF v7, with better SWF v8 and v9
- support under heavy developement. With the 0.8.2 release,
+ support under heavy developement. Since the 0.8.2 release,
Gnash includes initial parser support for SWF v8 and v9.
Not all ActionScript 2 classes are implemented yet, but all of the
most heavily used ones are. Many ActionScript 2 classes are
@@ -48,7 +48,7 @@
<para>
This is a quick list of what is currently implemented in Gnash
- as of March, 2008.
+ as of May, 2008.
<informaltable frame="all">
<?dbhtml table-width="75%" ?>
@@ -259,6 +259,21 @@
<row>
<entry valign="top" align="left">
+ <para><link linkend="askey">Implements</link></para>
+ </entry>
+ <entry valign="top" align="center">
+ <para>
+ swf v6
+ </para>
+ </entry>
+ <entry valign="top" align="center">
+ <para>
+ Fully implemented.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry valign="top" align="left">
<para><link linkend="askey">Key</link></para>
</entry>
<entry valign="top" align="center">
Index: doc/C/gnashref.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/gnashref.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- doc/C/gnashref.xml 2 Mar 2008 16:28:27 -0000 1.3
+++ doc/C/gnashref.xml 16 May 2008 13:23:41 -0000 1.4
@@ -2,7 +2,7 @@
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"; [
- <!ENTITY appversion "0.8.2">
+ <!ENTITY appversion "0.8.3">
<!ENTITY manrevision "0.4.3">
<!ENTITY date "Feb 2008">
<!ENTITY app "<application>Gnash</application>">
Index: doc/C/gnashuser.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/gnashuser.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- doc/C/gnashuser.xml 2 Mar 2008 16:28:27 -0000 1.3
+++ doc/C/gnashuser.xml 16 May 2008 13:23:41 -0000 1.4
@@ -2,7 +2,7 @@
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"; [
- <!ENTITY appversion "0.8.2">
+ <!ENTITY appversion "0.8.3">
<!ENTITY manrevision "0.2">
<!ENTITY date "Feb 2008">
<!ENTITY app "<application>Gnash</application>">
Index: doc/C/introduction.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/introduction.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- doc/C/introduction.xml 5 Mar 2008 21:05:55 -0000 1.3
+++ doc/C/introduction.xml 16 May 2008 13:23:41 -0000 1.4
@@ -47,7 +47,7 @@
<para>
Gnash is capable of reading up to SWF v9 files and opcodes,
but primarily supports SWF v7, with better SWF v8 and v9
- support under heavy development. With the 0.8.2 release,
+ support under heavy development. Since the 0.8.2 release,
Gnash includes initial parser support for SWF v8 and v9.
Not all ActionScript 2 classes are implemented yet, but all of the
most heavily used ones are. Many ActionScript 2 classes are
Index: doc/C/preformatted/gnash.1.in
===================================================================
RCS file: /sources/gnash/gnash/doc/C/preformatted/gnash.1.in,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- doc/C/preformatted/gnash.1.in 2 Mar 2008 16:32:21 -0000 1.1
+++ doc/C/preformatted/gnash.1.in 16 May 2008 13:23:42 -0000 1.2
@@ -1,11 +1,11 @@
-.\" -*- coding: us-ascii -*-
+'\" -*- coding: us-ascii -*-
.if \n(.g .ds T< \\FC
.if \n(.g .ds T> \\F[\n[.fam]]
.de URL
\\$2 \(la\\$1\(ra\\$3
..
.if \n(.g .mso www.tmac
-.TH gnash 1 "13 February 2008"
+.TH gnash 1 "14 May 2008" "" ""
.SH NAME
gnash \- GNU Flash (SWF) Player
.SH Synopsis
@@ -23,7 +23,7 @@
Scale the movie up/down by the specified factor.
.TP
-c
-Produce a core file instead of letting SDL trap it.
+Severe errors produce a core file instead of letting SDL trap them.
.TP
-d num
Number of milliseconds to delay in main loop.
@@ -33,7 +33,8 @@
.TP
-x
The XID of the parent window Gnash should use instead of
-creating a new one.
+creating a new one. This is only used when embedding the player
+into another window.
.TP
-j
Set the width of the window. This is only used when embedding
@@ -56,11 +57,11 @@
Specify the texture LOD bias (float, default is -1).
.TP
-p
-Run full speed (no sleep) and log frame rate.
+Run full speed (without sleeping), and log the frame rate.
.TP
-g
Start Gnash with a Flash debugger console so one can set
-break points or watchpoints.
+breakpoints or watchpoints.
.TP
-w
Write the gnash-dbg.log debug log to disk. By default the
@@ -94,8 +95,8 @@
Set filedescriptor to use for external communications.
.TP
--version
-Print the version number, and the configuration of the
-Gnash player. Please use this info when submitting bug
+Print the version number, and the configuration, of the
+Gnash player. Please provide this information when submitting bug
reports.
.SS KEYS
.TP
@@ -132,4 +133,4 @@
CTRL-B
Toggle background color.
.PP
-Flash is Trademarked by Adobe Corporation.
+Flash is a registered trademark of Adobe Corporation.
Index: doc/C/preformatted/gnash_ref.info.in
===================================================================
RCS file: /sources/gnash/gnash/doc/C/preformatted/gnash_ref.info.in,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- doc/C/preformatted/gnash_ref.info.in 2 Mar 2008 17:54:16 -0000
1.2
+++ doc/C/preformatted/gnash_ref.info.in 16 May 2008 13:23:42 -0000
1.3
@@ -1,7 +1,7 @@
-START-INFO-DIR-ENTRY
-This is gnash_ref.info, produced by makeinfo version 4.11 from gnash_ref.texi.
+This is gnash_ref.info, produced by makeinfo version 4.11 from stdin.
-* Gnash Reference Manual: (gnash_ref). Gnash
+START-INFO-DIR-ENTRY
+* Gnash Reference Manual: (gnash_ref). [MISSING TEXT]
END-INFO-DIR-ENTRY
@@ -28,7 +28,7 @@
Introduction
* Audience::
-* What Is Supported ?::
+* What Is Supported?::
Building from Source
@@ -102,21 +102,21 @@
application or as a plugin for several popular web browsers. It
supports playing media from a disk or streaming over a network
connection. Some popular video sharing sites like YouTube are supported
-from a wide vaariety of devices from embedded ones to modern desktops.
+on a wide variety of devices from embedded ones to modern desktops.
Gnash has a better focus on security, allowing the user tight
control of all network or disk based I/O. Gnash also supports extending
-ActionScript by creating your own. You can write wrappers for any
-development library, and import them into the player much like perl or
-python does.
+ActionScript by creating your own classes. You can write wrappers for
+any development library, and import them into the player much like Perl
+or Python does.
* Menu:
* Audience::
-* What Is Supported ?::
+* What Is Supported?::
-File: gnash_ref.info, Node: Audience, Next: What Is Supported ?, Up:
Introduction
+File: gnash_ref.info, Node: Audience, Next: What Is Supported?, Up:
Introduction
1.1 Audience
============
@@ -127,46 +127,46 @@
manual.
-File: gnash_ref.info, Node: What Is Supported ?, Prev: Audience, Up:
Introduction
+File: gnash_ref.info, Node: What Is Supported?, Prev: Audience, Up:
Introduction
-1.2 What Is Supported ?
-=======================
+1.2 What Is Supported?
+======================
Gnash is known to compile for most any POSIX and ANSI C++ conforming
system if you have all the dependent libraries installed. Systems we
-test on, and which Gnash is know to run on are Ubuntu, Fedora, Debian,
-OpenBSD, NetBSD, FreeBSD, Win32, and Darwin (OSX) primarily.
+test on, and which Gnash is known to run on are Ubuntu, Fedora, Debian,
+Mandriva, OpenBSD, NetBSD, FreeBSD, Win32, and Darwin (OSX) primarily.
Occasionally other platforms are built, primarily by those distribution
maintainers. This includes BeOS, Haiku, Syllable, OS/2, Solaris,
Slackware, and Gentoo.
- Gnash is a capable of reading up to SWF v9 files and opcodes, but
+ Gnash is capable of reading up to SWF v9 files and opcodes, but
primarily supports SWF v7, with better SWF v8 and v9 support under
-heavy developement. With the 0.8.2 release, Gnash includes initial
+heavy development. With the 0.8.2 release, Gnash includes initial
parser support for SWF v8 and v9. Not all ActionScript 2 classes are
implemented yet, but all of the most heavily used ones are. Many
ActionScript 2 classes are partially implemented; there is support for
all of the commonly used methods of each class.
- Gnash has implemented about 80% of ActionScript v. 2.0, and has
-begun implementing ActionScript v. 3.0. Gnash supports the majority of
-Flash opcodes up to SWF version 9, and a wide sampling of ActionScript
-classes for SWF version 8.
+ Gnash has implemented about 80% of ActionScript v2.0, and has begun
+implementing ActionScript v3.0. Gnash supports the majority of Flash
+opcodes up to SWF v9, and a wide sampling of ActionScript classes for
+SWF v8.
- As ActionsScript 3 is a more developed version of ActionScript 2,
+ As ActionScript 3 is a more developed version of ActionScript 2,
many of the same classes work for both. Support has been added to
Gnash's ActionScript library to support the new ActionScript 3 filters,
-which get applied to every class. Implementing ActionScript clases is
+which get applied to every class. Implementing ActionScript classes is
often the easiest way for new Gnash developers to make a contribution
-without a deep internal knpowledge of Gnash.
+without a deep internal knowledge of Gnash.
Gnash has included video support since early 2007, but this is an
-every changing field of reverse engineering. Many of the popular video
-sharing sites use SWF v8 or v9, which Gnash still has imperfect support
-for. This is improving all the time, so often builds from a development
-snapshot will work when using the older release packaged in your
-distribution doesn't. You can find daily snapshots of the latest CVS
-tree at: http://www.gnashdev.org/dev_snapshots
+ever changing field of reverse engineering. Many of the popular video
+sharing sites use SWF v8 or v9, which Gnash supports imperfectly. This
+is improving all the time, so often builds from a development snapshot
+will work when using the older release packaged in your distribution
+doesn't. You can find daily snapshots of the latest CVS tree at:
+http://www.gnashdev.org/dev_snapshots
(http://www.gnashdev.org/dev_snapshots/).
Gnash uses ffmpeg for codecs, so any file supported by Mplayer
@@ -663,7 +663,7 @@
2.4 Testing Dependencies
========================
-Gnash tries to run as many tests as possible, but will simply skip
+Gnash tries to run as many tests as possible, but will silentl skip
tests if the tools to run them are unavailable.
*Testing Dependency Table*
@@ -689,9 +689,9 @@
packages
are
available.
-swfc Optional part of Swfc a Swfc is No No
- swftools swf used in distributiondistribution
- 0.8.1 decompiler.some packages packages
+swfc Optional part of Swfc is Swfc is No No
+ swftools an swf used in distributiondistribution
+ 0.8.1 compiler. some packages packages
testcases. are are
available. available.No
distribution
@@ -793,7 +793,7 @@
used to required
convert if you
DocBook2X wish to
- output product
+ output produce
into GNU GNU info
info pages.
pages.
@@ -1000,19 +1000,20 @@
dir is extracted from kde-config.
`--disable-plugins' Disable build of both kparts and
npapi plugins
-`--enable-renderer=opengl|cairo|agg' Enable support for the a graphics
+`--enable-renderer=opengl|cairo|agg' Enable support for a graphics
backend. Currently only `opengl' and
- `agg' work sufficiently. OpenGL is
- used when you have hardware
- accelerated graphics. AGG i used
- when you do not have hardware
- accelerated graphics. Typically
- most desktop machines have OpenGL
- support, and most embedded systems
- do not. OpenGl is the default when
- building Gnash, although the
- quality of AGG's rendering is
- currently superior to OpenGL.
+ `agg' work sufficiently. Use OpenGL
+ when you have hardware accelerated
+ graphics. Use AGG when you do not
+ have hardware accelerated graphics
+ or when you are building for a wide
+ audience. Typically most desktop
+ machines have OpenGL support, and
+ most embedded systems do not. AGG
+ is the default when building Gnash,
+ although the speed of OpenGL's
+ rendering is currently superior to
+ AGG.
`--enable-sdk-install' Enable installing the libraries and
headers as an SDK.
`--disable-shared' Enable installing the shared
@@ -1591,18 +1592,17 @@
===================
The top level of Gnash has several libraries, _libgnashbase_,
-_libgnashgeo_, _libgnashserver_, _libgnashasobjs_ and
-_libgnashbackend_. There are several utility programs included for
-debug parsing and processing of Flash movie files, and other useful
-utilitis for examining local Shared Objects and sniffingh
-LocalConnections.
+_libgnashserver_, _libgnashmedia_, _libgnashamf_ and _libgnashbackend_.
+There are several utility programs included for debug parsing and
+processing of Flash movie files, and other useful utilities for
+examining local Shared Objects and sniffing LocalConnections.
* Menu:
* The Libraries::
* The Applications::
* The Plugin::
-* The Debug Logging System::
+* The Message Logging System::
File: gnash_ref.info, Node: The Libraries, Next: The Applications, Up: A
Tour of Gnash
@@ -1613,17 +1613,15 @@
* Menu:
* libgnashbase::
-* libgnashgeo::
-* libgnashgui::
* libgnashserver::
-* libgnashasobjs::
+* libgnashmedia::
* libgnashamf::
* libgnashbackend::
* libgnashplugin::
* libklashpart::
-File: gnash_ref.info, Node: libgnashbase, Next: libgnashgeo, Up: The
Libraries
+File: gnash_ref.info, Node: libgnashbase, Next: libgnashserver, Up: The
Libraries
3.1.1.1 libgnashbase
....................
@@ -1636,26 +1634,9 @@
pointers are used.
-File: gnash_ref.info, Node: libgnashgeo, Next: libgnashgui, Prev:
libgnashbase, Up: The Libraries
-
-3.1.1.2 libgnashgeo
-...................
-
-Libgnashgeo contains code for device independent graphics routines.
-
-
-File: gnash_ref.info, Node: libgnashgui, Next: libgnashserver, Prev:
libgnashgeo, Up: The Libraries
-
-3.1.1.3 libgnashgui
-...................
-
-Libgnashgui contains code for a portable GUI class that supports using
-GTK2, a framebuffer, SDL, or KDE, FLTK, or Aqua.
-
-
-File: gnash_ref.info, Node: libgnashserver, Next: libgnashasobjs, Prev:
libgnashgui, Up: The Libraries
+File: gnash_ref.info, Node: libgnashserver, Next: libgnashmedia, Prev:
libgnashbase, Up: The Libraries
-3.1.1.4 libgnashserver
+3.1.1.2 libgnashserver
......................
Libgnashserver is the guts of the interpreter itself. This is where the
@@ -1663,18 +1644,21 @@
support libraries for the parser and the core of the virtual machine.
-File: gnash_ref.info, Node: libgnashasobjs, Next: libgnashamf, Prev:
libgnashserver, Up: The Libraries
+File: gnash_ref.info, Node: libgnashmedia, Next: libgnashamf, Prev:
libgnashserver, Up: The Libraries
-3.1.1.5 libgnashasobjs
-......................
+3.1.1.3 libgnashmedia
+.....................
-Libgnashasobjs contains all the ActionScript classes used by the
-interpreter.
+Libgnashmedia handles Gnash's audio and video capabilities, dealing
+with streamed video and sound as well as decoding embedded media
+frames. Besides the standard Flash formats FLV, MPEG4, Nellymoser,
+ADPCM, MP3 and RAW, Gnash can decode other formats supports by
+gstreamer or ffmpeg, including the free OGG container and free codecs.
-File: gnash_ref.info, Node: libgnashamf, Next: libgnashbackend, Prev:
libgnashasobjs, Up: The Libraries
+File: gnash_ref.info, Node: libgnashamf, Next: libgnashbackend, Prev:
libgnashmedia, Up: The Libraries
-3.1.1.6 libgnashamf
+3.1.1.4 libgnashamf
...................
AMF is the data format used internally by SWF files. This is Gnash's
@@ -1685,7 +1669,7 @@
File: gnash_ref.info, Node: libgnashbackend, Next: libgnashplugin, Prev:
libgnashamf, Up: The Libraries
-3.1.1.7 libgnashbackend
+3.1.1.5 libgnashbackend
.......................
Libgnashbackend is a library containing the rendering code that glues
@@ -1695,7 +1679,7 @@
File: gnash_ref.info, Node: libgnashplugin, Next: libklashpart, Prev:
libgnashbackend, Up: The Libraries
-3.1.1.8 libgnashplugin
+3.1.1.6 libgnashplugin
......................
Libgnashplugin is the Mozilla/Firefox plugin.
@@ -1703,7 +1687,7 @@
File: gnash_ref.info, Node: libklashpart, Prev: libgnashplugin, Up: The
Libraries
-3.1.1.9 libklashpart
+3.1.1.7 libklashpart
....................
Libklashpart is the Konqueror plugin.
@@ -1714,8 +1698,8 @@
3.1.2 The Applications
----------------------
-There are currently a few standalone programs in Gnash, which serve to
-either assist with Gnash development or play flash movies.
+There are currently a few standalone programs in Gnash, which serve
+either to assist with Gnash development or to play flash movies.
* Menu:
@@ -1730,8 +1714,8 @@
3.1.2.1 The Standalone Player
.............................
-This is the standalone OpenGL back-end used to play movies. There are
-several command-line options and keyboard control keys used by Gnash.
+This is the standalone OpenGL backend used to play movies. There are
+several command line options and keyboard control keys used by Gnash.
File: gnash_ref.info, Node: Gprocessor, Next: SOLdumper, Prev: The
Standalone Player, Up: The Applications
@@ -1763,40 +1747,40 @@
_LocalConnection_ shared memory segment.
-File: gnash_ref.info, Node: The Plugin, Next: The Debug Logging System,
Prev: The Applications, Up: A Tour of Gnash
+File: gnash_ref.info, Node: The Plugin, Next: The Message Logging System,
Prev: The Applications, Up: A Tour of Gnash
3.1.3 The Plugin
----------------
The plugin is designed to work within Mozilla or Firefox, although
-there is Konqueror support as well. The plugin uses the Mozilla NSAPI
-plugin API to be cross platform, and is portable, as well as being well
-integrated into Mozilla based browsers.
+there is Konqueror support as well. The plugin uses the Mozilla plugin
+API (NPAPI) to be cross platform, and is portable, as well as being
+well integrated into Mozilla based browsers.
* Menu:
-* Current Status::
+* Current Implementation::
* GUI Support::
* Mozplugger::
* Klash::
-File: gnash_ref.info, Node: Current Status, Next: GUI Support, Up: The
Plugin
+File: gnash_ref.info, Node: Current Implementation, Next: GUI Support, Up:
The Plugin
-3.1.3.1 Current Status
-......................
+3.1.3.1 Current Implementation
+..............................
-As of March 30, 2006, the plugin works! This works in a fashion similar
-to MozPlugger in that the standalone player is used instead of using a
-thread. This gets around the issue of having to maintain a separate
-player to support the plugin. It also gets around the other issues that
-Gnash itself is not thread safe at this time.
+The plugin works in a fashion similar to MozPlugger: the standalone
+player is used instead of using a thread. This gets around the issue of
+having to maintain a separate player to support the plugin. It also
+gets around the other issues that Gnash itself is not thread safe at
+this time.
As of Jan, 2007, streaming video, ala "YouTube" works, along with
other video sharing sites.
-File: gnash_ref.info, Node: GUI Support, Next: Mozplugger, Prev: Current
Status, Up: The Plugin
+File: gnash_ref.info, Node: GUI Support, Next: Mozplugger, Prev: Current
Implementation, Up: The Plugin
3.1.3.2 GUI Support
...................
@@ -1888,143 +1872,143 @@
is nothing else that needs to be done to install Klash.
-File: gnash_ref.info, Node: The Debug Logging System, Prev: The Plugin, Up:
A Tour of Gnash
+File: gnash_ref.info, Node: The Message Logging System, Prev: The Plugin,
Up: A Tour of Gnash
-3.1.4 The Debug Logging System
-------------------------------
+3.1.4 The Message Logging System
+--------------------------------
-Gnash supports a debug logging system which supports both C and C++
-natively. This means you can use both _printf()_ style debug messages
-and C++ _iostreams_ style, where you can print C++ objects directly as
-you would when using _cout_.
-
- In the beginning, Gnash only supported the C API for debug logging,
-so it is the most heavily used in Gnash. This API was used in the
-_log_msg()_ and _log_error()_ functions, and used a callback to set
-them up.
+Gnash's common message logging system uses a _printf()_ style format.
+Despite the C-like appearance, however, Gnash's LogFile class by
+default does not use _printf()_ for formatting the messages at all.
+
+ All logging calls are converted using templated functions to use
+boost::format. This uses a similar syntax to printf(), but
+additionally guarantees type-safety and allows more advanced substition
+using positional identifiers besides the traditional printf() type
+identifiers. The conversion templates mean that the logging API remains
+exactly the same, regardless of which method is used to format the log
+output.
+
+ The templates for conversion are generated using Boost.Preprocessor.
+Currently, they allow for a maximum of 16 arguments (more than enough
+for all current usage), but that can be expanded or reduced by changing
+_#define ARG_NUMBER_ in _libbase/log.h_.
- If a filename is not specified at object construction time, a
+ If a filename is not specified before the log file is needed, a
default name of _gnash-dbg.log_ is used. If Gnash is started from the
command line, the debug log will be created in the current directory.
When executing Gnash from a launcher under _GNOME_ or _KDE_ the debug
file goes in your home directory, since that's considered the current
-directory.
-
- There is common functionality between using the C or C++ API.
-Optional output is based on flags that can be set or unset. Multiple
-levels of verbosity are supported, so you can get more output by
-supplying multiple _-v_ options on the command line. You can also
-disable the creation of the debug log.
-
- Currently the use of the C++ API for logging is discouraged, do to
-performance issues.and the generic log_msg() has been replaced by more
-spcific function calls to allow more control of what gets displayed and
-logged.
+directory. A file name can be specified using either _gnashrc_ or a
+call to the LogFile instance itself.
* Menu:
-* Logging System C API::
-* Logging System C++ API::
+* Logging System API::
+* The LogFile Instance::
-File: gnash_ref.info, Node: Logging System C API, Next: Logging System C++
API, Up: The Debug Logging System
+File: gnash_ref.info, Node: Logging System API, Next: The LogFile Instance,
Up: The Message Logging System
-3.1.4.1 Logging System C API
-............................
+3.1.4.1 Logging System API
+..........................
-These functions are clones of the originals as they were used for
-Gnash. These function the same as always except output can be logged to
-disk now as well. These currently print no timestamp with the output,
-which is the older functionality. As these functions are implemented on
-top of the C++ API now, they can be used without corrupting the output
-buffers.
-
-log_error(const char* fmt, ...)
- Display an error message if verbose output is enabled. By default
- the error messages are always written to the disk file, but
- optionally displayed in the terminal.
+Gnash provides 9 specialized logging calls, each using the
+_printf()_-style call similar to this:
-void log_unimpl
+ log_error(const char* fmt, ...)
+
+The different calls and their purposes are described below. The output
+to stdout and to disk are always identical, although writing the log to
+disk can be separately disabled.
+
+log_error
+ Display an error message if verbose output is enabled. This is
+ always printed at a verbosity level of 1 or more.
+
+log_unimpl
Displays a warning to the user about missing Gnash features. We
expect all calls to this function to disappear over time, as we
- implement those features of Flash.
-
-void log_trace
- Used only for explicit user traces
+ implement those features of Flash. This is always printed at a
+ verbosity level of 1 or more.
-void log_debug
- Logs debug information.
+log_trace
+ Used only for the output of the ActionScript _trace()_ function.
+ This is always printed at a verbosity level of 1 or more.
+
+log_debug
+ Logs debug information. This is printed at a verbosity level of 2
+ or more.
-void log_action
+log_action
Log action execution information. Wrap all calls to this function
(and other related statements) into an IF_VERBOSE_ACTION macro, so
to allow completely removing all the overhead at compile time and
- reduce it at runtime.
+ reduce it at runtime. This is printed at a verbosity level of 1 or
+ more only if action logging is enabled.
-void log_parse
+log_parse
Log SWF parsing Wrap all calls to this function (and other
related statements) into an IF_VERBOSE_PARSE macro, so to allow
completely removing all the overhead at compile time and reduce it
- at runtime.
+ at runtime. This is printed at a verbosity level of 1 or more only
+ if parser logging is enabled.
-void log_security
- Display a message with security related information.
+log_security
+ Display a message with security related information. This is always
+ printed at a verbosity level of 1 or more.
-void log_swferror
+log_swferror
This indicates an error in how the binary SWF file was
constructed, i.e.probably a bug in the tools used to build the SWF
file. Wrap all calls to this function (and other related
statements) into an IF_VERBOSE_MALFORMED_SWF macro, so to allow
completely removing all the overhead at compile time and reduce it
- at runtime.
+ at runtime. This is printed at a verbosity level of 1 or more only
+ if malformed SWF logging is enabled.
-log_warning(const char* fmt, ...)
- Display a warning message if verbose output is enabled. By default
- the error messages are always written to the disk file, but
- optionally displayed in the terminal.
+void log_aserror
+ This indicates an erroneous actionscript request such as an
+ incorrect number of arguments or an invalid argument. Wrap all
+ calls to this function (and other related statements) into an
+ IF_VERBOSE_ASCODING_ERRORS macro, so to allow completely removing
+ all the overhead at compile time and reduce it at runtime. This
+ is printed at a verbosity level of 1 or more only if AS coding
+ error logging is enabled.
-File: gnash_ref.info, Node: Logging System C++ API, Prev: Logging System C
API, Up: The Debug Logging System
+File: gnash_ref.info, Node: The LogFile Instance, Prev: Logging System API,
Up: The Message Logging System
-3.1.4.2 Logging System C++ API
-..............................
-
-This is the new C++ streams based API that can be used to print C++
-objects natively. All output lines are timestamped.
+3.1.4.2 The LogFile Instance
+............................
- There are two macros used for program tracing. these can be used in
-both C or C++ code with one little difference. Since C doesn't have
-destructors, you must call _GNASH_REPORT_RETURN_ at the end of a
-function to display the function returning message.
-
-GNASH_REPORT_FUNCTION;
- When this is included in a C++ method, a message is printed when
- entering and exiting this method by hooking into the constructor
- and destructor. These are always written to the disk file, but
- optionally written to the screen only at the highest levels of
- verbosity.
-
-GNASH_REPORT_RETURN;
- This is used by C functions to print the returning from function
- debug message. For C++, this macro is executed automatically by
- the destructor.
-
- This is the main API for the logging system. By default everything
-is setup to write to the default _gnash-dbg.log_ file whenever a
-verbose option is supplied. Optionally it is possible to open a log
-file with a specified name, allowing multiple output files.
+This is the main API for initializing and manipulating the logging
+output. By default, the log will be written to _gnash-dbg.log_ file
+whenever a verbose option is supplied.
+
+getDefaultInstance()
+ This allows the construction of a LogFile on the first call, so
+ ensuring that it the logfile is always initialised before use. It
+ is the only way to access a LogFile instance. The logfile itself
+ is never opened until it is needed.
+
+setLogFilename(const std::string& filename)
+ Use this to set a different name for the disk-based log file.
+ This setting can be overridden by a directive in gnashrc. If the
+ log file is already open, a call to setLogFilename() will close it;
+ a file with the new name will be opened when it is next needed.
-closeLog(void)
+closeLog()
Close a debug log. The disk file remains.
-removeLog(void)
+removeLog()
Delete the debug log file from disk.
-setVerbosity(void)
+setVerbosity()
Increment the verbosity level.
-setVerbosity(int)
- Set the verbosity level.
+setVerbosity(int level)
+ Set the verbosity level to a specified level.
setStamp(bool flag)
If _flag_ is _true_, then print a timestamp prefixed to every
@@ -2976,16 +2960,16 @@
****************
The Gnash project relies on the community of Gnash users to test the
-player, feedback is critical to any successful project. Not only does
+player. Feedback is critical to any successful project. Not only does
it let us know that people use Gnash, but it helps us understand the
community's needs. Gnash uses a bug tracker on
`http://savannah.gnu.org' to manage these reports.
When filing a report, please follow the guidelines below. The better
your bug report is, the easier it will be for the developers to address
-the issue. Bug reports without enough information will initially be
-asked to provide this information anyway. Adding critical details, like
-the Operating System you are on, it's version, and any relevant error
+the issue. Bug reports without enough information will be asked to
+provide this information anyway. Adding critical details, like the
+Operating System you are on, its version, and any relevant error
messages from Gnash that you get.
* Menu:
@@ -3006,8 +2990,8 @@
infrastructure allows the automated building of binary packages. Often
the version of Gnash as packaged by a GNU/Linux or BSD distribution is
based on the last official release, which could be months out of date.
-It is helpful if this is the case to try a newer packaged build of
-Gnash.
+It helps us, if this is the case, for you to try a newer packaged build
+of Gnash.
You can get a fresh binary package of Gnash, as well as recent
source packages from http://www.getgnash.org/packages
@@ -4089,9 +4073,9 @@
Gnash is maintained by Rob Savoye. Other active developers are: Sandro
Santilli, Bastiaan Jacques, Udo Giacomozzi, Chad Musick, Benjamin
-Wolsey, and Zou Lunkai. Please send all comments and suggestions to
-<address@hidden>. Past and sometimes current developers are Tomas
-Groth and Markus Gothe.
+Wolsey, Zou Lunkai, and Russ Nelson. Please send all comments and
+suggestions to <address@hidden>. Past and sometimes current
+developers are Tomas Groth and Markus Gothe.
Gnash was initially derived from GameSWF. GameSWF is maintained by
Thatcher Ulrich <address@hidden>. The following people contributed to
@@ -4549,144 +4533,142 @@
Tag Table:
Node: Top168
-Node: Introduction1999
-Node: Audience2800
-Node: What Is Supported ?3128
-Node: Building from Source5660
-Node: Overview6040
-Node: Getting The Source7082
-Node: Releases7288
-Node: CVS Access7656
-Node: Code Dependencies8368
-Ref: Code Dependency Table9065
-Node: Testing Dependencies34580
-Ref: Testing Dependency Table34888
-Node: Documentation Dependencies38812
-Ref: Documentation Dependency Table39081
-Node: Configuring Gnash48149
-Node: Features50443
-Ref: Configuration Options - Features51043
-Node: Specifying Custom Paths57373
-Ref: Custom Path Options57843
-Node: Compiling the Code67466
-Node: Creating the Documentation68407
-Node: Running the Tests69753
-Node: Using DejaGnu70207
-Node: Increasing Verbosity70570
-Node: Running Some Tests71106
-Node: Running The Tests Manually71926
-Node: Movie tests72588
-Node: ActionScript Unit Tests72942
-Node: Installation73259
-Node: Libraries74572
-Node: Executables75428
-Node: Documentation76298
-Node: Cross Configuring77053
-Node: Software Internals80133
-Node: A Tour of Gnash80402
-Node: The Libraries80969
-Node: libgnashbase81272
-Node: libgnashgeo81696
-Node: libgnashgui81911
-Node: libgnashserver82180
-Node: libgnashasobjs82551
-Node: libgnashamf82787
-Node: libgnashbackend83210
-Node: libgnashplugin83525
-Node: libklashpart83731
-Node: The Applications83901
-Node: The Standalone Player84268
-Node: Gprocessor84566
-Node: SOLdumper84960
-Node: Dumpshm85227
-Node: The Plugin85446
-Node: Current Status85924
-Node: GUI Support86482
-Node: Mozplugger88163
-Node: Klash90054
-Node: The Debug Logging System90604
-Node: Logging System C API92165
-Node: Logging System C++ API94369
-Node: Sound handling in Gnash96210
-Node: Sound types96953
-Node: Sound parsing97490
-Node: Sound playback98058
-Node: The SDL sound backend98588
-Node: The Gstreamer backend99907
-Node: Future audio backends100923
-Node: Detailed description of the Gstreamer backend101413
-Node: Testing103664
-Node: Testing Tools104135
-Node: Test Cases104967
-Node: Writing ActionScript Tests105546
-Node: Writing Ming-based self-contained SWF tests108049
-Node: Using Ming-based test generators facilities109206
-Node: Writing self-contained SWF tests with other compilers111566
-Node: Writing Test Runners114691
-Node: Using the generic test runner for self-contained SWF tests116440
-Node: Writing Movie testers118530
-Node: Adding New ActionScript Class120270
-Node: Prototype121450
-Node: Declaration122867
-Node: Instantiation123132
-Node: Methods123759
-Node: Accessing Arguments124150
-Node: Returning a Value to ActionScript124546
-Node: Additional fn_call Members124925
-Node: Dynamic Properties125779
-Node: The as_value Object Type127284
-Node: Data Types127722
-Node: Determining the Type128043
-Node: Fetching the Value128575
-Node: Setting the Value and Type129065
-Node: Further Reading129659
-Node: Object ActionScript Class130074
-Node: The Methods of the Class130414
-Node: The Properties of the Object Class130753
-Node: Object Class Conformance131068
-Node: Reporting Bugs132607
-Node: Get a Fresh Binary Package133600
-Node: Determine if the bug was previously reported134378
-Node: Review the bug writing guidelines135196
-Node: Filing a bug report136247
-Node: Gnash Extensions136530
-Node: Creating A New Extension138800
-Node: Crafting an Extension140218
-Node: Debugging An Extension144522
-Node: Included Extensions146214
-Node: Gtk Extension146658
-Node: File I/O Extension147645
-Node: MySQL Extension148831
-Node: RTMP Protocol149682
-Node: AMF Format159478
-Node: Mozilla/Firefox NPAPI Plugin160454
-Node: Plugin C API161472
-Node: Plugin C++ API163331
-Node: OpenGL and Threads166595
-Node: Plugin Event Handling167923
-Node: Appendix168892
-Node: Code Style169044
-Node: Authors172874
-Node: GNU Free Documentation License173570
-Node: 0_ PREAMBLE174333
-Node: 1_ APPLICABILITY AND DEFINITIONS175639
-Ref: fdl-document175864
-Ref: fdl-modified176155
-Ref: fdl-secondary176342
-Ref: fdl-invariant176987
-Ref: fdl-cover-texts177236
-Ref: fdl-transparent177449
-Ref: fdl-title-page178739
-Node: 2_ VERBATIM COPYING179128
-Node: 3_ COPYING IN QUANTITY180108
-Node: 4_ MODIFICATIONS182465
-Node: 5_ COMBINING DOCUMENTS188525
-Node: 6_ COLLECTIONS OF DOCUMENTS190022
-Node: 7_ AGGREGATION WITH INDEPENDENT WORKS190913
-Node: 8_ TRANSLATION192141
-Node: 9_ TERMINATION193044
-Node: 10_ FUTURE REVISIONS OF THIS LICENSE193699
-Node: Addendum194839
+Node: Introduction1998
+Node: Audience2803
+Node: What Is Supported?3130
+Node: Building from Source5636
+Node: Overview6016
+Node: Getting The Source7058
+Node: Releases7264
+Node: CVS Access7632
+Node: Code Dependencies8344
+Ref: Code Dependency Table9041
+Node: Testing Dependencies34556
+Ref: Testing Dependency Table34865
+Node: Documentation Dependencies38789
+Ref: Documentation Dependency Table39058
+Node: Configuring Gnash48126
+Node: Features50420
+Ref: Configuration Options - Features51020
+Node: Specifying Custom Paths57417
+Ref: Custom Path Options57887
+Node: Compiling the Code67510
+Node: Creating the Documentation68451
+Node: Running the Tests69797
+Node: Using DejaGnu70251
+Node: Increasing Verbosity70614
+Node: Running Some Tests71150
+Node: Running The Tests Manually71970
+Node: Movie tests72632
+Node: ActionScript Unit Tests72986
+Node: Installation73303
+Node: Libraries74616
+Node: Executables75472
+Node: Documentation76342
+Node: Cross Configuring77097
+Node: Software Internals80177
+Node: A Tour of Gnash80446
+Node: The Libraries81014
+Node: libgnashbase81284
+Node: libgnashserver81711
+Node: libgnashmedia82082
+Node: libgnashamf82571
+Node: libgnashbackend82993
+Node: libgnashplugin83308
+Node: libklashpart83514
+Node: The Applications83684
+Node: The Standalone Player84054
+Node: Gprocessor84351
+Node: SOLdumper84745
+Node: Dumpshm85012
+Node: The Plugin85231
+Node: Current Implementation85721
+Node: GUI Support86262
+Node: Mozplugger87951
+Node: Klash89842
+Node: The Message Logging System90392
+Node: Logging System API91949
+Node: The LogFile Instance94783
+Node: Sound handling in Gnash96267
+Node: Sound types97010
+Node: Sound parsing97547
+Node: Sound playback98115
+Node: The SDL sound backend98645
+Node: The Gstreamer backend99964
+Node: Future audio backends100980
+Node: Detailed description of the Gstreamer backend101470
+Node: Testing103721
+Node: Testing Tools104192
+Node: Test Cases105024
+Node: Writing ActionScript Tests105603
+Node: Writing Ming-based self-contained SWF tests108106
+Node: Using Ming-based test generators facilities109263
+Node: Writing self-contained SWF tests with other compilers111623
+Node: Writing Test Runners114748
+Node: Using the generic test runner for self-contained SWF tests116497
+Node: Writing Movie testers118587
+Node: Adding New ActionScript Class120327
+Node: Prototype121507
+Node: Declaration122924
+Node: Instantiation123189
+Node: Methods123816
+Node: Accessing Arguments124207
+Node: Returning a Value to ActionScript124603
+Node: Additional fn_call Members124982
+Node: Dynamic Properties125836
+Node: The as_value Object Type127341
+Node: Data Types127779
+Node: Determining the Type128100
+Node: Fetching the Value128632
+Node: Setting the Value and Type129122
+Node: Further Reading129716
+Node: Object ActionScript Class130131
+Node: The Methods of the Class130471
+Node: The Properties of the Object Class130810
+Node: Object Class Conformance131125
+Node: Reporting Bugs132664
+Node: Get a Fresh Binary Package133647
+Node: Determine if the bug was previously reported134433
+Node: Review the bug writing guidelines135251
+Node: Filing a bug report136302
+Node: Gnash Extensions136585
+Node: Creating A New Extension138855
+Node: Crafting an Extension140273
+Node: Debugging An Extension144577
+Node: Included Extensions146269
+Node: Gtk Extension146713
+Node: File I/O Extension147700
+Node: MySQL Extension148886
+Node: RTMP Protocol149737
+Node: AMF Format159533
+Node: Mozilla/Firefox NPAPI Plugin160509
+Node: Plugin C API161527
+Node: Plugin C++ API163386
+Node: OpenGL and Threads166650
+Node: Plugin Event Handling167978
+Node: Appendix168947
+Node: Code Style169099
+Node: Authors172929
+Node: GNU Free Documentation License173638
+Node: 0_ PREAMBLE174401
+Node: 1_ APPLICABILITY AND DEFINITIONS175707
+Ref: fdl-document175932
+Ref: fdl-modified176223
+Ref: fdl-secondary176410
+Ref: fdl-invariant177055
+Ref: fdl-cover-texts177304
+Ref: fdl-transparent177517
+Ref: fdl-title-page178807
+Node: 2_ VERBATIM COPYING179196
+Node: 3_ COPYING IN QUANTITY180176
+Node: 4_ MODIFICATIONS182533
+Node: 5_ COMBINING DOCUMENTS188593
+Node: 6_ COLLECTIONS OF DOCUMENTS190090
+Node: 7_ AGGREGATION WITH INDEPENDENT WORKS190981
+Node: 8_ TRANSLATION192209
+Node: 9_ TERMINATION193112
+Node: 10_ FUTURE REVISIONS OF THIS LICENSE193767
+Node: Addendum194907
End Tag Table
Index: doc/C/preformatted/gnash_user.info.in
===================================================================
RCS file: /sources/gnash/gnash/doc/C/preformatted/gnash_user.info.in,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- doc/C/preformatted/gnash_user.info.in 2 Mar 2008 17:54:16 -0000
1.2
+++ doc/C/preformatted/gnash_user.info.in 16 May 2008 13:23:42 -0000
1.3
@@ -1,7 +1,7 @@
-START-INFO-DIR-ENTRY
-This is gnash_user.info, produced by makeinfo version 4.11 from
gnash_user.texi.
+This is gnash_user.info, produced by makeinfo version 4.11 from stdin.
-* Gnash User Manual: (gnash_user). Gnash
+START-INFO-DIR-ENTRY
+* Gnash User Manual: (gnash_user). [MISSING TEXT]
END-INFO-DIR-ENTRY
@@ -25,7 +25,7 @@
Introduction
* Audience::
-* What Is Supported ?::
+* What Is Supported?::
Using Gnash
@@ -70,21 +70,21 @@
application or as a plugin for several popular web browsers. It
supports playing media from a disk or streaming over a network
connection. Some popular video sharing sites like YouTube are supported
-from a wide vaariety of devices from embedded ones to modern desktops.
+on a wide variety of devices from embedded ones to modern desktops.
Gnash has a better focus on security, allowing the user tight
control of all network or disk based I/O. Gnash also supports extending
-ActionScript by creating your own. You can write wrappers for any
-development library, and import them into the player much like perl or
-python does.
+ActionScript by creating your own classes. You can write wrappers for
+any development library, and import them into the player much like Perl
+or Python does.
* Menu:
* Audience::
-* What Is Supported ?::
+* What Is Supported?::
-File: gnash_user.info, Node: Audience, Next: What Is Supported ?, Up:
Introduction
+File: gnash_user.info, Node: Audience, Next: What Is Supported?, Up:
Introduction
1.1 Audience
============
@@ -95,46 +95,46 @@
manual.
-File: gnash_user.info, Node: What Is Supported ?, Prev: Audience, Up:
Introduction
+File: gnash_user.info, Node: What Is Supported?, Prev: Audience, Up:
Introduction
-1.2 What Is Supported ?
-=======================
+1.2 What Is Supported?
+======================
Gnash is known to compile for most any POSIX and ANSI C++ conforming
system if you have all the dependent libraries installed. Systems we
-test on, and which Gnash is know to run on are Ubuntu, Fedora, Debian,
-OpenBSD, NetBSD, FreeBSD, Win32, and Darwin (OSX) primarily.
+test on, and which Gnash is known to run on are Ubuntu, Fedora, Debian,
+Mandriva, OpenBSD, NetBSD, FreeBSD, Win32, and Darwin (OSX) primarily.
Occasionally other platforms are built, primarily by those distribution
maintainers. This includes BeOS, Haiku, Syllable, OS/2, Solaris,
Slackware, and Gentoo.
- Gnash is a capable of reading up to SWF v9 files and opcodes, but
+ Gnash is capable of reading up to SWF v9 files and opcodes, but
primarily supports SWF v7, with better SWF v8 and v9 support under
-heavy developement. With the 0.8.2 release, Gnash includes initial
+heavy development. With the 0.8.2 release, Gnash includes initial
parser support for SWF v8 and v9. Not all ActionScript 2 classes are
implemented yet, but all of the most heavily used ones are. Many
ActionScript 2 classes are partially implemented; there is support for
all of the commonly used methods of each class.
- Gnash has implemented about 80% of ActionScript v. 2.0, and has
-begun implementing ActionScript v. 3.0. Gnash supports the majority of
-Flash opcodes up to SWF version 9, and a wide sampling of ActionScript
-classes for SWF version 8.
+ Gnash has implemented about 80% of ActionScript v2.0, and has begun
+implementing ActionScript v3.0. Gnash supports the majority of Flash
+opcodes up to SWF v9, and a wide sampling of ActionScript classes for
+SWF v8.
- As ActionsScript 3 is a more developed version of ActionScript 2,
+ As ActionScript 3 is a more developed version of ActionScript 2,
many of the same classes work for both. Support has been added to
Gnash's ActionScript library to support the new ActionScript 3 filters,
-which get applied to every class. Implementing ActionScript clases is
+which get applied to every class. Implementing ActionScript classes is
often the easiest way for new Gnash developers to make a contribution
-without a deep internal knpowledge of Gnash.
+without a deep internal knowledge of Gnash.
Gnash has included video support since early 2007, but this is an
-every changing field of reverse engineering. Many of the popular video
-sharing sites use SWF v8 or v9, which Gnash still has imperfect support
-for. This is improving all the time, so often builds from a development
-snapshot will work when using the older release packaged in your
-distribution doesn't. You can find daily snapshots of the latest CVS
-tree at: http://www.gnashdev.org/dev_snapshots
+ever changing field of reverse engineering. Many of the popular video
+sharing sites use SWF v8 or v9, which Gnash supports imperfectly. This
+is improving all the time, so often builds from a development snapshot
+will work when using the older release packaged in your distribution
+doesn't. You can find daily snapshots of the latest CVS tree at:
+http://www.gnashdev.org/dev_snapshots
(http://www.gnashdev.org/dev_snapshots/).
Gnash uses ffmpeg for codecs, so any file supported by Mplayer
@@ -150,13 +150,13 @@
2 Using Gnash
*************
-When used as a standalone player, you can play any Flash file from the
+When used as a standalone player, you can play any SWF file from the
command line by entering a command of the format:
gnash <option> <flashfile.swf>
-The only required argument is the name (and location)of the file to be
+The only required argument is the name (and location) of the file to be
played.
The available options are listed in the following section, or you
@@ -164,12 +164,12 @@
command line:
- gnash --help |less
+ gnash --help | less
- The source code download of Gnash includes several example .SWF
+ The source code download of Gnash includes several example SWF
files. They are located in the `testsuite/samples/' directory of the
Gnash source directory. If you have installed Gnash correctly, issuing
-the a command similar to the following plays a short animation of a car
+a command similar to the following plays a short animation of a car
swerving and crashing:
@@ -371,7 +371,7 @@
==============================
No options are required for Gnash's default behavior. However, there
-are many options that can be used to that behavior.
+are many options that can be used to change that behavior.
gnash <options>
@@ -380,15 +380,15 @@
*Gnash Command Line Options*
Option Function
-`-h' Print usage information.
-`-s factor' Scale the movie up/down by the
+`-h, --help' Print usage information.
+`-s, --scale'<FACTOR> Scale the movie up/down by the
specified factor.
`-c' Produce a core file instead of
letting SDL trap it. By default,
SDL traps all signals, but
sometimes a core file is desired to
assist with debugging.
-`-d num' Number of milliseconds to delay in
+`-d, --delay'<NUM> Number of milliseconds to delay in
main loop. The main loop polls
continuously with a delay to adjust
how long _Gnash_ sleeps between
@@ -396,68 +396,65 @@
the number, the higher the CPU load
gets, and of course, the more
iterations of the main command loop.
-`-p' Run full speed (no sleep) and log
- frame rate.
-`-a' Enable Actionscript debugging.
-`-v' Be verbose; i.e. print debug
+`-v, --verbose' Be verbose; i.e. print important
messages to stdout.
-`-va' Be verbose about movie Actions.
+`-vv' Be very verbose; i.e. also print
+ debug messages to stdout.
+`-va' Be verbose about movie actions
+ (for ActionScript debugging). This
+ usually generates very large
+ amounts of text and will affect
+ Gnash's performance.
`-vp' Be verbose about parsing the
- movie. Warning: this can generate a
- lot of text, and can affect the
- performance of the movie you are
- playing.
-`-ml bias' Specify the texture LOD bias
- (float, default is -1) This affects
- the fuzziness of small objects,
- especially small text.
-`-w' Write a debug log called
- gnash-dbg.log. This will record of
- all the debug messages whether they
- are printed to the screen or not.
-`-j' Specify the width of the window.
- This is mostly used only by the
- plugin.
-`-k' Specify the height of the window.
- This is mostly used only by the
- plugin.
-`-1' Play once; exit when/if movie
- reaches the last frame. This is the
- default.
-`-r [0|1|2|3]' ? [undisplayable block object]
-`-t sec' Timeout and exit after the
+ movie. This generates a fairly large
+ amount of text, and is likely to
+ affect Gnash's performance.
+`-A'<FILE> Write the audio output to a wave
+ format file.
+`-D'<FILE> Write the video output to a raw
+ video file. This option is only
+ valid with dump-gnash.
+`-w, --writelog' Write the log messages to disk
+ using the file specified in the
+ gnashrc file. The default is
+ gnash-dbg.log.
+`-j, --width'<NUM> Specify the starting width of the
+ window. This is mostly used only by
+ the plugin.
+`-k, --height'<NUM> Specify the starting height of the
+ window. This is mostly used only by
+ the plugin.
+`-1, --once' Play once; exit if or when the
+ movie reaches the last frame.
+`-r, --render-mode'<0|1|2|3> ? [undisplayable block object]
+`-t, --timeout'<SEC> Timeout and exit after the
specified number of seconds. This
is useful for movies which repeat
themselves.
-`-g' Start Gnash with a Flash debugger
+`-g, --debugger' Start Gnash with a Flash debugger
console so one can set break points
or watchpoints.
-`-x id' This specifies the X11 window ID
+`-x, --xid'<ID> This specifies the X11 window ID
to display in; this is mainly used
by plugins.
-`-b bits' Bit depth of output window (for
- example, 16 or 32). Appropriate bit
- depths depend on the renderer and
- GUI library used.
-`-u url' Set the _url member of the root
+`-u, --real-url'<URL> Set the _url member of the root
movie. This is useful when you
download a movie and play it from a
different location. See also the -U
switch.
-`-U baseurl' Set base URL for this run. URLs
+`-U, --base-url'<URL> Set base URL for this run. URLs
are resolved relative to this base.
- If omitted defaults to the _url
- member of the top-level movie (see
- the -u switch).
-`-P entrymeter' Parameters are given in
- ParamName=Value syntax and are
- mostly useful to the plugin to
- honour EMBED tags attributes or
- explicit OBJECT PARAM tags. A
- common use for -P is to provide
- FlashVars (ie: -P
+ If omitted or empty, it defaults to
+ the _url member of the top-level
+ movie (see the -u switch).
+`-P, --param'<PARAMETER> Parameters are given in the syntax
+ "ParamName=Value" and are mostly
+ useful for the plugin to honour
+ EMBED tags attributes or explicit
+ OBJECT PARAM tags. A common use for
+ -P is to provide FlashVars (ie: -P
"FlashVars=home=http://www.gnu.org";).
-`-F filedescriptor' Use the given filedescriptor to
+`-F, --fd'<FILEDESCRIPTOR> Use the given filedescriptor to
send requests to the host
application. This is currently only
used for GETURL requests. The
@@ -467,6 +464,11 @@
NPAPI plugin to properly support
javascript and target windows in
geturl requests.
+`--max-advances'<NUM> Exit after the specified number of
+ frame advances.
+`--fullscreen' Start Gnash in fullscreen mode as
+ long as the GUI and window manager
+ support this.
File: gnash_user.info, Node: Gnash Interactive Control Keys, Next: User
Configuration File, Prev: Gnash Command Line Options, Up: Using Gnash
@@ -486,8 +488,6 @@
`ESC' Quit/Exit.
`CTRL-P' Toggle Pause.
`CTRL-R ' Restart the movie.
-`CTRL-[ or kp-' Step back one frame.
-`CTRL-] or kp+' Step forward one frame.
`CTRL-L' Force immediate redraw.
`CTRL-T' Debug. Test the set_variable()
function.
@@ -495,7 +495,6 @@
function.
`CTRL-M' Debug. Test the call_method()
function.
-`CTRL-B' Toggle the background color.
File: gnash_user.info, Node: User Configuration File, Prev: Gnash
Interactive Control Keys, Up: Using Gnash
@@ -614,7 +613,7 @@
_append_ to add new
sandboxes. Note that
there's currently no
- way to *drop* the
+ way to _drop_ the
directory of base dir
from the list of
allowed local sandboxes.
@@ -725,11 +724,11 @@
StreamsTimeout double Set the number of
seconds after which
streams download time
- out. Note that timeouts
- only occurs after the
- given number of seconds
- passed w/out anything
- was received.
+ out. Timeouts only
+ occur after the given
+ number of seconds have
+ passed without anything
+ being received.
insecureSSL on/off If set to _on_, no
verification of SSL
connections is
@@ -755,6 +754,19 @@
SOLreadonly on/off If set to _on_, Gnash
will not write Shared
Object files.
+ignoreFSCommand on/off If set to on (default),
+ Gnash will ignore
+ fscommands in
+ standalone mode.
+ Fscommands are requests
+ from the playing movie
+ to the operating system
+ or user interface: the
+ most common are quit,
+ fullscreen, showmenu
+ and exec. Gnash always
+ ignores fscommands when
+ running as a plugin.
URLOpenerFormat string Set the format of an
url opener command. The
%u label would be
@@ -889,8 +901,8 @@
Maemo 2.1 i385, ARMv5t
Scratchbox i386, ARMv5t
Access Linux Platform i386, ARMv5t
-Mandriva i386, MIPS
-Open Embedded, OpenMoko, Poky ARM
+Mandriva i386, x86-64, MIPS
+Open Embedded, OpenMoko ARM
YellowDog Linux 6 PowerPC, PS3
OpenSuSE 10 i586, x86-64
Red Hat Enterprise, CentOS x86-32, x86-64
@@ -907,7 +919,7 @@
3.1.2 Software Requirements
---------------------------
-The 0.8.2 release of Gnash has been designed to run on UNIX/Linux
+The 0.8.3 release of Gnash has been designed to run on UNIX/Linux
variants, and has been run on most of the free ones. However, Gnash
has successfully run on Windows, Darwin (Mac OS X), Irix, Solaris,
BeOs, OS/2, and Haiku. Gnash has also run on the following 64-bit
@@ -1027,16 +1039,16 @@
****************
The Gnash project relies on the community of Gnash users to test the
-player, feedback is critical to any successful project. Not only does
+player. Feedback is critical to any successful project. Not only does
it let us know that people use Gnash, but it helps us understand the
community's needs. Gnash uses a bug tracker on
`http://savannah.gnu.org' to manage these reports.
When filing a report, please follow the guidelines below. The better
your bug report is, the easier it will be for the developers to address
-the issue. Bug reports without enough information will initially be
-asked to provide this information anyway. Adding critical details, like
-the Operating System you are on, it's version, and any relevant error
+the issue. Bug reports without enough information will be asked to
+provide this information anyway. Adding critical details, like the
+Operating System you are on, its version, and any relevant error
messages from Gnash that you get.
* Menu:
@@ -1057,8 +1069,8 @@
infrastructure allows the automated building of binary packages. Often
the version of Gnash as packaged by a GNU/Linux or BSD distribution is
based on the last official release, which could be months out of date.
-It is helpful if this is the case to try a newer packaged build of
-Gnash.
+It helps us, if this is the case, for you to try a newer packaged build
+of Gnash.
You can get a fresh binary package of Gnash, as well as recent
source packages from http://www.getgnash.org/packages
@@ -1140,7 +1152,7 @@
AGG
AGG is the AntiGrain 2D graphics library, which can be used as a
renderer in Gnash. It is faster than OpenGL on systems without
- hardware graphics acceleration. As of Gnash version 0.8.1 it is
+ hardware graphics acceleration. As of Gnash version 0.8.2 it is
the more feature complete renderer.
AMF
@@ -1203,8 +1215,10 @@
Flash
The term _Flash_ is used to describe both the Adobe IDE for
creating _SWF_ files, and the technology itself. Flash is a
- trademarked term of Adobe's, we prfer to use SWF to refer to the
- files themselves, as well as the format, instead of flash(tm).
+ registered trademark belonging to Adobe. Unfortunately, neither
+ Macromedia nor Adobe have done a good job creating a generic name
+ for all things having to do with Flash. They risk loss of their
+ trademark.
FLV
FLV is a proprietary file format used to deliver Flash video. It
@@ -1252,15 +1266,14 @@
K
=
-Klash
- _Klash_ was the name given to the stand-alone instance of Gnash
+kde-gnash
+ _kde-gnash_ is the name given to the stand-alone instance of Gnash
which used the KDE GUI. It has been replaced with an
- implementation using Qt. Some documentation may incorrectly refer
- to the Konqueror plugin as _Klash_. The plugin was renamed
- _Kpart_.
+ implementation using Qt. The Konqueror plugin runs kde-gnash and
+ is called _Kparts_.
-Kpart
- _Kpart_ is a plugin for Konqueror which is enabled with the
+Kparts
+ _Kparts_ is a plugin for Konqueror which is enabled with the
configuration option -enable-kparts.
@@ -1371,17 +1384,15 @@
platforms' graphics, sound, and input APIs. Gnash can use it as a
GUI and/or as a sound handler. Note that the two usages are
independent of each other: you can use it for a task and not for
- the other if you wish. At time or writing (2007-01-11) the SDL GUI
- lacks menus and a performant input event architecture; the SDL
- sound handler is the most feature rich, supporting Video through
- ffmpeg.
+ the other if you wish. This version of Gnash does not implement
+ menus in the SDL GUI; the SDL sound handler is the most feature
+ rich, supporting video through ffmpeg.
sound handler
The _sound handler_ is the part of Gnash which handles both event
- sounds and streaming sound. Audio from external sources are also
- handled through the sound handler when SDL is used. The sound
- handler must be selected during configuration of Gnash when
- compiling.
+ sounds and streaming sound. Audio from external sources is sent
+ through the sound handler when SDL is used. The sound handler
+ must be selected during configuration of Gnash when compiling.
There are currently two sound handlers available in Gnash: ffmpeg
and Gstreamer. The ffmpeg sound handler uses SDL for mixing. The
@@ -1394,8 +1405,8 @@
inside another, having its own timeline.
Stage
- The visible area of a Flash movie. The name derives from a
- theater analogy. Graphical elements are referred to as characters.
+ The visible area of a Flash movie. The name derives from a theater
+ analogy. Graphical elements are referred to as characters.
SWF
_SWF_ is the file format for _Flash_ movies.
@@ -1435,9 +1446,9 @@
Gnash is maintained by Rob Savoye. Other active developers are: Sandro
Santilli, Bastiaan Jacques, Udo Giacomozzi, Chad Musick, Benjamin
-Wolsey, and Zou Lunkai. Please send all comments and suggestions to
-<address@hidden>. Past and sometimes current developers are Tomas
-Groth and Markus Gothe.
+Wolsey, Zou Lunkai, and Russ Nelson. Please send all comments and
+suggestions to <address@hidden>. Past and sometimes current
+developers are Tomas Groth and Markus Gothe.
Gnash was initially derived from GameSWF. GameSWF is maintained by
Thatcher Ulrich <address@hidden>. The following people contributed to
@@ -1894,72 +1905,72 @@
Tag Table:
-Node: Top166
-Node: Introduction1472
-Node: Audience2265
-Node: What Is Supported ?2594
-Node: Using Gnash5127
-Node: Gnash Command Line Options51455
-Ref: Gnash Command Line Options <1>51802
-Node: Gnash Interactive Control Keys57648
-Ref: Gnash Interactive Control Keys <1>58015
-Node: User Configuration File58952
-Ref: User Configuration Variables59737
-Node: Installing and Configuring Gnash78594
-Node: Requirements78955
-Node: Hardware Requirements79276
-Ref: Build Matrix80053
-Node: Software Requirements81275
-Node: Downloading Gnash82108
-Node: Getting the Source82743
-Node: Releases83103
-Node: Snapshot83661
-Node: Repository84132
-Node: Getting Codec Support84953
-Node: Reporting Bugs85670
-Node: Get a Fresh Binary Package86670
-Node: Determine if the bug was previously reported87449
-Node: Review the bug writing guidelines88268
-Node: Filing a bug report89320
-Node: Glossary89604
-Ref: A89718
-Ref: C90542
-Ref: D90828
-Ref: E91240
-Ref: F91480
-Ref: G92463
-Ref: K93448
-Ref: L93854
-Ref: M93990
-Ref: N94349
-Ref: O94506
-Ref: P95121
-Ref: Q95408
-Ref: R95592
-Ref: S96833
-Ref: T98373
-Ref: X99081
-Node: Authors99174
-Node: GNU Free Documentation License99871
-Node: 0_ PREAMBLE100635
-Node: 1_ APPLICABILITY AND DEFINITIONS101942
-Ref: fdl-document102168
-Ref: fdl-modified102459
-Ref: fdl-secondary102646
-Ref: fdl-invariant103291
-Ref: fdl-cover-texts103540
-Ref: fdl-transparent103753
-Ref: fdl-title-page105043
-Node: 2_ VERBATIM COPYING105432
-Node: 3_ COPYING IN QUANTITY106413
-Node: 4_ MODIFICATIONS108771
-Node: 5_ COMBINING DOCUMENTS114832
-Node: 6_ COLLECTIONS OF DOCUMENTS116330
-Node: 7_ AGGREGATION WITH INDEPENDENT WORKS117222
-Node: 8_ TRANSLATION118451
-Node: 9_ TERMINATION119355
-Node: 10_ FUTURE REVISIONS OF THIS LICENSE120011
-Node: Addendum121152
+Node: Top165
+Node: Introduction1470
+Node: Audience2267
+Node: What Is Supported?2595
+Node: Using Gnash5102
+Node: Gnash Command Line Options51425
+Ref: Gnash Command Line Options <1>51779
+Node: Gnash Interactive Control Keys57820
+Ref: Gnash Interactive Control Keys <1>58187
+Node: User Configuration File58936
+Ref: User Configuration Variables59721
+Node: Installing and Configuring Gnash79504
+Node: Requirements79865
+Node: Hardware Requirements80186
+Ref: Build Matrix80963
+Node: Software Requirements82193
+Node: Downloading Gnash83026
+Node: Getting the Source83661
+Node: Releases84021
+Node: Snapshot84579
+Node: Repository85050
+Node: Getting Codec Support85871
+Node: Reporting Bugs86588
+Node: Get a Fresh Binary Package87578
+Node: Determine if the bug was previously reported88365
+Node: Review the bug writing guidelines89184
+Node: Filing a bug report90236
+Node: Glossary90520
+Ref: A90634
+Ref: C91458
+Ref: D91744
+Ref: E92156
+Ref: F92396
+Ref: G93469
+Ref: K94454
+Ref: L94814
+Ref: M94950
+Ref: N95309
+Ref: O95466
+Ref: P96081
+Ref: Q96368
+Ref: R96552
+Ref: S97793
+Ref: T99279
+Ref: X99987
+Node: Authors100080
+Node: GNU Free Documentation License100790
+Node: 0_ PREAMBLE101554
+Node: 1_ APPLICABILITY AND DEFINITIONS102861
+Ref: fdl-document103087
+Ref: fdl-modified103378
+Ref: fdl-secondary103565
+Ref: fdl-invariant104210
+Ref: fdl-cover-texts104459
+Ref: fdl-transparent104672
+Ref: fdl-title-page105962
+Node: 2_ VERBATIM COPYING106351
+Node: 3_ COPYING IN QUANTITY107332
+Node: 4_ MODIFICATIONS109690
+Node: 5_ COMBINING DOCUMENTS115751
+Node: 6_ COLLECTIONS OF DOCUMENTS117249
+Node: 7_ AGGREGATION WITH INDEPENDENT WORKS118141
+Node: 8_ TRANSLATION119370
+Node: 9_ TERMINATION120274
+Node: 10_ FUTURE REVISIONS OF THIS LICENSE120930
+Node: Addendum122071
End Tag Table
Index: doc/C/preformatted/gnashref.html.in
===================================================================
RCS file: /sources/gnash/gnash/doc/C/preformatted/gnashref.html.in,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- doc/C/preformatted/gnashref.html.in 2 Mar 2008 17:54:16 -0000 1.2
+++ doc/C/preformatted/gnashref.html.in 16 May 2008 13:23:43 -0000 1.3
@@ -1,5 +1,5 @@
<html><head><meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"><title>Gnash Reference Manual</title><meta name="generator"
content="DocBook XSL Stylesheets V1.73.2"></head><body bgcolor="white"
text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book"
lang="en"><div class="titlepage"><div><div><h1 class="title"><a
name="index"></a>Gnash Reference Manual</h1></div><div><p class="releaseinfo">
- This manual describes version 0.8.2 of Gnash.
+ This manual describes version 0.8.3 of Gnash.
</p></div><div><p class="copyright">Copyright © 2005, 2006, 2007, 2008
Free Software Foundation</p></div><div><div class="legalnotice"><a
name="legalnotice"></a><p>
Permission is granted to copy, distribute and/or modify this document
under the terms of the <a class="link" href="#fdl" title="Appendix A. GNU
Free Documentation License"><em class="citetitle">GNU
@@ -18,60 +18,60 @@
</p>
<p class="publisher">Open Media Now! Foundation</p>
- </td></tr></table></div></div></div><hr></div><div class="toc"><p><b>Table
of Contents</b></p><dl><dt><span class="chapter"><a href="#intro">1.
Introduction</a></span></dt><dd><dl><dt><span class="sect1"><a
href="#audience">Audience</a></span></dt><dt><span class="sect1"><a
href="#runs-on">What Is Supported ?</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#build">2. Building from
Source</a></span></dt><dd><dl><dt><span class="sect1"><a
href="#building_overview">Overview</a></span></dt><dt><span class="sect1"><a
href="#gettingsource">Getting The Source</a></span></dt><dd><dl><dt><span
class="sect2"><a href="#sourcereleases">Releases</a></span></dt><dt><span
class="sect2"><a href="#sourcecvs">CVS
Access</a></span></dt></dl></dd><dt><span class="sect1"><a
href="#dependencies">Code Dependencies</a></span></dt><dt><span
class="sect1"><a href="#testdep">Testing Dependencies</a></span></dt><dt><span
class="sect1"><a href="#docdepend">Documentation
Dependencies</a></span></dt><dt><span class="sect1"><a
href="#configure">Configuring Gnash</a></span></dt><dt><span class="sect1"><a
href="#compile">Compiling the Code</a></span></dt><dt><span class="sect1"><a
href="#processdoc">Creating the Documentation</a></span></dt><dt><span
class="sect1"><a href="#runtests">Running the
Tests</a></span></dt><dd><dl><dt><span class="sect2"><a href="#dejagnu">Using
DejaGnu</a></span></dt><dt><span class="sect2"><a href="#manually">Running The
Tests Manually</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a
href="#internals">3. Software Internals</a></span></dt><dd><dl><dt><span
class="sect1"><a href="#tour">A Tour of Gnash</a></span></dt><dd><dl><dt><span
class="sect2"><a href="#The%20Libraries">The Libraries</a></span></dt><dt><span
class="sect2"><a href="#apps">The Applications</a></span></dt><dt><span
class="sect2"><a href="#plugin">The Plugin</a></span></dt><dt><span
class="sect2"><a href="#logging">The Debug Logging
System</a></span></dt></dl></dd><dt><span class="sect1"><a
href="#soundhandlers">Sound handling in Gnash</a></span></dt><dd><dl><dt><span
class="sect2"><a href="#soundtypes">Sound types</a></span></dt><dt><span
class="sect2"><a href="#soundparsing">Sound parsing</a></span></dt><dt><span
class="sect2"><a href="#soundplayback">Sound playback</a></span></dt><dt><span
class="sect2"><a href="#sdlsound">The SDL sound
backend</a></span></dt><dt><span class="sect2"><a href="#gstreamer">The
Gstreamer backend</a></span></dt><dt><span class="sect2"><a
href="#audio-future">Future audio backends</a></span></dt><dt><span
class="sect2"><a href="#gstreamer-details">Detailed description of the
Gstreamer backend</a></span></dt></dl></dd><dt><span class="sect1"><a
href="#testing">Testing </a></span></dt><dd><dl><dt><span class="sect2"><a
href="#testtools">Testing Tools</a></span></dt><dt><span class="sect2"><a
href="#testcases">Test Cases</a></span></dt><dt><span class="sect2"><a
href="#writeastests">Writing ActionScript Tests</a></span></dt><dt><span
class="sect2"><a href="#writemingtests">Writing Ming-based self-contained SWF
tests</a></span></dt><dt><span class="sect2"><a
href="#writing_dejagnu_so_tests">Writing self-contained SWF tests with other
compilers</a></span></dt><dt><span class="sect2"><a
href="#writing_test_runners">Writing Test
Runners</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a
href="#bugreport">5. Reporting Bugs</a></span></dt><dd><dl><dt><span
class="sect1"><a href="#bugstep_package">Get a Fresh Binary
Package</a></span></dt><dt><span class="sect1"><a
href="#bugstep_search">Determine if the bug was previously
reported</a></span></dt><dt><span class="sect1"><a
href="#bugstep_guidelines">Review the bug writing
guidelines</a></span></dt><dt><span class="sect1"><a
href="#bugstep_file">Filing a bug report</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#extensions">6. Gnash
Extensions</a></span></dt><dd><dl><dt><span class="sect1"><a
href="#newext">Creating A New Extension</a></span></dt><dd><dl><dt><span
class="sect2"><a href="#craftext">Crafting an
Extension</a></span></dt></dl></dd><dt><span class="sect1"><a
href="#debuext">Debugging An Extension</a></span></dt><dt><span
class="sect1"><a href="#inclext">Included
Extensions</a></span></dt></dl></dd><dt><span class="chapter"><a
href="#rtmp">7. RTMP Protocol</a></span></dt><dd><dl><dt><span class="sect1"><a
href="#amf">AMF Format</a></span></dt></dl></dd><dt><span class="chapter"><a
href="#nsapi">8. Mozilla/Firefox NPAPI Plugin</a></span></dt><dd><dl><dt><span
class="sect1"><a href="#plugincapi">Plugin C API</a></span></dt><dt><span
class="sect1"><a href="#plugincppapi">Plugin C++ API</a></span></dt><dt><span
class="sect1"><a href="#glthread">OpenGL and Threads</a></span></dt><dt><span
class="sect1"><a href="#eventhandle">Plugin Event
Handling</a></span></dt></dl></dd><dt><span class="chapter"><a
href="#authors">9. Authors</a></span></dt><dt><span class="appendix"><a
href="#fdl">A. GNU Free Documentation License</a></span></dt><dd><dl><dt><span
class="sect1"><a href="#fdl-preamble">0. PREAMBLE</a></span></dt><dt><span
class="sect1"><a href="#fdl-section1">1. APPLICABILITY AND
DEFINITIONS</a></span></dt><dt><span class="sect1"><a href="#fdl-section2">2.
VERBATIM COPYING</a></span></dt><dt><span class="sect1"><a
href="#fdl-section3">3. COPYING IN QUANTITY</a></span></dt><dt><span
class="sect1"><a href="#fdl-section4">4. MODIFICATIONS</a></span></dt><dt><span
class="sect1"><a href="#fdl-section5">5. COMBINING
DOCUMENTS</a></span></dt><dt><span class="sect1"><a href="#fdl-section6">6.
COLLECTIONS OF DOCUMENTS</a></span></dt><dt><span class="sect1"><a
href="#fdl-section7">7. AGGREGATION WITH INDEPENDENT
WORKS</a></span></dt><dt><span class="sect1"><a href="#fdl-section8">8.
TRANSLATION</a></span></dt><dt><span class="sect1"><a href="#fdl-section9">9.
TERMINATION</a></span></dt><dt><span class="sect1"><a href="#fdl-section10">10.
FUTURE REVISIONS OF THIS LICENSE</a></span></dt><dt><span class="sect1"><a
href="#fdl-using">Addendum</a></span></dt></dl></dd></dl></div><div
class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>2.1. <a
href="#codedeps">Code Dependency Table</a></dt><dt>2.2. <a
href="#testdeps">Testing Dependency Table</a></dt><dt>2.3. <a
href="#docdeps">Documentation Dependency Table</a></dt><dt>2.4. <a
href="#tb-config-features">Configuration Options - Features</a></dt><dt>2.5. <a
href="#tb-configure-paths">Custom Path Options</a></dt></dl></div><div
class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a
name="intro"></a>Chapter 1. Introduction</h2></div></div></div><div
class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a
href="#audience">Audience</a></span></dt><dt><span class="sect1"><a
href="#runs-on">What Is Supported ?</a></span></dt></dl></div><p>
+ </td></tr></table></div></div></div><hr></div><div class="toc"><p><b>Table
of Contents</b></p><dl><dt><span class="chapter"><a href="#intro">1.
Introduction</a></span></dt><dd><dl><dt><span class="sect1"><a
href="#audience">Audience</a></span></dt><dt><span class="sect1"><a
href="#runs-on">What Is Supported?</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#build">2. Building from
Source</a></span></dt><dd><dl><dt><span class="sect1"><a
href="#building_overview">Overview</a></span></dt><dt><span class="sect1"><a
href="#gettingsource">Getting The Source</a></span></dt><dd><dl><dt><span
class="sect2"><a href="#sourcereleases">Releases</a></span></dt><dt><span
class="sect2"><a href="#sourcecvs">CVS
Access</a></span></dt></dl></dd><dt><span class="sect1"><a
href="#dependencies">Code Dependencies</a></span></dt><dt><span
class="sect1"><a href="#testdep">Testing Dependencies</a></span></dt><dt><span
class="sect1"><a href="#docdepend">Documentation
Dependencies</a></span></dt><dt><span class="sect1"><a
href="#configure">Configuring Gnash</a></span></dt><dt><span class="sect1"><a
href="#compile">Compiling the Code</a></span></dt><dt><span class="sect1"><a
href="#processdoc">Creating the Documentation</a></span></dt><dt><span
class="sect1"><a href="#runtests">Running the
Tests</a></span></dt><dd><dl><dt><span class="sect2"><a href="#dejagnu">Using
DejaGnu</a></span></dt><dt><span class="sect2"><a href="#manually">Running The
Tests Manually</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a
href="#internals">3. Software Internals</a></span></dt><dd><dl><dt><span
class="sect1"><a href="#tour">A Tour of Gnash</a></span></dt><dd><dl><dt><span
class="sect2"><a href="#The%20Libraries">The Libraries</a></span></dt><dt><span
class="sect2"><a href="#apps">The Applications</a></span></dt><dt><span
class="sect2"><a href="#plugin">The Plugin</a></span></dt><dt><span
class="sect2"><a href="#logging">The Message Logging
System</a></span></dt></dl></dd><dt><span class="sect1"><a
href="#soundhandlers">Sound handling in Gnash</a></span></dt><dd><dl><dt><span
class="sect2"><a href="#soundtypes">Sound types</a></span></dt><dt><span
class="sect2"><a href="#soundparsing">Sound parsing</a></span></dt><dt><span
class="sect2"><a href="#soundplayback">Sound playback</a></span></dt><dt><span
class="sect2"><a href="#sdlsound">The SDL sound
backend</a></span></dt><dt><span class="sect2"><a href="#gstreamer">The
Gstreamer backend</a></span></dt><dt><span class="sect2"><a
href="#audio-future">Future audio backends</a></span></dt><dt><span
class="sect2"><a href="#gstreamer-details">Detailed description of the
Gstreamer backend</a></span></dt></dl></dd><dt><span class="sect1"><a
href="#testing">Testing </a></span></dt><dd><dl><dt><span class="sect2"><a
href="#testtools">Testing Tools</a></span></dt><dt><span class="sect2"><a
href="#testcases">Test Cases</a></span></dt><dt><span class="sect2"><a
href="#writeastests">Writing ActionScript Tests</a></span></dt><dt><span
class="sect2"><a href="#writemingtests">Writing Ming-based self-contained SWF
tests</a></span></dt><dt><span class="sect2"><a
href="#writing_dejagnu_so_tests">Writing self-contained SWF tests with other
compilers</a></span></dt><dt><span class="sect2"><a
href="#writing_test_runners">Writing Test
Runners</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a
href="#bugreport">5. Reporting Bugs</a></span></dt><dd><dl><dt><span
class="sect1"><a href="#bugstep_package">Get a Fresh Binary
Package</a></span></dt><dt><span class="sect1"><a
href="#bugstep_search">Determine if the bug was previously
reported</a></span></dt><dt><span class="sect1"><a
href="#bugstep_guidelines">Review the bug writing
guidelines</a></span></dt><dt><span class="sect1"><a
href="#bugstep_file">Filing a bug report</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#extensions">6. Gnash
Extensions</a></span></dt><dd><dl><dt><span class="sect1"><a
href="#newext">Creating A New Extension</a></span></dt><dd><dl><dt><span
class="sect2"><a href="#craftext">Crafting an
Extension</a></span></dt></dl></dd><dt><span class="sect1"><a
href="#debuext">Debugging An Extension</a></span></dt><dt><span
class="sect1"><a href="#inclext">Included
Extensions</a></span></dt></dl></dd><dt><span class="chapter"><a
href="#rtmp">7. RTMP Protocol</a></span></dt><dd><dl><dt><span class="sect1"><a
href="#amf">AMF Format</a></span></dt></dl></dd><dt><span class="chapter"><a
href="#nsapi">8. Mozilla/Firefox NPAPI Plugin</a></span></dt><dd><dl><dt><span
class="sect1"><a href="#plugincapi">Plugin C API</a></span></dt><dt><span
class="sect1"><a href="#plugincppapi">Plugin C++ API</a></span></dt><dt><span
class="sect1"><a href="#glthread">OpenGL and Threads</a></span></dt><dt><span
class="sect1"><a href="#eventhandle">Plugin Event
Handling</a></span></dt></dl></dd><dt><span class="chapter"><a
href="#authors">9. Authors</a></span></dt><dt><span class="appendix"><a
href="#fdl">A. GNU Free Documentation License</a></span></dt><dd><dl><dt><span
class="sect1"><a href="#fdl-preamble">0. PREAMBLE</a></span></dt><dt><span
class="sect1"><a href="#fdl-section1">1. APPLICABILITY AND
DEFINITIONS</a></span></dt><dt><span class="sect1"><a href="#fdl-section2">2.
VERBATIM COPYING</a></span></dt><dt><span class="sect1"><a
href="#fdl-section3">3. COPYING IN QUANTITY</a></span></dt><dt><span
class="sect1"><a href="#fdl-section4">4. MODIFICATIONS</a></span></dt><dt><span
class="sect1"><a href="#fdl-section5">5. COMBINING
DOCUMENTS</a></span></dt><dt><span class="sect1"><a href="#fdl-section6">6.
COLLECTIONS OF DOCUMENTS</a></span></dt><dt><span class="sect1"><a
href="#fdl-section7">7. AGGREGATION WITH INDEPENDENT
WORKS</a></span></dt><dt><span class="sect1"><a href="#fdl-section8">8.
TRANSLATION</a></span></dt><dt><span class="sect1"><a href="#fdl-section9">9.
TERMINATION</a></span></dt><dt><span class="sect1"><a href="#fdl-section10">10.
FUTURE REVISIONS OF THIS LICENSE</a></span></dt><dt><span class="sect1"><a
href="#fdl-using">Addendum</a></span></dt></dl></dd></dl></div><div
class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>2.1. <a
href="#codedeps">Code Dependency Table</a></dt><dt>2.2. <a
href="#testdeps">Testing Dependency Table</a></dt><dt>2.3. <a
href="#docdeps">Documentation Dependency Table</a></dt><dt>2.4. <a
href="#tb-config-features">Configuration Options - Features</a></dt><dt>2.5. <a
href="#tb-configure-paths">Custom Path Options</a></dt></dl></div><div
class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a
name="intro"></a>Chapter 1. Introduction</h2></div></div></div><div
class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a
href="#audience">Audience</a></span></dt><dt><span class="sect1"><a
href="#runs-on">What Is Supported?</a></span></dt></dl></div><p>
<span class="application">Gnash</span> is a free SWF movie player. It is
available as a
stand-alone application or as a plugin for several popular
web browsers. It supports playing media from a disk or streaming
over a network connection. Some popular video sharing sites like
- YouTube are supported from a wide vaariety of devices from
+ YouTube are supported on a wide variety of devices from
embedded ones to modern desktops.
</p><p>
<span class="application">Gnash</span> has a better focus on security,
allowing the user tight
control of all network or disk based I/O. Gnash also supports
- extending ActionScript by creating your own. You can write
+ extending ActionScript by creating your own classes. You can write
wrappers for any development library, and import them into the
- player much like perl or python does.
+ player much like Perl or Python does.
</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2
class="title" style="clear: both"><a
name="audience"></a>Audience</h2></div></div></div><p>
This manual is primarily focused on users interested in how to
get Gnash installed from a package, and basic usage as a web
browser plugin. For more technical details, please refer to the
Gnash Reference manual.
- </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="runs-on"></a>What Is Supported ?</h2></div></div></div><p>
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="runs-on"></a>What Is Supported?</h2></div></div></div><p>
Gnash is known to compile for most any POSIX and ANSI C++
conforming system if you have all the dependent libraries
- installed. Systems we test on, and which Gnash is know to
- run on are Ubuntu, Fedora, Debian, OpenBSD, NetBSD, FreeBSD,
+ installed. Systems we test on, and which Gnash is known to
+ run on are Ubuntu, Fedora, Debian, Mandriva, OpenBSD, NetBSD, FreeBSD,
Win32, and Darwin (OSX) primarily. Occasionally other platforms
are built, primarily by those distribution maintainers. This
includes BeOS, Haiku, Syllable, OS/2, Solaris, Slackware, and
Gentoo.
</p><p>
- Gnash is a capable of reading up to SWF v9 files and opcodes,
+ Gnash is capable of reading up to SWF v9 files and opcodes,
but primarily supports SWF v7, with better SWF v8 and v9
- support under heavy developement. With the 0.8.2 release,
+ support under heavy development. With the 0.8.2 release,
Gnash includes initial parser support for SWF v8 and v9.
Not all ActionScript 2 classes are implemented yet, but all of the
most heavily used ones are. Many ActionScript 2 classes are
partially implemented; there is support for all of the
commonly used methods of each class.
</p><p>
- Gnash has implemented about 80% of ActionScript v. 2.0, and has
- begun implementing ActionScript v. 3.0. Gnash supports the
- majority of Flash opcodes up to SWF version 9, and a wide
- sampling of ActionScript classes for SWF version 8.
+ Gnash has implemented about 80% of ActionScript v2.0, and has
+ begun implementing ActionScript v3.0. Gnash supports the
+ majority of Flash opcodes up to SWF v9, and a wide
+ sampling of ActionScript classes for SWF v8.
</p><p>
- As ActionsScript 3 is a more developed version of
+ As ActionScript 3 is a more developed version of
ActionScript 2, many of the same classes work for
both. Support has been added to Gnash's ActionScript library
to support the new ActionScript 3 filters, which get applied
- to every class. Implementing ActionScript clases is often the
+ to every class. Implementing ActionScript classes is often the
easiest way for new Gnash developers to make a contribution
- without a deep internal knpowledge of Gnash.
+ without a deep internal knowledge of Gnash.
</p><p>
Gnash has included video support since early 2007, but this is
- an every changing field of reverse engineering. Many of the
+ an ever changing field of reverse engineering. Many of the
popular video sharing sites use SWF v8 or v9, which Gnash
- still has imperfect support for. This is improving all the
+ supports imperfectly. This is improving all the
time, so often builds from a development snapshot will work
when using the older release packaged in your distribution
doesn't. You can find daily snapshots of the latest CVS tree
@@ -325,7 +325,7 @@
if you are using the development source from CVS.
</td><td align="left"><code
class="filename">libltdl3-dev</code></td><td align="left"><code
class="filename">libtool</code></td><td align="left"><code
class="filename">libtool</code></td></tr></tbody></table></div></div><br
class="table-break"></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="testdep"></a>Testing Dependencies</h2></div></div></div><p>
<span class="application">Gnash</span> tries to run as many tests as
possible, but will
- simply skip tests if the tools to run them are unavailable.
+ silentl skip tests if the tools to run them are unavailable.
</p><div class="table"><a name="testdeps"></a><p class="title"><b>Table 2.2.
Testing Dependency Table</b></p><div class="table-contents"><table
summary="Testing Dependency Table"
border="1"><colgroup><col><col><col><col><col><col><col></colgroup><thead><tr><th
align="left">Name</th><th align="left">Level</th><th
align="left">Version</th><th align="left">Description</th><th
align="left">Explanation</th><th align="left">apt-get package</th><th
align="left">RPM/Yum package</th><th align="left">BSD
package</th></tr></thead><tbody><tr><td align="left">Ming</td><td
align="left">Optional</td><td align="left">0.4.0_beta4 or higher</td><td
align="left">
Ming is an ActionScript compiler.
</td><td align="left">
@@ -335,7 +335,7 @@
</td><td align="left">
Mtasc is used in some tests.
</td><td align="left"><code class="filename">mtasc</code></td><td
align="left">No distribution packages are available.</td><td align="left">No
distribution packages are available.</td></tr><tr><td align="left">swfc</td><td
align="left">Optional</td><td align="left">part of swftools 0.8.1</td><td
align="left">
- Swfc a swf decompiler.
+ Swfc is an swf compiler.
</td><td align="left">
Swfc is used in some testcases.
</td><td align="left">No distribution packages are available.</td><td
align="left">No distribution packages are available.</td><td align="left">No
distribution packages are available.</td></tr><tr><td
align="left">swfmill</td><td align="left">Optional</td><td align="left">
0.2.12</td><td align="left">
@@ -384,7 +384,7 @@
into GNU info pages. You can download it from
<a class="ulink" href="http://ftp.gnu.org/gnu/texinfo/";
target="_top">http://ftp.gnu.org/gnu/texinfo/</a>.
</td><td align="left">
- Texinfo is required if you wish to product GNU info
+ Texinfo is required if you wish to produce GNU info
pages.
</td><td align="left"><code class="filename">texinfo</code></td><td
align="left"><code class="filename">texinfo</code></td><td align="left"><code
class="filename">texinfo</code></td></tr><tr><td align="left">FOP</td><td
align="left">Optional</td><td align="left">0.20.5</td><td align="left">
Formatting Objects Processor is a print formatter
@@ -525,7 +525,7 @@
works with KDE is opengl.
</p></dd><dt><span class="term">FLTK</span></dt><dd><p>
Fast Light ToolKit, low on resource usage.
- Since all build using fltk are now broken, we declare it
+ Since all builds using fltk are now broken, we declare it
"for developers".
</p></dd><dt><span class="term">FB</span></dt><dd><p>
The Linux Frame Buffer, also known as /dev/fb0.
@@ -565,15 +565,16 @@
</td></tr><tr><td align="left">
<code class="option">--disable-plugins</code>
</td><td align="left">Disable build of both kparts and npapi
plugins</td></tr><tr><td align="left"><code
class="option">--enable-renderer=opengl|cairo|agg</code>
- </td><td align="left">Enable support for the a graphics backend.
Currently
+ </td><td align="left">Enable support for a graphics backend. Currently
only <code class="option">opengl</code> and
- <code class="option">agg</code> work sufficiently. OpenGL is
- used when you have hardware accelerated graphics. AGG i
- used when you do not have hardware accelerated
- graphics. Typically most desktop machines have OpenGL
- support, and most embedded systems do not. OpenGl is the
- default when building Gnash, although the quality of AGG's
- rendering is currently superior to OpenGL.</td></tr><tr><td
align="left"><code class="option">--enable-sdk-install</code>
+ <code class="option">agg</code> work sufficiently. Use OpenGL
+ when you have hardware accelerated graphics. Use AGG
+ when you do not have hardware accelerated
+ graphics or when you are building for a wide audience.
+ Typically most desktop machines have OpenGL
+ support, and most embedded systems do not. AGG is the
+ default when building Gnash, although the speed of OpenGL's
+ rendering is currently superior to AGG.</td></tr><tr><td
align="left"><code class="option">--enable-sdk-install</code>
</td><td align="left">Enable installing the libraries and headers as
an SDK.
</td></tr><tr><td align="left"><code
class="option">--disable-shared</code>
</td><td align="left">Enable installing the shared libraries and
headers.
@@ -1101,14 +1102,15 @@
./configure -target=arm-unknown-linux-gnu --prefix=/usr/arm \
--host=arm-unknown-linux-gnu --build=i686-pc-linux-gnu --disable-plugin
</pre><p>
- </p></div></div></div><div class="chapter" lang="en"><div
class="titlepage"><div><div><h2 class="title"><a name="internals"></a>Chapter
3. Software Internals</h2></div></div></div><div class="toc"><p><b>Table of
Contents</b></p><dl><dt><span class="sect1"><a href="#tour">A Tour of
Gnash</a></span></dt><dd><dl><dt><span class="sect2"><a
href="#The%20Libraries">The Libraries</a></span></dt><dt><span class="sect2"><a
href="#apps">The Applications</a></span></dt><dt><span class="sect2"><a
href="#plugin">The Plugin</a></span></dt><dt><span class="sect2"><a
href="#logging">The Debug Logging System</a></span></dt></dl></dd><dt><span
class="sect1"><a href="#soundhandlers">Sound handling in
Gnash</a></span></dt><dd><dl><dt><span class="sect2"><a
href="#soundtypes">Sound types</a></span></dt><dt><span class="sect2"><a
href="#soundparsing">Sound parsing</a></span></dt><dt><span class="sect2"><a
href="#soundplayback">Sound playback</a></span></dt><dt><span class="sect2"><a
href="#sdlsound">The SDL sound backend</a></span></dt><dt><span
class="sect2"><a href="#gstreamer">The Gstreamer
backend</a></span></dt><dt><span class="sect2"><a href="#audio-future">Future
audio backends</a></span></dt><dt><span class="sect2"><a
href="#gstreamer-details">Detailed description of the Gstreamer
backend</a></span></dt></dl></dd><dt><span class="sect1"><a
href="#testing">Testing </a></span></dt><dd><dl><dt><span class="sect2"><a
href="#testtools">Testing Tools</a></span></dt><dt><span class="sect2"><a
href="#testcases">Test Cases</a></span></dt><dt><span class="sect2"><a
href="#writeastests">Writing ActionScript Tests</a></span></dt><dt><span
class="sect2"><a href="#writemingtests">Writing Ming-based self-contained SWF
tests</a></span></dt><dt><span class="sect2"><a
href="#writing_dejagnu_so_tests">Writing self-contained SWF tests with other
compilers</a></span></dt><dt><span class="sect2"><a
href="#writing_test_runners">Writing Test
Runners</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="tour"></a>A Tour of Gnash</h2></div></div></div><p>
+ </p></div></div></div><div class="chapter" lang="en"><div
class="titlepage"><div><div><h2 class="title"><a name="internals"></a>Chapter
3. Software Internals</h2></div></div></div><div class="toc"><p><b>Table of
Contents</b></p><dl><dt><span class="sect1"><a href="#tour">A Tour of
Gnash</a></span></dt><dd><dl><dt><span class="sect2"><a
href="#The%20Libraries">The Libraries</a></span></dt><dt><span class="sect2"><a
href="#apps">The Applications</a></span></dt><dt><span class="sect2"><a
href="#plugin">The Plugin</a></span></dt><dt><span class="sect2"><a
href="#logging">The Message Logging System</a></span></dt></dl></dd><dt><span
class="sect1"><a href="#soundhandlers">Sound handling in
Gnash</a></span></dt><dd><dl><dt><span class="sect2"><a
href="#soundtypes">Sound types</a></span></dt><dt><span class="sect2"><a
href="#soundparsing">Sound parsing</a></span></dt><dt><span class="sect2"><a
href="#soundplayback">Sound playback</a></span></dt><dt><span class="sect2"><a
href="#sdlsound">The SDL sound backend</a></span></dt><dt><span
class="sect2"><a href="#gstreamer">The Gstreamer
backend</a></span></dt><dt><span class="sect2"><a href="#audio-future">Future
audio backends</a></span></dt><dt><span class="sect2"><a
href="#gstreamer-details">Detailed description of the Gstreamer
backend</a></span></dt></dl></dd><dt><span class="sect1"><a
href="#testing">Testing </a></span></dt><dd><dl><dt><span class="sect2"><a
href="#testtools">Testing Tools</a></span></dt><dt><span class="sect2"><a
href="#testcases">Test Cases</a></span></dt><dt><span class="sect2"><a
href="#writeastests">Writing ActionScript Tests</a></span></dt><dt><span
class="sect2"><a href="#writemingtests">Writing Ming-based self-contained SWF
tests</a></span></dt><dt><span class="sect2"><a
href="#writing_dejagnu_so_tests">Writing self-contained SWF tests with other
compilers</a></span></dt><dt><span class="sect2"><a
href="#writing_test_runners">Writing Test
Runners</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="tour"></a>A Tour of Gnash</h2></div></div></div><p>
The top level of Gnash has several libraries, <span
class="emphasis"><em>libgnashbase</em></span>,
- <span class="emphasis"><em>libgnashgeo</em></span>, <span
class="emphasis"><em>libgnashserver</em></span>,
- <span class="emphasis"><em>libgnashasobjs</em></span> and
+ <span class="emphasis"><em>libgnashserver</em></span>,
+ <span class="emphasis"><em>libgnashmedia</em></span>,
+ <span class="emphasis"><em>libgnashamf</em></span> and
<span class="emphasis"><em>libgnashbackend</em></span>. There are
several utility programs
included for debug parsing and processing of Flash movie files,
- and other useful utilitis for examining local Shared Objects and
- sniffingh LocalConnections.
+ and other useful utilities for examining local Shared Objects and
+ sniffing LocalConnections.
</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3
class="title"><a name="The%20Libraries"></a>The
Libraries</h3></div></div></div><div class="sect3" lang="en"><div
class="titlepage"><div><div><h4 class="title"><a
name="libbase"></a>libgnashbase</h4></div></div></div><p>
Libgnashbase contains support classes used by the rest of the
code.This library has no dependencies on any of the other
@@ -1117,19 +1119,18 @@
<span class="application">Gnash</span> makes heavy use of smart
pointers, so memory allocations
are freed up automatically by the interpreter. Both STL and
Boost smart pointers are used.
- </p></div><div class="sect3" lang="en"><div
class="titlepage"><div><div><h4 class="title"><a
name="libgnashgeo"></a>libgnashgeo</h4></div></div></div><p>
- Libgnashgeo contains code for device independent graphics routines.
- </p></div><div class="sect3" lang="en"><div
class="titlepage"><div><div><h4 class="title"><a
name="libgnashgui"></a>libgnashgui</h4></div></div></div><p>
- Libgnashgui contains code for a portable GUI class that
- supports using GTK2, a framebuffer, SDL, or KDE, FLTK, or Aqua.
</p></div><div class="sect3" lang="en"><div
class="titlepage"><div><div><h4 class="title"><a
name="libgnashserver"></a>libgnashserver</h4></div></div></div><p>
Libgnashserver is the guts of the interpreter itself. This is where
the main code for the interpreter lives. Includes in
libserver are the two support libraries for the parser and
the core of the virtual machine.
- </p></div><div class="sect3" lang="en"><div
class="titlepage"><div><div><h4 class="title"><a
name="libgnashasobjs"></a>libgnashasobjs</h4></div></div></div><p>
- Libgnashasobjs contains all the ActionScript classes used by
- the interpreter.
+ </p></div><div class="sect3" lang="en"><div
class="titlepage"><div><div><h4 class="title"><a
name="libgnashmedia"></a>libgnashmedia</h4></div></div></div><p>
+ Libgnashmedia handles Gnash's audio and video capabilities,
+ dealing with streamed video and sound as well as decoding
+ embedded media frames. Besides the standard Flash formats
+ FLV, MPEG4, Nellymoser, ADPCM, MP3 and RAW, <span
class="application">Gnash</span> can
+ decode other formats supports by gstreamer or ffmpeg,
+ including the free OGG container and free codecs.
</p></div><div class="sect3" lang="en"><div
class="titlepage"><div><div><h4 class="title"><a
name="libgnashamf"></a>libgnashamf</h4></div></div></div><p>
AMF is the data format used internally by SWF files. This is
Gnash's support library to handle AMF data. This is used by
@@ -1146,11 +1147,11 @@
Libklashpart is the Konqueror plugin.
</p></div></div><div class="sect2" lang="en"><div
class="titlepage"><div><div><h3 class="title"><a name="apps"></a>The
Applications</h3></div></div></div><p>
There are currently a few standalone programs in Gnash,
- which serve to either assist with Gnash development or play flash
+ which serve either to assist with Gnash development or to play flash
movies.
</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4
class="title"><a name="Gnash"></a>The Standalone
Player</h4></div></div></div><p>
- This is the standalone OpenGL back-end used to play
- movies. There are several command-line options and keyboard
+ This is the standalone OpenGL backend used to play
+ movies. There are several command line options and keyboard
control keys used by Gnash.
</p></div><div class="sect3" lang="en"><div
class="titlepage"><div><div><h4 class="title"><a
name="processor"></a>Gprocessor</h4></div></div></div><p>
Gprocessor is used to print out the actions (using the -va
@@ -1168,12 +1169,12 @@
</p></div></div><div class="sect2" lang="en"><div
class="titlepage"><div><div><h3 class="title"><a name="plugin"></a>The
Plugin</h3></div></div></div><p>
The plugin is designed to work within Mozilla or Firefox,
although there is Konqueror support as well. The plugin uses
- the Mozilla NSAPI plugin API to be cross platform, and is
+ the Mozilla plugin API (NPAPI) to be cross platform, and is
portable, as well as being well integrated into Mozilla based
browsers.
- </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4
class="title"><a name="pluginstatus"></a>Current
Status</h4></div></div></div><p>
- As of March 30, 2006, the plugin works! This works in a
- fashion similar to MozPlugger in that the standalone player
+ </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4
class="title"><a name="pluginstatus"></a>Current
Implementation</h4></div></div></div><p>
+ The plugin works in a
+ fashion similar to MozPlugger: the standalone player
is used instead of using a thread. This gets around the
issue of having to maintain a separate player to support the
plugin. It also gets around the other issues that Gnash
@@ -1269,111 +1270,112 @@
use the <span class="emphasis"><em>--enable-klash</em></span> option
when
configuring. Other than installing, there is nothing else
that needs to be done to install Klash.
- </p></div></div><div class="sect2" lang="en"><div
class="titlepage"><div><div><h3 class="title"><a name="logging"></a>The Debug
Logging System</h3></div></div></div><p>
- Gnash supports a debug logging system which supports both C and C++
- natively. This means you can use both <span
class="emphasis"><em>printf()</em></span> style
- debug messages and C++ <span class="emphasis"><em>iostreams</em></span>
style, where you can
- print C++ objects directly as you would when using
- <span class="emphasis"><em>cout</em></span>.
- </p><p>
- In the beginning, Gnash only supported the C API for debug
- logging, so it is the most heavily used in Gnash. This API was used in
- the <span class="emphasis"><em>log_msg()</em></span> and <span
class="emphasis"><em>log_error()</em></span> functions,
- and used a callback to set them up.
+ </p></div></div><div class="sect2" lang="en"><div
class="titlepage"><div><div><h3 class="title"><a name="logging"></a>The Message
Logging System</h3></div></div></div><p>
+ <span class="application">Gnash</span>'s common message logging system
uses a <span class="emphasis"><em>printf()</em></span>
+ style format. Despite the C-like appearance, however, <span
class="application">Gnash</span>'s LogFile class
+ by default does not use <span class="emphasis"><em>printf()</em></span>
for formatting the
+ messages at all.
+ </p><p>
+ All logging calls are converted using templated functions to use
boost::format.
+ This uses a similar syntax to printf(), but additionally guarantees
type-safety
+ and allows more advanced substition using positional identifiers besides
the
+ traditional printf() type identifiers. The conversion templates mean that
+ the logging API remains exactly the same, regardless of which method is
+ used to format the log output.
+ </p><p>
+ The templates for conversion are generated using Boost.Preprocessor.
Currently,
+ they allow for a maximum of 16 arguments (more than enough for all current
+ usage), but that can be expanded or reduced by changing
+ <span class="emphasis"><em>#define ARG_NUMBER</em></span> in <span
class="emphasis"><em>libbase/log.h</em></span>.
</p><p>
- If a filename is not specified at object construction time, a
+ If a filename is not specified before the log file is needed, a
default name of <span class="emphasis"><em>gnash-dbg.log</em></span> is
used. If Gnash is
started from the command line, the debug log will be created in
the current directory. When executing Gnash from a launcher under
<span class="emphasis"><em>GNOME</em></span> or <span
class="emphasis"><em>KDE</em></span> the debug file goes in your
- home directory, since that's considered the current directory.
- </p><p>
- There is common functionality between using the C or C++
- API. Optional output is based on flags that can be set or
- unset. Multiple levels of verbosity are supported, so you can get
- more output by supplying multiple <span
class="emphasis"><em>-v</em></span> options on the
- command line. You can also disable the creation of the debug log.
- </p><p>
- Currently the use of the C++ API for logging is discouraged, do to
- performance issues.and the generic log_msg() has been replaced by
- more spcific function calls to allow more control of what gets
- displayed and logged.
- </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4
class="title"><a name="capi"></a>Logging System C API</h4></div></div></div><p>
- These functions are clones of the originals as they were used
- for Gnash. These function the same as always except output can
- be logged to disk now as well. These currently print no
- timestamp with the output, which is the older functionality. As
- these functions are implemented on top of the C++ API now, they
- can be used without corrupting the output buffers.
- </p><div class="variablelist"><dl><dt><span class="term">log_error(const
char* fmt, ...)</span></dt><dd><p>
- Display an error message if verbose output is enabled. By
- default the error messages are always written to the disk
- file, but optionally displayed in the terminal.
- </p></dd><dt><span class="term">void log_unimpl</span></dt><dd><p>
+ home directory, since that's considered the current directory. A file name
+ can be specified using either <span
class="emphasis"><em>gnashrc</em></span> or a
+ call to the LogFile instance itself.
+ </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4
class="title"><a name="api"></a>Logging System API</h4></div></div></div><p>
+ <span class="application">Gnash</span> provides 9 specialized logging
calls, each using the <span class="emphasis"><em>printf()</em></span>-style
+ call similar to this:
+ </p><pre class="programlisting">log_error(const char* fmt,
...)</pre><p>
+ The different
+ calls and their purposes are described below. The output to stdout and
to disk
+ are always identical, although writing the log to disk can be
separately disabled.
+ </p><div class="variablelist"><dl><dt><span
class="term">log_error</span></dt><dd><p>
+ Display an error message if verbose output is enabled. This is
+ always printed at a verbosity level of 1 or more.
+ </p></dd><dt><span class="term">log_unimpl</span></dt><dd><p>
Displays a warning to the user about missing Gnash features.
We expect all calls to this function to disappear over time, as we
- implement those features of Flash.
- </p></dd><dt><span class="term">void log_trace</span></dt><dd><p>
- Used only for explicit user traces
- </p></dd><dt><span class="term">void log_debug</span></dt><dd><p>
- Logs debug information.
- </p></dd><dt><span class="term">void log_action</span></dt><dd><p>
+ implement those features of Flash. This is
+ always printed at a verbosity level of 1 or more.
+ </p></dd><dt><span class="term">log_trace</span></dt><dd><p>
+ Used only for the output of the ActionScript <span
class="emphasis"><em>trace()</em></span>
+ function. This is
+ always printed at a verbosity level of 1 or more.
+ </p></dd><dt><span class="term">log_debug</span></dt><dd><p>
+ Logs debug information. This is printed at a verbosity level of 2
or more.
+ </p></dd><dt><span class="term">log_action</span></dt><dd><p>
Log action execution information. Wrap all calls to this
function (and other related statements) into an
IF_VERBOSE_ACTION macro, so to allow completely removing
all the overhead at compile time and reduce it at
- runtime.
- </p></dd><dt><span class="term">void log_parse</span></dt><dd><p>
+ runtime. This is printed at a verbosity level of 1 or more
+ only if action logging is enabled.
+ </p></dd><dt><span class="term">log_parse</span></dt><dd><p>
Log SWF parsing Wrap all calls to this function (and
other related statements) into an IF_VERBOSE_PARSE macro,
so to allow completely removing all the overhead at
- compile time and reduce it at runtime.
- </p></dd><dt><span class="term">void log_security</span></dt><dd><p>
- Display a message with security related information.
- </p></dd><dt><span class="term">void log_swferror</span></dt><dd><p>
+ compile time and reduce it at runtime. This is printed at a
+ verbosity level of 1 or more
+ only if parser logging is enabled.
+ </p></dd><dt><span class="term">log_security</span></dt><dd><p>
+ Display a message with security related information. This is always
+ printed at a verbosity level of 1 or more.
+ </p></dd><dt><span class="term">log_swferror</span></dt><dd><p>
This indicates an error in how the binary SWF file was
constructed, i.e.probably a bug in the tools used to build
the SWF file. Wrap all calls to this function (and other
related statements) into an IF_VERBOSE_MALFORMED_SWF
macro, so to allow completely removing all the overhead at
+ compile time and reduce it at runtime. This is printed at a
+ verbosity level of 1 or more
+ only if malformed SWF logging is enabled.
+ </p></dd><dt><span class="term">void log_aserror</span></dt><dd><p>
+ This indicates an erroneous actionscript request such as
+ an incorrect number of arguments or an invalid argument.
+ Wrap all calls to this function (and other
+ related statements) into an IF_VERBOSE_ASCODING_ERRORS
+ macro, so to allow completely removing all the overhead at
compile time and reduce it at runtime.
- </p></dd><dt><span class="term">log_warning(const char* fmt,
...)</span></dt><dd><p>
- Display a warning message if verbose output is enabled. By
- default the error messages are always written to the disk
- file, but optionally displayed in the terminal.
- </p></dd></dl></div></div><div class="sect3" lang="en"><div
class="titlepage"><div><div><h4 class="title"><a name="cppapi"></a>Logging
System C++ API</h4></div></div></div><p>
- This is the new C++ streams based API that can be used to print
- C++ objects natively. All output lines are timestamped.
- </p><p>
- There are two macros used for program tracing. these can be used
- in both C or C++ code with one little difference. Since C
- doesn't have destructors, you must call
- <span class="emphasis"><em>GNASH_REPORT_RETURN</em></span> at the end of
a function to
- display the function returning message.
- </p><div class="variablelist"><dl><dt><span
class="term">GNASH_REPORT_FUNCTION;</span></dt><dd><p>
- When this is included in a C++ method, a message is
- printed when entering and exiting this method by hooking
- into the constructor and destructor. These are always
- written to the disk file, but optionally written to the
- screen only at the highest levels of verbosity.
- </p></dd><dt><span
class="term">GNASH_REPORT_RETURN;</span></dt><dd><p>
- This is used by C functions to print the returning from
- function debug message. For C++, this macro is executed
- automatically by the destructor.
- </p></dd></dl></div><p>
- This is the main API for the logging system. By default
- everything is setup to write to the default
- <span class="emphasis"><em>gnash-dbg.log</em></span> file whenever a
verbose option is
- supplied. Optionally it is possible to open a log file with a
- specified name, allowing multiple output files.
- </p><div class="variablelist"><dl><dt><span
class="term">closeLog(void)</span></dt><dd><p>
+ This is printed at a
+ verbosity level of 1 or more
+ only if AS coding error logging is enabled.
+ </p></dd></dl></div></div><div class="sect3" lang="en"><div
class="titlepage"><div><div><h4 class="title"><a name="logfileinstance"></a>The
LogFile Instance</h4></div></div></div><p>
+ This is the main API for initializing and manipulating the logging
output.
+ By default, the log will be written to <span
class="emphasis"><em>gnash-dbg.log</em></span>
+ file whenever a verbose option is
+ supplied.
+ </p><div class="variablelist"><dl><dt><span
class="term">getDefaultInstance()</span></dt><dd><p>
+ This allows the construction of a LogFile on the first call, so
+ ensuring that it the logfile is always initialised before use.
+ It is the only way to access a LogFile instance. The logfile
+ itself is never opened until it is needed.
+ </p></dd><dt><span class="term">setLogFilename(const std::string&
filename)</span></dt><dd><p>
+ Use this to set a different name for the disk-based log file.
+ This setting can be overridden by a directive in gnashrc. If the
+ log file is already open, a call to setLogFilename() will close it;
+ a file with the new name will be opened when it is next needed.
+ </p></dd><dt><span class="term">closeLog()</span></dt><dd><p>
Close a debug log. The disk file remains.
- </p></dd><dt><span class="term">removeLog(void)</span></dt><dd><p>
+ </p></dd><dt><span class="term">removeLog()</span></dt><dd><p>
Delete the debug log file from disk.
- </p></dd><dt><span class="term">setVerbosity(void)</span></dt><dd><p>
+ </p></dd><dt><span class="term">setVerbosity()</span></dt><dd><p>
Increment the verbosity level.
- </p></dd><dt><span class="term">setVerbosity(int)</span></dt><dd><p>
- Set the verbosity level.
+ </p></dd><dt><span class="term">setVerbosity(int
level)</span></dt><dd><p>
+ Set the verbosity level to a specified level.
</p></dd><dt><span class="term">setStamp(bool flag)</span></dt><dd><p>
If <span class="emphasis"><em>flag</em></span> is <span
class="emphasis"><em>true</em></span>, then print a
timestamp prefixed to every output line. If
@@ -2184,7 +2186,7 @@
</td></tr></tbody></table></div><p>
</p></div></div></div></div><div class="chapter" lang="en"><div
class="titlepage"><div><div><h2 class="title"><a name="bugreport"></a>Chapter
5. Reporting Bugs</h2></div></div></div><div class="toc"><p><b>Table of
Contents</b></p><dl><dt><span class="sect1"><a href="#bugstep_package">Get a
Fresh Binary Package</a></span></dt><dt><span class="sect1"><a
href="#bugstep_search">Determine if the bug was previously
reported</a></span></dt><dt><span class="sect1"><a
href="#bugstep_guidelines">Review the bug writing
guidelines</a></span></dt><dt><span class="sect1"><a
href="#bugstep_file">Filing a bug report</a></span></dt></dl></div><p>
The Gnash project relies on the community of Gnash users to test
- the player, feedback is critical to any successful project. Not
+ the player. Feedback is critical to any successful project. Not
only does it let us know that people use Gnash, but it helps us
understand the community's needs. Gnash uses a bug tracker on
<a class="ulink" href="http://savannah.gnu.org";
target="_top">http://savannah.gnu.org</a> to manage these reports.
@@ -2192,8 +2194,8 @@
When filing a report, please follow the guidelines below. The better
your bug report is, the easier it will be for the developers to
address the issue. Bug reports without enough information will
- initially be asked to provide this information anyway. Adding
- critical details, like the Operating System you are on, it's
+ be asked to provide this information anyway. Adding
+ critical details, like the Operating System you are on, its
version, and any relevant error messages from Gnash that you get.
</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2
class="title" style="clear: both"><a name="bugstep_package"></a>Get a Fresh
Binary Package</h2></div></div></div><p>
For starters, it's a good idea to obtain a copy of the latest
@@ -2201,8 +2203,8 @@
Gnash build infrastructure allows the automated building of
binary packages. Often the version of Gnash as packaged by a
GNU/Linux or BSD distribution is based on the last official
- release, which could be months out of date. It is helpful if
- this is the case to try a newer packaged build of Gnash.
+ release, which could be months out of date. It helps us, if
+ this is the case, for you to try a newer packaged build of Gnash.
</p><p>
You can get a fresh binary package of Gnash, as well as recent
source packages from
@@ -3113,10 +3115,10 @@
</p></div></div><div class="chapter" lang="en"><div
class="titlepage"><div><div><h2 class="title"><a name="authors"></a>Chapter 9.
Authors</h2></div></div></div><p>
<span class="application">Gnash</span> is maintained by Rob Savoye.
Other active developers
are: Sandro Santilli, Bastiaan Jacques, Udo Giacomozzi, Chad
- Musick, Benjamin Wolsey, and Zou Lunkai. Please send all
- comments and suggestions to <code class="email"><<a class="email"
href="mailto:address@hidden";>address@hidden
- </a>></code>. Past and sometimes current developers are Tomas
- Groth and Markus Gothe.
+ Musick, Benjamin Wolsey, Zou Lunkai, and Russ Nelson. Please
+ send all comments and suggestions to
+ <code class="email"><<a class="email"
href="mailto:address@hidden";>address@hidden</a>></code>. Past and sometimes
current
+ developers are Tomas Groth and Markus Gothe.
</p><p>
<span class="application">Gnash</span> was initially derived from
<span class="application">GameSWF</span>.
<span class="application">GameSWF</span> is maintained by
Index: doc/C/preformatted/gnashuser.html.in
===================================================================
RCS file: /sources/gnash/gnash/doc/C/preformatted/gnashuser.html.in,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- doc/C/preformatted/gnashuser.html.in 2 Mar 2008 17:54:16 -0000
1.2
+++ doc/C/preformatted/gnashuser.html.in 16 May 2008 13:23:43 -0000
1.3
@@ -1,5 +1,5 @@
<html><head><meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"><title>Gnash User Manual</title><meta name="generator"
content="DocBook XSL Stylesheets V1.73.2"></head><body bgcolor="white"
text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book"
lang="en"><div class="titlepage"><div><div><h1 class="title"><a
name="index"></a>Gnash User Manual</h1></div><div><p class="releaseinfo">
- This manual describes version 0.8.2 of Gnash.
+ This manual describes version 0.8.3 of Gnash.
</p></div><div><p class="copyright">Copyright © 2005, 2006, 2007, 2008
Free Software Foundation</p></div><div><div class="legalnotice"><a
name="legalnotice"></a><p>
Permission is granted to copy, distribute and/or modify this document
under the terms of the <a class="link" href="#fdl" title="Appendix A. GNU
Free Documentation License"><em class="citetitle">GNU
@@ -13,64 +13,64 @@
<p class="author">Rob Savoye
<code class="email"><<a class="email"
href="mailto:address@hidden";>address@hidden</a>></code>
The end user parts of the manual have been pulled out of
- the original version of the manual, and rewritten.
+ the original version of the manual and rewritten.
</p>
<p class="publisher">Open Media Now! Foundation</p>
- </td></tr></table></div></div></div><hr></div><div class="toc"><p><b>Table
of Contents</b></p><dl><dt><span class="chapter"><a href="#intro">1.
Introduction</a></span></dt><dd><dl><dt><span class="sect1"><a
href="#audience">Audience</a></span></dt><dt><span class="sect1"><a
href="#runs-on">What Is Supported ?</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#usage">2. Using <span
class="application">Gnash</span></a></span></dt><dd><dl><dt><span
class="sect1"><a href="#options"><span class="application">Gnash</span> Command
Line Options</a></span></dt><dt><span class="sect1"><a href="#keys"><span
class="application">Gnash</span> Interactive Control
Keys</a></span></dt><dt><span class="sect1"><a href="#gnashrc">User
Configuration File</a></span></dt></dl></dd><dt><span class="chapter"><a
href="#build">3. Installing and Configuring
Gnash</a></span></dt><dd><dl><dt><span class="sect1"><a
href="#requirements">Requirements</a></span></dt><dd><dl><dt><span
class="sect2"><a href="#hardware">Hardware
Requirements</a></span></dt><dt><span class="sect2"><a
href="#software">Software Requirements</a></span></dt></dl></dd><dt><span
class="sect1"><a href="#downloading">Downloading
Gnash</a></span></dt><dd><dl><dt><span class="sect2"><a
href="#gettingsource">Getting the Source</a></span></dt><dt><span
class="sect2"><a href="#getcodecs">Getting Codec
Support</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a
href="#bugreport">4. Reporting Bugs</a></span></dt><dd><dl><dt><span
class="sect1"><a href="#bugstep_package">Get a Fresh Binary
Package</a></span></dt><dt><span class="sect1"><a
href="#bugstep_search">Determine if the bug was previously
reported</a></span></dt><dt><span class="sect1"><a
href="#bugstep_guidelines">Review the bug writing
guidelines</a></span></dt><dt><span class="sect1"><a
href="#bugstep_file">Filing a bug report</a></span></dt></dl></dd><dt><span
class="glossary"><a href="#glossary">Glossary</a></span></dt><dt><span
class="chapter"><a href="#authors">5. Authors</a></span></dt><dt><span
class="appendix"><a href="#fdl">A. GNU Free Documentation
License</a></span></dt><dd><dl><dt><span class="sect1"><a
href="#fdl-preamble">0. PREAMBLE</a></span></dt><dt><span class="sect1"><a
href="#fdl-section1">1. APPLICABILITY AND DEFINITIONS</a></span></dt><dt><span
class="sect1"><a href="#fdl-section2">2. VERBATIM
COPYING</a></span></dt><dt><span class="sect1"><a href="#fdl-section3">3.
COPYING IN QUANTITY</a></span></dt><dt><span class="sect1"><a
href="#fdl-section4">4. MODIFICATIONS</a></span></dt><dt><span class="sect1"><a
href="#fdl-section5">5. COMBINING DOCUMENTS</a></span></dt><dt><span
class="sect1"><a href="#fdl-section6">6. COLLECTIONS OF
DOCUMENTS</a></span></dt><dt><span class="sect1"><a href="#fdl-section7">7.
AGGREGATION WITH INDEPENDENT WORKS</a></span></dt><dt><span class="sect1"><a
href="#fdl-section8">8. TRANSLATION</a></span></dt><dt><span class="sect1"><a
href="#fdl-section9">9. TERMINATION</a></span></dt><dt><span class="sect1"><a
href="#fdl-section10">10. FUTURE REVISIONS OF THIS
LICENSE</a></span></dt><dt><span class="sect1"><a
href="#fdl-using">Addendum</a></span></dt></dl></dd></dl></div><div
class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>2.1. <a
href="#tb-command-line-options">Gnash Command Line Options</a></dt><dt>2.2. <a
href="#tb-control-keys">Gnash Interactive Control Keys</a></dt><dt>2.3. <a
href="#tb-config-variables">User Configuration Variables</a></dt><dt>3.1. <a
href="#tb-os-cpu">Build Matrix</a></dt></dl></div><div class="chapter"
lang="en"><div class="titlepage"><div><div><h2 class="title"><a
name="intro"></a>Chapter 1. Introduction</h2></div></div></div><div
class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a
href="#audience">Audience</a></span></dt><dt><span class="sect1"><a
href="#runs-on">What Is Supported ?</a></span></dt></dl></div><p>
+ </td></tr></table></div></div></div><hr></div><div class="toc"><p><b>Table
of Contents</b></p><dl><dt><span class="chapter"><a href="#intro">1.
Introduction</a></span></dt><dd><dl><dt><span class="sect1"><a
href="#audience">Audience</a></span></dt><dt><span class="sect1"><a
href="#runs-on">What Is Supported?</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#usage">2. Using <span
class="application">Gnash</span></a></span></dt><dd><dl><dt><span
class="sect1"><a href="#options"><span class="application">Gnash</span> Command
Line Options</a></span></dt><dt><span class="sect1"><a href="#keys"><span
class="application">Gnash</span> Interactive Control
Keys</a></span></dt><dt><span class="sect1"><a href="#gnashrc">User
Configuration File</a></span></dt></dl></dd><dt><span class="chapter"><a
href="#build">3. Installing and Configuring
Gnash</a></span></dt><dd><dl><dt><span class="sect1"><a
href="#requirements">Requirements</a></span></dt><dd><dl><dt><span
class="sect2"><a href="#hardware">Hardware
Requirements</a></span></dt><dt><span class="sect2"><a
href="#software">Software Requirements</a></span></dt></dl></dd><dt><span
class="sect1"><a href="#downloading">Downloading
Gnash</a></span></dt><dd><dl><dt><span class="sect2"><a
href="#gettingsource">Getting the Source</a></span></dt><dt><span
class="sect2"><a href="#getcodecs">Getting Codec
Support</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a
href="#bugreport">4. Reporting Bugs</a></span></dt><dd><dl><dt><span
class="sect1"><a href="#bugstep_package">Get a Fresh Binary
Package</a></span></dt><dt><span class="sect1"><a
href="#bugstep_search">Determine if the bug was previously
reported</a></span></dt><dt><span class="sect1"><a
href="#bugstep_guidelines">Review the bug writing
guidelines</a></span></dt><dt><span class="sect1"><a
href="#bugstep_file">Filing a bug report</a></span></dt></dl></dd><dt><span
class="glossary"><a href="#glossary">Glossary</a></span></dt><dt><span
class="chapter"><a href="#authors">5. Authors</a></span></dt><dt><span
class="appendix"><a href="#fdl">A. GNU Free Documentation
License</a></span></dt><dd><dl><dt><span class="sect1"><a
href="#fdl-preamble">0. PREAMBLE</a></span></dt><dt><span class="sect1"><a
href="#fdl-section1">1. APPLICABILITY AND DEFINITIONS</a></span></dt><dt><span
class="sect1"><a href="#fdl-section2">2. VERBATIM
COPYING</a></span></dt><dt><span class="sect1"><a href="#fdl-section3">3.
COPYING IN QUANTITY</a></span></dt><dt><span class="sect1"><a
href="#fdl-section4">4. MODIFICATIONS</a></span></dt><dt><span class="sect1"><a
href="#fdl-section5">5. COMBINING DOCUMENTS</a></span></dt><dt><span
class="sect1"><a href="#fdl-section6">6. COLLECTIONS OF
DOCUMENTS</a></span></dt><dt><span class="sect1"><a href="#fdl-section7">7.
AGGREGATION WITH INDEPENDENT WORKS</a></span></dt><dt><span class="sect1"><a
href="#fdl-section8">8. TRANSLATION</a></span></dt><dt><span class="sect1"><a
href="#fdl-section9">9. TERMINATION</a></span></dt><dt><span class="sect1"><a
href="#fdl-section10">10. FUTURE REVISIONS OF THIS
LICENSE</a></span></dt><dt><span class="sect1"><a
href="#fdl-using">Addendum</a></span></dt></dl></dd></dl></div><div
class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>2.1. <a
href="#tb-command-line-options">Gnash Command Line Options</a></dt><dt>2.2. <a
href="#tb-control-keys">Gnash Interactive Control Keys</a></dt><dt>2.3. <a
href="#tb-config-variables">User Configuration Variables</a></dt><dt>3.1. <a
href="#tb-os-cpu">Build Matrix</a></dt></dl></div><div class="chapter"
lang="en"><div class="titlepage"><div><div><h2 class="title"><a
name="intro"></a>Chapter 1. Introduction</h2></div></div></div><div
class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a
href="#audience">Audience</a></span></dt><dt><span class="sect1"><a
href="#runs-on">What Is Supported?</a></span></dt></dl></div><p>
<span class="application">Gnash</span> is a free SWF movie player. It is
available as a
stand-alone application or as a plugin for several popular
web browsers. It supports playing media from a disk or streaming
over a network connection. Some popular video sharing sites like
- YouTube are supported from a wide vaariety of devices from
+ YouTube are supported on a wide variety of devices from
embedded ones to modern desktops.
</p><p>
<span class="application">Gnash</span> has a better focus on security,
allowing the user tight
control of all network or disk based I/O. Gnash also supports
- extending ActionScript by creating your own. You can write
+ extending ActionScript by creating your own classes. You can write
wrappers for any development library, and import them into the
- player much like perl or python does.
+ player much like Perl or Python does.
</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2
class="title" style="clear: both"><a
name="audience"></a>Audience</h2></div></div></div><p>
This manual is primarily focused on users interested in how to
get Gnash installed from a package, and basic usage as a web
browser plugin. For more technical details, please refer to the
Gnash Reference manual.
- </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="runs-on"></a>What Is Supported ?</h2></div></div></div><p>
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="runs-on"></a>What Is Supported?</h2></div></div></div><p>
Gnash is known to compile for most any POSIX and ANSI C++
conforming system if you have all the dependent libraries
- installed. Systems we test on, and which Gnash is know to
- run on are Ubuntu, Fedora, Debian, OpenBSD, NetBSD, FreeBSD,
+ installed. Systems we test on, and which Gnash is known to
+ run on are Ubuntu, Fedora, Debian, Mandriva, OpenBSD, NetBSD, FreeBSD,
Win32, and Darwin (OSX) primarily. Occasionally other platforms
are built, primarily by those distribution maintainers. This
includes BeOS, Haiku, Syllable, OS/2, Solaris, Slackware, and
Gentoo.
</p><p>
- Gnash is a capable of reading up to SWF v9 files and opcodes,
+ Gnash is capable of reading up to SWF v9 files and opcodes,
but primarily supports SWF v7, with better SWF v8 and v9
- support under heavy developement. With the 0.8.2 release,
+ support under heavy development. With the 0.8.2 release,
Gnash includes initial parser support for SWF v8 and v9.
Not all ActionScript 2 classes are implemented yet, but all of the
most heavily used ones are. Many ActionScript 2 classes are
partially implemented; there is support for all of the
commonly used methods of each class.
</p><p>
- Gnash has implemented about 80% of ActionScript v. 2.0, and has
- begun implementing ActionScript v. 3.0. Gnash supports the
- majority of Flash opcodes up to SWF version 9, and a wide
- sampling of ActionScript classes for SWF version 8.
+ Gnash has implemented about 80% of ActionScript v2.0, and has
+ begun implementing ActionScript v3.0. Gnash supports the
+ majority of Flash opcodes up to SWF v9, and a wide
+ sampling of ActionScript classes for SWF v8.
</p><p>
- As ActionsScript 3 is a more developed version of
+ As ActionScript 3 is a more developed version of
ActionScript 2, many of the same classes work for
both. Support has been added to Gnash's ActionScript library
to support the new ActionScript 3 filters, which get applied
- to every class. Implementing ActionScript clases is often the
+ to every class. Implementing ActionScript classes is often the
easiest way for new Gnash developers to make a contribution
- without a deep internal knpowledge of Gnash.
+ without a deep internal knowledge of Gnash.
</p><p>
Gnash has included video support since early 2007, but this is
- an every changing field of reverse engineering. Many of the
+ an ever changing field of reverse engineering. Many of the
popular video sharing sites use SWF v8 or v9, which Gnash
- still has imperfect support for. This is improving all the
+ supports imperfectly. This is improving all the
time, so often builds from a development snapshot will work
when using the older release packaged in your distribution
doesn't. You can find daily snapshots of the latest CVS tree
@@ -84,26 +84,26 @@
in a SWF file. Ffmpeg contains the codecs used by the current
SWF defintion, FLV, VP6 (ON2), H.263, H.264, and MP3.
</p></div></div><div class="chapter" lang="en"><div
class="titlepage"><div><div><h2 class="title"><a name="usage"></a>Chapter 2.
Using <span class="application">Gnash</span></h2></div></div></div><div
class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a
href="#options"><span class="application">Gnash</span> Command Line
Options</a></span></dt><dt><span class="sect1"><a href="#keys"><span
class="application">Gnash</span> Interactive Control
Keys</a></span></dt><dt><span class="sect1"><a href="#gnashrc">User
Configuration File</a></span></dt></dl></div><p>
- When used as a standalone player, you can play any Flash file from
+ When used as a standalone player, you can play any SWF file from
the command line by entering a command of the format:
</p><pre class="programlisting">
gnash <em class="replaceable"><code><option>
<flashfile.swf></code></em>
</pre><p>
- The only required argument is the name (and location)of the file
+ The only required argument is the name (and location) of the file
to be played.
</p><p>
The available options are listed in the following section, or you
may view them in the terminal window by executing the following at
the command line:
</p><pre class="programlisting">
- gnash --help |less
+ gnash --help | less
</pre><p>
</p><p>
- The source code download of <span class="application">Gnash</span>
includes several example .SWF
+ The source code download of <span class="application">Gnash</span>
includes several example SWF
files. They are located in the
<code class="filename">testsuite/samples/</code> directory of the <span
class="application">Gnash</span>
source directory. If you have installed <span
class="application">Gnash</span> correctly, issuing
- the a command similar to the following plays a short animation of
+ a command similar to the following plays a short animation of
a car swerving and crashing:
</p><pre class="programlisting">
gnash
@@ -122,16 +122,16 @@
Flash files are difficult to play.
</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2
class="title" style="clear: both"><a name="options"></a><span
class="application">Gnash</span> Command Line Options</h2></div></div></div><p>
No options are required for <span class="application">Gnash</span>'s
default behavior. However,
- there are many options that can be used to that behavior.
+ there are many options that can be used to change that behavior.
</p><p>
</p><pre class="programlisting">
gnash <em class="replaceable"><code><options></code></em>
<code class="filename">filename.swf</code>
</pre><p>
- </p><div class="table"><a name="tb-command-line-options"></a><p
class="title"><b>Table 2.1. Gnash Command Line Options</b></p><div
class="table-contents"><table summary="Gnash Command Line Options"
border="1"><colgroup><col><col></colgroup><thead><tr><th
align="left">Option</th><th
align="left">Function</th></tr></thead><tbody><tr><td align="left"><code
class="option">-h</code></td><td align="left">
+ </p><div class="table"><a name="tb-command-line-options"></a><p
class="title"><b>Table 2.1. Gnash Command Line Options</b></p><div
class="table-contents"><table summary="Gnash Command Line Options"
border="1"><colgroup><col><col></colgroup><thead><tr><th
align="left">Option</th><th
align="left">Function</th></tr></thead><tbody><tr><td align="left"><code
class="option">-h, --help</code></td><td align="left">
Print usage information.
</td></tr><tr><td align="left">
- <code class="option">-s factor</code>
+ <code class="option">-s, --scale</code> <em
class="replaceable"><code><factor></code></em>
</td><td align="left">
Scale the movie up/down by the specified factor.
</td></tr><tr><td align="left">
@@ -141,7 +141,7 @@
default, SDL traps all signals, but sometimes a core file
is desired to assist with debugging.
</td></tr><tr><td align="left">
- <code class="option">-d num</code>
+ <code class="option">-d, --delay</code> <em
class="replaceable"><code><num></code></em>
</td><td align="left">
Number of milliseconds to delay in main loop. The main
loop polls continuously with a delay to adjust how long
@@ -150,116 +150,117 @@
gets, and of course, the more iterations of the main
command loop.
</td></tr><tr><td align="left">
- <code class="option">-p</code>
+ <code class="option">-v, --verbose</code>
</td><td align="left">
- Run full speed (no sleep) and log frame rate.
+ Be verbose; i.e. print important messages to stdout.
</td></tr><tr><td align="left">
- <code class="option">-a</code>
+ <code class="option">-vv</code>
</td><td align="left">
- Enable Actionscript debugging.
- </td></tr><tr><td align="left">
- <code class="option">-v</code>
- </td><td align="left">
- Be verbose; i.e. print debug messages to stdout.
+ Be very verbose; i.e. also print debug messages to stdout.
</td></tr><tr><td align="left">
<code class="option">-va</code>
</td><td align="left">
- Be verbose about movie Actions.
+ Be verbose about movie actions (for ActionScript debugging). This
usually
+ generates very large amounts of text and will affect <span
class="application">Gnash</span>'s performance.
</td></tr><tr><td align="left">
<code class="option">-vp</code>
</td><td align="left">
- Be verbose about parsing the movie. Warning: this can
- generate a lot of text, and can affect the performance of
- the movie you are playing.
+ Be verbose about parsing the movie. This generates a fairly large
+ amount of text, and is likely to affect <span
class="application">Gnash</span>'s performance.
</td></tr><tr><td align="left">
- <code class="option">-ml bias</code>
+ <code class="option">-A</code> <em
class="replaceable"><code><file></code></em>
</td><td align="left">
- Specify the texture LOD bias (float, default is -1) This
- affects the fuzziness of small objects, especially small
- text.
+ Write the audio output to a wave format file.
</td></tr><tr><td align="left">
- <code class="option">-w</code>
+ <code class="option">-D</code> <em
class="replaceable"><code><file></code></em>
</td><td align="left">
- Write a debug log called gnash-dbg.log. This will
- record of all the debug messages whether they are printed
- to the screen or not.
+ Write the video output to a raw video file. This option
+ is only valid with dump-gnash.
</td></tr><tr><td align="left">
- <code class="option">-j</code>
+ <code class="option">-w, --writelog</code>
</td><td align="left">
- Specify the width of the window. This is mostly used
+ Write the log messages to disk using the file specified in the
gnashrc file.
+ The default is gnash-dbg.log.
+ </td></tr><tr><td align="left">
+ <code class="option">-j, --width</code> <em
class="replaceable"><code><num></code></em>
+ </td><td align="left">
+ Specify the starting width of the window. This is mostly used
only by the plugin.
</td></tr><tr><td align="left">
- <code class="option">-k</code>
+ <code class="option">-k, --height</code> <em
class="replaceable"><code><num></code></em>
</td><td align="left">
- Specify the height of the window. This is mostly used
+ Specify the starting height of the window. This is mostly used
only by the plugin.
</td></tr><tr><td align="left">
- <code class="option">-1</code>
+ <code class="option">-1, --once</code>
</td><td align="left">
- Play once; exit when/if movie reaches the last
- frame. This is the default.
+ Play once; exit if or when the movie reaches the last
+ frame.
</td></tr><tr><td align="left">
- <code class="option">-r [0|1|2|3]</code>
+ <code class="option">-r, --render-mode</code> <em
class="replaceable"><code><0|1|2|3></code></em>
</td><td align="left">
<div class="itemizedlist"><ul type="disc"><li><p>
0 disables rendering and sound (good for batch tests).
</p></li><li><p>
- 1 enables rendering and disables sound (default setting).
+ 1 enables rendering and disables sound.
</p></li><li><p>
2 enables sound and disables rendering.
</p></li><li><p>
- 3 enables rendering and sound.
+ 3 enables rendering and sound (default).
</p></li></ul></div>
</td></tr><tr><td align="left">
- <code class="option">-t sec</code>
+ <code class="option">-t, --timeout</code> <em
class="replaceable"><code><sec></code></em>
</td><td align="left">
Timeout and exit after the specified number of
seconds. This is useful for movies which repeat
themselves.
</td></tr><tr><td align="left">
- <code class="option">-g</code>
+ <code class="option">-g, --debugger</code>
</td><td align="left">
Start <span class="application">Gnash</span> with a Flash
debugger console so one can set
break points or watchpoints.
</td></tr><tr><td align="left">
- <code class="option">-x id</code>
+ <code class="option">-x, --xid</code> <em
class="replaceable"><code><ID></code></em>
</td><td align="left">
This specifies the X11 window ID to display
in; this is mainly used by plugins.
</td></tr><tr><td align="left">
- <code class="option">-b bits</code>
- </td><td align="left">
- Bit depth of output window (for example, 16 or 32). Appropriate
- bit depths depend on the renderer and GUI library used.
-
- </td></tr><tr><td align="left">
- <code class="option">-u url</code>
+ <code class="option">-u, --real-url</code> <em
class="replaceable"><code><URL></code></em>
</td><td align="left">
Set the _url member of the root movie. This is useful
when you download a movie and play it from a different
location. See also the -U switch.
</td></tr><tr><td align="left">
- <code class="option">-U baseurl</code>
+ <code class="option">-U, --base-url</code> <em
class="replaceable"><code><URL></code></em>
</td><td align="left">
Set base URL for this run. URLs are resolved relative to
- this base. If omitted defaults to the _url member of the
+ this base. If omitted or empty, it defaults to the _url member of
the
top-level movie (see the -u switch).
</td></tr><tr><td align="left">
- <code class="option">-P entrymeter</code>
+ <code class="option">-P, --param</code> <em
class="replaceable"><code><parameter></code></em>
</td><td align="left">
- Parameters are given in ParamName=Value syntax and are mostly
- useful to the plugin to honour EMBED tags attributes
+ Parameters are given in the syntax "ParamName=Value" and are
mostly
+ useful for the plugin to honour EMBED tags attributes
or explicit OBJECT PARAM tags. A common use for -P
is to provide FlashVars
(ie: -P "FlashVars=home=http://www.gnu.org";).
</td></tr><tr><td align="left">
- <code class="option">-F filedescriptor</code>
+ <code class="option">-F, --fd</code> <em
class="replaceable"><code><filedescriptor></code></em>
</td><td align="left">
Use the given filedescriptor to send requests to the host
application. This is currently only used for GETURL requests.
The protocol is not documented yet, and also needs improvement.
Primary use for this switch is for the NPAPI plugin to properly
support javascript and target windows in geturl requests.
+ </td></tr><tr><td align="left">
+ <code class="option">--max-advances</code> <em
class="replaceable"><code><num></code></em>
+ </td><td align="left">
+ Exit after the specified number of frame advances.
+ </td></tr><tr><td align="left">
+ <code class="option">--fullscreen</code>
+ </td><td align="left">
+ Start <span class="application">Gnash</span> in fullscreen mode as
long as the GUI and window
+ manager support this.
</td></tr></tbody></table></div></div><br
class="table-break"></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="keys"></a><span class="application">Gnash</span> Interactive Control
Keys</h2></div></div></div><p>
While a movie is playing, there are several control
keys. These can be used to step through frames, pause the
@@ -285,14 +286,6 @@
</td><td align="left">
Restart the movie.
</td></tr><tr><td align="left">
- <code class="option">CTRL-[ or kp-</code>
- </td><td align="left">
- Step back one frame.
- </td></tr><tr><td align="left">
- <code class="option">CTRL-] or kp+</code>
- </td><td align="left">
- Step forward one frame.
- </td></tr><tr><td align="left">
<code class="option">CTRL-L</code>
</td><td align="left">
Force immediate redraw.
@@ -308,10 +301,6 @@
<code class="option">CTRL-M</code>
</td><td align="left">
Debug. Test the call_method() function.
- </td></tr><tr><td align="left">
- <code class="option">CTRL-B</code>
- </td><td align="left">
- Toggle the background color.
</td></tr></tbody></table></div></div><br
class="table-break"></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="gnashrc"></a>User Configuration File</h2></div></div></div><p>
Individual user preferences may be set by editing variables with
the <code class="filename">.gnashrc</code> file:
@@ -362,7 +351,7 @@
Because several files can be parsed in succession, each file can
override
or add to lists in other files. Use <span
class="emphasis"><em>set</em></span> to override
all other lists or <span class="emphasis"><em>append</em></span> to
add new sandboxes.
- Note that there's currently no way to *drop* the directory of base dir
+ Note that there's currently no way to <span
class="emphasis"><em>drop</em></span> the directory of base dir
from the list of allowed local sandboxes.
</td></tr><tr><td align="left">delay</td><td
align="left">Number</td><td align="left"><span class="application">Gnash</span>
uses a timer-based event mechanism to advance frames
at a steady rate. This option overrides the default
@@ -391,14 +380,19 @@
Note that the version advertised by the plugin is NOT affected by
this setting,
instead you need to set the GNASH_FLASH_VERSION environment variable
for
the latter (which doesn't affect $version and
System.capabilities.version).</td></tr><tr><td
align="left">flashSystemOS</td><td align="left">string</td><td align="left">The
string that Gnash should return for System.capabilities.OS</td></tr><tr><td
align="left">flashSystemManufacturer</td><td align="left">string</td><td
align="left">The string that Gnash should return for
System.capabilities.manufacturer</td></tr><tr><td
align="left">StreamsTimeout</td><td align="left">double</td><td align="left">
- Set the number of seconds after which streams download time out.
Note that timeouts only occurs after the given number of seconds
- passed w/out anything was received.
+ Set the number of seconds after which streams download time
+ out. Timeouts only occur after the given number
+ of seconds have passed without anything being received.
</td></tr><tr><td align="left">insecureSSL</td><td
align="left">on/off</td><td align="left">If set to <span
class="emphasis"><em>on</em></span>, no verification of SSL connections
is performed. This means that, although the connection is encrypted,
the server
certificate could be invalid, may not belong to the host, or both.
Equivalent
to curl --insecure. By default, this option is <span
class="emphasis"><em>off</em></span> and
connections will fail when a host cannot be
verified.</td></tr><tr><td align="left">SOLsafedir</td><td
align="left">Absolute path</td><td align="left">The full path to a directory
where <span class="application">Gnash</span> should store Shared Object files
("flash cookies") if
- they are enabled.</td></tr><tr><td align="left">SOLreadonly</td><td
align="left">on/off</td><td align="left">If set to <span
class="emphasis"><em>on</em></span>, <span class="application">Gnash</span>
will not write Shared Object files.</td></tr><tr><td
align="left">URLOpenerFormat</td><td align="left">string</td><td align="left">
+ they are enabled.</td></tr><tr><td align="left">SOLreadonly</td><td
align="left">on/off</td><td align="left">If set to <span
class="emphasis"><em>on</em></span>, <span class="application">Gnash</span>
will not write Shared Object files.</td></tr><tr><td
align="left">ignoreFSCommand</td><td align="left">on/off</td><td
align="left">If set to on (default), <span class="application">Gnash</span>
will ignore fscommands in standalone mode.
+ Fscommands are requests from the playing movie to the operating
system or
+ user interface: the most common are quit, fullscreen, showmenu and
exec. <span class="application">Gnash</span>
+ always ignores fscommands when running as a plugin.
+ </td></tr><tr><td align="left">URLOpenerFormat</td><td
align="left">string</td><td align="left">
Set the format of an url opener command. The %u label would be
substituted by the actual url to be opened.
Examples:
<pre class="programlisting">
@@ -494,7 +488,7 @@
</td></tr><tr><td align="left">Gentoo</td><td align="left">AMD64,
PowerPC, SPARC, x86
</td></tr><tr><td align="left">Maemo 2.1</td><td
align="left">i385, ARMv5t</td></tr><tr><td align="left">Scratchbox</td><td
align="left">i386, ARMv5t</td></tr><tr><td align="left">Access Linux Platform
</td><td align="left">i386, ARMv5t</td></tr><tr><td
align="left">Mandriva
- </td><td align="left">i386, MIPS</td></tr><tr><td
align="left">Open Embedded, OpenMoko, Poky
+ </td><td align="left">i386, x86-64, MIPS</td></tr><tr><td
align="left">Open Embedded, OpenMoko
</td><td align="left">ARM
</td></tr><tr><td align="left">YellowDog Linux 6
</td><td align="left">PowerPC, PS3
@@ -509,7 +503,7 @@
</td></tr><tr><td align="left">Darwin (MacOS X)
</td><td align="left">PowerPC and x86-32
</td></tr><tr><td align="left">Windows XP, Windows Vista</td><td
align="left">x86-32</td></tr></tbody></table></div></div><br
class="table-break"></div><div class="sect2" lang="en"><div
class="titlepage"><div><div><h3 class="title"><a name="software"></a>Software
Requirements</h3></div></div></div><p>
- The 0.8.2 release of Gnash has been designed to run on
+ The 0.8.3 release of Gnash has been designed to run on
UNIX/Linux variants, and has been run on most of the free ones.
However, Gnash has successfully run on Windows, Darwin (Mac OS X),
Irix, Solaris, BeOs, OS/2, and Haiku. Gnash has also run on the
@@ -583,7 +577,7 @@
from your distributions repository.
</p></div></div></div><div class="chapter" lang="en"><div
class="titlepage"><div><div><h2 class="title"><a name="bugreport"></a>Chapter
4. Reporting Bugs</h2></div></div></div><div class="toc"><p><b>Table of
Contents</b></p><dl><dt><span class="sect1"><a href="#bugstep_package">Get a
Fresh Binary Package</a></span></dt><dt><span class="sect1"><a
href="#bugstep_search">Determine if the bug was previously
reported</a></span></dt><dt><span class="sect1"><a
href="#bugstep_guidelines">Review the bug writing
guidelines</a></span></dt><dt><span class="sect1"><a
href="#bugstep_file">Filing a bug report</a></span></dt></dl></div><p>
The Gnash project relies on the community of Gnash users to test
- the player, feedback is critical to any successful project. Not
+ the player. Feedback is critical to any successful project. Not
only does it let us know that people use Gnash, but it helps us
understand the community's needs. Gnash uses a bug tracker on
<a class="ulink" href="http://savannah.gnu.org";
target="_top">http://savannah.gnu.org</a> to manage these reports.
@@ -591,8 +585,8 @@
When filing a report, please follow the guidelines below. The better
your bug report is, the easier it will be for the developers to
address the issue. Bug reports without enough information will
- initially be asked to provide this information anyway. Adding
- critical details, like the Operating System you are on, it's
+ be asked to provide this information anyway. Adding
+ critical details, like the Operating System you are on, its
version, and any relevant error messages from Gnash that you get.
</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2
class="title" style="clear: both"><a name="bugstep_package"></a>Get a Fresh
Binary Package</h2></div></div></div><p>
For starters, it's a good idea to obtain a copy of the latest
@@ -600,8 +594,8 @@
Gnash build infrastructure allows the automated building of
binary packages. Often the version of Gnash as packaged by a
GNU/Linux or BSD distribution is based on the last official
- release, which could be months out of date. It is helpful if
- this is the case to try a newer packaged build of Gnash.
+ release, which could be months out of date. It helps us, if
+ this is the case, for you to try a newer packaged build of Gnash.
</p><p>
You can get a fresh binary package of Gnash, as well as recent
source packages from
@@ -660,7 +654,7 @@
AGG is the AntiGrain 2D graphics library, which can be used
as a renderer in Gnash. It is faster than OpenGL on systems
without hardware graphics acceleration. As of Gnash version
- 0.8.1 it is the more feature complete renderer.
+ 0.8.2 it is the more feature complete renderer.
</p></dd><dt>
AMF
</dt><dd><p>
@@ -722,9 +716,11 @@
</dt><dd><p>
The term <span class="emphasis"><em>Flash</em></span> is used to
describe both the
Adobe IDE for creating <span class="emphasis"><em>SWF</em></span>
- files, and the technology itself. Flash is a trademarked
- term of Adobe's, we prfer to use SWF to refer to the files
- themselves, as well as the format, instead of flash(tm).
+ files, and the technology itself. Flash is a registered trademark
+ belonging to Adobe. Unfortunately, neither Macromedia nor
+ Adobe have done a good job creating a generic name for all
+ things having to do with Flash. They risk
+ loss of their trademark.
</p></dd><dt>
FLV
</dt><dd><p>
@@ -776,17 +772,16 @@
You must choose a GUI library during the
configuration stage of building Gnash.
</p></dd></dl></div><div class="glossdiv"><h3
class="title">K</h3><dl><dt>
- Klash
+ kde-gnash
</dt><dd><p>
- <span class="emphasis"><em>Klash</em></span> was the name given to
the stand-alone
+ <span class="emphasis"><em>kde-gnash</em></span> is the name given to
the stand-alone
instance of <span class="application">Gnash</span> which used the KDE
GUI. It has been replaced with
- an implementation using Qt. Some documentation may incorrectly
- refer to the Konqueror plugin as <span
class="emphasis"><em>Klash</em></span>.
- The plugin was renamed <span class="emphasis"><em>Kpart</em></span>.
+ an implementation using Qt. The Konqueror plugin runs kde-gnash
+ and is called <span class="emphasis"><em>Kparts</em></span>.
</p></dd><dt>
- Kpart
+ Kparts
</dt><dd><p>
- <span class="emphasis"><em>Kpart</em></span> is a plugin for
Konqueror which is
+ <span class="emphasis"><em>Kparts</em></span> is a plugin for
Konqueror which is
enabled with the configuration option --enable-kparts.
</p></dd></dl></div><div class="glossdiv"><h3
class="title">L</h3><dl><dt>
libmad
@@ -882,16 +877,15 @@
platforms' graphics, sound, and input APIs. Gnash can use it
as a GUI and/or as a sound handler. Note that the two usages
are independent of each other: you can use it for a task and
- not for the other if you wish. At time or writing (2007-01-11)
- the SDL GUI lacks menus and a performant input event
- architecture; the SDL sound handler is the most feature rich,
- supporting Video through ffmpeg.
+ not for the other if you wish. This version of Gnash does not
+ implement menus in the SDL GUI; the SDL sound handler is the
+ most feature rich, supporting video through ffmpeg.
</p></dd><dt>
sound handler
</dt><dd><p>
The <span class="emphasis"><em>sound handler</em></span> is the part
of <span class="application">Gnash</span>
which handles both event sounds and streaming sound. Audio
- from external sources are also handled through the sound handler
+ from external sources is sent through the sound handler
when SDL is used. The sound handler must be selected during
configuration of Gnash when compiling.
</p><p>
@@ -910,7 +904,8 @@
</p></dd><dt>
Stage
</dt><dd><p>
- The visible area of a Flash movie. The name derives from a
theater analogy. Graphical elements are referred to as
+ The visible area of a Flash movie. The name derives from a
+ theater analogy. Graphical elements are referred to as
characters.
</p></dd><dt>
SWF
@@ -942,10 +937,10 @@
</p></dd></dl></div></div><div class="chapter" lang="en"><div
class="titlepage"><div><div><h2 class="title"><a name="authors"></a>Chapter 5.
Authors</h2></div></div></div><p>
<span class="application">Gnash</span> is maintained by Rob Savoye.
Other active developers
are: Sandro Santilli, Bastiaan Jacques, Udo Giacomozzi, Chad
- Musick, Benjamin Wolsey, and Zou Lunkai. Please send all
- comments and suggestions to <code class="email"><<a class="email"
href="mailto:address@hidden";>address@hidden
- </a>></code>. Past and sometimes current developers are Tomas
- Groth and Markus Gothe.
+ Musick, Benjamin Wolsey, Zou Lunkai, and Russ Nelson. Please
+ send all comments and suggestions to
+ <code class="email"><<a class="email"
href="mailto:address@hidden";>address@hidden</a>></code>. Past and sometimes
current
+ developers are Tomas Groth and Markus Gothe.
</p><p>
<span class="application">Gnash</span> was initially derived from
<span class="application">GameSWF</span>.
<span class="application">GameSWF</span> is maintained by
Index: doc/C/refmanual/documentation_dependencies.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/refmanual/documentation_dependencies.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- doc/C/refmanual/documentation_dependencies.xml 2 Mar 2008 16:28:29
-0000 1.3
+++ doc/C/refmanual/documentation_dependencies.xml 16 May 2008 13:23:43
-0000 1.4
@@ -95,7 +95,7 @@
url="http://ftp.gnu.org/gnu/texinfo/";>http://ftp.gnu.org/gnu/texinfo/</ulink>.
</entry>
<entry>
- Texinfo is required if you wish to product GNU info
+ Texinfo is required if you wish to produce GNU info
pages.
</entry>
<entry><filename>texinfo</filename></entry>
Index: doc/C/refmanual/feature_configuration.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/refmanual/feature_configuration.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- doc/C/refmanual/feature_configuration.xml 2 Mar 2008 16:28:29 -0000
1.3
+++ doc/C/refmanual/feature_configuration.xml 16 May 2008 13:23:43 -0000
1.4
@@ -134,7 +134,7 @@
<listitem>
<para>
Fast Light ToolKit, low on resource usage.
- Since all build using fltk are now broken, we declare it
+ Since all builds using fltk are now broken, we declare it
"for developers".
</para>
</listitem>
@@ -207,15 +207,16 @@
<row>
<entry><option>--enable-renderer=opengl|cairo|agg</option>
</entry>
- <entry>Enable support for the a graphics backend. Currently
+ <entry>Enable support for a graphics backend. Currently
only <option>opengl</option> and
- <option>agg</option> work sufficiently. OpenGL is
- used when you have hardware accelerated graphics. AGG i
- used when you do not have hardware accelerated
- graphics. Typically most desktop machines have OpenGL
- support, and most embedded systems do not. OpenGl is the
- default when building Gnash, although the quality of AGG's
- rendering is currently superior to OpenGL.</entry>
+ <option>agg</option> work sufficiently. Use OpenGL
+ when you have hardware accelerated graphics. Use AGG
+ when you do not have hardware accelerated
+ graphics or when you are building for a wide audience.
+ Typically most desktop machines have OpenGL
+ support, and most embedded systems do not. AGG is the
+ default when building Gnash, although the speed of OpenGL's
+ rendering is currently superior to AGG.</entry>
</row>
<row>
<entry><option>--enable-sdk-install</option>
Index: doc/C/refmanual/testing_dependencies.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/refmanual/testing_dependencies.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- doc/C/refmanual/testing_dependencies.xml 27 Mar 2008 10:25:02 -0000
1.4
+++ doc/C/refmanual/testing_dependencies.xml 16 May 2008 13:23:44 -0000
1.5
@@ -3,7 +3,7 @@
<para>
&app; tries to run as many tests as possible, but will
- simply skip tests if the tools to run them are unavailable.
+ silentl skip tests if the tools to run them are unavailable.
</para>
<table frame='all' id="testdeps">
Index: doc/C/usermanual/usage.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/usermanual/usage.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- doc/C/usermanual/usage.xml 17 Mar 2008 14:50:57 -0000 1.13
+++ doc/C/usermanual/usage.xml 16 May 2008 13:23:44 -0000 1.14
@@ -25,7 +25,7 @@
files. They are located in the
<filename>testsuite/samples/</filename> directory of the &app;
source directory. If you have installed &app; correctly, issuing
- the a command similar to the following plays a short animation of
+ a command similar to the following plays a short animation of
a car swerving and crashing:
<programlisting>
gnash
@@ -148,6 +148,23 @@
</row>
<row>
<entry>
+ <option>-A</option> <replaceable><file></replaceable>
+ </entry>
+ <entry>
+ Write the audio output to a wave format file.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <option>-D</option> <replaceable><file></replaceable>
+ </entry>
+ <entry>
+ Write the video output to a raw video file. This option
+ is only valid with dump-gnash.
+ </entry>
+ </row>
+ <row>
+ <entry>
<option>-w, --writelog</option>
</entry>
<entry>
@@ -173,8 +190,8 @@
only by the plugin.
</entry>
</row>
- <row>
<!--
+ <row>
<entry>
<option>-e</option>
</entry>
@@ -184,8 +201,8 @@
improve performance for some types of movies.
</entry>
</row>
- <row>
-->
+ <row>
<entry>
<option>-1, --once</option>
</entry>
Index: macros/boost.m4
===================================================================
RCS file: /sources/gnash/gnash/macros/boost.m4,v
retrieving revision 1.82
retrieving revision 1.83
diff -u -b -r1.82 -r1.83
--- macros/boost.m4 30 Apr 2008 16:06:34 -0000 1.82
+++ macros/boost.m4 16 May 2008 13:23:44 -0000 1.83
@@ -33,10 +33,10 @@
libname=""
dnl this is a list of *required* headers. If any of these are missing, this
dnl test will return a failure, and Gnash won't build.
- boost_headers="detail/lightweight_mutex.hpp thread/thread.hpp
multi_index_container.hpp multi_index/key_extractors.hpp thread/mutex.hpp
filesystem/convenience.hpp filesystem/operations.hpp filesystem/exception.hpp"
+ boost_headers="detail/lightweight_mutex.hpp thread/thread.hpp
multi_index_container.hpp multi_index/key_extractors.hpp thread/mutex.hpp"
dnl this is a list of *required* libraries. If any of these are missing, this
dnl test will return a failure, and Gnash won't build.
- boost_libs="thread date_time filesystem"
+ boost_libs="thread date_time"
dnl this is a list of *recommended* libraries. If any of these are missing,
this
dnl test will return a warning, and Gnash will build, but testing won't work.
extra_boost_libs="serialization"
Index: macros/docbook.m4
===================================================================
RCS file: /sources/gnash/gnash/macros/docbook.m4,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- macros/docbook.m4 1 Mar 2008 14:48:45 -0000 1.30
+++ macros/docbook.m4 16 May 2008 13:23:45 -0000 1.31
@@ -58,8 +58,12 @@
AC_MSG_NOTICE([checking for other programs needed to process the DocBook
files])
AC_PATH_PROG(FOP, fop.sh, [],
[$PATH:/usr/local/fop-0.20.5/:/usr/fop-0.20.5/:/usr/local/fop:/usr/lib/java/fop])
+ if test x"$FOP" == x; then
+ AC_PATH_PROG(FOP, fop, [],
+
[$PATH:/usr/local/fop-0.20.5/:/usr/fop-0.20.5/:/usr/local/fop:/usr/lib/java/fop])
+ fi
if test x"$FOP" != x; then
- dirlist="/usr/lib/jre /usr/jre /opt/local/Java/JavaSDK ~/ReQuest/jre
$J2REDIR"
+ dirlist="/usr /usr/lib/jre /usr/jre /opt/local/Java/JavaSDK
~/ReQuest/jre $J2REDIR"
JAVA=
for i in $dirlist; do
if test -f $i/bin/java; then
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Gnash-commit] gnash ChangeLog NEWS README doc/C/actionscript....,
Russ Nelson <=