-- Original message --
If you're not a geek, please disregard this message.
For a javascript-driven Ajaxy skin, we would need an API. For a
smartphone app, we would need an API. And smartphone apps matter, as
they're far more usable than browsing the web directly on a smarphone:
http://www.useit.com/alertbox/mobile-usability.html. And I'd like an
Ajaxy skin.
One way or another, then, we need an API. Does an API exist?
I'm the sort of freaky weirdo who actually likes reading technical
documentation. And, even weirder, likes writing it. So if an API
doesn't exist, and you want one designed, I wouldn't mind giving it a
shot. (In fact, I designed a certain amount of it in my head while on
a 22km walk down the canal on Saturday.)
Should I write that up (and fill in the numerous gaps which are
inevitably left when you design something in your head)?
TRiG.
P.S. As I have a degree in chemistry, I still think of an API as an
active pharmaceutical ingredient.
Yes, that's a smartphone by the definition given in
http://www.useit.com/alertbox/mobile-usability.html.
Anything discussed here would be in addition to, not as a replacement
of, the current site. Just a different way of navigating the same
information. I doubt I'd use a smartphone app myself, as I've always
preferred fairly simple phones. But you never know. I might be
convinced to change my mind.
TRiG.
Yes smartphone it's not very smart it doen't make me a [_]D of coffee.
Oh your email addy @.name goes know where! This is the email I use for
facebook which I've just read they're to charge for the use of it.. If
they stop fiddling about with it changing the platform+settings they
wouldn't need to charge if it's true etc... They can close it for me
I'm sick of people sending 'POKES' I get an email everytime.. See you
Trig.