|
02/25/2009, 09:04 PM
#27
Just wanted to keep everyone posted. The timer is working, so I can actually convert your alarms into an alert that comes up. Really I was surprised how much code is required for a little alarm clock, but you need a data structure, you need to be able to read and write it, you need to be able to take user inputted times and scheduling info and convert that into something that the code can read and compare with the current time, etc... It's not a bigger deal than I thought, but still it's surprising. It's not a full time thing, I'm thinking half the interface is complete for the basic alarm functions. I need to write a snooze interface, and a config interface for the various options available.
On the latter option there, I was debating how Palm would handle what options might be available. Do I need to put in an icon that goes to the options screen, or maybe there's an options function on the drop down menu from the titlebar? I might just do an icon for the moment and then remove it later if necessary.
I watched the webOS webcast today as well and it all looked pretty basic, so there shouldn't be any problem for me to convert it to a native application within a few days of having a Pre in hand.
I'm looking forward to more chapters of the O'Reilly book so I can get details on alerts and dashboard functions. And getting the media playback for the Pre is still going to be a challenge until it's in hand, that will be something that happens on the day of release probably. Media is just so random on the web, you'd think playing an MP3 through the browser would be easy, but unfortunately it's not. Once the Pre is out though, I expect those components to be easier, assuming they are documented by Palm.
And then if anyone has Javascript questions out there, I'd be happy to help where I can, but my first piece of advice is to use the Firebug extension for Firefox. There is no better Javascript debugger available. It's saved me from so many hours of frustration I can't even count. Sure Firefox isn't webkit, but when it comes to developing, Safari has fewer debug tools than IE even.
|
|
|