Re: Homevision xPL Success.....

[Ian Lowe]

----- Original Message -----
From: "armagh_elect" <<a
href="/group/ukha_xpl/post?postID=El-Vfrk84jza95fAKDtqkhuBuRsP0uwgSJiV7yWDry9i5L17JGaOy3_M1qoIDytvfsi4-ZwtVsBaT117Tg">fmcalind@b...</a>>
> Just a couple of questions....(sorry) I thought you could only send
> one line of text per message...In Ians example he sends 2 ??

Welcome to heirarchical message schemas.. ;)

The OSD.BASIC schema which all others are derived from specifies the
minimum
features that all OSD devices must support..

so, TEXT= is the lowest common denominator, which all OSD devices can do
(ie, TIVO's OSD can only do one line just now). If a display (like SLIMP3,
or VFD) can handle extra features, you can add those in..

This particular stuff is still *very* in development, so there isn't a
proper set of extension from OSD yet..
What will probably happen is, that a specific OSD.TIVO, OSD.SLIMP3, OSD.VFD
will be written, allowing the unique features of each display to be used...

(for instance, at the moment, the OSD.BASIC schema contains
"colour"
entries: this will be moved to the TIVO extended schema.. )

>If more than 1 is allowed do you assume every TEXT = message starts a
new
> line ???

No.. the "TEXT2=" is an optional developer added tag, different
from the
original TEXT=
Developers can add optional tags into their own apps using the .BASIC
version of a schema, at the bottom, after the "official" tags. I
*suspect*
that my OSD sender script isn't properly compliant in this version, as it
sends the "official" DELAY= tag *after* the developer
"TEXT2=" tag.. and
that's wrong (although Tony's framework is forgiving enough to allow it to
work)

There won't be any changes to the Schemas before UKHA2003 (we have a bunch
of stuff sitting in limbo), but I think I'll sort out the OSD Schema family
to reflect the needs of the new display devices we have code for as soon as
I can, get the various extensions sorted out..

The thing to remember is: xPL Schemas inherit their tags from the parent
schema..

So, OSD.BASIC defines a set of tags, therefore OSD.TIVO will automatically
include all of those, but include new tags supported by Tivo's OSD.. (like
colour, coordinates on screen etc).

At the same time, OSD.VFD will include all of the OSD.BASIC Tags, and those
extensions which are available on the FDV Hardware (like 2 lines,
brightness
levels etc)

Wherever possible, we will make sure that extended schemas use the same
tags..

so, for instance, OSD.TIVO would use the same tags to describe foreground
and background colour as OSD.STV350 (or whatever that chip's name is!)

>Also what does this mean
> [xpl-text=<generic text pickup from any schema>

This means that any schema (for volume control, lighting, whatever) can
include an XPL-TEXT= tag somewhere in the message, and this will then be
picked up by any suitable OSD device for display

Ian.