Main > Audio/Jukebox/MP3 Forum
Plugins: Document API for JukePlugSys
Space Fractal:
originally it was a commands.txt that do that purchase, I later removed. UncleT could not see the logic of it.
But should I bring it back? Commands.txt was the best idea for fixed that problem instead of commandlist().
Personly I would wrote my plugin to support ALL commands in commands.txt and let user configuration it what they do. Otherwice it might not been combatible with all software.
And on the other way, if the plugin write only need few commands, let the user tell the plugin which command it really is from the list (etc a list form)...
I might even want to call some commands with other names than others.
Space Fractal:
I try again.
I added a value to the commandsend value. Any ON and OFF commands should not been used, just set the proper value for that.
It seen a commands.txt should been used (headkaze: instead of Plugin.txt), but I also wrote about a plugin might define a default set used, if the list is not found or not needed. I also wrote to been very clean when they write the commands.txt file.
So it up to plugin write the list would been used or not, but I recommered of course use the list.
Is that one better and cleaner? Depite of that, only 2 commands is now needed istead of 5.
loadman:
--- Quote from: Space Fractal on January 06, 2008, 11:46:16 am ---If you as Jukebox Author do not need to send a full list to the plug-in, You do not need to that. Its up to you.
The plug-in need to known which commands that is available to use, otherwise the user can not configure what commands that would do that in the plug in configuration. Example to play a sound when the plug in got a "CoinInsert" command.
--- End quote ---
I know of a expression: KISS
Keep It Simple Stupid (No offence) ;)
I'm with UncleT's/ HeakKaze thoughts on this command stuff.
I agree that 'Space Fractal' does not seem to understand the points made here. A language barrier at a guess.
The documentation with the SDK will tell you what the commands do. If you want to add more update the SDK
Keep the Plug-in Simple and let's get on with starting to build some. :cheers:
Barry Barcrest:
I don't see why the list of things to send to the plugin is complicated. The plugin itself will do most of what it wants it only needs to know when to do it. So song start and end are good things to send across but why send across the maximum volume setting or page change? I can't possibly imagine a plugin will do anything based on that information. Like loadman says lets get some plugins working.
Space Fractal:
Hey, I think I do not update the first post in a while now (to avoid break any commands by now).
If I should add more commands I still want feedback. Otherwise Should I finalize the current version as version 1.0?
So I do NOT touch the current list from now off, and see what it bringing.
But I might add new commands if somebody have suggestions, but I do NOT change anything with current functions.
Later this I got MultiJuke supported most of these functions as long others.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version