Here's an idea for a "customiseable combo plugin" to
a) avoid combo-collisions from different plugins
b) allow plugins juste to just wait for requests triggered by a combo without checking for pressed combos themself
c) avoid the need for Devs to check if a combo is already in use by another plugin
Unfortuanally i don't have the PS3 programming skills to make such a plugin myself because i only develop apps on pc from time 2 time.
So pls take this as what it is: A basic idea open up for discussion.
---------------------------------------------------------------------------------------------------------------------------------------------------------------
A "customiseable combo plugin" might consists of 2 parts:
1. A configuration app where user can create a new combo (or edit an existing one) by selecting/entering
a) An activation switch
b) An unique ID (might be just the plugins name) to identify the plugin for which the combo is meant for
c) The buttons for a 3-button-combo (via dropdown menus or manual entering... 3 buttons should provide enough possible combinations i guess !?)
d) The command(s) (via dropdown menu and/or manual editing) that has to be directed to the appropiate plugin when the combo is pressed by the user.
e) (optional) Parameter(s) for the command
Notes:
- The app should not allow the user to create double defined combos... but this is obvious because it's the main idea behind it
- It should be possible for a Dev to provide a list of available commands for his/her plugin for use in the dropdown menu. eg by a simple "[Unique ID]_commands"-file containing one line for each command and short description of what it does.
2. The plugin itself, which just sits in background waiting for incoming combos and directs their command(s) and optional parameters to the appropiated plugin
(May be by simply creating a temporary file "[Unique ID]_requests"... just like "wm_requests" used in webMAN_Mod)
With such a system any existing and future plugins can just wait for it's "[Unique ID]_requests"-file to appear and then execute it's command(s).
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Well... That's basicallly my idea and may be it's just stupid, not realizable or simply to much effort. I don't know !?
And my hope is i explained it well enough because english isn't my native language.
Regards
Rudi
a) avoid combo-collisions from different plugins
b) allow plugins juste to just wait for requests triggered by a combo without checking for pressed combos themself
c) avoid the need for Devs to check if a combo is already in use by another plugin
Unfortuanally i don't have the PS3 programming skills to make such a plugin myself because i only develop apps on pc from time 2 time.
So pls take this as what it is: A basic idea open up for discussion.
---------------------------------------------------------------------------------------------------------------------------------------------------------------
A "customiseable combo plugin" might consists of 2 parts:
1. A configuration app where user can create a new combo (or edit an existing one) by selecting/entering
a) An activation switch
b) An unique ID (might be just the plugins name) to identify the plugin for which the combo is meant for
c) The buttons for a 3-button-combo (via dropdown menus or manual entering... 3 buttons should provide enough possible combinations i guess !?)
d) The command(s) (via dropdown menu and/or manual editing) that has to be directed to the appropiate plugin when the combo is pressed by the user.
e) (optional) Parameter(s) for the command
Notes:
- The app should not allow the user to create double defined combos... but this is obvious because it's the main idea behind it
- It should be possible for a Dev to provide a list of available commands for his/her plugin for use in the dropdown menu. eg by a simple "[Unique ID]_commands"-file containing one line for each command and short description of what it does.
2. The plugin itself, which just sits in background waiting for incoming combos and directs their command(s) and optional parameters to the appropiated plugin
(May be by simply creating a temporary file "[Unique ID]_requests"... just like "wm_requests" used in webMAN_Mod)
With such a system any existing and future plugins can just wait for it's "[Unique ID]_requests"-file to appear and then execute it's command(s).
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Well... That's basicallly my idea and may be it's just stupid, not realizable or simply to much effort. I don't know !?
And my hope is i explained it well enough because english isn't my native language.
Regards
Rudi