RE: slimp3.pl plugins patches and comments

> I am still not following.
> 
> The default+custom mapping files map a physical button name (which 
> corresponds to a IR code for a given remote)
> to a function name.  We have default mappings under COMMON 
> for each of 
> the buttons on our remotes to well-known function names.
> 
> Plugin authors write their plugins and create functions based 
> on these 
> well-known names.
> 
> Under what circumstances would a plugin author need to alter the map 
> away from the standard function names?

I gave such an example.  In the Shooter plugin the 'play' function is used
to fire the weapon.  This is not a descriptive name for the function, in my
opinion.  It would be better to name the function 'fire' and map play = fire
in the [PLUGINS.Shooter] mode.

Similarly in SlimTris, 'play' rotates one way and 'add' rotates the other.
Ideally there would be a 'rotate' function which would be mapped like this:
play = rotate_1
add = rotate_-1

In Rescan, the 'play' function initiates the rescan.  This should be
'rescan' with a play = rescan map.

My preference is for function names to reflect what they do, not arbitrarily
match the function names for the most common use of the button.

------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get 128 Bit SSL Encryption!
http://us.click.yahoo.com/FpY02D/vN2EAA/xGHJAA/rIp0lB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
[email protected]

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/