[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnash-commit] gnash ChangeLog doc/C/Makefile.am doc/C/appendi...
|
From: |
Rob Savoye |
|
Subject: |
[Gnash-commit] gnash ChangeLog doc/C/Makefile.am doc/C/appendi... |
|
Date: |
Sat, 01 Mar 2008 21:14:07 +0000 |
CVSROOT: /sources/gnash
Module name: gnash
Changes by: Rob Savoye <rsavoye> 08/03/01 21:14:07
Modified files:
. : ChangeLog
doc/C : Makefile.am appendix.xml gnashref.xml
doc/C/refmanual: code_dependencies.xml codestyle.xml
configuration.xml install.xml internals.xml
logging.xml new_as_class.xml object.xml
plugin.xml
doc/C/refmanual/extensions: extensions.xml
Removed files:
doc/C : fileext.xml gnash.xml gtkext.xml
Log message:
* doc/C/refmanual/logging.xml: Add new log_*() functions. Mark
C++
streaming API as discouraged.
* doc/C/Makefile.am: Add extra dependencies for the gnash
reference manual, now that it's back to life.
* doc/C/appendix.xml: Don't include RTMP chapter here.
* doc/C/refmanual/codestyle.xml: Don't include RTMP chapter
here. Drop useless opcode section.
* doc/C/gnashref.xml: Rearrange top level chapters.
* doc/C/refmanual/configuration.xml: Don't include
featureoptions
or custompath here anymore.
* doc/C/refmanual/internals.xml: Update to match reality. Add
new
utilities.
* doc/C/refmanual/new_as_class.xml: Include asvaluie section
here
too.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnash/ChangeLog?cvsroot=gnash&r1=1.5769&r2=1.5770
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/Makefile.am?cvsroot=gnash&r1=1.55&r2=1.56
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/appendix.xml?cvsroot=gnash&r1=1.12&r2=1.13
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/gnashref.xml?cvsroot=gnash&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/fileext.xml?cvsroot=gnash&r1=1.2&r2=0
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/gnash.xml?cvsroot=gnash&r1=1.52&r2=0
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/gtkext.xml?cvsroot=gnash&r1=1.1&r2=0
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/refmanual/code_dependencies.xml?cvsroot=gnash&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/refmanual/codestyle.xml?cvsroot=gnash&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/refmanual/configuration.xml?cvsroot=gnash&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/refmanual/install.xml?cvsroot=gnash&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/refmanual/internals.xml?cvsroot=gnash&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/refmanual/logging.xml?cvsroot=gnash&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/refmanual/new_as_class.xml?cvsroot=gnash&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/refmanual/object.xml?cvsroot=gnash&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/refmanual/plugin.xml?cvsroot=gnash&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/refmanual/extensions/extensions.xml?cvsroot=gnash&r1=1.1&r2=1.2
Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/gnash/gnash/ChangeLog,v
retrieving revision 1.5769
retrieving revision 1.5770
diff -u -b -r1.5769 -r1.5770
--- ChangeLog 1 Mar 2008 16:37:56 -0000 1.5769
+++ ChangeLog 1 Mar 2008 21:14:04 -0000 1.5770
@@ -1,8 +1,35 @@
2008-03-01 Rob Savoye <address@hidden>
+ * doc/C/refmanual/logging.xml: Add new log_*() functions. Mark C++
+ streaming API as discouraged.
+ * doc/C/Makefile.am: Add extra dependencies for the gnash
+ reference manual, now that it's back to life.
+ * doc/C/appendix.xml: Don't include RTMP chapter here.
+ * doc/C/refmanual/codestyle.xml: Don't include RTMP chapter
+ here. Drop useless opcode section.
+ * doc/C/gnashref.xml: Rearrange top level chapters.
+ * doc/C/refmanual/configuration.xml: Don't include featureoptions
+ or custompath here anymore.
+ * doc/C/refmanual/internals.xml: Update to match reality. Add new
+ utilities.
+ * doc/C/refmanual/new_as_class.xml: Include asvaluie section here
+ too.
+
+ * doc/C/refmanual/building.xml, code_dependencies.xml,
+ configuration.xml, cross_compiling.xml,
+ custompath_configuration.xml, documentation_dependencies.xml,
+ feature_configuration.xml, testing_dependencies.xml: Updated to
+ match reality.
+
+ * doc/C/refmanual/new_as_class.xml: changes to a chapter. Merge
+ main.xml into body. Include as_value.xml from here.
+ * doc/C/refmanual/as_value.xml: Make a sect1 for new_as_class.
+
* doc/C/Makefile.am: Tweak dependencies for the info files, as
they go through a name transformation, which is unfortunately
- different between Ubuntu and Fedora.
+ different between Ubuntu and Fedora. Additional tweaks for Ubuntu
+ Hardy, the .texi names don't get transformed during this step for
+ this version of the docbook tools.
2008-03-01 Rob Savoye <address@hidden>
@@ -22,7 +49,7 @@
* doc/C/gnashref.xml: New reference manual top level page. This
contains much of what was in the old manual.
* asspec/*: Move to BackLash directory.
- * doc/C/Makefile.am: don't klist asspec files. Add directory for
+ * doc/C/Makefile.am: don't list asspec files. Add directory for
installing html file. Add separate variables for the user manual
and the reference manual. Get rid of the useless
entities. variable. Drop include xmlmake and omfmake, fix tghe
Index: doc/C/Makefile.am
===================================================================
RCS file: /sources/gnash/gnash/doc/C/Makefile.am,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -b -r1.55 -r1.56
--- doc/C/Makefile.am 1 Mar 2008 16:51:50 -0000 1.55
+++ doc/C/Makefile.am 1 Mar 2008 21:14:04 -0000 1.56
@@ -78,12 +78,16 @@
$(XML_MAIN:.xml=.info)
#noinst_SCRIPT = gen-doc.sh
+# We list the texi and info pages twice, as differing versions of the
+# docbook-utils transform the name at different steps in the process.
+# This is an easy way to handle it either way, since we only need it as
+# dependency anyway.
dist_man_MANS = gnash.1 gprocessor.1 dumpshm.1 soldumper.1 cygnal.1
MANSRC = $(dist_man_MANS:.1=.man-xml)
-INFOS = gnash_user.info gnashuser.info # gnash_ref.info
+INFOS = gnash_user.info gnashuser.info gnash_ref.info gnashref.info
HTMLS = $(XML_MAIN:.xml=.html)
PDFS = $(XML_MAIN:.xml=.pdf)
-TEXIS = gnash_user.texi gnashuser.texi
+TEXIS = gnash_user.texi gnashuser.texi gnash_ref.texi gnashref.texi
# dist_html_DATA = gnash.html actionscript.html
# dist_info_DATA = gnash.info actionscript.info
Index: doc/C/appendix.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/appendix.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- doc/C/appendix.xml 4 Dec 2006 19:12:39 -0000 1.12
+++ doc/C/appendix.xml 1 Mar 2008 21:14:05 -0000 1.13
@@ -122,8 +122,6 @@
</para>
</sect2>
- &rtmp;
-
<!--
<sect2 id="opcodes">
<title>Shockwave Movie Opcodes</title>
Index: doc/C/gnashref.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/gnashref.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- doc/C/gnashref.xml 1 Mar 2008 14:47:16 -0000 1.1
+++ doc/C/gnashref.xml 1 Mar 2008 21:14:06 -0000 1.2
@@ -20,7 +20,7 @@
<!ENTITY plugin SYSTEM "refmanual/plugin.xml">
<!ENTITY memory SYSTEM "refmanual/memory.xml">
<!ENTITY newasclass SYSTEM "refmanual/new_as_class.xml">
-
+ <!ENTITY asvalue SYSTEM "refmanual/as_value.xml">
<!ENTITY revisionhistory SYSTEM "refmanual/revisions.xml">
<!ENTITY specification SYSTEM "refmanual/specification.xml">
<!ENTITY installation SYSTEM "refmanual/installation.xml">
@@ -88,18 +88,26 @@
&introduction;
<!-- ============= Document Body ============================= -->
- &sources;
- &install;
- &configuration;
- &codedependencies;
- &testdependencies;
- &docdependencies;
- &newasclass;
- &logging;
+
+<!-- This chapter includes all the other sections used to document how to
+ configure and compile Gnash. -->
+ &building;
+
+<!-- This chapter includes all the other sections used to document the
+ internals of how Gnash works. -->
&internals;
+
&extensions;
+
+
+<!-- This chapter includes all the other sections used to document
+ protocols and formats used by Gnash. -->
+
&rtmp;
&plugin;
+
+ <!-- The appendix. Nobody reads these coding style suggestions
+ anyway -->
&codestyle;
<!-- ============= Authors =================================== -->
Index: doc/C/refmanual/code_dependencies.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/refmanual/code_dependencies.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- doc/C/refmanual/code_dependencies.xml 1 Mar 2008 19:47:09 -0000
1.2
+++ doc/C/refmanual/code_dependencies.xml 1 Mar 2008 21:14:06 -0000
1.3
@@ -1,4 +1,4 @@
-<sect1 id="codedep">
+<sect1 id="dependencies">
<title>Code Dependencies</title>
<para>
Index: doc/C/refmanual/codestyle.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/refmanual/codestyle.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- doc/C/refmanual/codestyle.xml 1 Mar 2008 15:15:29 -0000 1.1
+++ doc/C/refmanual/codestyle.xml 1 Mar 2008 21:14:06 -0000 1.2
@@ -122,46 +122,6 @@
</para>
</sect2>
- &rtmp;
-
-<!--
- <sect2 id="opcodes">
- <title>Shockwave Movie Opcodes</title>
-
- <sect3 id="v5">
- <title>Version 5</title>
- <para>
- FIXME:
- </para>
- </sect3>
- <sect3 id="v6">
- <title>Version 6</title>
- <para>
- FIXME:
- </para>
- </sect3>
- <sect3 id="v7">
- <title>Version 7</title>
- <para>
- FIXME:
- </para>
- </sect3>
- <sect3 id="v8">
- <title>Version 8</title>
- <para>
- FIXME:
- </para>
- </sect3>
- <sect3 id="v9">
- <title>Version 9</title>
- <para>
- FIXME:
- </para>
- </sect3>
-
- </sect2>
--->
-
</sect1>
Index: doc/C/refmanual/configuration.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/refmanual/configuration.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- doc/C/refmanual/configuration.xml 1 Mar 2008 19:47:09 -0000 1.2
+++ doc/C/refmanual/configuration.xml 1 Mar 2008 21:14:06 -0000 1.3
@@ -70,12 +70,8 @@
overdriving &app;'s ability to do the right thing.
</para>
- <sect2 id="features">
&featureoptions;
- </sect2>
- <sect2 id="custompath">
&custompath;
- </sect2>
</sect1>
Index: doc/C/refmanual/install.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/refmanual/install.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- doc/C/refmanual/install.xml 1 Mar 2008 16:59:30 -0000 1.1
+++ doc/C/refmanual/install.xml 1 Mar 2008 21:14:06 -0000 1.2
@@ -1,14 +1,18 @@
-<title>Installation</title>
+<sect1 id="install">
+ <title>Installation</title>
-<para>
-Now that &app; has been compiled and tested, use the following command to
install it:
+ <para>
+ Now that &app; has been compiled and tested, use the following command to
install it:
<programlisting>
make install
</programlisting>
-The above command installs the standalone player. If the correct files were
found by <command>configure</command> and if the
<option>--disable-plugin</option> option was not specified, the &app; browser
plugin is also installed.
-</para>
+ The above command installs the standalone player. If the correct
+ files were found by <command>configure</command> and if the
+ <option>--disable-plugin</option> option was not specified, the
+ &app; browser plugin is also installed.
+ </para>
-<para>
+ <para>
&app; installs a number of <link linkend="libinstall">libraries</link>,
namely: <emphasis>libbase</emphasis>,
<emphasis>libgeometry</emphasis>, <emphasis>libbackend</emphasis>,
@@ -21,17 +25,17 @@
<emphasis>--prefix</emphasis> <link linkend="custompath">configure
option</link>, except for plugins, which are explicitly set with
<emphasis>--plugin-dir</emphasis>.
-</para>
+ </para>
-<para>
+ <para>
Note that if you are using a single file-system <emphasis>NFS</emphasis>
mounted to multiple platforms, the
<link linkend="custompath">configuration option</link>
<emphasis>--exec-prefix</emphasis> may be used to specify where
platform-dependent executables and libraries are installed.
-</para>
+ </para>
-<sect2 id="libinstall">
+ <sect2 id="libinstall">
<title>Libraries</title>
<para>
@@ -60,9 +64,9 @@
run <emphasis>ldconfig</emphasis> as root to update the runtime
cache.
</para>
-</sect2>
+ </sect2>
-<sect2 id="appinstall">
+ <sect2 id="appinstall">
<title>Executables</title>
<para>
@@ -84,9 +88,9 @@
If no path was specified, the default is
<filename>/usr/local/bin</filename>.
</para>
-</sect2>
+ </sect2>
-<sect2 id="docinstall">
+ <sect2 id="docinstall">
<title>Documentation</title>
<para>
@@ -99,7 +103,7 @@
<command>man</command> and <command>info</command>
are installed in <filename>/usr/local/share/man</filename>
and <filename>/usr/local/share/info</filename> respectively, unless
- the <option>--mandif</option> or <option>--infodir</option>
+ the <option>--mandir</option> or <option>--infodir</option>
<link linkend="custompath">configuration options</link> are used.
</para>
@@ -111,4 +115,5 @@
which menu item &app; appears in the <emphasis>GNOME help</emphasis>
system.
</para>
-</sect2>
+ </sect2>
+</sect1>
Index: doc/C/refmanual/internals.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/refmanual/internals.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- doc/C/refmanual/internals.xml 1 Mar 2008 15:15:29 -0000 1.1
+++ doc/C/refmanual/internals.xml 1 Mar 2008 21:14:06 -0000 1.2
@@ -1,117 +1,117 @@
-<sect1 id="internals">
+<chapter id="internals">
<title>Software Internals</title>
- <sect2 id="tour">
+ <sect1 id="tour">
<title>A Tour of Gnash</title>
<para>
The top level of Gnash has several libraries,
<emphasis>libgnashbase</emphasis>,
<emphasis>libgnashgeo</emphasis>, <emphasis>libgnashserver</emphasis>,
<emphasis>libgnashasobjs</emphasis> and
- <emphasis>libgnashbackend</emphasis>. There are two utility programs
- included for debug parsing and processing of Flash movie files
- which test the Actionscript interpreter. There is also a standalone
- flash movie player.
+ <emphasis>libgnashbackend</emphasis>. 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.
</para>
- <sect3 id="The Libraries">
+ <sect2 id="The Libraries">
<title>The Libraries</title>
- <sect4 id="libbase">
+ <sect3 id="libbase">
<title>libgnashbase</title>
<para>
Libgnashbase contains support classes used by the rest of the
- code. Among these classes is a small and efficient STL library
- clone that uses smart pointers. A current goal is to replace
- this small STL clone with standard STL containers to reduce
- the amount of code which has to be maintained, and to add
- functionality not currently in the smaller
- implementation.
+ code.This library has no dependencies on any of the other
+ &app; libraries.
</para>
<para>
- Gnash makes heavy use of smart pointers, so memory allocations
- are freed up automatically by the interpreter.
+ &app; makes heavy use of smart pointers, so memory allocations
+ are freed up automatically by the interpreter. Both STL and
+ Boost smart pointers are used.
</para>
- </sect4>
+ </sect3>
- <sect4 id="libgnashgeo">
+ <sect3 id="libgnashgeo">
<title>libgnashgeo</title>
<para>
Libgnashgeo contains code for device independent graphics routines.
</para>
- </sect4>
+ </sect3>
- <sect4 id="libgnashgui">
+ <sect3 id="libgnashgui">
<title>libgnashgui</title>
<para>
Libgnashgui contains code for a portable GUI class that
- supports using GTK2, a framebuffer, SDL, or KDE.
+ supports using GTK2, a framebuffer, SDL, or KDE, FLTK, or Aqua.
</para>
- </sect4>
+ </sect3>
- <sect4 id="libgnashserver">
+ <sect3 id="libgnashserver">
<title>libgnashserver</title>
<para>
Libgnashserver is the guts of the interpreter itself. This is where
- the main code for the interpreter lives.
+ 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.
</para>
- </sect4>
+ </sect3>
- <sect4 id="libgnashasobjs">
+ <sect3 id="libgnashasobjs">
<title>libgnashasobjs</title>
<para>
Libgnashasobjs contains all the ActionScript classes used by
the interpreter.
</para>
- </sect4>
+ </sect3>
- <sect4 id="libgnashamf">
+ <sect3 id="libgnashamf">
<title>libgnashamf</title>
<para>
- AMF is the data format used internally by Flash. This is
- Gnash's support library to handle AMF data. This is
- currently unused, but when the LocalConnection class is more
- fully implemented, this will be used to transfer data
- between flash movies.
+ AMF is the data format used internally by SWF files. This is
+ Gnash's support library to handle AMF data. This is used by
+ the ActionScript classes SharedObject and
+ LocalConnection. This is also used by the NetStream class
+ when using thre RTMP streaming network protocol.
</para>
- </sect4>
+ </sect3>
- <sect4 id="libgnashbackend">
+ <sect3 id="libgnashbackend">
<title>libgnashbackend</title>
<para>
- Libgnashbackend is a small library containing OpenGL and SDL
- code that glues this display to the Gnash display.
+ Libgnashbackend is a library containing the rendering
+ code that glues this display to the Gnash. Supported
+ rendering backends are OpenGL, Cairo, and AGG.
</para>
- </sect4>
- <sect4 id="libgnashpluin">
+ </sect3>
+ <sect3 id="libgnashpluin">
<title>libgnashplugin</title>
<para>
Libgnashplugin is the Mozilla/Firefox plugin.
</para>
- </sect4>
- <sect4 id="libklashpart">
+ </sect3>
+ <sect3 id="libklashpart">
<title>libklashpart</title>
<para>
Libklashpart is the Konqueror plugin.
</para>
- </sect4>
</sect3>
+ </sect2>
- <sect3 id="apps">
+ <sect2 id="apps">
<title>The Applications</title>
<para>
@@ -120,30 +120,18 @@
movies.
</para>
- <sect4 id="Gnash">
+ <sect3 id="Gnash">
<title>The Standalone Player</title>
<para>
This is the standalone OpenGL back-end used to play
movies. There are several command-line options and keyboard
- control keys used by Gnash which <link linkend="usage"> are
- documented here.</link>
+ control keys used by Gnash.
</para>
- </sect4>
-
- <sect4 id="parser">
- <title>Gparser</title>
-
- <para>
- Gparser uses the Gnash parser to disassemble the flash
- movie, and dumps the object types, the depth, and other
- information to make sure Gnash is parsing the file
- correctly.
- </para>
+ </sect3>
- </sect4>
- <sect4 id="processor">
+ <sect3 id="processor">
<title>Gprocesser</title>
<para>
@@ -154,29 +142,40 @@
loading of files.
</para>
- </sect4>
</sect3>
+ <sect3 id="soldumper">
+ <title>SOLdumper</title>
+
+ <para>
+ SOLDumper is a utility program used to find and dump the
+ content of <emphasis>Local Shared Objects</emphasis>, also
+ called "Flash Cookies" by some.
+ </para>
+
+ </sect3>
+ <sect3 id="dumpshm">
+ <title>Dumpshm</title>
- <sect3 id="plugin">
+ <para>
+ Dumpshm is a program used to find and dump the contents of
+ the <emphasis>LocalConnection</emphasis> shared memory segment.
+ </para>
+
+ </sect3>
+ </sect2>
+
+ <sect2 id="plugin">
<title>The Plugin</title>
<para>
The plugin is designed to work within Mozilla or Firefox,
although there is Konqueror support as well. The plugin uses
- the Mozilla NSPR plugin API to be cross platform, and is
+ the Mozilla NSAPI plugin API to be cross platform, and is
portable, as well as being well integrated into Mozilla based
browsers.
</para>
- <para>
- One future thought for the plugin is to use the new Firefox
- 1.0.5 or greater version of Firefox. This version has added a
- GTK drawable window which supports hardware acceleration, and
- is designed to support things like rendering directly into the
- window without needing OpenGL.
- </para>
-
- <sect4 id="pluginstatus">
+ <sect3 id="pluginstatus">
<title>Current Status</title>
<para>
As of March 30, 2006, the plugin works! This works in a
@@ -187,14 +186,12 @@
itself is not thread safe at this time.
</para>
<para>
- There are a few limitations in the current implementation,
- but it works well enough to be used for web surfing. The
- main limitations are the SDL version has no event handling,
- and sound doesn't work yet.
+ As of Jan, 2007, streaming video, ala "YouTube"
+ works, along with other video sharing sites.
</para>
- </sect4>
+ </sect3>
- <sect4 id="gui">
+ <sect3 id="gui">
<title>GUI Support</title>
<para>
@@ -206,11 +203,8 @@
</para>
<para>
- Gnash can use either SDL or GTK now to create the window,
- and to handle events for the standalone player. Work is
- underway to add a portable interface for more windowing
- toolkits to allow better embedded device support when
- running in framebuffer only devices.
+ Gnash can use either several different GUI toolkits to create the
window,
+ and to handle events for the standalone player.
</para>
<para>
@@ -247,9 +241,9 @@
way the existing keyboard commands do.
</para>
- </sect4>
+ </sect3>
- <sect4 id="mozplugger">
+ <sect3 id="mozplugger">
<title>Mozplugger</title>
<para>
@@ -307,9 +301,9 @@
mozplugger. You should see an entry for Gnash now.
</para>
- </sect4>
+ </sect3>
- <sect4 id="Klash">
+ <sect3 id="Klash">
<title>Klash</title>
<para>
Klash is MozPlugger type support for KDE's Konqueror web
@@ -325,38 +319,15 @@
configuring. Other than installing, there is nothing else
that needs to be done to install Klash.
</para>
- </sect4>
-
- &plugin;
-
</sect3>
- &logging;
-
</sect2>
- <sect2 id="engine">
- <title>The Interpreter Engine</title>
- <para>
- FIXME:
- </para>
-
- <sect3 id="loop">
- <title>The Main Loop</title>
- <para>
- FIXME:
- </para>
- </sect3>
+ &logging;
- <sect3 id="io">
- <title>I/O Processing</title>
- <para>
- FIXME:
- </para>
- </sect3>
- </sect2>
+ </sect1>
- <sect2 id="soundhandlers">
+ <sect1 id="soundhandlers">
<title>Sound handling in Gnash</title>
<para>
@@ -373,7 +344,7 @@
configured, for instance to block sound from advertisements.
</para>
- <sect3 id="soundtypes">
+ <sect2 id="soundtypes">
<title>Sound types</title>
<para>
Sounds can be divided into two groups: event-sounds and soundstreams.
@@ -383,9 +354,9 @@
gotoframe-action jumps to a frame which contains data for a soundstream,
playback of the stream can be picked up from there.
</para>
- </sect3>
+ </sect2>
- <sect3 id="soundparsing">
+ <sect2 id="soundparsing">
<title>Sound parsing</title>
<para>
When Gnash parses a SWF-file, it creates a sound handler if possible
@@ -395,9 +366,9 @@
SWF-file has been parsed. But since the entire soundstream doesn't need
to be present when playback starts, it is not necessary to wait.
</para>
- </sect3>
+ </sect2>
- <sect3 id="soundplayback">
+ <sect2 id="soundplayback">
<title>Sound playback</title>
<para>
When a sound is about to be played Gnash calls the sound handler, which
@@ -407,9 +378,9 @@
means that we have to trust both the graphic backend and the audio
backend to play at correct speed.
</para>
- </sect3>
+ </sect2>
- <sect3 id="sdlsound">
+ <sect2 id="sdlsound">
<title>The SDL sound backend</title>
<para>
The current SDL sound backend has replaced the original sound
@@ -431,9 +402,9 @@
while its only real disadvantage is that it has to be compiled with
MP3 support, which some Linux distributions will probably not like...
</para>
- </sect3>
+ </sect2>
- <sect3 id="gstreamer">
+ <sect2 id="gstreamer">
<title>The Gstreamer backend</title>
<para>
The Gstreamer backend, though not complete, supports both soundstreams
@@ -449,9 +420,9 @@
it has longer "reply delay" when starting the playback of a sound, and
it suffers under some bugs in Gstreamer that are yet to be fixed.
</para>
- </sect3>
+ </sect2>
- <sect3 id="audio-future">
+ <sect2 id="audio-future">
<title>Future audio backends</title>
<para>
It would probably be desirable to make more backends in the future,
@@ -459,9 +430,9 @@
attention, or perhaps because an internal sound handling is better
suited for embedded platform with limited software installed.
</para>
- </sect3>
+ </sect2>
- <sect3 id="gstreamer-details">
+ <sect2 id="gstreamer-details">
<title>Detailed description of the Gstreamer backend</title>
<para>
Gstreamer uses pipelines, bins and elements. Pipelines are the
@@ -524,12 +495,12 @@
the adder in rapid succession, which causes to adder to "die" and stop
the playback.
</para>
- </sect3>
+ </sect2>
- </sect2>
+ </sect1>
- <sect2 id="testing">
+ <sect1 id="testing">
<title>Testing </title>
<para>
@@ -537,7 +508,7 @@
can be found in the section on building Gnash.
</para>
- <sect3 id="testtools">
+ <sect2 id="testtools">
<title>Testing Tools</title>
<para>
@@ -566,9 +537,9 @@
<ulink type="http" url="http://www.samba.org";>Samba</ulink>.
</para>
- </sect3>
+ </sect2>
- <sect3 id="testcases">
+ <sect2 id="testcases">
<title>Test Cases</title>
<para>
@@ -582,9 +553,9 @@
kind of tests.
</para>
- </sect3>
+ </sect2>
- <sect3 id="writeastests">
+ <sect2 id="writeastests">
<title>Writing ActionScript Tests</title>
<para>
@@ -669,9 +640,9 @@
</programlisting>
</para>
- </sect3>
+ </sect2>
- <sect3 id="writemingtests">
+ <sect2 id="writemingtests">
<title>Writing Ming-based self-contained SWF tests</title>
<para>
@@ -697,7 +668,7 @@
url="http://www.libming.org/";>http://www.libming.org</ulink>.
</para>
- <sect4 id="ming_testgenerator_facilities">
+ <sect3 id="ming_testgenerator_facilities">
<title>Using Ming-based test generators facilities</title>
<para>
@@ -768,11 +739,11 @@
</para>
- </sect4>
-
</sect3>
- <sect3 id="writing_dejagnu_so_tests">
+ </sect2>
+
+ <sect2 id="writing_dejagnu_so_tests">
<title>Writing self-contained SWF tests with other compilers</title>
<para>
@@ -852,9 +823,9 @@
for information about writing a test runners for your self-contained
tests.
</para>
- </sect3>
+ </sect2>
- <sect3 id="writing_test_runners">
+ <sect2 id="writing_test_runners">
<title>Writing Test Runners</title>
<para>
@@ -989,7 +960,7 @@
</informaltable>
</para>
- <sect4 id="generic_test_runner">
+ <sect3 id="generic_test_runner">
<title>Using the generic test runner for self-contained SWF
tests</title>
<para>
@@ -1041,9 +1012,9 @@
When both -f and -r are given, the first exit condition reached will
take effect.
</para>
- </sect4>
+ </sect3>
- <sect4 id="writing_movie_testers">
+ <sect3 id="writing_movie_testers">
<title>Writing Movie testers</title>
<para>
@@ -1088,8 +1059,12 @@
to implement a Movie tester for it. Some knowledge about the
expected behavior suffices.
</para>
- </sect4>
</sect3>
</sect2>
-</sect1>
+ </sect1>
+
+ &newasclass;
+
+
+</chapter>
Index: doc/C/refmanual/logging.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/refmanual/logging.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- doc/C/refmanual/logging.xml 1 Mar 2008 15:15:30 -0000 1.1
+++ doc/C/refmanual/logging.xml 1 Mar 2008 21:14:06 -0000 1.2
@@ -17,12 +17,6 @@
</para>
<para>
- It became apparent one day the callback was never needed, and I
- got tired of having to use <emphasis>c_str()</emphasis> on string data
- just to print them out.
- </para>
-
- <para>
If a filename is not specified at object construction time, a
default name of <emphasis>gnash-dbg.log</emphasis> is used. If Gnash is
started from the command line, the debug log will be created in
@@ -39,6 +33,13 @@
command line. You can also disable the creation of the debug log.
</para>
+ <para>
+ 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.
+ </para>
+
<sect3 id="capi">
<title>Logging System C API</title>
@@ -53,26 +54,88 @@
<variablelist>
<varlistentry>
- <term>void log_msg(const char* fmt, ...)</term>
+ <term>log_error(const char* fmt, ...)</term>
<listitem>
<para>
- Display a message if verbose output is enabled. By default
- the messages are always written to the disk file, but
- optionally displayed in the terminal.
+ 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.
</para>
</listitem>
</varlistentry>
+
<varlistentry>
- <term>log_error(const char* fmt, ...)</term>
+ <term>void log_unimpl</term>
<listitem>
<para>
- 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.
+ 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.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>void log_trace</term>
+ <listitem>
+ <para>
+ Used only for explicit user traces
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>void log_debug</term>
+ <listitem>
+ <para>
+ Logs debug information.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>void log_action</term>
+ <listitem>
+ <para>
+ 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.
</para>
</listitem>
</varlistentry>
<varlistentry>
+ <term>void log_parse</term>
+ <listitem>
+ <para>
+ 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.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>void log_security</term>
+ <listitem>
+ <para>
+ Display a message with security related information.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>void log_swferror</term>
+ <listitem>
+ <para>
+ 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.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
<term>log_warning(const char* fmt, ...)</term>
<listitem>
<para>
@@ -137,17 +200,6 @@
<variablelist>
<varlistentry>
- <term>openLog(const char *filespec)</term>
- <listitem>
- <para>
- Open the debug file with the name specified by
- <emphasis>filespec</emphasis>. This file goes in the current
- directory, or your home directory if using a menu based
- launcher.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
<term>closeLog(void)</term>
<listitem>
<para>
Index: doc/C/refmanual/new_as_class.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/refmanual/new_as_class.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- doc/C/refmanual/new_as_class.xml 1 Mar 2008 17:25:15 -0000 1.2
+++ doc/C/refmanual/new_as_class.xml 1 Mar 2008 21:14:06 -0000 1.3
@@ -212,6 +212,7 @@
</sect1>
&asvalue;
+ &object;
</chapter>
Index: doc/C/refmanual/object.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/refmanual/object.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- doc/C/refmanual/object.xml 1 Mar 2008 15:15:30 -0000 1.1
+++ doc/C/refmanual/object.xml 1 Mar 2008 21:14:07 -0000 1.2
@@ -1,11 +1,11 @@
-<sect4 id="asobject">
+<sect1 id="asobject">
<title>Object ActionScript Class</title>
<para>
This class implements an Object object.
</para>
- <sect5 id="objectmethods">
+ <sect2 id="objectmethods">
<title>The Methods of the Class</title>
<para>
<variablelist>
@@ -91,8 +91,8 @@
</varlistentry>
</variablelist>
</para>
- </sect5>
- <sect5 id="objectprops">
+ </sect2>
+ <sect2 id="objectprops">
<title>The Properties of the Object Class</title>
<para>
@@ -140,9 +140,9 @@
</variablelist>
</para>
- </sect5>
+ </sect2>
- <sect5 id="objectconf">
+ <sect2 id="objectconf">
<title>Object Class Conformance</title>
<para>
@@ -314,5 +314,5 @@
</tgroup>
</informaltable>
</para>
- </sect5>
-</sect4>
+ </sect2>
+</sect1>
Index: doc/C/refmanual/plugin.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/refmanual/plugin.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- doc/C/refmanual/plugin.xml 1 Mar 2008 15:15:30 -0000 1.1
+++ doc/C/refmanual/plugin.xml 1 Mar 2008 21:14:07 -0000 1.2
@@ -1,5 +1,5 @@
-<sect4 id="mozplugin">
- <title>Mozilla/Firefox Plugin</title>
+<chapter id="nsapi">
+ <title>Mozilla/Firefox NSAPI Plugin</title>
<para>
The Mozilla SDK has two API layers for plugins. The older layer is
@@ -24,7 +24,7 @@
typically called once for each plugin that is loaded.
</para>
- <sect5 id="plugincapi">
+ <sect1 id="plugincapi">
<title>Plugin C API</title>
<para>
@@ -113,9 +113,9 @@
</listitem>
</varlistentry>
</variablelist>
- </sect5>
+ </sect1>
- <sect5 id="plugincppapi">
+ <sect1 id="plugincppapi">
<title>Plugin C++ API</title>
<para>
@@ -283,9 +283,9 @@
</listitem>
</varlistentry>
</variablelist>
- </sect5>
+ </sect1>
- <sect5 id="glthread">
+ <sect1 id="glthread">
<title>OpenGL and Threads</title>
<para>
Neither OpenGL nor X11 has any built-in support for threads. Most
@@ -321,9 +321,9 @@
display must be wrapped with a mutex.
</para>
- </sect5>
+ </sect1>
- <sect5 id="eventhandle">
+ <sect1 id="eventhandle">
<title>Plugin Event Handling</title>
<para>
Firefox on most UNIX systems is a GTK+ application, so it is
@@ -349,5 +349,5 @@
</para>
- </sect5>
-</sect4>
+ </sect1>
+</chapter>
Index: doc/C/refmanual/extensions/extensions.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/refmanual/extensions/extensions.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- doc/C/refmanual/extensions/extensions.xml 1 Mar 2008 15:24:43 -0000
1.1
+++ doc/C/refmanual/extensions/extensions.xml 1 Mar 2008 21:14:07 -0000
1.2
@@ -119,8 +119,7 @@
<programlisting>
// Attach DummyClass 'func1' and 'func2' methods to the given object
static void
- attachInterface(as_object& obj)
- {
+ attachInterface(as_object& obj) {
obj.init_member("func1", &ext_func1);
obj.init_member("func2", &ext_func2);
}
@@ -222,8 +221,7 @@
</para>
<programlisting>
// Creates a new button with the label as the text.
- as_value func1(const fn_call& fn)
- {
+ as_value func1(const fn_call& fn) {
// Following line will ensure 'func1' is called for a DummyExt
instance,
// or would throw an exception which should behave as if we
returned the
// undefined value.
Index: doc/C/fileext.xml
===================================================================
RCS file: doc/C/fileext.xml
diff -N doc/C/fileext.xml
--- doc/C/fileext.xml 22 Feb 2007 19:23:59 -0000 1.2
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,150 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<sect3 id="fileioext">
- <title>File I/O Extension</title>
-
- <para>
- Flash movies are traditionally forbidden from accessing the
- filesystem, but this may be necessary for some embedded
- applications. Especially in the case of a user console, currently
- there is no way to get input into a Flash movie but through a
- TextField.
- </para>
-
- <variablelist>
- <varlistentry>
- <term>fopen</term>
- <listitem>
- <para>
- Open the file.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>fread</term>
- <listitem>
- <para>
- Read a series of bytes from the opened file.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>fgetc</term>
- <listitem>
- <para>
- Read a single byte from the opened file.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>fgets</term>
- <listitem>
- <para>
- Read a single line until a Carriage Return from the opened file.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>gets</term>
- <listitem>
- <para>
- Read a single line from the standard in.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>getchar</term>
- <listitem>
- <para>
- Read a single character from the standard in.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>fwrite</term>
- <listitem>
- <para>
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>fputc</term>
- <listitem>
- <para>
- Write a single character to the opened file.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>fputs</term>
- <listitem>
- <para>
- Write a single line to the opened file.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>puts</term>
- <listitem>
- <para>
- Write a single line to standard out..
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>putchar</term>
- <listitem>
- <para>
- Write a single character to standard out..
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>fflush</term>
- <listitem>
- <para>
- Flush the current opened file to disk.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>fseek</term>
- <listitem>
- <para>
- Seek to a location within the opened file.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>ftell</term>
- <listitem>
- <para>
- Report the current position within the opened file.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>fclose</term>
- <listitem>
- <para>
- Close the opened file.
- </para>
- </listitem>
- </varlistentry>
-
- </variablelist>
-
-</sect3>
Index: doc/C/gnash.xml
===================================================================
RCS file: doc/C/gnash.xml
diff -N doc/C/gnash.xml
--- doc/C/gnash.xml 20 Feb 2008 11:33:53 -0000 1.52
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,111 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-
-<!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 manrevision "0.4.3">
- <!ENTITY date "Feb 2008">
- <!ENTITY app "<application>Gnash</application>">
- <!ENTITY appname "Gnash">
- <!ENTITY AS "ActionScript">
-
- <!ENTITY legal SYSTEM "legal.xml">
- <!ENTITY fdl-app SYSTEM "fdl-appendix.xml">
- <!ENTITY amf SYSTEM "amf.xml">
- <!ENTITY rtmp SYSTEM "rtmp.xml">
- <!ENTITY programmers SYSTEM "app_authors.xml">
-
- <!ENTITY extensions SYSTEM "extensions.xml">
- <!ENTITY fileext SYSTEM "fileext.xml">
- <!ENTITY gtkext SYSTEM "gtkext.xml">
- <!ENTITY mysqlext SYSTEM "mysqlext.xml">
- <!ENTITY internals SYSTEM "internals.xml">
- <!ENTITY object SYSTEM "object.xml">
- <!ENTITY plugin SYSTEM "plugin.xml">
-
-
- <!ENTITY acknowledgments SYSTEM "usermanual/acknowledgments.xml">
- <!ENTITY conventions SYSTEM "usermanual/conventions.xml">
-
- <!ENTITY writers SYSTEM "usermanual/doc_authors.xml">
- <!ENTITY revisionhistory SYSTEM "usermanual/revisions.xml">
- <!ENTITY introduction SYSTEM "usermanual/introduction.xml">
- <!ENTITY specification SYSTEM "usermanual/specification.xml">
- <!ENTITY installation SYSTEM "usermanual/installation.xml">
- <!ENTITY usage SYSTEM "usermanual/usage.xml">
- <!ENTITY gnashrc SYSTEM "usermanual/usage/gnashrc.xml">
- <!ENTITY glossary SYSTEM "usermanual/glossary.xml">
- <!ENTITY bugreport SYSTEM "usermanual/bugreport.xml">
-
- <!ENTITY custompath SYSTEM
"usermanual/installation/custompath_configuration.xml">
- <!ENTITY featureoptions SYSTEM
"usermanual/installation/feature_configuration.xml">
- <!ENTITY docdependencies SYSTEM
"usermanual/installation/documentation_dependencies.xml">
- <!ENTITY codedependencies SYSTEM
"usermanual/installation/code_dependencies.xml">
- <!ENTITY testdependencies SYSTEM
"usermanual/installation/testing_dependencies.xml">
- <!ENTITY sources SYSTEM "usermanual/installation/sources.xml">
- <!ENTITY pkgmanager SYSTEM
"usermanual/installation/packagemanager.xml">
- <!ENTITY configuration SYSTEM
"usermanual/installation/configuration.xml">
- <!ENTITY crosscompiling SYSTEM
"usermanual/installation/cross_compiling.xml">
- <!ENTITY building SYSTEM "usermanual/installation/building.xml">
- <!ENTITY install SYSTEM "usermanual/installation/install.xml">
- ]
->
-
-
-<!-- TRANSLATOR NOTE: do not change the id, just the lang -->
-<book lang="en" id="index">
-<title>Gnash Manual</title>
-<titleabbrev>Gnash</titleabbrev>
-
-<!-- =============Document Header ============================ -->
-
- <bookinfo>
- <title>&app;</title>
- <copyright>
- <year>2005, 2006, 2007, 2008</year>
- <holder>Free Software Foundation</holder>
- </copyright>
-
- <!-- TRANSLATOR NOTE: uncomment this section
-
- <copyright>
- <year>2008</year>
- <holder>ME-THE-TRANSLATOR (Latin translation)</holder>
- </copyright>
-
- -->
-
- &legal;
- &revisionhistory;
-
- <releaseinfo>
- This manual describes version &appversion; of &appname;.
- </releaseinfo>
-
- </bookinfo>
-
-
-<!-- ============= Introduction ============================== -->
- &introduction;
-
-
-<!-- ============= Document Body ============================= -->
-
- &usage;
-
- &installation;
- &bugreport;
- &specification;
- &glossary;
-
- &rtmp;
-
-<!-- ============= Authors =================================== -->
- &programmers;
-<!-- &writers; -->
-
-<!-- ============= Application License ======================= -->
- &fdl-app;
-
-</book>
Index: doc/C/gtkext.xml
===================================================================
RCS file: doc/C/gtkext.xml
diff -N doc/C/gtkext.xml
--- doc/C/gtkext.xml 16 Feb 2007 05:34:21 -0000 1.1
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,88 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<sect3 id="gtkext">
- <title>Gtk Extension</title>
-
- <para>
- The GTK ActionScript class follows the same API as Gtk2, even down
- to the same arguments to the same function names. This means
- you're actually programming GTK,you're just using ActionScript
- instead of python, perl, or C. This extension makes it possible to
- write Flash movies that use the Gtk2 widgets for user interface
- components.
- </para>
-
- <variablelist>
- <varlistentry>
- <term>window_new</term>
- <listitem>
- <para>
- Create a new window.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>signal_connect</term>
- <listitem>
- <para>
- Add an event handler to a widget.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>container_set_border_width</term>
- <listitem>
- <para>
- Set the width of the window border.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>button_new_with_label</term>
- <listitem>
- <para>
- Create a new button and give it the specified label.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>signal_connect_swapped</term>
- <listitem>
- <para>
- Swap signals. Commonly used for <emphasis>delete</emphasis> event
handling.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>container_add</term>
- <listitem>
- <para>
- Add one widget to another as a child.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>widget_show</term>
- <listitem>
- <para>
- Display the widget on the screen.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>main</term>
- <listitem>
- <para>
- Start the main GTK event loop. This function does not return.
- </para>
- </listitem>
- </varlistentry>
-
- </variablelist>
-</sect3>
\ No newline at end of file
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Gnash-commit] gnash ChangeLog doc/C/Makefile.am doc/C/appendi...,
Rob Savoye <=