Yes, a scripts database is something that has already been a long time in people's heads, including in mine.
Database:
As I suggested in the past, I'd like a database for all decent scripts, with all necessary information on them. The entries should contain script name, version, original date, last update, main category, subcategory, tags...
Interface:
Trusted/approved script developers should be able to log in on a page so they can add/edit their entries directly in the database.
New scripters have to gain trust and their scripts should pass through a trusted/approved script developer first.
Changes in the database should also be mentioned (automaticly of course) in a "What's new" kind of section on the scripts(database/forum) page.
Script manager:
A script manager within MediaMonkey would query the webdatabase and would receive a zipped up-to-date text version of the database.
Then, the script manager can check if all installed scripts are up-to-date or not, and if not it can prompt which scripts can be updated.
Installed/All scripts can easily be searched within the scripts manager by name, author, categories, tags. They can automaticly be installed/uninstalled (without special things to do for the user).
Discussions about the script can easily be followed by a direct link to the forum page.
Script packages/folders:
The scripts would be packed in one script package or in a separate script folder for each script (doesn't matter what script type, they all follow the same logic). The script manager would not keep a list of installed scripts because that can give problems if it gets corrupted or people delete it or so. Instead, it would just look in the scripts folder, and get the script info right from the script header (file).
Blabla:
I started "developing" something like this script manager, but I only did some basic stuff (like mySql-database, text file generation, downlaod-php-page for the zipped text file, basic download-and-list portion of the script manager).
The devs promise some kind of scripts manager in the next major release (2.6) so I'm curious.
I have been thinking about redoing both the general wishlist and the scripts list. I think scripters should be able to assign a "general wish" as ToScript. They should be able to say if they're working on it or not.
Just, I don't have the time to do this right now. The only thing so far I have done is made a categorised list of my own scripts.
(Old) MMScriptsManager:
BTW: for people that want to more easily install/manage scripts, I have already an application that combines most script-necessary stuff.
MMScriptsManager (External App for .Net Framework v2):
http://www.mediamonkey.com/forum/viewto ... 6310#36310
So you have all necessary MM-folders by hand, don't have to go in the Scripts.ini file, can easily add/remove script entries and see faulty ones,... and install new scripts by drag-and-dropping either the code text, or the script file link.
Yes, a scripts database is something that has already been a long time in people's heads, including in mine.
[u][b]Database:[/b][/u]
As I suggested in the past, I'd like a database for all decent scripts, with all necessary information on them. The entries should contain script name, version, original date, last update, main category, subcategory, tags...
[u][b]Interface:[/b][/u]
Trusted/approved script developers should be able to log in on a page so they can add/edit their entries directly in the database.
New scripters have to gain trust and their scripts should pass through a trusted/approved script developer first.
Changes in the database should also be mentioned (automaticly of course) in a "What's new" kind of section on the scripts(database/forum) page.
[u][b]Script manager:[/b][/u]
A script manager within MediaMonkey would query the webdatabase and would receive a zipped up-to-date text version of the database.
Then, the script manager can check if all installed scripts are up-to-date or not, and if not it can prompt which scripts can be updated.
Installed/All scripts can easily be searched within the scripts manager by name, author, categories, tags. They can automaticly be installed/uninstalled (without special things to do for the user).
Discussions about the script can easily be followed by a direct link to the forum page.
[u][b]Script packages/folders:[/b][/u]
The scripts would be packed in one script package or in a separate script folder for each script (doesn't matter what script type, they all follow the same logic). The script manager would not keep a list of installed scripts because that can give problems if it gets corrupted or people delete it or so. Instead, it would just look in the scripts folder, and get the script info right from the script header (file).
[u][b]Blabla:[/b][/u]
I started "developing" something like this script manager, but I only did some basic stuff (like mySql-database, text file generation, downlaod-php-page for the zipped text file, basic download-and-list portion of the script manager).
The devs promise some kind of scripts manager in the next major release (2.6) so I'm curious.
I have been thinking about redoing both the general wishlist and the scripts list. I think scripters should be able to assign a "general wish" as ToScript. They should be able to say if they're working on it or not.
Just, I don't have the time to do this right now. The only thing so far I have done is made a categorised list of my own scripts.
[u][b](Old) MMScriptsManager:[/b][/u]
BTW: for people that want to more easily install/manage scripts, I have already an application that combines most script-necessary stuff.
MMScriptsManager (External App for .Net Framework v2): http://www.mediamonkey.com/forum/viewtopic.php?p=36310#36310
So you have all necessary MM-folders by hand, don't have to go in the Scripts.ini file, can easily add/remove script entries and see faulty ones,... and install new scripts by drag-and-dropping either the code text, or the script file link.