Quoting kyleki <[EMAIL PROTECTED]>:
I really appreciate you helping me through this, KDF. I hope I'm not
being too much of a bother. I only have surface level knowledge of how
slimserver is setup and what underlying dependency requirements it has.
I was hoping to be able to and add something like the following around
line 314:
'0.hold' => 'Plugins::TrackStat::saveRating_0',
'1.hold' => 'Plugins::TrackStat::saveRating_1',
'2.hold' => 'Plugins::TrackStat::saveRating_2',
'3.hold' => 'Plugins::TrackStat::saveRating_3',
'4.hold' => 'Plugins::TrackStat::saveRating_4',
'5.hold' => 'Plugins::TrackStat::saveRating_5',
Is cross-communicating between plugins like this possible (or even a
good idea)?
hopefully erland can chime in at some point. I'm really not familiar
with trackstat. I dont have it on my system, so have never looked at
the code. If it is written to have a 'saveRating' function, then you
can use:
0.hold = modeFunction_TrackStat->saveRating_0
Of course, this varies depending on the naming of the mode. If they
are functions that are only added to the playlist mode, then
0.hold = modeFunction_playlist->saveRating_0
might do it.
Slimserver is open source, so there is nothing stopping you from
editing and customising to make it do anything you like. That's how I
started writing code for Slimserver in the first place. The only
caveat is that you have to be careful when you upgrade either plugin
later. Server changes can also affect behaviour, so you should be
familiar with the --d_plugins debugging and running slimserver from
the command line to check on any plugin loading failures. Chances are
if one plugin fails, both will be useless and could potentiall cause
server creshes when the other us used.
-kdf
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/plugins
