diff options
Diffstat (limited to 'DOCS')
| -rw-r--r-- | DOCS/man/en/mplayer.1 | 73 | ||||
| -rw-r--r-- | DOCS/tech/MAINTAINERS | 2 | ||||
| -rw-r--r-- | DOCS/tech/binary-packaging.txt | 22 | ||||
| -rw-r--r-- | DOCS/xml/en/documentation.xml | 1 | ||||
| -rw-r--r-- | DOCS/xml/en/faq.xml | 6 | ||||
| -rw-r--r-- | DOCS/xml/en/install.xml | 29 | ||||
| -rw-r--r-- | DOCS/xml/en/skin.xml | 1200 |
7 files changed, 10 insertions, 1323 deletions
diff --git a/DOCS/man/en/mplayer.1 b/DOCS/man/en/mplayer.1 index 9582c62222..cc1672c546 100644 --- a/DOCS/man/en/mplayer.1 +++ b/DOCS/man/en/mplayer.1 @@ -124,11 +124,6 @@ tivo://host/[list|llist|fsid] [options] . .br -.B gmplayer -[options] -[\-skin\ skin] -. -.br .B mencoder [options] file [file|URL|\-] [\-o file | file://file | smb://[user:pass@]host/filepath] @@ -362,30 +357,6 @@ Seek backward/\:forward 1 minute. .PD 1 .PP .RS -(The following keys are only valid if GUI support is compiled in -and will take precedence over the keys defined above.) -.RE -.PP -.PD 0 -.RS -.IPs ENTER -Start playing. -.IPs "ESC\ \ " -Stop playing. -.IPs "l\ \ \ \ " -Load file. -.IPs "t\ \ \ \ " -Load subtitle. -.IPs "c\ \ \ \ " -Open skin browser. -.IPs "p\ \ \ \ " -Open playlist. -.IPs "r\ \ \ \ " -Open preferences. -.RE -.PD 1 -.PP -.RS (The following keys are only valid if you compiled with TV or DVB input support and will take precedence over the keys defined above.) .RE @@ -715,8 +686,6 @@ Available options are: .RSs .IPs "all\ \ " all configuration files -.IPs "gui (GUI only)" -GUI configuration file .IPs system system configuration file .IPs "user\ " @@ -752,7 +721,6 @@ Use the given profile(s), \-profile help displays a list of the defined profiles .TP .B \-really\-quiet (also see \-quiet) Display even less output and status messages than with \-quiet. -Also suppresses the GUI error message boxes. . .TP .B \-show\-profile <profile> @@ -860,11 +828,6 @@ later. See http://www.mplayerhq.hu/\:DOCS/\:HTML/\:en/\:edl.html for details. . .TP -.B \-enqueue (GUI only) -Enqueue files given on the command line in the playlist instead of playing them -immediately. -. -.TP .B \-nofixed\-vo \-fixed\-vo enforces a fixed video system for multiple files (one (un)initialization for all files). @@ -881,12 +844,6 @@ Video filters are not applied to such frames. For B-frames even decoding is skipped completely. . .TP -.B \-(no)gui -Enable or disable the GUI interface (default depends on binary name). -Only works as the first argument on the command line. -Does not work as a config-file option. -. -.TP .B \-h, \-help, \-\-help Show short summary of options. . @@ -1118,20 +1075,6 @@ Use the specified device for RTC timing. Play files in random order. . .TP -.B \-skin <name> (GUI only) -Loads a skin from the directory given as parameter below the default skin -directories, /usr/\:local/\:share/\:mplayer/\:skins/\: and ~/.mplayer/\:skins/. -.sp 1 -.I EXAMPLE: -.PD 0 -.RSs -.IPs "\-skin fittyfene" -Tries /usr/\:local/\:share/\:mplayer/\:skins/\:fittyfene -and afterwards ~/.mplayer/\:skins/\:fittyfene. -.RE -.PD 1 -. -.TP .B \-slave (also see \-input) Switches on slave mode, in which MPlayer works as a backend for other programs. Instead of intercepting keyboard events, MPlayer will read commands separated @@ -3156,12 +3099,6 @@ Places the window at the bottom right corner of the screen. .PD 1 . .TP -.B \-guiwid <window ID> (also see \-wid) (GUI only) -This tells the GUI to also use an X11 window and stick itself to the bottom -of the video, which is useful to embed a mini-GUI in a browser (with the -MPlayer plugin for instance). -. -.TP .B \-hue <\-100\-100> Adjust the hue of the video signal (default: 0). You can get a colored negative of the image with this option. @@ -3292,7 +3229,7 @@ the new display mode. Enables VBI for the vesa, dfbmga and svga video output drivers. . .TP -.B \-wid <window ID> (also see \-guiwid) (X11, OpenGL and DirectX only) +.B \-wid <window ID> (X11, OpenGL and DirectX only) This tells MPlayer to attach to an existing window. Useful to embed MPlayer in a browser (e.g.\& the plugger extension). . @@ -11068,14 +11005,6 @@ MEncoder user settings input bindings (see '\-input keylist' for the full list) . .TP -~/.mplayer/\:gui.conf -GUI configuration file -. -.TP -~/.mplayer/\:gui.pl -GUI playlist -. -.TP ~/.mplayer/\:font/ font directory (There must be a font.desc file and files with .RAW extension.) . diff --git a/DOCS/tech/MAINTAINERS b/DOCS/tech/MAINTAINERS index 680906e4e2..fcd4566c41 100644 --- a/DOCS/tech/MAINTAINERS +++ b/DOCS/tech/MAINTAINERS @@ -84,8 +84,6 @@ MPlayer code: * playtree, input layer: Alban Bedel * libswscale: Michael Niedermayer, Luca Abeni * DVB support: Nico Sabbi - * GUI: None - * GUI skins: Diego Biurrun * EDL code: Reynaldo H. Verdejo Pinochet, Oded Shimon Imported libs/projects: diff --git a/DOCS/tech/binary-packaging.txt b/DOCS/tech/binary-packaging.txt index 9d852372db..974a20d46f 100644 --- a/DOCS/tech/binary-packaging.txt +++ b/DOCS/tech/binary-packaging.txt @@ -66,9 +66,6 @@ the following features MUST be included in any official binary package: (*) if available for your OS/hardware -There is great demand for the GUI, so it SHOULD be included, but it MUST -come as a separate package (see Tips and Tricks for details). - Including other features, like LIVE.COM streaming or JACK support, is acceptable. They SHOULD, however, be build-time configurable, with the default build configuration containing the above set. @@ -111,7 +108,6 @@ for Red Hat and Fedora RPMs I am using FHS-compliant paths: /usr/share/doc/mplayer-version/ docs /usr/share/man/man1/ man page /usr/share/man/XX/man1/ translated man page -/usr/share/mplayer/skins/ GUI skins You MUST NOT include the codecs.conf file in your package. It is useful only for development purposes and often causes obscure problems for users. @@ -129,13 +125,9 @@ install only what you need. This is the layout I am using for Red Hat and Fedora RPMs: mencoder contains MEncoder binary (mencoder) -mplayer contains MPlayer binary without GUI (mplayer), - config files, man pages and documentation; - required by mplayer-gui +mplayer contains MPlayer binary config files, man pages and + documentation; mplayer-codecs-* contain binary codecs available from MPlayer's site -mplayer-gui contains MPlayer binary with GUI (gmplayer); - contains default skin (Blue) -mplayer-skin-* contain various MPlayer GUI skins There is no strict policy for now, just use your common sense. @@ -200,14 +192,8 @@ ao=alsa, Tips and tricks ~~~~~~~~~~~~~~~ -In my package layout, mplayer and mplayer-gui can be installed at the same -time, because they contain differently named binaries and there is no -conflict. The trick is to build MPlayer once with --enable-gui, rename the -resulting binary to "gmplayer" and then build it again, without GUI, but -keeping the rest of ./configure options the same. - -To provide man pages for all MPlayer suite binaries (mplayer, gmplayer, -mencoder), you can use man-links instead of regular symbolic links. +To provide man pages for all MPlayer suite binaries (mplayer, mencoder), you +can use man-links instead of regular symbolic links. Creating a mencoder man page linked to mplayer is as simple as: echo ".so mplayer.1" >> mencoder.1 diff --git a/DOCS/xml/en/documentation.xml b/DOCS/xml/en/documentation.xml index c1f0fb5527..2108533f96 100644 --- a/DOCS/xml/en/documentation.xml +++ b/DOCS/xml/en/documentation.xml @@ -175,4 +175,3 @@ can be distributed under the terms of the GNU General Public License Version 2. &encoding-guide.xml; &faq.xml; &bugreports.xml; -&skin.xml; diff --git a/DOCS/xml/en/faq.xml b/DOCS/xml/en/faq.xml index 83989dbf3a..9234ad7334 100644 --- a/DOCS/xml/en/faq.xml +++ b/DOCS/xml/en/faq.xml @@ -644,11 +644,7 @@ your configuration file. Add <programlisting> vo = <replaceable>selected_vo</replaceable> </programlisting> -to <filename>~/.mplayer/config</filename> and/or -<programlisting> -vo_driver = <replaceable>selected_vo</replaceable> -</programlisting> -to <filename>~/.mplayer/gui.conf</filename>. +to <filename>~/.mplayer/config</filename> </para></answer> </qandaentry> diff --git a/DOCS/xml/en/install.xml b/DOCS/xml/en/install.xml index f8019fe3f9..86afaaf65d 100644 --- a/DOCS/xml/en/install.xml +++ b/DOCS/xml/en/install.xml @@ -106,10 +106,6 @@ answers. <itemizedlist> <listitem><para> - Decide if you need GUI. If you do, see the <link linkend="gui">GUI</link> - section before compiling. -</para></listitem> -<listitem><para> If you want to install <application>MEncoder</application> (our great all-purpose encoder), see the <link linkend="mencoder"><application>MEncoder</application></link> section. @@ -184,27 +180,10 @@ See the <link linkend="subosd">Subtitles and OSD</link> section for details. <title>What about the GUI?</title> <para> -The GUI needs GTK 1.2.x or GTK 2.0 (it isn't fully GTK, but the panels are), -so <systemitem class="library">GTK</systemitem> (and the devel stuff, usually -called <systemitem class="library">gtk-dev</systemitem>) has to be installed. -You can build it by specifying <option>--enable-gui</option> during -<filename>./configure</filename>. Then, to turn on GUI mode, you have to -execute the <command>gmplayer</command> binary. -</para> - -<para> -As <application>MPlayer</application> doesn't have a skin included, you -have to download one if you want to use the GUI. See the <ulink -url="http://www.mplayerhq.hu/dload.html">download page</ulink>. -It should be extracted to the usual system-wide directory (<filename -class="directory">$PREFIX/share/mplayer/skins</filename>), or to <filename -class="directory">$HOME/.mplayer/skins</filename>. -<application>MPlayer</application> by default looks in these directories -for a directory named <filename class="directory">default</filename>, but -you can use the <option>-skin <replaceable>newskin</replaceable></option> -option, or the <literal>skin=newskin</literal> config file directive to use -the skin in the <filename class="directory">*/skins/newskin</filename> -directory. +MPlayer used to have an internal GUI, but it was removed because it was +buggy, unmaintained and there are much better alternatives. See <ulink +url="http://www.mplayerhq.hu/design7/projects.html#mplayer_frontends">the +frontends page</ulink> for a list of existing GUIs. </para> </sect1> diff --git a/DOCS/xml/en/skin.xml b/DOCS/xml/en/skin.xml deleted file mode 100644 index 38feef6782..0000000000 --- a/DOCS/xml/en/skin.xml +++ /dev/null @@ -1,1200 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!-- $Revision$ --> -<appendix id="skin"> -<title><application>MPlayer</application> skin format</title> - -<sect1 id="skin-overview"> -<title>Overview</title> - -<!-- ********** --> - -<sect2 id="skin-overview-components"> -<title>Skin components</title> - -<para> -Skins are quite free-format (unlike the fixed-format skins of -<application>Winamp</application>/<application>XMMS</application>, -for example), so it is up to you to create something great. -</para> - -<para> -Currently there are four windows to be decorated: the -<link linkend="skin-file-main">main window</link>, the -<link linkend="skin-file-subwindow">subwindow</link>, the -<link linkend="skin-file-main">playbar</link>, and the -<link linkend="skin-file-menu">skin menu</link> (which can be activated -by a right click). - -<itemizedlist> -<listitem> - <para> - The <emphasis role="bold">main window</emphasis> and/or the - <emphasis role="bold">playbar</emphasis> is where you can control - <application>MPlayer</application>. The background of the window is an image. - Various items can (and must) be placed in the window: - <emphasis>buttons</emphasis>, <emphasis>potmeters</emphasis> (sliders) and - <emphasis>labels</emphasis>. - For every item, you must specify its position and size. - </para> - - <para> - A <emphasis role="bold">button</emphasis> has three states (pressed, released, - disabled), thus its image must be divided into three parts vertically. See the - <link linkend="skin-button">button</link> item for details. - </para> - - <para> - A <emphasis role="bold">potmeter</emphasis> (mainly used for the seek bar and - volume/balance control) can have any number of phases by dividing its image - into different parts below each other. See - <link linkend="skin-hpotmeter">hpotmeter</link> and - <link linkend="skin-potmeter">potmeter</link> for details. - </para> - - <para> - <emphasis role="bold">Labels</emphasis> are a bit special: The characters - needed to draw them are taken from an image file, and the characters in the - image are described by a - <link linkend="skin-fonts">font description file</link>. - The latter is a plain text file which specifies the x,y position and size of - each character in the image (the image file and its font description file - form a font <emphasis>together</emphasis>). - See <link linkend="skin-dlabel">dlabel</link> - and <link linkend="skin-slabel">slabel</link> for details. - </para> - - <note><para> - All images can have full transparency as described in the section about - <link linkend="skin-overview-formats">image formats</link>. If the X server - doesn't support the XShape extension, the parts marked transparent will be - black. If you'd like to use this feature, the width of the main window's - background image must be dividable by 8. - </para></note> -</listitem> - -<listitem><para> - The <emphasis role="bold">subwindow</emphasis> is where the movie appears. It - can display a specified image if there is no movie loaded (it is quite boring - to have an empty window :-)) <emphasis role="bold">Note:</emphasis> - transparency is <emphasis role="bold">not allowed</emphasis> here. -</para></listitem> - -<listitem> - <para> - The <emphasis role="bold">skin menu</emphasis> is just a way to control - <application>MPlayer</application> by means of menu entries. Two images - are required for the menu: one of them is the base image that shows the - menu in its normal state, the other one is used to display the selected - entries. When you pop up the menu, the first image is shown. If you move - the mouse over the menu entries, the currently selected entry is copied - from the second image over the menu entry below the mouse pointer - (the second image is never shown as a whole). - </para> - <para> - A menu entry is defined by its position and size in the image (see the - section about the <link linkend="skin-file-menu">skin menu</link> for - details). - </para> -</listitem> -</itemizedlist> -</para> - -<para> -There is an important thing not mentioned yet: For buttons, potmeters and -menu entries to work, <application>MPlayer</application> must know what to -do if they are clicked. This is done by <link linkend="skin-gui">messages</link> -(events). For these items you must define the messages to be generated when -they are clicked. -</para> -</sect2> - -<sect2 id="skin-overview-formats"> -<title>Image formats</title> - -<para>Images must be truecolor (24 or 32 bpp) PNGs.</para> -<para> -In the main window and in the playbar (see below) you can use images with -`transparency': Regions filled with the color #FF00FF (magenta) are fully -transparent when viewed by <application>MPlayer</application>. This means -that you can even have shaped windows if your X server has the XShape extension. -</para> -</sect2> - -<!-- ********** --> - -<sect2 id="skin-files"> -<title>Files</title> - -<para> -You need the following files to build a skin: -<itemizedlist> -<listitem><para> - The configuration file named <link linkend="skin-file">skin</link> tells - <application>MPlayer</application> how to put different parts of the skin - together and what to do if you click somewhere in the window. -</para></listitem> -<listitem><para> - The background image for the main window. -</para></listitem> -<listitem><para> - Images for the items in the main window (including one or more font - description files needed to draw labels). -</para></listitem> -<listitem><para> - The image to be displayed in the subwindow (optional). -</para></listitem> -<listitem><para> - Two images for the skin menu (they are needed only if you want to create - a menu). -</para></listitem> -</itemizedlist> - With the exception of the skin configuration file, you can name the other - files whatever you want (but note that font description files must have - a <filename>.fnt</filename> extension). -</para> -</sect2> -</sect1> - - -<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --> - - -<sect1 id="skin-file"> -<title>The skin file</title> - -<para> -As mentioned above, this is the skin configuration file. It is line oriented; -comment lines start with a '<literal>;</literal>' character at the beginning of -the line (only spaces and tabs are allowed before the '<literal>;</literal>'). -</para> - -<para> -The file is made up of sections. Each section describes the skin for an -application and has the following form: -<programlisting> -section = <replaceable>section name</replaceable> -. -. -. -end -</programlisting> -</para> - -<para> -Currently there is only one application, so you need only one section: its name -is <emphasis role="bold">movieplayer</emphasis>. -</para> - -<para> -Within this section each window is described by a block of the following form: -<programlisting> -window = <replaceable>window name</replaceable> -. -. -. -end -</programlisting> -</para> - -<para> -where <replaceable>window name</replaceable> can be one of these strings: -<itemizedlist> -<listitem><para> - <emphasis role="bold">main</emphasis> - for the main window -</para></listitem> -<listitem><para> - <emphasis role="bold">sub</emphasis> - for the subwindow -</para></listitem> -<listitem><para> - <emphasis role="bold">menu</emphasis> - for the skin menu -</para></listitem> -<listitem><para> - <emphasis role="bold">playbar</emphasis> - playbar -</para></listitem> -</itemizedlist> -</para> - -<para> -(The sub and menu blocks are optional - you do not need to create a menu or -decorate the subwindow.) -</para> - -<para> -Within a window block, you can define each item for the window by a line in -this form: -<programlisting>item = parameter</programlisting> -Where <literal>item</literal> is a string that identifies the type of the GUI -item, <literal>parameter</literal> is a numeric or textual value (or a list of -values separated by commas). -</para> - -<para> -Putting the above together, the whole file looks something like this: -<programlisting> -section = movieplayer - window = main - ; ... items for main window ... - end - - window = sub - ; ... items for subwindow ... - end - - window = menu - ; ... items for menu ... - end - - window = playbar - ; ... items for playbar ... - end -end -</programlisting> -</para> - -<para> -The name of an image file must be given without leading directories - images -are searched for in the <filename class="directory">skins</filename> directory. -You may (but you need not) specify the extension of the file. If the file does -not exist, <application>MPlayer</application> tries to load the file -<filename><filename>.<ext></filename>, where <literal>png</literal> -and <literal>PNG</literal> are tried for <filename><ext></filename> -(in this order). The first matching file will be used. -</para> - -<para> -Here is an example to make this clear. Suppose that you have an image called -<filename>main.png</filename> that you use for the main window: -<programlisting>base = main, -1, -1</programlisting> -<application>MPlayer</application> tries to load <filename>main</filename>, -<filename>main.png</filename>, <filename>main.PNG</filename> files. -</para> - -<para> -Finally some words about positioning. The main window and the subwindow can be -placed in the different corners of the screen by giving <literal>X</literal> -and <literal>Y</literal> coordinates. <literal>0</literal> is top or left, -<literal>-1</literal> is center and <literal>-2</literal> is right or bottom, as -shown in this illustration: -<informalfigure> -<screen> -(0, 0)----(-1, 0)----(-2, 0) - | | | - | | | -(0,-1)----(-1,-1)----(-2,-1) - | | | - | | | -(0,-2)----(-1,-2)----(-2,-2) -</screen> -</informalfigure> -</para> - -<!-- ********** --> - -<sect2 id="skin-file-main"> -<title>Main window and playbar</title> - -<para> -Below is the list of entries that can be used in the -'<literal>window = main</literal>' ... '<literal>end</literal>', -and the '<literal>window = playbar</literal>' ... '<literal>end</literal>' -blocks. -</para> - -<variablelist> -<varlistentry> - <term><literal> - <anchor id="skin-main-base"/>base = image, X, Y - </literal></term> - <listitem> - <para> - Lets you specify the background image to be used for the main window. - The window will appear at the given <literal>X,Y</literal> position on - the screen The window will have the size of the image. - </para> - <note><para> - These coordinates do not currently work for the display window. - </para></note> - <warning><para>Transparent regions in the image (colored #FF00FF) appear black - on X servers without the XShape extension. The image's width must be dividable - by 8.</para></warning> - </listitem> -</varlistentry> - -<varlistentry> - <term><literal> - <anchor id="skin-button"/>button = image, X, Y, width, height, message - </literal></term> - <listitem> - <para> - Place a button of <literal>width</literal> * <literal>height</literal> size at - position <literal>X,Y</literal>. The specified <literal>message</literal> is - generated when the button is clicked. The image given by - <literal>image</literal> must have three parts below each other (according to - the possible states of the button), like this: - </para> - <informalfigure> - <screen> -+------------+ -| pressed | -+------------+ -| released | -+------------+ -| disabled | -+------------+<!-- - --></screen> - </informalfigure> - </listitem> -</varlistentry> - -<varlistentry> - <term><literal> - <anchor id="skin-decoration"/>decoration = enable|disable - </literal></term> - <listitem> - <para> - Enable or disable window manager decoration of the main window. Default is - <emphasis role="bold">disable</emphasis>. - </para> - <note><para> - This doesn't work for the display window, there is no need to. - </para></note> - </listitem> -</varlistentry> - -<varlistentry> - <term><literal> - <anchor id="skin-hpotmeter"/>hpotmeter = button, bwidth, bheight, phases, numphases, default, X, Y, width, height, message - </literal></term> - <listitem><para> - </para></listitem> -</varlistentry> - -<varlistentry> - <term><literal> - <anchor id="skin-vpotmeter"/>vpotmeter = button, bwidth, bheight, phases, numphases, default, X, Y, width, height, message - </literal></term> - <listitem><para> - Place a horizontal (hpotmeter) or vertical (vpotmeter) potmeter of - <literal>width</literal> * <literal>height</literal> size at position - <literal>X,Y</literal>. The image can be divided into different parts for the - different phases of the potmeter (for example, you can have a pot for volume - control that turns from green to red while its value changes from the minimum - to the maximum.). <literal>hpotmeter</literal> can have a button that can be - dragged horizontally. The parameters are: - <itemizedlist> - <listitem><para> - <literal>button</literal> - the image to be used for the - button (must have three parts below each other, like in case of - <link linkend="skin-button">button</link>) - </para></listitem> - <listitem><para> - <literal>bwidth</literal>, <literal>bheight</literal> - size - of the button - </para></listitem> - <listitem><para> - <literal>phases</literal> - the image to be used for the - different phases of the hpotmeter. A special value of <literal>NULL</literal> - can be used if you want no such image. The image must be divided into - <literal>numphases</literal> parts vertically like this: - <informalfigure><screen> -+------------+ -| phase #1 | -+------------+ -| phase #2 | -+------------+ - ... -+------------+ -| phase #n | -+------------+<!-- - --></screen></informalfigure> - </para></listitem> - <listitem><para> - <literal>numphases</literal> - number of phases stored in the - <literal>phases</literal> image - </para></listitem> - <listitem><para> - <literal>default</literal> - default value for hpotmeter - (in the range <literal>0</literal> to <literal>100</literal>) - </para></listitem> - <listitem><para> - <literal>X</literal>, <literal>Y</literal> - position for the hpotmeter - </para></listitem> - <listitem><para> - <literal>width</literal>, <literal>height</literal> - width and height - of the <literal>hpotmeter</literal> - </para></listitem> - <listitem><para> - <literal>message</literal> - the message to be generated when the - value of <literal>hpotmeter</literal> is changed - </para></listitem> - </itemizedlist> - </para></listitem> -</varlistentry> - -<varlistentry> - <term><literal> - <anchor id="skin-potmeter"/>potmeter = phases, numphases, default, X, Y, width, height, message - </literal></term> - <listitem><para> - A <literal>hpotmeter</literal> without a button. (I guess it is meant to be - turned around, but it reacts to horizontal dragging only.) For the description - of the parameters see <link linkend="skin-hpotmeter">hpotmeter</link>. - <literal>phases</literal> can be <literal>NULL</literal>, but it is quite - useless, since you cannot see where the <literal>potmeter</literal> is set. - </para></listitem> -</varlistentry> - -<varlistentry> - <term><literal> - <anchor id="skin-font"/>font = fontfile, fontid - </literal></term> - <listitem><para> - Defines a font. <literal>fontfile</literal> is the name of a font description - file with a <filename>.fnt</filename> extension (do not specify the extension - here). <literal>fontid</literal> is used to refer to the font - (see <link linkend="skin-dlabel">dlabel</link> - and <link linkend="skin-slabel">slabel</link>). Up to 25 fonts can be defined. - </para></listitem> -</varlistentry> - -<varlistentry> - <term><literal> - <anchor id="skin-slabel"/>slabel = X, Y, fontid, "text" - </literal></term> - <listitem><para> - Place a static label at the position <literal>X,Y</literal>. - <literal>text</literal> is displayed using the font identified by - <literal>fontid</literal>. The text is just a raw string - (<literal>$x</literal> variables do not work) that must be enclosed between - double quotes (but the " character cannot be part of the text). The - label is displayed using the font identified by <literal>fontid</literal>. - </para></listitem> -</varlistentry> - -<varlistentry> - <term><literal> - <anchor id="skin-dlabel"/>dlabel = X, Y, length, align, fontid, "text" - </literal></term> - <listitem> - <para> - Place a dynamic label at the position <literal>X,Y</literal>. The label is - called dynamic because its text is refreshed periodically. The maximum length - of the label is given by <literal>length</literal> (its height is the height - of a character). If the text to be displayed is wider than that, it will be - scrolled, - otherwise it is aligned within the specified space by the value of the - <literal>align</literal> parameter: <literal>0</literal> is for right, - <literal>1</literal> is for center, <literal>2</literal> is for left. - </para> - <para> - The text to be displayed is given by <literal>text</literal>: It must be - written between double quotes (but the " character cannot be part of the - text). The label is displayed using the font identified by - <literal>fontid</literal>. You can use the following variables in the text: - </para> - - <informaltable> - <tgroup cols="2"> - <thead> - <row><entry>Variable</entry><entry>Meaning</entry></row> - </thead> - <tbody> - <row> - <entry>$1</entry> - <entry>play time in <emphasis>hh:mm:ss</emphasis> format</entry> - </row> - <row> - <entry>$2</entry> - <entry>play time in <emphasis>mmmm:ss</emphasis> format</entry> - </row> - <row> - <entry>$3</entry> - <entry>play time in <emphasis>hh</emphasis> format (hours)</entry> - </row> - <row> - <entry>$4</entry> - <entry>play time in <emphasis>mm</emphasis> format (minutes)</entry> - </row> - <row> - <entry>$5</entry> - <entry>play time in <emphasis>ss</emphasis> format (seconds)</entry> - </row> - <row> - <entry>$6</entry> - <entry>movie length in <emphasis>hh:mm:ss</emphasis> format</entry> - </row> - <row> - <entry>$7</entry> - <entry>movie length in <emphasis>mmmm:ss</emphasis> format</entry> - </row> - <row> - <entry>$8</entry> - <entry>play time in <emphasis>h:mm:ss</emphasis> format</entry> - </row> - <row> - <entry>$v</entry> - <entry>volume in <emphasis>xxx.xx</emphasis>% format</entry> - </row> - <row> - <entry>$V</entry> - <entry>volume in <emphasis>xxx.xx</emphasis> format</entry> - </row> - <row> - <entry>$b</entry> - <entry>balance in <emphasis>xxx.xx</emphasis>% format</entry> - </row> - <row> - <entry>$B</entry> - <entry>balance in <emphasis>xxx.xx</emphasis> format</entry> - </row> - <row> - <entry>$$</entry> - <entry>the $ character</entry> - </row> - <row> - <entry>$a</entry> - <entry>a character according to the audio type (none: <literal>n</literal>, - mono: <literal>m</literal>, stereo: <literal>t</literal>)</entry> - </row> - <row> - <entry>$t</entry> - <entry>track number (in playlist)</entry> - </row> - <row> - <entry>$o</entry> - <entry>filename</entry> - </row> - <row> - <entry>$f</entry> - <entry>filename in lower case</entry> - </row> - <row> - <entry>$F</entry> - <entry>filename in upper case</entry> - </row> - <row> - <entry>$T</entry> - <entry> - a character according to the stream type (file: <literal>f</literal>, - Video CD: <literal>v</literal>, DVD: <literal>d</literal>, - URL: <literal>u</literal>) - </entry> - </row> - <row> - <entry>$p</entry> - <entry>the <keycap>p</keycap> character (if a movie is playing and the font - has the <keycap>p</keycap> character)</entry> - </row> - <row> - <entry>$s</entry> - <entry>the <keycap>s</keycap> character (if the movie is stopped and the - font has the <keycap>s</keycap> character)</entry> - </row> - <row> - <entry>$e</entry> - <entry>the & |