Main > Audio/Jukebox/MP3 Forum
Plugins: Document API for JukePlugSys
Space Fractal:
--- Quote from: unclet on January 08, 2008, 12:49:38 pm ---** Now ..... perhaps you wanted the plugin application to be "automatically" updated somehow when new "commands" are added to the SDK and somehow have the plugin application understand that a new command exists now without the plugin author having to update their plugin application manually everytime a new command was defined in the SDK? Is this what you were trying to do? I personally would not know how to do something like this but it might explain why you wanted the plugin application to know about all existing commands. Perhaps ..... this is just a guess obviously.
PS: Thanks headkaze for providing the Plugin Manager pics :applaud:
--- End quote ---
YES, Here is the screen shot how i would make a common sound plugin (sending COIN_INSERT@MOVE_UP@MOVE_DIGIT(1,2,3,4) as a commandset string)
Since this sound plugin dosen't need digit values, the plugin will simply just ignorie them.
You software might use other commandset, but the plugin would then just change the list in the "Select a Jukebox Command" in the screenshot to suit your software....
unclet:
--- Quote ---YES !!
--- End quote ---
I think we just made some progress :applaud:
Let me think about all of this for a bit (and get some actual real job work done now) and I will get back to this later. At least I understand what you want to do now! :)
Space Fractal:
Why did I not create a screenshots a long ago?
Thanks headkaze for jumping in. It help alots.
No we have a future progress and it seen the SDK soon can been done.
unclet:
Quickly thinking about this, I think the idea of having the plugin know all the commands up front will work for some plugin functions (like your example of associating a sound to a command) but I think for other commands, which are added to the SDK in the future, the plugin application will be required to be manually updated by the plugin author.
For example, some commands are going to be stand-alone commands which require the plugin author to provide a new setting option within their plugin application.
Let me think about all of this now .....
Space Fractal:
or course, this depend which type of plug-in he write....
Sometimes they might of course want to use given commands, that might have different names. Here the user can tell the plug-in config which command name that is excepted to been used.
If a plugin would use some screensaver mode, a user would either select SCREEN_SAVER (MultiJuke) or ATTRACT_MODE (UncleT Jukebox) in its plugin config. These commands does nearly the same.
I also think we should only use ON/OFF/DISABLE and any numbers as a argument to the command?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version