RE: Re: Interface design choices?...

["Paul Gordon" <paul_gordon@xxxxxxx>]

> >
>I would suggest javascript as that works on the ePOD. In fact after a
>little
>searching I found this which is really cool, I just tried it on the
ePOD
>and
>it works fine.
>http://javascript.internet.com/clocks/digital-clock.html
>

Cool! - that looks pretty good... Hmm.. never done anything with Javascript
before - anyone recommend a good beginners book?...


> >
> >
>I'm really not sure about whether there is a problem with leaving ePODs
>turned on or not. I fully intend to have some of mine on all the time
with
>pictures changing  every few minutes. I only heard of one case of an
ePOD
>dying that had been on for some time. And of course there is no way of
>proving that it was that that killed it.
>

That sounds encouraging...


> >
>
> >
>I use Snowcrash which is a browser front end to WinAmp, it allows full
>control of MP3s on the server without the need for TS or anything else.
>

Yeah, there are numerous web front-ends for Winamp. What I'm after though
is
a general-purpose interface of the stuff I need by the side of the bed,
which may or may not include Winamp control....


> >
>Time is the only thing preventing me from going down the W2KS route as
>well.
>

>
>I have no experience of Homeseer, but if it can take instructions from
a
>text file, then I would use ASP to write a file on the server based
upon
>input from a browser. This would be pretty easy to set up given some
>knowledge of JavaScript and ASP.
>

Homeseer is pretty flexible - it has native Javascript support....

Paul G.



_________________________________________________________________