[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnash-commit] /srv/bzr/gnash/trunk r10725: preformatted info and manual
|
From: |
Sandro Santilli |
|
Subject: |
[Gnash-commit] /srv/bzr/gnash/trunk r10725: preformatted info and manual pages regenerated |
|
Date: |
Thu, 19 Mar 2009 10:13:48 +0100 |
|
User-agent: |
Bazaar (1.5) |
------------------------------------------------------------
revno: 10725
committer: Sandro Santilli <address@hidden>
branch nick: trunk
timestamp: Thu 2009-03-19 10:13:48 +0100
message:
preformatted info and manual pages regenerated
modified:
doc/C/preformatted/gnash.1.in
doc/C/preformatted/gnash_ref.info.in
doc/C/preformatted/gnash_user.info.in
=== modified file 'doc/C/preformatted/gnash.1.in'
--- a/doc/C/preformatted/gnash.1.in 2008-06-23 04:34:05 +0000
+++ b/doc/C/preformatted/gnash.1.in 2009-03-19 09:13:48 +0000
@@ -5,7 +5,7 @@
\\$2 \(la\\$1\(ra\\$3
..
.if \n(.g .mso www.tmac
-.TH gnash 1 "20 June 2008" "" ""
+.TH gnash 1 "19 March 2009" "" ""
.SH NAME
gnash \- GNU Flash (SWF) Player
.SH Synopsis
=== modified file 'doc/C/preformatted/gnash_ref.info.in'
--- a/doc/C/preformatted/gnash_ref.info.in 2008-06-23 04:34:05 +0000
+++ b/doc/C/preformatted/gnash_ref.info.in 2009-03-19 09:13:48 +0000
@@ -214,9 +214,11 @@
make check
make install
- If you are compiling with GCC you will probably need to use a machine
-with at least 128 megabytes of physical RAM; 64MB is not enough for a
-couple of the files, even with swap enabled and optimisation turned off.
+ If you are compiling with GCC you will need to use a machine with at
+least 128 megabytes of physical RAM; 64MB is not enough for a couple of
+the files, even with swap enabled and optimisation turned off. With
+less than 512 megabytes available, many build combinations can still be
+a long and painful experience.
At present the Gnash source is about 30 MB extracted and configured
and requires a total of about 125 megabytes to compile it.
@@ -233,10 +235,10 @@
* Menu:
* Releases::
-* CVS Access::
+* Bzr Access::
-File: gnash_ref.info, Node: Releases, Next: CVS Access, Up: Getting The
Source
+File: gnash_ref.info, Node: Releases, Next: Bzr Access, Up: Getting The
Source
2.2.1 Releases
--------------
@@ -247,24 +249,26 @@
http://ftp.gnu.org/gnu/gnash (http://ftp.gnu.org/gnu/gnash)
-File: gnash_ref.info, Node: CVS Access, Prev: Releases, Up: Getting The
Source
+File: gnash_ref.info, Node: Bzr Access, Prev: Releases, Up: Getting The
Source
-2.2.2 CVS Access
+2.2.2 Bzr Access
----------------
-The latest Gnash development sources are available via anonymous CVS.
-Use the following commands to check them out (just hit return when you
-are prompted for the password):
-
-
- export CVS_RSH=ssh
- cvs -z3 -d:pserver:address@hidden:/sources/gnash co gnash
-
-You will then be able to update your copy from the repository using
-
-
- cd gnash
- cvs update -d
+The latest Gnash development sources are available via bzr. Use the
+following commands to check them out:
+
+
+ mkdir gnash
+ cd gnash
+ bzr branch http://bzr.savannah.gnu.org/r/gnash/trunk
+
+At any time, other temporary development branches may also be
+available. Replace _trunk_ with the branch name to check these out.
+You can update your copy from the main repository using:
+
+
+ cd trunk
+ bzr pull
If you only have access to the internet via a web proxy, you will
find daily source snapshots of the latest CVS tree in
@@ -279,13 +283,13 @@
Gnash has a number of dependencies on other packages. If you install
the dependencies using a package manager, be certain to install the
-development versions of the packages. The normal versions are often
-missing the headers Gnash needs to compile.
+development versions of the packages. The normal versions often lack
+the headers Gnash needs to compile.
- Some dependencies have other dependencies, like GTk also needs
-glib2, atk, and pango to produce a fully linked executable. Different
-distributions also use differing dependencies, sometimes a package will
-depend on libxml2 on one system, but libexpat on another.
+ Some dependencies have other dependencies: for instance, GTK also
+needs glib2, atk, and pango to produce a fully linked executable.
+Different distributions also use differing dependencies, sometimes a
+package will depend on libxml2 on one system, but libexpat on another.
*Code Dependency Table*
@@ -306,18 +310,6 @@
thread
and mutext
handling.
-libxml2 Required Libxml2 This
`libxml2-dev'`libxml2-devel'`libxml2'
- is the library
- GNOME XML is used
- parser to parse
- library messages
- and is for the
- available XML
- at XMLNode,
- http://xmlsoft.orgor
- (http://xmlsoft.org).XMLSocket
- ActionScript
- classes.
AGG Possibly 2.4 or AGG is Gnash
`libagg-dev'`agg-devel'`agg'
Required higher the requires
AntiGrain the
@@ -546,25 +538,44 @@
can be
used
directly.
-JPEG Optional JPEG This
`libjpeg62-dev'`libjpeg'`jpeg'
+JPEG Required JPEG This
`libjpeg62-dev'`libjpeg'`jpeg'
(http://www.ijg.org/)library
is a is used
lossy for
- image rendering
- format JPEGs.
- which is
- heavily
- used for
- images.
-PNG Optional PNG This
`libpng12-dev'`libpng'`png'
+ image reading
+ format external
+ which is JPEGs and
+ heavily JPEG data
+ used for embedded
+ images. in SWF
+ files.
+PNG Required PNG This
`libpng12-dev'`libpng'`png'
(http://www.libpng.org/pub/png/)library
is a is used
patent-freefor
- image rendering
- format PNGs.
- which is
- comparable
- to _GIF_.
+ image loading
+ format external
+ which is PNG
+ comparable images
+ to _GIF_. (part of
+ the SWF8
+ specification)
+ and for
+ writing
+ images in
+ the PNG
+ format.
+GIF Required GIF is a This
`libungif-dev'`libungif-devel'`gif'
+ common library
+ image is used
+ format for
+ that loading
+ should now external
+ be free GIF
+ of patent images
+ restrictions.(part of
+ _GIF_. the SWF8
+ specification).
libcurl Optional libcurl This
`libcurl4-gnutls'`libcurl'`curl'
is the library
multiprotocalis used
@@ -1031,6 +1042,16 @@
`--enable-write' Makes the Mozilla plugin write the
currently playing SWF movie to
`/tmp'.
+`--disable-sa-launcher' Drops the NPAPI plugin support for
+ writing a standalone executable
+ launcher script for the currently
+ playing SWF movie to `/tmp'. Note
+ that you'll still need to add a
+ 'writelauncher' string to your
+ GNASH_OPTIONS environment variable
+ for the script to be created, even
+ if the compile-time support is
+ enabled.
`--disable-mit-shm' Disable support for the MIT-SHM X
extensions. Currently support is
only available using GTK gui and
@@ -1057,12 +1078,6 @@
Option Function
`--x-includes=DIR' X include files are in DIR.
`--x-libraries=DIR' X library files are in DIR.
-`--with-libxml=PFX' Prefix to where libxml is
- installed.
-`--with-libxml-libraries=DIR' Directory where libxml library is
- installed.
-`--with-libxml-includes=DIR' Directory where libxml header
- files are installed.
`--with-docbook=DIR' Directory where the DocBook
style-sheets are installed.
`--with-sdl-prefix=PFX' Prefix where SDL is installed.
@@ -1420,9 +1435,9 @@
2.9.2.1 Movie tests
...................
-This creates a Flash movie version of the test case, which can be run
-with a standalone Flash player. For instance, the target for SWF
-version 6 could be run with Gnash:
+This creates a SWF movie version of the test case, which can be run
+with a standalone SWF player. For instance, the target for SWF version
+6 could be run with Gnash:
gnash -v XML-v6.swf
@@ -1630,8 +1645,8 @@
The top level of Gnash has several libraries, _libgnashbase_,
_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.
+processing of SWF movie files, and other useful utilities for examining
+local Shared Objects and sniffing LocalConnections.
* Menu:
@@ -1687,9 +1702,9 @@
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.
+frames. Besides the standard SWF 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:
libgnashmedia, Up: The Libraries
@@ -1735,7 +1750,7 @@
----------------------
There are currently a few standalone programs in Gnash, which serve
-either to assist with Gnash development or to play flash movies.
+either to assist with Gnash development or to play SWF movies.
* Menu:
@@ -1760,7 +1775,7 @@
..................
Gprocessor is used to print out the actions (using the -va option) or
-the parsing (using the -vp option) of a flash movie. It is also used to
+the parsing (using the -vp option) of a SWF movie. It is also used to
produce the _.gsc_ files that Gnash uses to cache data, thereby
speeding up the loading of files.
@@ -1866,8 +1881,8 @@
its output in the browser.
While this is not an optimal solution, it does enable one to use
-Gnash as the flash player when browsing. The main issue appears to be
-that the Flash movie being played doesn't get any mouse or keyboard
+Gnash as the SWF player when browsing. The main issue appears to be
+that the SWF movie being played doesn't get any mouse or keyboard
input. That may be a mozplugger configuration issue, however.
Use of MozPlugger is obsolete now that the Gnash plugin works.
@@ -2128,19 +2143,18 @@
based on SDL_mixer, which by design had some limitations, making it
difficult to implement needed features such as support for soundstreams.
The SDL sound backend supports both event-sounds and soundstreams,
-using Gnash's internal ADPCM, and optionally MP3 support, using either
-FFMPEG or LIBMAD. When it receives sound data it is stored without
-being decoded, unless it is ADPCM, which is decoded in the parser. When
-playing, backend relies on a function callback for retrieving output
-sound, which is decoded and re-sampled if needed, and all sound output
-is mixed together. The current SDL sound backend was made since Gnash
-needed a working sound backend as soon as possible, and since the
-gstreamer backend at the time suffered from bugs and/or lack of
-features in gstreamer. The result was the most complete and best sound
-handler so far. The advantages of the SDL sound handler is speed, and
-ease of use, while its only real disadvantage is that it has to be
-compiled with MP3 support, which some Linux distributions will probably
-not like...
+using Gnash's internal ADPCM, and optionally MP3 support, using FFMPEG.
+When it receives sound data it is stored without being decoded, unless
+it is ADPCM, which is decoded in the parser. When playing, backend
+relies on a function callback for retrieving output sound, which is
+decoded and re-sampled if needed, and all sound output is mixed
+together. The current SDL sound backend was made since Gnash needed a
+working sound backend as soon as possible, and since the gstreamer
+backend at the time suffered from bugs and/or lack of features in
+gstreamer. The result was the most complete and best sound handler so
+far. The advantages of the SDL sound handler is speed, and ease of use,
+while its only real disadvantage is that it has to be compiled with MP3
+support, which some Linux distributions will probably not like...
File: gnash_ref.info, Node: The Gstreamer backend, Next: Future audio
backends, Prev: The SDL sound backend, Up: Sound handling in Gnash
@@ -2251,9 +2265,9 @@
-------------------
Currently Gnash uses three other tools to help with testing. Two of
-these are free compilers for the Flash format. This lets us write
-simple test cases for Gnash to test specific features, and to see how
-the features operate.
+these are free compilers for the SWF format. This lets us write simple
+test cases for Gnash to test specific features, and to see how the
+features operate.
The primary compiler used at this time is Ming (http://ming.sf.net).
Since release 0.3, _Ming_ includes a command-line compiler, _makeswf_.
@@ -2325,7 +2339,7 @@
Additionally, the check.as file provides a transparent way to send
results to a TextField rather then using trace. This is very useful
-when you use a flash player without tracing support.
+when you use a SWF player without tracing support.
Test units are built by running _make TestName-v#.swf_. This will
use TestName.as as source and the value of # as target version.
@@ -3096,23 +3110,23 @@
5 Gnash Extensions
******************
-Gnash supports extending the Flash specification by creating custom
+Gnash supports extending the SWF specification by creating custom
ActionScript classes that are compiled code, as opposed to the existing
method of defining custom classes as ActionScript. Executing compiled
code has many performance benefits over having to interpret the byte
stream of the ActionScript opcodes.
I can already hear people complaining now about the concept of
-extending Flash, so this in no way affects Gnash's ability to play
-Flash movies when functioning as a browser plugin. Gnash's goal is
-still to function in a way that is compatible with the current
-proprietary Flash player.
+extending SWF, so this in no way affects Gnash's ability to play SWF
+movies when functioning as a browser plugin. Gnash's goal is still to
+function in a way that is compatible with the current proprietary Flash
+player.
- But at the same time, we see Flash as the ideal scripting language
-for a digital multi-media streaming environment. There are many
-resources for Flash movie creators for widgets, higher level APIs, all
-sorts of desirable things. But for those of use committed to using free
-software tools for Flash, our options are very limited.
+ But at the same time, we see SWF as the ideal scripting language for
+a digital multi-media streaming environment. There are many resources
+for SWF movie creators for widgets, higher level APIs, all sorts of
+desirable things. But for those of use committed to using free software
+tools for SWF, our options are very limited.
Rather than launching a multi-year project to duplicate all classes
in the commercial Flash IDE, it's much more efficient to use existing
@@ -3124,13 +3138,13 @@
the proprietary IDE in them play in Gnash just fine, as it's all just
byte codes by then.
- This trick works because until Flash player version 9, all the
-ActionScript class names and methods are passed as ASCII strings into
-the Flash movie. So the Gnash Virtual Machine just loads the extension
-file if that class name is invoked in the movie. All extension files
-specify the class name and methods it implements in an identical style
-as adding any new ActionScript class. The advantage is the class itself
-is compiled code, and runs much faster than the equivalent byte codes
+ This trick works because until SWF version 9, all the ActionScript
+class names and methods are passed as ASCII strings into the SWF movie.
+So the Gnash Virtual Machine just loads the extension file if that
+class name is invoked in the movie. All extension files specify the
+class name and methods it implements in an identical style as adding
+any new ActionScript class. The advantage is the class itself is
+compiled code, and runs much faster than the equivalent byte codes
which all have to be interpreted..
* Menu:
@@ -3191,7 +3205,7 @@
sets the other function callbacks for all the methods this class
supports. The method callbacks are attached to the parent class by
using _init_member()_ to set a C function pointer to the string value
-used in the Flash movie.
+used in the SWF movie.
// Attach DummyClass 'func1' and 'func2' methods to the given object
@@ -3333,8 +3347,8 @@
}
Once you have set the breakpoints you want, reset the value of the
-_stall_ variable to break out of the loop, and the Flash movie will
-then continue playing.
+_stall_ variable to break out of the loop, and the SWF movie will then
+continue playing.
(gdb) set variable stall = false;
@@ -3494,13 +3508,13 @@
protocol and AMF format. _tcpdump_ and _ethereal_ are your friend. Some
additional info that got me started was from the Red5
(http://www.osflash.org/red5) project. _Red5_ is the only other open
-source Flash server. So some details are still vague, but as the
+source SWF server. So some details are still vague, but as the
implementation appears to work, we'll figure out what they are later.
The Real Time Messaging Protocol was created by MacroMedia (now
-Adobe) for delivering Flash objects and video over a network
-connection. Currently the only servers which support this format are
-the MacroMedia Media sever, and the Open Source Red5 project.
+Adobe) for delivering SWF objects and video over a network connection.
+Currently the only servers which support this format are the MacroMedia
+Media sever, and the Open Source Red5 project.
This is a simple protocol, optimized for poor bandwidth connections.
It can support up to 64 concurrent streams over the same network
@@ -3514,8 +3528,6 @@
The basics of the RTMP protocol are as follows. All communications
are initiated by the client.
-Image of the RTMP protocol.
-
The client starts the RTMP connection by sending a single byte with
a value of 0x3. This byte is followed by a data block of 1536 bytes.
The format if this data block is unknown, but it appears to not be
@@ -3536,8 +3548,8 @@
is happy with the handshake, and ready to start reading packets.
The second packet is the _NetConnection_ object from the client.
-This ActionScript class is used by the Flash movie to create the
-network connection to the server.
+This ActionScript class is used by the SWF movie to create the network
+connection to the server.
The third packet is the _NetStream_ object from the client. This is
the ActionScript class used to specify the file to be streamed by the
@@ -3560,10 +3572,10 @@
The RTMP header is first, followed by the connect message as an
ASCII string as the message body. The following AMF packet is the
-_NetConnection_ one, which specifies that this is coming from a Flash
+_NetConnection_ one, which specifies that this is coming from a SWF
application. This also contains the file path the server can use to
find the file to stream. This is then followed by the version number,
-which I assume is the version of the Flash player, so the server knows
+which I assume is the version of the SWF player, so the server knows
what it is talking to.
The third packet is the one from _NetStream_, which specifies the
@@ -3571,7 +3583,7 @@
security.
For the next level of detail, we'll explain the format of AMF. AMF
-is used by the RTMP protocol to transfer data. Each Flash object is
+is used by the RTMP protocol to transfer data. Each SWF object is
encapsulated in an AMF packet, including streaming audio or video.
The first byte of the RTMP header determines two things about the
@@ -3642,7 +3654,7 @@
0x14
This specifies the content type of the RTMP message is remote
- procedure call. This invokes the method of a Flash class remotely.
+ procedure call. This invokes the method of a SWF class remotely.
There are two sets of data types to consider. One set is used by the
to specify the content type of the AMF object, the other is an
@@ -3653,7 +3665,7 @@
0x0
This specifies the data in the AMF packet is a numeric value. All
- numeric values in Flash are 64 bit, _big-endian_.
+ numeric values in SWF are 64 bit, _big-endian_.
0x1
This specifies the data in the AMF packet is a boolean value.
@@ -3662,21 +3674,21 @@
This specifies the data in the AMF packet is an _ASCII_ string.
0x3
- This specifies the data in the AMF packet is a Flash object. The
- Flash object data type field further along in the message
- specifies which type of ActionScript object it is.
+ This specifies the data in the AMF packet is a SWF object. The SWF
+ object data type field further along in the message specifies
+ which type of ActionScript object it is.
0x4
- This specifies the data in the AMF packet is a Flash movie, ie.
- another Flash movie.
+ This specifies the data in the AMF packet is a SWF movie, ie.
+ another SWF movie.
0x5
This specifies the data in the AMF packet is a NULL value. NULL is
- often used as the return code from calling Flash functions.
+ often used as the return code from calling SWF functions.
0x6
This specifies the data in the AMF packet is a undefined. This is
- also used as the return code from calling Flash functions.
+ also used as the return code from calling SWF functions.
0x7
This specifies the data in the AMF packet is a reference.
@@ -3762,8 +3774,8 @@
The AMF format is used in the LocalConnection, SharedObject,
NetConnection, and NetStream ActionScript classes. This is a means of
-binary data interchange between Flash movies, or between a Flash player
-and a Flash server.
+binary data interchange between SWF movies, or between a SWF player and
+a SWF server.
Like the RTMP messages, an AMF packet header can be of a variable
size. The size is either the same as the initial header of the RTMP
@@ -4574,137 +4586,137 @@
Node: What Is Supported?3130
Node: Building from Source5637
Node: Overview6017
-Node: Getting The Source7059
-Node: Releases7265
-Node: CVS Access7633
-Node: Code Dependencies8345
-Ref: Code Dependency Table9042
-Node: Testing Dependencies34557
-Ref: Testing Dependency Table34866
-Node: Documentation Dependencies38790
-Ref: Documentation Dependency Table39059
-Node: Configuring Gnash48127
-Node: Features50421
-Ref: Configuration Options - Features51021
-Node: Specifying Custom Paths57418
-Ref: Custom Path Options57888
-Node: Compiling the Code69993
-Node: Creating the Documentation70934
-Node: Running the Tests72280
-Node: Using DejaGnu72734
-Node: Increasing Verbosity73097
-Node: Running Some Tests73633
-Node: Running The Tests Manually74453
-Node: Movie tests75115
-Node: ActionScript Unit Tests75469
-Node: Installation75786
-Node: Libraries77099
-Node: Executables77955
-Node: Documentation78825
-Node: Cross Configuring79580
-Node: Software Internals82660
-Node: A Tour of Gnash82929
-Node: The Libraries83497
-Node: libgnashbase83767
-Node: libgnashserver84194
-Node: libgnashmedia84565
-Node: libgnashamf85054
-Node: libgnashbackend85476
-Node: libgnashplugin85791
-Node: libklashpart85997
-Node: The Applications86167
-Node: The Standalone Player86537
-Node: Gprocessor86834
-Node: SOLdumper87228
-Node: Dumpshm87495
-Node: The Plugin87714
-Node: Current Implementation88204
-Node: GUI Support88745
-Node: Mozplugger90434
-Node: Klash92325
-Node: The Message Logging System92875
-Node: Logging System API94432
-Node: The LogFile Instance97266
-Node: Sound handling in Gnash98750
-Node: Sound types99493
-Node: Sound parsing100030
-Node: Sound playback100598
-Node: The SDL sound backend101128
-Node: The Gstreamer backend102447
-Node: Future audio backends103463
-Node: Detailed description of the Gstreamer backend103953
-Node: Testing106204
-Node: Testing Tools106675
-Node: Test Cases107507
-Node: Writing ActionScript Tests108086
-Node: Writing Ming-based self-contained SWF tests110589
-Node: Using Ming-based test generators facilities111746
-Node: Writing self-contained SWF tests with other compilers114106
-Node: Writing Test Runners117231
-Node: Using the generic test runner for self-contained SWF tests118980
-Node: Writing Movie testers121070
-Node: Adding New ActionScript Class122810
-Node: Prototype123990
-Node: Declaration125407
-Node: Instantiation125672
-Node: Methods126299
-Node: Accessing Arguments126690
-Node: Returning a Value to ActionScript127086
-Node: Additional fn_call Members127465
-Node: Dynamic Properties128319
-Node: The as_value Object Type129824
-Node: Data Types130262
-Node: Determining the Type130583
-Node: Fetching the Value131115
-Node: Setting the Value and Type131605
-Node: Further Reading132199
-Node: Object ActionScript Class132614
-Node: The Methods of the Class132954
-Node: The Properties of the Object Class133293
-Node: Object Class Conformance133608
-Node: Reporting Bugs135147
-Node: Get a Fresh Binary Package136130
-Node: Determine if the bug was previously reported136916
-Node: Review the bug writing guidelines137734
-Node: Filing a bug report138785
-Node: Gnash Extensions139068
-Node: Creating A New Extension141338
-Node: Crafting an Extension142756
-Node: Debugging An Extension147060
-Node: Included Extensions148752
-Node: Gtk Extension149196
-Node: File I/O Extension150183
-Node: MySQL Extension151369
-Node: RTMP Protocol152220
-Node: AMF Format162016
-Node: Mozilla/Firefox NPAPI Plugin162992
-Node: Plugin C API164010
-Node: Plugin C++ API165869
-Node: OpenGL and Threads169133
-Node: Plugin Event Handling170461
-Node: Appendix171430
-Node: Code Style171582
-Node: Authors175412
-Node: GNU Free Documentation License176121
-Node: 0_ PREAMBLE176884
-Node: 1_ APPLICABILITY AND DEFINITIONS178190
-Ref: fdl-document178415
-Ref: fdl-modified178706
-Ref: fdl-secondary178893
-Ref: fdl-invariant179538
-Ref: fdl-cover-texts179787
-Ref: fdl-transparent180000
-Ref: fdl-title-page181290
-Node: 2_ VERBATIM COPYING181679
-Node: 3_ COPYING IN QUANTITY182659
-Node: 4_ MODIFICATIONS185016
-Node: 5_ COMBINING DOCUMENTS191076
-Node: 6_ COLLECTIONS OF DOCUMENTS192573
-Node: 7_ AGGREGATION WITH INDEPENDENT WORKS193464
-Node: 8_ TRANSLATION194692
-Node: 9_ TERMINATION195595
-Node: 10_ FUTURE REVISIONS OF THIS LICENSE196250
-Node: Addendum197390
+Node: Getting The Source7159
+Node: Releases7365
+Node: Bzr Access7733
+Node: Code Dependencies8482
+Ref: Code Dependency Table9181
+Node: Testing Dependencies35154
+Ref: Testing Dependency Table35463
+Node: Documentation Dependencies39387
+Ref: Documentation Dependency Table39656
+Node: Configuring Gnash48724
+Node: Features51018
+Ref: Configuration Options - Features51618
+Node: Specifying Custom Paths58693
+Ref: Custom Path Options59163
+Node: Compiling the Code70910
+Node: Creating the Documentation71851
+Node: Running the Tests73197
+Node: Using DejaGnu73651
+Node: Increasing Verbosity74014
+Node: Running Some Tests74550
+Node: Running The Tests Manually75370
+Node: Movie tests76032
+Node: ActionScript Unit Tests76382
+Node: Installation76699
+Node: Libraries78012
+Node: Executables78868
+Node: Documentation79738
+Node: Cross Configuring80493
+Node: Software Internals83573
+Node: A Tour of Gnash83842
+Node: The Libraries84408
+Node: libgnashbase84678
+Node: libgnashserver85105
+Node: libgnashmedia85476
+Node: libgnashamf85963
+Node: libgnashbackend86385
+Node: libgnashplugin86700
+Node: libklashpart86906
+Node: The Applications87076
+Node: The Standalone Player87444
+Node: Gprocessor87741
+Node: SOLdumper88133
+Node: Dumpshm88400
+Node: The Plugin88619
+Node: Current Implementation89109
+Node: GUI Support89650
+Node: Mozplugger91339
+Node: Klash93226
+Node: The Message Logging System93776
+Node: Logging System API95333
+Node: The LogFile Instance98167
+Node: Sound handling in Gnash99651
+Node: Sound types100394
+Node: Sound parsing100931
+Node: Sound playback101499
+Node: The SDL sound backend102029
+Node: The Gstreamer backend103330
+Node: Future audio backends104346
+Node: Detailed description of the Gstreamer backend104836
+Node: Testing107087
+Node: Testing Tools107558
+Node: Test Cases108388
+Node: Writing ActionScript Tests108967
+Node: Writing Ming-based self-contained SWF tests111468
+Node: Using Ming-based test generators facilities112625
+Node: Writing self-contained SWF tests with other compilers114985
+Node: Writing Test Runners118110
+Node: Using the generic test runner for self-contained SWF tests119859
+Node: Writing Movie testers121949
+Node: Adding New ActionScript Class123689
+Node: Prototype124869
+Node: Declaration126286
+Node: Instantiation126551
+Node: Methods127178
+Node: Accessing Arguments127569
+Node: Returning a Value to ActionScript127965
+Node: Additional fn_call Members128344
+Node: Dynamic Properties129198
+Node: The as_value Object Type130703
+Node: Data Types131141
+Node: Determining the Type131462
+Node: Fetching the Value131994
+Node: Setting the Value and Type132484
+Node: Further Reading133078
+Node: Object ActionScript Class133493
+Node: The Methods of the Class133833
+Node: The Properties of the Object Class134172
+Node: Object Class Conformance134487
+Node: Reporting Bugs136026
+Node: Get a Fresh Binary Package137009
+Node: Determine if the bug was previously reported137795
+Node: Review the bug writing guidelines138613
+Node: Filing a bug report139664
+Node: Gnash Extensions139947
+Node: Creating A New Extension142194
+Node: Crafting an Extension143612
+Node: Debugging An Extension147914
+Node: Included Extensions149604
+Node: Gtk Extension150048
+Node: File I/O Extension151035
+Node: MySQL Extension152221
+Node: RTMP Protocol153072
+Node: AMF Format162811
+Node: Mozilla/Firefox NPAPI Plugin163781
+Node: Plugin C API164799
+Node: Plugin C++ API166658
+Node: OpenGL and Threads169922
+Node: Plugin Event Handling171250
+Node: Appendix172219
+Node: Code Style172371
+Node: Authors176201
+Node: GNU Free Documentation License176910
+Node: 0_ PREAMBLE177673
+Node: 1_ APPLICABILITY AND DEFINITIONS178979
+Ref: fdl-document179204
+Ref: fdl-modified179495
+Ref: fdl-secondary179682
+Ref: fdl-invariant180327
+Ref: fdl-cover-texts180576
+Ref: fdl-transparent180789
+Ref: fdl-title-page182079
+Node: 2_ VERBATIM COPYING182468
+Node: 3_ COPYING IN QUANTITY183448
+Node: 4_ MODIFICATIONS185805
+Node: 5_ COMBINING DOCUMENTS191865
+Node: 6_ COLLECTIONS OF DOCUMENTS193362
+Node: 7_ AGGREGATION WITH INDEPENDENT WORKS194253
+Node: 8_ TRANSLATION195481
+Node: 9_ TERMINATION196384
+Node: 10_ FUTURE REVISIONS OF THIS LICENSE197039
+Node: Addendum198179
End Tag Table
=== modified file 'doc/C/preformatted/gnash_user.info.in'
--- a/doc/C/preformatted/gnash_user.info.in 2009-02-25 22:33:03 +0000
+++ b/doc/C/preformatted/gnash_user.info.in 2009-03-19 09:13:48 +0000
@@ -1,7 +1,7 @@
+This is gnash_user.info, produced by makeinfo version 4.11 from stdin.
+
START-INFO-DIR-ENTRY
-This is gnash_user.info, produced by makeinfo version 4.11 from
gnash_user.texi.
-
-* Gnash User Manual: (gnash_user). Gnash
+* Gnash User Manual: (gnash_user). [MISSING TEXT]
END-INFO-DIR-ENTRY
@@ -603,6 +603,25 @@
Examples: ?
[undisplayable block
object]
+XVideo on/off If set to _on_, Gnash
+ will attempt to render
+ using the X Video
+ Extension, if system
+ support was found
+ during compilation. By
+ default, X Video
+ rendering is disabled.
+quality [-1|0|1|2|3] Set rendering quality.
+ If set to _-1_, Gnash
+ will use whatever
+ quality set by the
+ movie being run. If
+ set to any value from
+ _0_ to _3_Gnash will
+ lock quality to the
+ specified value (0=low,
+ 1=medium, 2=high,
+ 3=best). Defaults to -1.
The following example `.gnashrc' file allows a user to only play
Flash files saved locally to the machine on which Gnash is running. It
@@ -747,7 +766,7 @@
3.1.2 Software Requirements
---------------------------
-The 0.8.3 release of Gnash has been designed to run on UNIX/Linux
+The 0.8.5 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
@@ -973,7 +992,7 @@
=
ActionScript
- _ActionScript_, or "AS", is the scripting language for _Flash_
+ _ActionScript_, or "AS", is the scripting language for _SWF_
applications. It is compiled to bytecode, which is a subset of the
_SWF_ format.
@@ -984,7 +1003,7 @@
the more feature complete renderer.
AMF
- _AMF_ is the object format used by _Flash_ for shared objects and
+ _AMF_ is the object format used by _SWF_ for shared objects and
streaming video.
as_environment
@@ -1028,8 +1047,8 @@
extensions
A Gnash _extension_ is a plugin (not a browser plugin) which
- implements additional functionality beyond what is covered by
- _Flash_ specification. These are shared libraries which are loaded
+ implements additional functionality beyond what is covered by the
+ _SWF_ specification. These are shared libraries which are loaded
at runtime.
@@ -1042,11 +1061,8 @@
Flash
The term _Flash_ is used to describe both the Adobe IDE for
- creating _SWF_ 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.
+ creating _SWF_ files, and Adobe's player. Flash is a registered
+ trademark belonging to Adobe.
FLV
FLV is a proprietary file format used to deliver Flash video. It
@@ -1105,14 +1121,6 @@
configuration option -enable-kparts.
-L
-=
-
-libmad
- libmad is a mp3-decoding library, which used to be an option for
- Gnash handling of sound (dropped since 0.8.2).
-
-
M
=
@@ -1122,9 +1130,9 @@
'Mesa' interchangeably.
Ming
- Ming is a C library for generating SWF ("Flash") format movies,
- plus a set of wrappers for using the library. It is used by the
- Gnash project for generating testcases.
+ Ming is a C library for generating _SWF_ format movies, plus a set
+ of wrappers for using the library. It is used by the Gnash project
+ for generating testcases.
N
@@ -1237,7 +1245,7 @@
analogy. Graphical elements are referred to as characters.
SWF
- _SWF_ is the file format for _Flash_ movies.
+ _SWF_ is the generic name for _Flash_ movies.
T
@@ -1286,8 +1294,8 @@
File: gnash_user.info, Node: GNU Free Documentation License, Prev: Authors,
Up: Top
-Anhang A GNU Free Documentation License
-***************************************
+Appendix A GNU Free Documentation License
+*****************************************
* Menu:
@@ -1713,7 +1721,7 @@
the License in the document and put the following copyright and license
notices just after the title page:
- Copyright 2008, 2009 Free Software Foundation.
+ Copyright 2008, Free Software Foundation.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -1733,72 +1741,71 @@
Tag Table:
-Node: Top166
-Node: Introduction1471
-Node: Audience2268
-Node: What Is Supported?2596
-Node: Using Gnash5104
-Node: Gnash Command Line Options6540
-Ref: Gnash Command Line Options <1>6894
-Node: Gnash Interactive Control Keys12935
-Ref: Gnash Interactive Control Keys <1>13302
-Node: User Configuration File14051
-Ref: User Configuration Variables14836
-Node: Installing and Configuring Gnash34619
-Node: Requirements34980
-Node: Hardware Requirements35301
-Ref: Build Matrix36078
-Node: Software Requirements37308
-Node: Downloading Gnash38141
-Node: Getting the Source38776
-Node: Releases39136
-Node: Snapshot39694
-Node: Repository40165
-Node: Getting Codec Support40986
-Node: Reporting Bugs41703
-Node: Get a Fresh Binary Package42693
-Node: Determine if the bug was previously reported43480
-Node: Review the bug writing guidelines44299
-Node: Filing a bug report45351
-Node: Glossary45635
-Ref: A45749
-Ref: C46573
-Ref: D46859
-Ref: E47271
-Ref: F47511
-Ref: G48584
-Ref: K49569
-Ref: L49929
-Ref: M50065
-Ref: N50424
-Ref: O50581
-Ref: P51196
-Ref: Q51483
-Ref: R51667
-Ref: S52908
-Ref: T54394
-Ref: X55102
-Node: Authors55195
-Node: GNU Free Documentation License55905
-Node: 0_ PREAMBLE56665
-Node: 1_ APPLICABILITY AND DEFINITIONS57972
-Ref: fdl-document58198
-Ref: fdl-modified58489
-Ref: fdl-secondary58676
-Ref: fdl-invariant59321
-Ref: fdl-cover-texts59570
-Ref: fdl-transparent59783
-Ref: fdl-title-page61073
-Node: 2_ VERBATIM COPYING61462
-Node: 3_ COPYING IN QUANTITY62443
-Node: 4_ MODIFICATIONS64801
-Node: 5_ COMBINING DOCUMENTS70862
-Node: 6_ COLLECTIONS OF DOCUMENTS72360
-Node: 7_ AGGREGATION WITH INDEPENDENT WORKS73252
-Node: 8_ TRANSLATION74481
-Node: 9_ TERMINATION75385
-Node: 10_ FUTURE REVISIONS OF THIS LICENSE76041
-Node: Addendum77182
+Node: Top165
+Node: Introduction1470
+Node: Audience2267
+Node: What Is Supported?2595
+Node: Using Gnash5103
+Node: Gnash Command Line Options6539
+Ref: Gnash Command Line Options <1>6893
+Node: Gnash Interactive Control Keys12934
+Ref: Gnash Interactive Control Keys <1>13301
+Node: User Configuration File14050
+Ref: User Configuration Variables14835
+Node: Installing and Configuring Gnash35967
+Node: Requirements36328
+Node: Hardware Requirements36649
+Ref: Build Matrix37426
+Node: Software Requirements38656
+Node: Downloading Gnash39489
+Node: Getting the Source40124
+Node: Releases40484
+Node: Snapshot41042
+Node: Repository41513
+Node: Getting Codec Support42334
+Node: Reporting Bugs43051
+Node: Get a Fresh Binary Package44041
+Node: Determine if the bug was previously reported44828
+Node: Review the bug writing guidelines45647
+Node: Filing a bug report46699
+Node: Glossary46983
+Ref: A47097
+Ref: C47917
+Ref: D48203
+Ref: E48615
+Ref: F48857
+Ref: G49742
+Ref: K50727
+Ref: M51087
+Ref: N51438
+Ref: O51595
+Ref: P52210
+Ref: Q52497
+Ref: R52681
+Ref: S53922
+Ref: T55409
+Ref: X56117
+Node: Authors56210
+Node: GNU Free Documentation License56920
+Node: 0_ PREAMBLE57684
+Node: 1_ APPLICABILITY AND DEFINITIONS58991
+Ref: fdl-document59217
+Ref: fdl-modified59508
+Ref: fdl-secondary59695
+Ref: fdl-invariant60340
+Ref: fdl-cover-texts60589
+Ref: fdl-transparent60802
+Ref: fdl-title-page62092
+Node: 2_ VERBATIM COPYING62481
+Node: 3_ COPYING IN QUANTITY63462
+Node: 4_ MODIFICATIONS65820
+Node: 5_ COMBINING DOCUMENTS71881
+Node: 6_ COLLECTIONS OF DOCUMENTS73379
+Node: 7_ AGGREGATION WITH INDEPENDENT WORKS74271
+Node: 8_ TRANSLATION75500
+Node: 9_ TERMINATION76404
+Node: 10_ FUTURE REVISIONS OF THIS LICENSE77060
+Node: Addendum78201
End Tag Table
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Gnash-commit] /srv/bzr/gnash/trunk r10725: preformatted info and manual pages regenerated,
Sandro Santilli <=