[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: xAP 1.3 and BSC 1.4(!?)
------=_Part_30630_15889167.1227883220495
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
I don't think I saw this e-mail. I'm happy to look at ratification of a xAP
1.3 spec.
P.
2008/11/28 Kevin Hawkins <yahoogroupskh@xxxxxxx>
> Been away on hols Lehane - so only just seen this...
>
> There have a been a few posts re this on the lists but its woeful that
> we still haven't got a published xAP v1.3 spec. I only got one
reply
> (from James) to my last direct email to everyone with the outline
> changes that I thought were in the spec :-( Having said that there
> are a lot of application out there now implementing xAP v1.3 and I
ahve
> tried to ensure with the developers thay they all meet the spec - or
at
> least my interpretation of it ;-) We do need to get this documented
> and published !
>
> Re BSC v1.4 - or at least an addendum to BSC1.3 to handle xAP v1.3
UID's
> - again we need to do this although I hope it's fairly obvious - you
> just need to cope with the longer UID's that xAP v1.3 supports.
> ID=xxxx ID=xxxxxx etc . In BSC v1.4 there has been the ongoing
talk
> about a 'choice' device and Edward and I are both using his suggested
> way of implementing this - and it is in the released HouseBot plugin.
> We have not persued an actual menu structure type treatment of this -
> which is something that you might like for your switches, this
probbaly
> should be its own schema. I know IanB was looking at this.
>
> There are some clarifications we need to make to the existing BSC v1.3
> spec as it is ambiguous in some areas. I'm happy to work with you on
> this and the xAP v1.3 spec if you wish ??
>
> Kevin
>
>
>
> about Lehane Kellett wrote:
> > I've just been working on updating the LCD switch display to use
a
> > newer board. As part of this I added support for extended UID's
but
> > found there isn't a reference on the web. I guess this needs some
> > focus before we create mildly different variants in our code.
> >
> > In the same way, ID=xxxx needs adding to BSC and some clarity
added.
> >
> > I'm willing to have a go at BSC 1.4 for the extensions but what
else
> > needs adding or changing?
> >
> > Lehane
> > http://www.mm-wave.com/honeycottage/xaplcd2.htm
for the display. I'll
> > add photos in the back box shortly.
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
------=_Part_30630_15889167.1227883220495
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html><head>
<style type="text/css">
<!--
#ygrp-mkp{
border: 1px solid #d8d8d8;
font-family: Arial;
margin: 14px 0px;
padding: 0px 14px;
}
#ygrp-mkp hr{
border: 1px solid #d8d8d8;
}
#ygrp-mkp #hd{
color: #628c2a;
font-size: 85%;
font-weight: bold;
line-height: 122%;
margin: 10px 0px;
}
#ygrp-mkp #ads{
margin-bottom: 10px;
}
#ygrp-mkp .ad{
padding: 0 0;
}
#ygrp-mkp .ad a{
color: #0000ff;
text-decoration: none;
}
-->
</style>
</head>
<body>
I don't think I saw this e-mail. I'm happy to look at
ratification of a xAP 1.3
spec.<br><br>P.<br><br><div
class="gmail_quote">2008/11/28 Kevin Hawkins <span
dir="ltr"><<a href="mailto:yahoogroupskh@xxxxxxx";>yahoogroupskh@xxxxxxx</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left:
1ex;">Been away on hols Lehane - so only just seen
this...<br>
<br>
There have a been a few posts re this on the lists but its woeful
that<br>
we still haven't got a published xAP v1.3 spec.
I only got one reply<br>
(from James) to my last direct email to everyone with the
outline<br>
changes that I thought were in the spec :-( Having
said that there<br>
are a lot of application out there now implementing xAP v1.3 and I
ahve<br>
tried to ensure with the developers thay they all meet the spec - or
at<br>
least my interpretation of it ;-) We do need to get
this documented<br>
and published !<br>
<br>
Re BSC v1.4 - or at least an addendum to BSC1.3 to handle xAP v1.3
UID's<br>
- again we need to do this although I hope it's fairly obvious -
you<br>
just need to cope with the longer UID's that xAP v1.3
supports.<br>
ID=xxxx ID=xxxxxx etc . In BSC v1.4 there
has been the ongoing talk<br>
about a 'choice' device and Edward and I are both using his
suggested<br>
way of implementing this - and it is in the released HouseBot
plugin.<br>
We have not persued an actual menu structure type treatment of this
-<br>
which is something that you might like for your switches, this
probbaly<br>
should be its own schema. I know IanB was looking at this.<br>
<br>
There are some clarifications we need to make to the existing BSC
v1.3<br>
spec as it is ambiguous in some areas. I'm happy to work
with you on<br>
this and the xAP v1.3 spec if you wish ??<br>
<font color="#888888"><br>
Kevin<br>
</font><div><div></div><div
class="Wj3C7c"><br>
<br>
<br>
about Lehane Kellett wrote:<br>
> I've just been working on updating the LCD switch display
to use a<br>
> newer board. As part of this I added support for extended
UID's but<br>
> found there isn't a reference on the web. I guess this
needs some<br>
> focus before we create mildly different variants in our
code.<br>
><br>
> In the same way, ID=xxxx needs adding to BSC and some clarity
added.<br>
><br>
> I'm willing to have a go at BSC 1.4 for the extensions but
what else<br>
> needs adding or changing?<br>
><br>
> Lehane<br>
> <a href="http://www.mm-wave.com/honeycottage/xaplcd2.htm";
target="_blank">http://www.mm-wave.com/honeycottage/xaplcd2.htm</a>
for the display. I'll<br>
> add photos in the back box shortly.<br>
><br>
><br>
><br>
> ------------------------------------<br>
><br>
> Yahoo! Groups Links<br>
><br>
><br>
><br>
><br>
><br>
<br>
<br>
------------------------------------<br>
<br>
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|