MediaMonkey Wiki - User contributions [en]

Tagging Search Sites

2007-11-29T23:53:45Z

Gege: Added Coveralia and LyricWiki.org

Forum discussion topic for this list is [http://www.mediamonkey.com/forum/viewtopic.php?t=17993 here].

'''TODO:'''
* Quality, quantity and specialization (e.g. commercial, electronic, oldtimers, ...) of the information
* Cover quality (and size) and only front, or also label, inside, back?
* Indication of usability for automatic taggers (e.g. MM Search scripts)
* Layout improvements (use icons instead of common descriptions, use more columns, nicer table style, ...)

== Multiple tag information ==

{| border="1"
|-
! Website !! Comments
|-
|[http://www.allmusic.com All Music] || Huge collection, mostly popular and classical. Very good quality, includes front cover.
|-
|[http://www.amazon.com Amazon.com] || Huge collection, mostly popular and classical. Good quality, includes front cover.
|-
|[http://www.amazon.co.uk Amazon.co.uk] || Huge collection, mostly popular and classical. Good quality, includes front cover.
|-
| [http://www.amazon.ca Amazon.ca] || Huge collection, mostly popular and classical. Good quality, includes front cover.
|-
|[http://www.amazon.de Amazon.de] || Huge collection, mostly popular and classical. Good quality, includes front cover.
|-
|[http://www.amazon.fr Amazon.fr] || Huge collection, mostly popular and classical. Good quality, includes front cover.
|-
|[http://www.amazon.co.jp Amazon.co.jp] || Huge collection, mostly popular and classical. Good quality, includes front cover.
|-
|[http://www.gracenote.com/prof/music/index_old.html Gracenote CDDB] ||
|-
|[http://www.musicip.com/dns/index.jsp MusicDNS] ||
|-
|[http://www.musicbrainz.org MusicBrainz] ||
|-
|[http://www.freedb.org FreeDB] ||
|-
|[http://www.rateyourmusic.com Rate Your Music] || For old vinyl releases, LPs and Singles.
|-
|[http://www.discogs.com Discogs] || For electronic and DJ music. Includes front cover.
|-
|[http://www.juno.co.uk Juno Records] || For electronic music. Large artwork.
|-
|[http://musik.ciao.de/ CIAO! (Musik Category)] ||
|-
|[http://www.swisscharts.com Swiss Charts] ||
|-
|[http://www.cdnow.com CDNow] ||
|-
|[http://www.cduniverse.com/ CD Universe] ||
|-
|[http://www.wikipedia.com Wikipedia] ||
|-
|[http://www.tesco.com/entertainment/search.aspx?Ntt=&Ntk=primary&VSI=2-CD&Ntx=mode%2Bmatchall&Nty=1&N=7 Tesco Entertainment] ||
|}

== LRC Lyrics Only ==

{| border="1"
|-
! Website !! Comments
|-
|[http://www.lrcdb.org/browse.php LrcDB] || Extensive. Search on lyrics text, artist, title. Single letter index. With preview. Ability to upload (once registered).
|-
|[http://www.fortunecity.com/tinpan/marrfield/500/all_lyrics.htm AllLyrics] || Quite extensive. No search capabilities. Single letter index.
|-
|[http://lrclyrics.50webs.com/ LrcLyrics] || Few. No search capabilities. Multi-letter index.
|-
|[http://filebox.vt.edu/a/aekamal/Lyrics/ Lyrics] || Very few. Simple file listing.
|}

== Lyric Sites ==

{| border="1"
|-
! Website !! Comments
|-[http://www.azlyrics.com AZLyrics] || Many Lyrics from Multiple Artists
|-
|[http://www.songmeangings.net SongMeanings] || Many Lyrics with Comments that describe what the song is about
|-
|[http://www.hhdb.com/ HipHopAintDead] || Hip-hop/Underground Hip-Hop Lyrics
|-
|[http://www.undergroundraplyrics.com/ Underground Rap Lyrics] || Hip-hop/Underground Hip-Hop Lyrics
|-
|[http://http://www.hiphop-lyrics.com/ Hip-Hop Lyrics] || Hip-hop/Underground Hip-Hop Lyrics
|-
|[http://www.elyrics.net/ Elyrics] || Many Lyrics from Multiple Artists
|-
|[http://www.goodwinmusic.com/lyrics.html GoodWinMusic] || Country Music Lyrics
|-
|[http://www.leoslyrics.com/ LeoLyrics] || Many Lyrics from Multiple Artists
|-
|[http://lyricsplayground.com/ Lyrics PlayGround] || Many Lyrics from Multiple Artists
|-
|[http://www.music-sites.net/mediasearch/lyrics.html Music-Sites] || Meta-Search For Lyrics
|-
|[http://www.rockabilly.nl/lyrics/lyrics.htm Rock A Billy] || Rock n Roll Lyrics
|-
|[http://blueslyrics.tripod.com/ Blue's Lyrics] || Blue's Lyrics
|-
|[http://www.heptune.com/lyrics.html Heptune] || Jazz and Blue's Lyrics
|-
|[http://www.sing365.com/index.html Sing365] || Many Lyrics from Multiple Artists
|-
|[http://www.lyricwiki.org LyricWiki.org] || Community maintained database.
|}

== Covers Only ==

{| border="1"
|-
! Website !! Comments
|-
|[http://www.albumart.org/ Album Art] || (Amazon covers) Good quality. Minimum 300px.
|-
|[http://images.google.com Google Images] || Various. Good quality.
|-
|[http://images.search.yahoo.com Yahoo! Images] || Various. Good quality.
|-
|[http://www.urbancovers.com Urban Covers] ||
|-
|[http://mega-search.net Mega Search] ||
|-
|[http://coverparadise.to Cover Paradise] || Clean site. German, but easy to use nonetheless.
|-
|[http://www.freecovers.net Free Covers] || Huge collection. Ability to upload (once registered).
|-
|[http://www.allcdcovers.com/ AllCdCovers] ||
|-
|[http://www.thejosher.net/iTunes/ iTunes] ||
|-
|[http://www.cdcovers.cc/ CdCovers] ||
|-
|[http://freespace.virgin.net/love.day/coverheaven/index.htm Cover Heaven] ||
|-
|[http://epiclectic.com/ Epiclectic] || For older music.
|-
|[http://www.flickr.com/groups/album_art_1/ Flickr] ||
|-
|[http://www.kompaktkiste.de Kompakt Kiste] || All kinds of electronic music (not euro-dance or other chart-electronics) Large artwork.
|-
|[http://www.mixtrap.com/shop/ Mixtrap] || Hip-Hop Mixtapes Covers
|-
|[http://www.mixtapeusa.com/ Mix Tape USA] || Hip-Hop Mixtapes Covers
|-
|[http://www.smartpunk.com/ Smart Punk] || Rock/Alternative etc Covers
|-
|[http://www.interpunk.com/ InterPunk] || Punk Music Covers
|-
|[http://cdbaby.com/ CDBaby] || Indie Music
|-
|[http://www.coveralia.com/ Coveralia] || Spanish site. High-resolution covers.
|}

Installation Packages (MM4)

2007-11-27T16:23:27Z

Gege:

==Installation Packages structure==

Additional Extensions can be easily installed in MediaMonkey using Installation Packages. Each installation package is a ZIP
file with MMIP extension, when such a file is executed, it is automatically installed in MediaMonkey (see Tools|Extensions menu item).
Inside the package can be included any files that need to be installed, but there are also some special files that can or must be included:

;Install.ini
:Mandantory - this file describes the package and what to install.
;App.ico
:Optional - Icon of the package.
;Uninstall.ini
:Optional (but suggested) - describes steps on uninstall, which files to remove, etc.
;Uninstall.vbs
:Optional - is automatically preserved by installer and can be called by Uninstall.ini on uninstallation.

===Install.ini file===

The installation file has a structure of an ini file, i.e. some sections with keys and values.

====[Header] section====

Each install.ini file starts with a mandantory section [Header]. It contains basic information about the product being installed, namely:

;ID
:Unique string identification of the product. It should contain only alphanumeric characters, digits or underscores.
;Title
:Product title shown to user.
;Description
:Detailed product description.
;VersionMajor
:Major version number.
;VersionMinor
:Minor version number.
;VersionRelease
:Release number.
;VersionBuild
:Build number. Any of these numbers can be missing, e.g. if only VersionMajor and VersionMinor are present, the version number shown to user would be 'VersionMajor.VersionMinor'.
;Type
:Type of product being installed. Either script, skin or misc. This is used so that MM knows more about the extension.
;UpdateURL
:URL where MM should look for updates of this product. If this key is missing, MM can still try to find out whether a new version has been released by asking MM web scripting repository using product ID above.

====Other sections====

After the header section, there can follow an arbitrary number of other sections specifying actions installer should do. The possible sections follow.

====[Copy] section====

This section tells where individual files from the installer ZIP file should be placed. Expected keys there include:
;Src
:Source file name in the installer ZIP file.
;Tgt
:Destination file path. It can contain constants useful for placing files in common paths (the same as InnoSetup constants). Currently implemented constants:
:*{app} = MediaMonkey installation folder.
;Flags
:Comma separated list of flags related to this copy operation. Can be any of:
:;Overwriteifnewer
::If the target file already exists, it will be overwritten only if the source file is newer. If this flag isn't specified, the target file will always be overwritten.
If your package contains various files to be copied, you need one [Copy] Section for each individual file.

====[Delete] section====

This section is primarily for 'uninstall.ini' file. The only parameter is:

;File
:Full path of the file to be deleted.

====[Execute] section====

This section allows developer to execute a script and thus do any other necessary installation/uninstallation actions, for example prepare Scripts.ini content. Expected keys here are:
;File
:A script file to execute. There is either a fully specified path entered here, or if there is no path information, the script is expected to be located in the installation ZIP file and is prepared to a temporary location prior its execution. For uninstaller 'uninstall.vbs' can be specified here and it would be called from its location.
;Function
:A name of function to be called within the script file. If this entry is missing or empty, it's supposed that there's no need for calling a function and simple execution of the script file does whatever a developer wants to do.

===Uninstall.ini file===

'Uninstall.ini' file will is very similar to 'Install.ini' file, just [Header] section is missing. Other sections allow developers to properly delete installed files and remove any other traces of installation, e.g. execute a script that would delete some entries in Scripts.ini file.

==Sample Installation Package==

===Sample content of MMIP file===

Sample MMIP file can contain e.g. the following files:
*App.ico
*Install.ini
*Sample Option Sheets.vbs
*Uninstall.ini
*Uninstall.vbs

===Sample Install.ini file===

<source lang=ini>
[Header]
ID=MyScript1
Title=Sample Option Sheets
Description=Sample Option Sheets.vbs
VersionMajor=1
VersionMinor=0
VersionRelease=0
VersionBuild=0
Type=script
UpdateURL=http://localhost/myscript1/version.xml

[Copy]
Src=Sample Option Sheets.vbs
Tgt={app}\scripts\auto\Sample Option Sheets.vbs

[Copy]
Src=Sample.ico
Tgt={app}\scripts\auto\Sample.ico

[Copy]
Src=Icons\*.*
Tgt={app}\Icons\

[Execute]
File={app}\scripts\auto\Sample Option Sheets.vbs
Function=OnStartup()
</source>

===Sample Uninstall.ini file===

<source lang=ini>
[Delete]
File={app}\scripts\auto\Sample Option Sheets.vbs
File={app}\scripts\auto\Sample.ico

[Execute]
File=Uninstall.vbs
</source>

===Sample Uninstall.vbs file===

<source lang="vb">
myName = "Sample Script" 'Put script name here
iniSec = "SampleScript" 'Put ini section name here

MsgDeleteSettings = "Do you want to remove " & myName & " settings as well?" & vbNewLine & _
"If you click No, script settings will be left in MediaMonkey.ini"

If (Not (SDB.IniFile Is Nothing)) and (MsgBox(MsgDeleteSettings, vbYesNo) = vbYes) Then
SDB.IniFile.DeleteSection(iniSec)
End If
</source>

Installation Packages (MM4)

2007-10-31T18:54:28Z

Gege: /* Sample Uninstall.vbs file */

==Installation Packages structure==

Additional Extensions can be easily installed in MediaMonkey using Installation Packages. Each installation package is a ZIP
file with MMIP extension, when such a file is executed, it is automatically installed in MediaMonkey (see Tools|Extensions menu item).
Inside the package can be included any files that need to be installed, but there are also some special files that can or must be included:

;Install.ini
:Mandantory - this file describes the package and what to install.
;App.ico
:Optional - Icon of the package.
;Uninstall.ini
:Optional (but suggested) - describes steps on uninstall, which files to remove, etc.
;Uninstall.vbs
:Optional - is automatically preserved by installer and can be called by Uninstall.ini on uninstallation.

===Install.ini file===

The installation file has a structure of an ini file, i.e. some sections with keys and values.

====[Header] section====

Each install.ini file starts with a mandantory section [Header]. It contains basic information about the product being installed, namely:

;ID
:Unique string identification of the product. It should contain only alphanumeric characters, digits or underscores.
;Title
:Product title shown to user.
;Description
:Detailed product description.
;VersionMajor
:Major version number.
;VersionMinor
:Minor version number.
;VersionRelease
:Release number.
;VersionBuild
:Build number. Any of these numbers can be missing, e.g. if only VersionMajor and VersionMinor are present, the version number shown to user would be 'VersionMajor.VersionMinor'.
;Type
:Type of product being installed. Either script, skin or misc. This is used so that MM knows more about the extension.
;UpdateURL
:URL where MM should look for updates of this product. If this key is missing, MM can still try to find out whether a new version has been released by asking MM web scripting repository using product ID above.

====Other sections====

After the header section, there can follow an arbitrary number of other sections specifying actions installer should do. The possible sections follow.

====[Copy] section====

This section tells where individual files from the installer ZIP file should be placed. Expected keys there include:
;Src
:Source file name in the installer ZIP file.
;Tgt
:Destination file path. It can contain constants useful for placing files in common paths (the same as InnoSetup constants). Currently implemented constants:
:*{app} = MediaMonkey installation folder.
;Flags
:Comma separated list of flags related to this copy operation. Can be any of:
:;Overwriteifnewer
::If the target file already exists, it will be overwritten only if the source file is newer. If this flag isn't specified, the target file will always be overwritten.
If your package contains various files to be copied, you need one [Copy] Section for each individual file.

====[Delete] section====

This section is primarily for 'uninstall.ini' file. The only parameter is:

;File
:Full path of the file to be deleted.

====[Execute] section====

This section allows developer to execute a script and thus do any other necessary installation/uninstallation actions, for example prepare Scripts.ini content. Expected keys here are:
;File
:A script file to execute. There is either a fully specified path entered here, or if there is no path information, the script is expected to be located in the installation ZIP file and is prepared to a temporary location prior its execution. For uninstaller 'uninstall.vbs' can be specified here and it would be called from its location.
;Function
:A name of function to be called within the script file. If this entry is missing or empty, it's supposed that there's no need for calling a function and simple execution of the script file does whatever a developer wants to do.

===Uninstall.ini file===

'Uninstall.ini' file will is very similar to 'Install.ini' file, just [Header] section is missing. Other sections allow developers to properly delete installed files and remove any other traces of installation, e.g. execute a script that would delete some entries in Scripts.ini file.

==Sample Installation Package==

===Sample content of MMIP file===

Sample MMIP file can contain e.g. the following files:
*App.ico
*Install.ini
*Sample Option Sheets.vbs
*Uninstall.ini
*Uninstall.vbs

===Sample Install.ini file===

<source lang=ini>
[Header]
ID=MyScript1
Title=Sample Option Sheets
Description=Sample Option Sheets.vbs
VersionMajor=1
VersionMinor=0
VersionRelease=0
VersionBuild=0
Type=script
UpdateURL=http://localhost/myscript1/version.xml

[Copy]
Src=Sample Option Sheets.vbs
Tgt={app}\scripts\auto\Sample Option Sheets.vbs

[Copy]
Src=Sample.ico
Tgt={app}\scripts\auto\Sample.ico

[Execute]
File={app}\scripts\auto\Sample Option Sheets.vbs
Function=OnStartup()
</source>

===Sample Uninstall.ini file===

<source lang=ini>
[Delete]
File={app}\scripts\auto\Sample Option Sheets.vbs

[Execute]
File=Uninstall.vbs
</source>

===Sample Uninstall.vbs file===

<source lang="vb">
myName = "Sample Script" 'Put script name here
iniSec = "SampleScript" 'Put ini section name here

MsgDeleteSettings = "Do you want to remove " & myName & " settings as well?" & vbNewLine & _
"If you click No, script settings will be left in MediaMonkey.ini"

If (Not (SDB.IniFile Is Nothing)) and (MsgBox(MsgDeleteSettings, vbYesNo) = vbYes) Then
SDB.IniFile.DeleteSection(iniSec)
End If
</source>

Installation Packages (MM4)

2007-10-31T12:09:03Z

Gege: Added multiple copies sample to Install.ini

==Installation Packages structure==

Additional Extensions can be easily installed in MediaMonkey using Installation Packages. Each installation package is a ZIP
file with MMIP extension, when such a file is executed, it is automatically installed in MediaMonkey (see Tools|Extensions menu item).
Inside the package can be included any files that need to be installed, but there are also some special files that can or must be included:

;Install.ini
:Mandantory - this file describes the package and what to install.
;App.ico
:Optional - Icon of the package.
;Uninstall.ini
:Optional (but suggested) - describes steps on uninstall, which files to remove, etc.
;Uninstall.vbs
:Optional - is automatically preserved by installer and can be called by Uninstall.ini on uninstallation.

===Install.ini file===

The installation file has a structure of an ini file, i.e. some sections with keys and values.

====[Header] section====

Each install.ini file starts with a mandantory section [Header]. It contains basic information about the product being installed, namely:

;ID
:Unique string identification of the product. It should contain only alphanumeric characters, digits or underscores.
;Title
:Product title shown to user.
;Description
:Detailed product description.
;VersionMajor
:Major version number.
;VersionMinor
:Minor version number.
;VersionRelease
:Release number.
;VersionBuild
:Build number. Any of these numbers can be missing, e.g. if only VersionMajor and VersionMinor are present, the version number shown to user would be 'VersionMajor.VersionMinor'.
;Type
:Type of product being installed. Either script, skin or misc. This is used so that MM knows more about the extension.
;UpdateURL
:URL where MM should look for updates of this product. If this key is missing, MM can still try to find out whether a new version has been released by asking MM web scripting repository using product ID above.

====Other sections====

After the header section, there can follow an arbitrary number of other sections specifying actions installer should do. The possible sections follow.

====[Copy] section====

This section tells where individual files from the installer ZIP file should be placed. Expected keys there include:
;Src
:Source file name in the installer ZIP file.
;Tgt
:Destination file path. It can contain constants useful for placing files in common paths (the same as InnoSetup constants). Currently implemented constants:
:*{app} = MediaMonkey installation folder.
;Flags
:Comma separated list of flags related to this copy operation. Can be any of:
:;Overwriteifnewer
::If the target file already exists, it will be overwritten only if the source file is newer. If this flag isn't specified, the target file will always be overwritten.
If your package contains various files to be copied, you need one [Copy] Section for each individual file.

====[Delete] section====

This section is primarily for 'uninstall.ini' file. The only parameter is:

;File
:Full path of the file to be deleted.

====[Execute] section====

This section allows developer to execute a script and thus do any other necessary installation/uninstallation actions, for example prepare Scripts.ini content. Expected keys here are:
;File
:A script file to execute. There is either a fully specified path entered here, or if there is no path information, the script is expected to be located in the installation ZIP file and is prepared to a temporary location prior its execution. For uninstaller 'uninstall.vbs' can be specified here and it would be called from its location.
;Function
:A name of function to be called within the script file. If this entry is missing or empty, it's supposed that there's no need for calling a function and simple execution of the script file does whatever a developer wants to do.

===Uninstall.ini file===

'Uninstall.ini' file will is very similar to 'Install.ini' file, just [Header] section is missing. Other sections allow developers to properly delete installed files and remove any other traces of installation, e.g. execute a script that would delete some entries in Scripts.ini file.

==Sample Installation Package==

===Sample content of MMIP file===

Sample MMIP file can contain e.g. the following files:
*App.ico
*Install.ini
*Sample Option Sheets.vbs
*Uninstall.ini
*Uninstall.vbs

===Sample Install.ini file===

<source lang=ini>
[Header]
ID=MyScript1
Title=Sample Option Sheets
Description=Sample Option Sheets.vbs
VersionMajor=1
VersionMinor=0
VersionRelease=0
VersionBuild=0
Type=script
UpdateURL=http://localhost/myscript1/version.xml

[Copy]
Src=Sample Option Sheets.vbs
Tgt={app}\scripts\auto\Sample Option Sheets.vbs

[Copy]
Src=Sample.ico
Tgt={app}\scripts\auto\Sample.ico

[Execute]
File={app}\scripts\auto\Sample Option Sheets.vbs
Function=OnStartup()
</source>

===Sample Uninstall.ini file===

<source lang=ini>
[Delete]
File={app}\scripts\auto\Sample Option Sheets.vbs

[Execute]
File=Uninstall.vbs
</source>

===Sample Uninstall.vbs file===

<source lang="vb">
Dim ini : Set ini = SDB.IniFile
Dim myName : myName = "Sample Script" 'Put script name here
Dim iniSec : iniSec = "SampleScript" 'Put ini section name here

MsgDeleteSettings = "Do you want to remove " & myName & " settings as well?" & vbNewLine & _
"If you click No, script settings will be left in MediaMonkey.ini"

If (Not (ini Is Nothing)) and (MsgBox(MsgDeleteSettings, vbYesNo) = vbYes) Then
ini.DeleteSection(iniSec)
End If
</source>

Installation Packages (MM4)

2007-10-31T12:03:00Z

Gege: /* Sample Uninstall.ini file */

==Installation Packages structure==

Additional Extensions can be easily installed in MediaMonkey using Installation Packages. Each installation package is a ZIP
file with MMIP extension, when such a file is executed, it is automatically installed in MediaMonkey (see Tools|Extensions menu item).
Inside the package can be included any files that need to be installed, but there are also some special files that can or must be included:

;Install.ini
:Mandantory - this file describes the package and what to install.
;App.ico
:Optional - Icon of the package.
;Uninstall.ini
:Optional (but suggested) - describes steps on uninstall, which files to remove, etc.
;Uninstall.vbs
:Optional - is automatically preserved by installer and can be called by Uninstall.ini on uninstallation.

===Install.ini file===

The installation file has a structure of an ini file, i.e. some sections with keys and values.

====[Header] section====

Each install.ini file starts with a mandantory section [Header]. It contains basic information about the product being installed, namely:

;ID
:Unique string identification of the product. It should contain only alphanumeric characters, digits or underscores.
;Title
:Product title shown to user.
;Description
:Detailed product description.
;VersionMajor
:Major version number.
;VersionMinor
:Minor version number.
;VersionRelease
:Release number.
;VersionBuild
:Build number. Any of these numbers can be missing, e.g. if only VersionMajor and VersionMinor are present, the version number shown to user would be 'VersionMajor.VersionMinor'.
;Type
:Type of product being installed. Either script, skin or misc. This is used so that MM knows more about the extension.
;UpdateURL
:URL where MM should look for updates of this product. If this key is missing, MM can still try to find out whether a new version has been released by asking MM web scripting repository using product ID above.

====Other sections====

After the header section, there can follow an arbitrary number of other sections specifying actions installer should do. The possible sections follow.

====[Copy] section====

This section tells where individual files from the installer ZIP file should be placed. Expected keys there include:
;Src
:Source file name in the installer ZIP file.
;Tgt
:Destination file path. It can contain constants useful for placing files in common paths (the same as InnoSetup constants). Currently implemented constants:
:*{app} = MediaMonkey installation folder.
;Flags
:Comma separated list of flags related to this copy operation. Can be any of:
:;Overwriteifnewer
::If the target file already exists, it will be overwritten only if the source file is newer. If this flag isn't specified, the target file will always be overwritten.
If your package contains various files to be copied, you need one [Copy] Section for each individual file.

====[Delete] section====

This section is primarily for 'uninstall.ini' file. The only parameter is:

;File
:Full path of the file to be deleted.

====[Execute] section====

This section allows developer to execute a script and thus do any other necessary installation/uninstallation actions, for example prepare Scripts.ini content. Expected keys here are:
;File
:A script file to execute. There is either a fully specified path entered here, or if there is no path information, the script is expected to be located in the installation ZIP file and is prepared to a temporary location prior its execution. For uninstaller 'uninstall.vbs' can be specified here and it would be called from its location.
;Function
:A name of function to be called within the script file. If this entry is missing or empty, it's supposed that there's no need for calling a function and simple execution of the script file does whatever a developer wants to do.

===Uninstall.ini file===

'Uninstall.ini' file will is very similar to 'Install.ini' file, just [Header] section is missing. Other sections allow developers to properly delete installed files and remove any other traces of installation, e.g. execute a script that would delete some entries in Scripts.ini file.

==Sample Installation Package==

===Sample content of MMIP file===

Sample MMIP file can contain e.g. the following files:
*App.ico
*Install.ini
*Sample Option Sheets.vbs
*Uninstall.ini
*Uninstall.vbs

===Sample Install.ini file===

<source lang=ini>
[Header]
ID=MyScript1
Title=Sample Option Sheets
Description=Sample Option Sheets.vbs
VersionMajor=1
VersionMinor=0
VersionRelease=0
VersionBuild=0
Type=script
UpdateURL=http://localhost/myscript1/version.xml

[Copy]
Src=Sample Option Sheets.vbs
Tgt={app}\scripts\auto\Sample Option Sheets.vbs

[Execute]
File={app}\scripts\auto\Sample Option Sheets.vbs
Function=OnStartup()
</source>

===Sample Uninstall.ini file===

<source lang=ini>
[Delete]
File={app}\scripts\auto\Sample Option Sheets.vbs

[Execute]
File=Uninstall.vbs
</source>

===Sample Uninstall.vbs file===

<source lang="vb">
Dim ini : Set ini = SDB.IniFile
Dim myName : myName = "Sample Script" 'Put script name here
Dim iniSec : iniSec = "SampleScript" 'Put ini section name here

MsgDeleteSettings = "Do you want to remove " & myName & " settings as well?" & vbNewLine & _
"If you click No, script settings will be left in MediaMonkey.ini"

If (Not (ini Is Nothing)) and (MsgBox(MsgDeleteSettings, vbYesNo) = vbYes) Then
ini.DeleteSection(iniSec)
End If
</source>

Installation Packages (MM4)

2007-10-31T12:02:27Z

Gege: Added sample Uninstall.vbs

==Installation Packages structure==

Additional Extensions can be easily installed in MediaMonkey using Installation Packages. Each installation package is a ZIP
file with MMIP extension, when such a file is executed, it is automatically installed in MediaMonkey (see Tools|Extensions menu item).
Inside the package can be included any files that need to be installed, but there are also some special files that can or must be included:

;Install.ini
:Mandantory - this file describes the package and what to install.
;App.ico
:Optional - Icon of the package.
;Uninstall.ini
:Optional (but suggested) - describes steps on uninstall, which files to remove, etc.
;Uninstall.vbs
:Optional - is automatically preserved by installer and can be called by Uninstall.ini on uninstallation.

===Install.ini file===

The installation file has a structure of an ini file, i.e. some sections with keys and values.

====[Header] section====

Each install.ini file starts with a mandantory section [Header]. It contains basic information about the product being installed, namely:

;ID
:Unique string identification of the product. It should contain only alphanumeric characters, digits or underscores.
;Title
:Product title shown to user.
;Description
:Detailed product description.
;VersionMajor
:Major version number.
;VersionMinor
:Minor version number.
;VersionRelease
:Release number.
;VersionBuild
:Build number. Any of these numbers can be missing, e.g. if only VersionMajor and VersionMinor are present, the version number shown to user would be 'VersionMajor.VersionMinor'.
;Type
:Type of product being installed. Either script, skin or misc. This is used so that MM knows more about the extension.
;UpdateURL
:URL where MM should look for updates of this product. If this key is missing, MM can still try to find out whether a new version has been released by asking MM web scripting repository using product ID above.

====Other sections====

After the header section, there can follow an arbitrary number of other sections specifying actions installer should do. The possible sections follow.

====[Copy] section====

This section tells where individual files from the installer ZIP file should be placed. Expected keys there include:
;Src
:Source file name in the installer ZIP file.
;Tgt
:Destination file path. It can contain constants useful for placing files in common paths (the same as InnoSetup constants). Currently implemented constants:
:*{app} = MediaMonkey installation folder.
;Flags
:Comma separated list of flags related to this copy operation. Can be any of:
:;Overwriteifnewer
::If the target file already exists, it will be overwritten only if the source file is newer. If this flag isn't specified, the target file will always be overwritten.
If your package contains various files to be copied, you need one [Copy] Section for each individual file.

====[Delete] section====

This section is primarily for 'uninstall.ini' file. The only parameter is:

;File
:Full path of the file to be deleted.

====[Execute] section====

This section allows developer to execute a script and thus do any other necessary installation/uninstallation actions, for example prepare Scripts.ini content. Expected keys here are:
;File
:A script file to execute. There is either a fully specified path entered here, or if there is no path information, the script is expected to be located in the installation ZIP file and is prepared to a temporary location prior its execution. For uninstaller 'uninstall.vbs' can be specified here and it would be called from its location.
;Function
:A name of function to be called within the script file. If this entry is missing or empty, it's supposed that there's no need for calling a function and simple execution of the script file does whatever a developer wants to do.

===Uninstall.ini file===

'Uninstall.ini' file will is very similar to 'Install.ini' file, just [Header] section is missing. Other sections allow developers to properly delete installed files and remove any other traces of installation, e.g. execute a script that would delete some entries in Scripts.ini file.

==Sample Installation Package==

===Sample content of MMIP file===

Sample MMIP file can contain e.g. the following files:
*App.ico
*Install.ini
*Sample Option Sheets.vbs
*Uninstall.ini
*Uninstall.vbs

===Sample Install.ini file===

<source lang=ini>
[Header]
ID=MyScript1
Title=Sample Option Sheets
Description=Sample Option Sheets.vbs
VersionMajor=1
VersionMinor=0
VersionRelease=0
VersionBuild=0
Type=script
UpdateURL=http://localhost/myscript1/version.xml

[Copy]
Src=Sample Option Sheets.vbs
Tgt={app}\scripts\auto\Sample Option Sheets.vbs

[Execute]
File={app}\scripts\auto\Sample Option Sheets.vbs
Function=OnStartup()
</source>

===Sample Uninstall.ini file===

<source lang=ini>
[Delete]
File={app}\scripts\auto\Sample Option Sheets.vbs

[Execute]
File=uninstall.vbs
</source>

===Sample Uninstall.vbs file===

<source lang="vb">
Dim ini : Set ini = SDB.IniFile
Dim myName : myName = "Sample Script" 'Put script name here
Dim iniSec : iniSec = "SampleScript" 'Put ini section name here

MsgDeleteSettings = "Do you want to remove " & myName & " settings as well?" & vbNewLine & _
"If you click No, script settings will be left in MediaMonkey.ini"

If (Not (ini Is Nothing)) and (MsgBox(MsgDeleteSettings, vbYesNo) = vbYes) Then
ini.DeleteSection(iniSec)
End If
</source>

Installation Packages (MM4)

2007-10-12T15:24:13Z

Gege: /* [Copy] section */ Added info about multiple files to be copied

==Installation Packages structure==

Additional Extensions can be easily installed in MediaMonkey using Installation Packages. Each installation package is a ZIP
file with MMIP extension, when such a file is executed, it is automatically installed in MediaMonkey (see Tools|Extensions menu item).
Inside the package can be included any files that need to be installed, but there are also some special files that can or must be included:

;Install.ini
:Mandantory - this file describes the package and what to install.
;App.ico
:Optional - Icon of the package.
;Uninstall.ini
:Optional (but suggested) - describes steps on uninstall, which files to remove, etc.
;Uninstall.vbs
:Optional - is automatically preserved by installer and can be called by Uninstall.ini on uninstallation.

===Install.ini file===

The installation file has a structure of an ini file, i.e. some sections with keys and values.

====[Header] section====

Each install.ini file starts with a mandantory section [Header]. It contains basic information about the product being installed, namely:

;ID
:Unique string identification of the product. It should contain only alphanumeric characters, digits or underscores.
;Title
:Product title shown to user.
;Description
:Detailed product description.
;VersionMajor
:Major version number.
;VersionMinor
:Minor version number.
;VersionRelease
:Release number.
;VersionBuild
:Build number. Any of these numbers can be missing, e.g. if only VersionMajor and VersionMinor are present, the version number shown to user would be 'VersionMajor.VersionMinor'.
;Type
:Type of product being installed. Either script, skin or misc. This is used so that MM knows more about the extension.
;UpdateURL
:URL where MM should look for updates of this product. If this key is missing, MM can still try to find out whether a new version has been released by asking MM web scripting repository using product ID above.

====Other sections====

After the header section, there can follow an arbitrary number of other sections specifying actions installer should do. The possible sections follow.

====[Copy] section====

This section tells where individual files from the installer ZIP file should be placed. Expected keys there include:
;Src
:Source file name in the installer ZIP file.
;Tgt
:Destination file path. It can contain constants useful for placing files in common paths (the same as InnoSetup constants). Currently implemented constants:
:*{app} = MediaMonkey installation folder.
;Flags
:Comma separated list of flags related to this copy operation. Can be any of:
:;Overwriteifnewer
::If the target file already exists, it will be overwritten only if the source file is newer. If this flag isn't specified, the target file will always be overwritten.
If your package contains various files to be copied, you need one [Copy] Section for each individual file.

====[Delete] section====

This section is primarily for 'uninstall.ini' file. The only parameter is:

;File
:Full path of the file to be deleted.

====[Execute] section====

This section allows developer to execute a script and thus do any other necessary installation/uninstallation actions, for example prepare Scripts.ini content. Expected keys here are:
;File
:A script file to execute. There is either a fully specified path entered here, or if there is no path information, the script is expected to be located in the installation ZIP file and is prepared to a temporary location prior its execution. For uninstaller 'uninstall.vbs' can be specified here and it would be called from its location.
;Function
:A name of function to be called within the script file. If this entry is missing or empty, it's supposed that there's no need for calling a function and simple execution of the script file does whatever a developer wants to do.

===Uninstall.ini file===

'Uninstall.ini' file will is very similar to 'Install.ini' file, just [Header] section is missing. Other sections allow developers to properly delete installed files and remove any other traces of installation, e.g. execute a script that would delete some entries in Scripts.ini file.

==Sample Installation Package==

===Sample content of MMIP file===

Sample MMIP file can contain e.g. the following files:
*App.ico
*Install.ini
*Sample Option Sheets.vbs
*Uninstall.ini
*Uninstall.vbs

===Sample Install.ini file===

<source lang=ini>
[Header]
ID=MyScript1
Title=Sample Option Sheets
Description=Sample Option Sheets.vbs
VersionMajor=1
VersionMinor=0
VersionRelease=0
VersionBuild=0
Type=script
UpdateURL=http://localhost/myscript1/version.xml

[Copy]
Src=Sample Option Sheets.vbs
Tgt={app}\scripts\auto\Sample Option Sheets.vbs

[Execute]
File={app}\scripts\auto\Sample Option Sheets.vbs
Function=OnStartup()
</source>

===Sample Uninstall.ini file===

<source lang=ini>
[Delete]
File={app}\scripts\auto\Sample Option Sheets.vbs

[Execute]
File=uninstall.vbs
</source>

Skins for MediaMonkey v3.0 and higher

2007-04-10T17:19:10Z

Gege: Changed link in top of the page from external to internal link

[[Skinning|''Go back to the '''main''' skinning page'']]

'''Listed Below are some skins for MediaMonkey v3.0 which currently is in the alpha stages. You may need to right click and use the "Save link as" option in your internet browser.'''

==Blake's skins==
===Monkey11===
[[Image:WMP11_blakeloth.jpg|right|thumb|300px|Blake's WMP11 look-a-like]]

'''Author:''' [[User:Blake|Blake]]

'''First released:''' 2007-02-25

'''Current version:''' [http://www.mediafire.com/?cjzxzjjmx2h Download #1] | [http://lajevardi.googlepages.com/Monkey11.msz Download #2] | [http://lajevardi.persiangig.com/app/mm.v3.0/Monkey11.msz Download #3] (v?.? - 2007-0?-??)

'''Notes:''' This skin is more inspired by WMP and it feels more like the original MediaMonkey skin. There are two versions available: The blue version (original) and the green version as shown in the screenshot

<br clear="all" />

==Morten's skins==

===WMP11===
[[Image:WMP11_m.jpg|right|thumb|300px|Morten's WMP11 skin for MM3]]

'''Author:''' [[User:Morten9300|Morten]]

'''First released:''' 2007-01-26

'''Current version:''' [http://www.diskusjon.no/index.php?act=Attach&type=post&id=139130 Download] (v1.2 - 2007-01-28)

'''Notes:''' This skin tries to look like Windows Media Player v11 as much as possible. Some usability enhancements are made that are not available in WMP11 itself.

<br clear="all" />

===iTunes 7===
[[Image:ITunes_morten.jpg|right|thumb|300px|Morten's iTunes 7 skin for MM3]]

'''Author:''' [[User:Morten9300|Morten]]

'''First released:''' 2007-01-26

'''Current version:''' [http://www.diskusjon.no/index.php?act=Attach&type=post&id=135227 Download] (v1.2 - 2007-01-28)

'''Notes:''' This skin tries to look like ITunes v7 as much as possible. Some usability enhancements are made that are not available in ITunes7 itself.

<br clear="all" />

==Tommae88's skins==
===Red Bruise===

[[Image:Red_bruise.jpg|right|thumb|300px|Tommae88's Red Bruise skin]]

'''Author:''' [[User:Tommae88|Tommae88]]

'''First released:''' 2007-03-02

'''Current version:''' [http://www.mediafire.com/?1nvhvvimmmz Download] (v1.2 - 2007-01-28)

'''Notes:''' This skin has a nice red quality over itself and is based on the default theme.

<br clear="all" />

== Authors with More than 2 Skin Screenshots ==

===Rovingcowboy's skins===

'''[http://www.mediamonkey.com/forum/viewtopic.php?p=27829#27829 For More Information Read This Forum Thread]
'''

'''[[Roving Cowboy's MM 3_ScreenShots]] |''' [http://www.angelfire.com/tx5/rovingcowboy/msagentsongs.html#Skins MM 3 DownLoads]'''

===Default Skin Recolored===
'''by Blake and by Tommae88'''

'''[http://www.mediamonkey.com/forum/viewtopic.php?p=78163#78163 the default royal blue, in modified colours Download links] |

'''[[Re - Colored Screenshots]]'''