# HG changeset patch # User diego # Date 1136037827 0 # Node ID 3f842e148e1c6fd6c4b2480587cbbcef6842df54 # Parent 4c590d768a07da647221cff3e104b7182414d8e7 Guide on creating quality skins. diff -r 4c590d768a07 -r 3f842e148e1c DOCS/xml/en/skin.xml --- a/DOCS/xml/en/skin.xml Sat Dec 31 14:01:19 2005 +0000 +++ b/DOCS/xml/en/skin.xml Sat Dec 31 14:03:47 2005 +0000 @@ -1103,4 +1103,54 @@ + +Creating quality skins + + +So you have read up on creating skins for the +MPlayer GUI, done your best with the +Gimp and wish to submit your skin to us? +Read on for some guidelines to avoid common mistakes and produce +a high quality skin. + + + +We want skins that we add to our repository to conform to certain +quality standards. There are also a number of things that you can do +to make our lives easier. + + + +As an example you can look at the Blue skin, +it satisfies all the criteria listed below since version 1.5. + + + + Each skin should come with a + README file that contains information about + you, the author, copyright and license notices and anything else + you wish to add. If you wish to have a changelog, this file is a + good place. + + There should be a file VERSION + with nothing more than the version number of the skin on a single + line (e.g. 1.0). + + Horizontal and vertical controls (sliders like volume + or position) should have the center of the knob properly centered on + the middle of the slider. It should be possible to move the knob to + both ends of the slider, but not past it. + + Skin elements should have the right sizes declared + in the skin file. If this is not the case you can click outside of + e.g. a button and still trigger it or click inside its area and not + trigger it. + + The skin file should be + prettyprinted and not contain tabs. Prettyprinted means that the + numbers should line up neatly in columns. + + + +