Andy Grundman;182359 Wrote: 
> On Feb 21, 2007, at 5:15 PM, Tarn wrote:
> 
> > So, just to confirm:  There is no way at all to control the  
> > Transporter
> > when its hooked up to the squeeze network, except for IR?
> >
> 
> That's basically right.  There's a web API used internally by the  
> website that's possible to use from a script but it's one-way only.
> 
> 

Allowing CLI control is still planned for SlimServer 7.0, right?

http://wiki.slimdevices.com/index.cgi?SlimServer7Spec

Andy, is there a document that more fully describes the SN integration
plans?

I'd very much like Perl API integration so that 
- my local Slimserver plugins could ascertain the status of players
(so BottleRocket, AMPSwitch, and IRBlaster could know when to make
changes to amp volume or power status)
- my local Slimserver plugins could intercept remote control activity
(e.g. VolumeLock could prevent volume changes when on SN, StatusFirst
could show Sleep status instead of starting a sleep timer)
- my local Slimserver plugins could intercept display changes from SN
-- for instance, allowing SaverSwitcher to alternate between local
screensavers (SuperDateTime for weather, system status, etc.) and SN
savers like Now Playing (or maybe allow Michael Herger's Music
Information Screen saver to get info from SN so that I could still use
his plugin for my When Playing screensaver).

Having access to a document that better describes the planned
SN/Slimserver integration features and schedule would be helpful.
Perhaps entering the features as Bugzilla feature enhancement tickets
and allowing customers to vote on them would help prioritize your
work?

Thanks,

Peter


-- 
peterw
------------------------------------------------------------------------
peterw's Profile: http://forums.slimdevices.com/member.php?userid=2107
View this thread: http://forums.slimdevices.com/showthread.php?t=32930

_______________________________________________
squeezenetwork mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/squeezenetwork

Reply via email to