The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: Display types


  • Subject: Re: Display types
  • From: Michael McSharry
  • Date: Sat, 14 Feb 2004 17:44:00 +0000

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
<DIV><FONT face="Arial" size="2">It is
totally reasonable to provide xml/html tags in the data messages if the
source desires specific formatting and the target would act like a broswer
and ignore&nbsp;tags it did not know how to deal with.&nbsp; It is
possible to provide a query response&nbsp;in which a provider will
provide a single response from an enumerated set of "display
class" possibilities.&nbsp; I think trying to itemize all the
possible display propertries is too subject&nbsp;to continual expansion
of the schema.&nbsp; The specifics of the formatting ultimately needs
to reside of the target while the source can provided
preferences.&nbsp; The target should not be disclosing all its display
properties since that then imposes a need for other xap applications to be
cognizant of the specific properties of&nbsp;each
possible&nbsp;display device.&nbsp; The issued that exists with
approaches such as using meta tags is that
very dumb display devivces would still need to be able to
interpret&nbsp;message content&nbsp;as tags vs
data.</FONT></DIV>
<BLOCKQUOTE>
<DIV>----- Original Message ----- </DIV>
<DIV><B>From:</B> <A title="lists@xxxxxxx"
href="mailto:lists@xxxxxxx";>Stuart
Booth</A> </DIV>
<DIV><B>To:</B> <A
title="xAP_developer@xxxxxxx" href="mailto:xAP_developer@xxxxxxx";>xAP_developer@xxxxxxx</A>
</DIV>
<DIV><B>Sent:</B> Saturday, February 14, 2004 2:25
AM</DIV>
<DIV><B>Subject:</B> [xAP_developer] Display
types</DIV>
<DIV></DIV><TT>I was wondering this morning, given
various display types can havedifferent capabilities, would it be of any
use if the display device,along with stating "Hey, I can display
things!", provided itscapabilities?For
instance:Display.Features{Height=(number of lines of
display)&nbsp;&nbsp;&nbsp; --- may be some special value to
signify unlimited potentialWidth=(maximum number of [fixed width?]
characters per line)Colour=(1 0)&nbsp;&nbsp;&nbsp; --- or
true/false etcCoords=(1  0)&nbsp;&nbsp;&nbsp; --- (whether or
not it can cope with coordinate based output)}Other items might include its
ability to Queue, Prioritise, etc.This of course presumes that another
application elsewhere on the xAPnetwork knows how it wants its data to be
displayed, as opposed to thedisplay device doing it all.S-- Stuart Booth
<stuart@xxxxxxx>xAPFramework.net - a xAP software development
framework for .net<A href="http://www.xapautomation.org/";>http://www.xapautomation.org/</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<A href="http://www.xapframework.net/";>http://www.xapframework.net/</A></TT>




xAP_Development Main Index | xAP_Development Thread Index | xAP_Development Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.