RE: Display JPEGs on your Tivo from ANYWHERE

["Sullivan, Glenn" <gsullivan@xxxxxxxxxxxxxx>]

Spare Time at Work: with the US Thanksgiving Holiday tomorrow, no one is
doing crap here today... But normally, I'm in your shoes.

You mention heartbeats... Does your Slim Connector send a different
heartbeat for each sub address?  I'm not a slim user, so I haven't tried
it... Do you start a separate heartbeat-capable object for each one in
your app (I'm a xFx user...)?

Since the TiVo has no ability for you to answer an on screen prompt,
there are no "buttons", so I don't see the .Info or .Event being
used...
Those are designed to "answer" with the button pressed, yes?

As to the sub-sub addressing, that is a good idea.  Let me work on the
concept first, and then I can add that later on.

Thanks,

Glenn Sullivan, MCSE+I MCDBA
David Clark Company Inc.
-----Original Message-----
From: xAP_developer@xxxxxxx
[mailto:xAP_developer@xxxxxxx]
On Behalf Of Stuart Booth
Sent: Wednesday, November 23, 2005 2:55 PM
To: xAP_developer@xxxxxxx
Subject: Re: [xAP_developer] Display JPEGs on your Tivo from ANYWHERE

On Wed, 23 Nov 2005 10:00:05 -0500, "Sullivan, Glenn"
<gsullivan@xxxxxxx> wrote:

>Have some spare time at work, so I'm working on this xAPplication.

At work?! Nice! It's ten balls in the air where I am, so I can only
wish.

>How about targeting?
>
>For example, let's say you have two TiVo's... Would you want the
>Display.Service message to be sent out for each instance?    IE, if the
>xAPplication is BushSoft.xAPTiVoJPEGWriter.GMSServer, should the TiVo's

>be individually addressable:
>	BushSoft.xAPTiVoJPEGWriter.GMSServer:LivingRoom
>	BushSoft.xAPTiVoJPEGWriter.GMSServer:MasterBR

That's how my SlimServerConnector addresses all the Slims in the house.
And I believe my nobby little TiVoYAC tool does the same as I recall.
Certainly it's what I'd expect of similar xAPplications.

I daresay a single Display.Service is all that is required from the
Connector rather than each individual hardware subaddress (TiVo):

BushSoft.xAPTiVoJPEGWriter.GMSServer

But that will only tell you the general display properties, rather than
allowing you to find all the available devices unless you listen for
heartbeats.

>And individually respond to display.locate (and message.display)
>messages?

Well, Message.Display, definitely, with .Info and .Event messages
(because you might target a single TiVo), but Display.Locate/Service go
hand-in-hand. Heartbeats serve half the purpose if the Connector itself
responds with a single format device, but if different capabilities are
present on individual TiVo's, then individual responses would be
required.

For example, in my case, Slims of different display capabilities exist,
graphical vs textual.

>I guess it makes sense to do that, and then an app can send out a
>display message to either the whole set of TiVo's (by addressing to
>BushSoft.xAPTiVoJPEGWriter.GMSServer), or to an individual TiVo (by
>addressing to BushSoft.xAPTiVoJPEGWriter.GMSServer:LivingRoom)

Or even grouped via additional subaddress nodes e.g.:

BushSoft.xAPTiVoJPEGWriter.GMSServer:Downstairs.LivingRoom
BushSoft.xAPTiVoJPEGWriter.GMSServer:Downstairs.Kitchen

thus:

BushSoft.xAPTiVoJPEGWriter.GMSServer:Downstairs.>

S
--
Stuart Booth <stuart@xxxxxxx>
xAPFramework.NET - a xAP software development framework for .NET

http://www.xapautomation.org/ 
     http://www.xapframework.net/