From 6eaad0c49243d14040b0e478eec734eb73a9cc6c Mon Sep 17 00:00:00 2001 From: wight Date: Sun, 30 Nov 2003 13:07:40 +0000 Subject: attack git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@11541 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/xml/en/skin.xml | 63 +++++++++++++++++++++++++++------------------------- 1 file changed, 33 insertions(+), 30 deletions(-) (limited to 'DOCS/xml/en/skin.xml') diff --git a/DOCS/xml/en/skin.xml b/DOCS/xml/en/skin.xml index ae6063e312..28e2714dcc 100644 --- a/DOCS/xml/en/skin.xml +++ b/DOCS/xml/en/skin.xml @@ -1,10 +1,11 @@ -MPlayer skin format +<application>MPlayer</application> skin format -The purpose of this document is to describe the MPlayer skin format. -The information contained here might be wrong, for +The purpose of this document is to describe the +MPlayer skin format. The information contained here +might be wrong, for It is not me who wrote the GUI. The GUI is not finished. @@ -21,9 +22,9 @@ So do not be surprised if something does not work as described here. Overview It does not really have anything to do with the skin format, but you should -know that MPlayer has no builtin skin, so -at least one skin must be installed in order to be able -to use the GUI. +know that MPlayer has no +builtin skin, so at least one skin must be installed +in order to be able to use the GUI. @@ -44,9 +45,9 @@ The directories searched for skins are (in order): -Note that the first path may vary according to the way MPlayer was configured -(see the and arguments of -the configure script). +Note that the first path may vary according to the way MPlayer +was configured (see the and +arguments of the configure script). @@ -62,8 +63,8 @@ listed above, for example: 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 MPlayer. This means that you can even have shaped -windows if your X server has the XShape extension. +transparent when viewed by MPlayer. This means +that you can even have shaped windows if your X server has the XShape extension. @@ -85,11 +86,11 @@ by a right click). The main window and/or the - playbar is where you can control MPlayer. - The background of the window is an image. Various items can (and must) be placed - in the window: buttons, potmeters - (sliders) and labels. For every item, you must specify its - position and size. + playbar is where you can control + MPlayer. The background of the window is an image. + Various items can (and must) be placed in the window: buttons, + potmeters (sliders) and labels. + For every item, you must specify its position and size. A button has three states (pressed, released, disabled), thus its image must be divided into three parts vertically. See the @@ -125,12 +126,13 @@ by a right click). - The skin menu is just a way to control MPlayer 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 skin menu is just a way to control + MPlayer 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). A menu entry is defined by its position and size in the image (see the @@ -141,9 +143,10 @@ by a right click). There is an important thing not mentioned yet: For buttons, potmeters and - menu entries to work, MPlayer must know what to do if they are clicked. This - is done by messages (events). For these items - you must define the messages to be generated when they are clicked. + menu entries to work, MPlayer must know what to + do if they are clicked. This is done by messages + (events). For these items you must define the messages to be generated when + they are clicked. @@ -154,8 +157,8 @@ You need the following files to build a skin: The configuration file named skin tells - MPlayer how to put different parts of the skin together and what to do if - you click somewhere in the window. + MPlayer how to put different parts of the skin + together and what to do if you click somewhere in the window. The background image for the main window. @@ -266,7 +269,7 @@ end The name of an image file must be given without leading directories - images are searched for in the Skin directory. You may (but you need not) specify the extension of the file. If the file does -not exist, MPlayer tries to load the file +not exist, MPlayer tries to load the file <filename>.<ext>, where png and PNG are tried for <ext> (in this order). The first matching file will be used. @@ -295,8 +298,8 @@ shown in this illustration: Here is an example to make this clear. Suppose that you have an image called main.png that you use for the main window: base = main, -1, -1 -MPlayer tries to load main, main.png, -main.PNG files. +MPlayer tries to load main, +main.png, main.PNG files. -- cgit v1.2.3