Main > Audio/Jukebox/MP3 Forum
Plugins: Document API for JukePlugSys
headkaze:
--- Quote from: Space Fractal on January 06, 2008, 11:46:16 am ---The plug-in need to known which commands that is available to use, otherwise the user can not configurere what commands that would do that in the plugin configuration. Example to play a sound when the plugin got a "CoinInsert" command.
--- End quote ---
The plugin doesn't need to know if the software has a command! It either sends the command or it doesn't.
So for example in my plugin I have the following
--- Code: ---int Juke_Command(String Name, String Value)
{
switch(Name)
{
case "JUKE_COIN_INSERT":
PlaySound("CoinInsert.wav");
break;
}
return 1;
}
--- End code ---
"Jukebox Software A" supports the JUKE_COIN_INSERT command and "Jukebox Software B" doesn't.
When a coin is inserted in "Jukebox Software A" it sends the command.
--- Code: ---plugin[i].Juke_Command("JUKE_COIN_INSERT", null);
--- End code ---
And the plugin plays the sound.
In "Jukebox Software B" there is no support for the command... So it does NOTHING. The Jukebox software never sends the command and the plugin never receives it.
There is no need for a command list. It's not necessary. Your just over complicating things.
Space Fractal:
All Juke_Command* functions is removed !!!!
I can't agree, so its better to remove them. otherwise this debate would never end.
I through it was pretty easier for jukebox software writers to support these command, but take a some time for the plug-in writer to get the power of commandlist command for expanded use.
Otherwice it would been very confuction for jukebox authors to tell all comands they used. Suddently we all over 200 commands where under 50% would been used. That seen to hard to tried to tell about that. I wich I could see it was ONLY arvaiable commands that can been used. And here is so the main problem you would use:
The plugin would been out of date very fast when we expand the list, if you dosent update thier plugin with new commands.
That is what I throuch commandlist() could fix, so it was more controlable by Jukebox Software authors.
So, Sorry, but that it !! I cant take about these commands any more, only if you have better idea how we can use these commands?
I simple dislike a default list, since it can been out of date very fast.
headkaze:
--- Quote from: Space Fractal on January 06, 2008, 03:14:20 pm ---All Juke_Command* functions is removed !!!!
--- End quote ---
You still need one Juke_Command(). Hey your entitled to disagree but I feel like you don't understand what I was saying. My thoughts were why add more functions when you don't need them? It will only confuse other coders. If it was necessary I would agree but they are not. One function should be enough.
You got to understand I don't even use Jukebox software so I am donating my time here to help because Loadman asked me to. Hey I understand that English is not your first language so I've repeated myself several times just to help get my point across. Sometimes it seems to take a few posts before you "get" what I mean.
Space Fractal:
I have created few commands in the MultiJuke since version 1.00... If the plugin could not see these new commands, the user can never use these command in thier plugin to thier ledwiz device or such.
That is the main problem with a fixed list.
I do not like a fixed command list, which dosent have a future. I do like dynmaic list like the queue commands I made, wich require such a linked list anyway.
So we need doing something so we have a dynamic list with various commands... but NO fixed list, otherwice we cant expand and control it by the jukebox software.
any ideas and used arguments? I guess some plugins might need a commandlist to get it configurated by the user.
headkaze:
--- Quote from: Space Fractal on January 06, 2008, 03:36:44 pm ---
I have created few commands in the MultiJuke since version 1.00... If the plugin could not see these new commands, the user can never use these command in thier plugin to thier ledwiz device or such.
That is the main problem with a fixed list.
I do not like a fixed command list, which dosent have a future. I do like dynmaic list like the queue commands I made, wich require such a linked list anyway.
So we need doing something so we have a dynamic list with various commands... but NO fixed list, otherwice we cant expand and control it by the jukebox software.
any ideas and used arguments? I guess some plugins might need a commandlist to get it configurated by the user.
--- End quote ---
The thing is there are fixed commands and non-fixed commands. Because they are strings they can be anything.
You could have JUKE_DO_WHATEVER_YOU_WANT as a command!
There would need to be a plugin.txt for each Jukebox outlining the commands the software supports. It's up to the plugin coder what commands that want to add support for. Some commands might work in some Jukes some might not.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version