I typically use my mobile telephone as an alarm clock (because that works, and I can't be bothered to get a separate one, and it has a basic "different alarms for different days" function). I was very impressed with what Simon described.
(For me, mostly the calendar function, because that's only occasionally useful, but very useful. The advantage of using a phone is that you _can_ take it with you when you get up, so it doesn't matter so much if it goes off later in the day.)
But in that case, surely my correct solution is to write a program for the phone that does what Simon's does on his Chumby. (Or maybe to buy a chumby, but I don't know that the benefits for _me_ really justify it.) If so I don't know if I can actually find Simon's code useful, although having a specification for what a comprehensive, well-designed alarm clock ought to do definitely would be a killer helper.
(For me, mostly the calendar function, because that's only occasionally useful, but very useful. The advantage of using a phone is that you _can_ take it with you when you get up, so it doesn't matter so much if it goes off later in the day.)
But in that case, surely my correct solution is to write a program for the phone that does what Simon's does on his Chumby. (Or maybe to buy a chumby, but I don't know that the benefits for _me_ really justify it.) If so I don't know if I can actually find Simon's code useful, although having a specification for what a comprehensive, well-designed alarm clock ought to do definitely would be a killer helper.