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: xPLRioNet beta v3.5d released


  • Subject: Re: xPLRioNet beta v3.5d released
  • From: "rleong1" <rleong1@xxxxxxxxx>
  • Date: Sun, 01 Aug 2004 15:54:35 -0000

--- In ukha_xpl@xxxxxxx, "UKHA" <ukha@b...> wrote:

>
> I started messing about with the web interface to try and beautify
it a little, and ran into 1 or 2 issues, mainly caused by the use of
{blah} where {blah} is replaced by the html. Some of these would be
easier to fix than others, for example:
>
> {cmd_vol_up}
>
> gets replaced with
>
> <a
href="rio.htm?device=unit2&cmd=volup&style=artists&query=A&id=-1&source=artists&this=2004080105003620">Vol+
(42)</a>
>
> IMHO, it would be better if it returned:
>
>
"rio.htm?device=unit2&cmd=volup&style=artists&query=A&id=-1&source=artists&this=2004080105003620"
>
> on it's own so that I could add (for example)
>
> <a href=  and  ><img src=images/volup.jpg
borde=0></a> myself giving:
>
> <a
href="rio.htm?device=unit2&cmd=volup&style=artists&query=A&id=-1&source=artists&this=2004080105003620"><img
src=images/volup.jpg borde=0></a>

i already asked for & received this feature in 3.5d :)

http://groups.yahoo.com/group/ukha_xpl/message/2829

>
> It'd also be nice (again IMHO) to have {volume_level} rather than
passing it back as part of the {cmd_vol_up}.
>
> Similar things apply to the other links on the main page. The only
one I'm not sure how you would do is the {selections} part, again I'd
like to replace some parts of the returned results with graphic images.
>

{volume_level} is separate.  look at the rio.xml file in the web directory




xPL Main Index | xPL Thread Index | xPL 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.