Well, a few things:
There's already been reported on one of these lists some issues with the
WebKit that Android uses and some of the CSS styling the site in
question uses. It felt, based on those comments, that the issue was
really with WebKit but might be worked around via CSS changes.
The WebKit issues may take a rather long time to implement, just because
we're talking firmware updates and such, and possibly even changes to
WebKit proper. CSS workarounds would presumably take less time.
However, there's a question of focus. On the whole, I rather expect that
there are over 1,000 things on the core Android team's queue that, IMHO,
are more important than having this site readable on the G1. Now, it
could be there is somebody for whom this issue might rise towards the
top (e.g., a documentation specialist). And, if Google's logs suggest
that lots of people are attempting to view the documentation through the
G1 browser, perhaps MHO of the priority of this issue is incorrect.
Moreover, this is an issue that somebody with the itch can readily
scratch themselves. Compared to, say, adding new Bluetooth profiles,
writing a script to convert the docs into a more-G1-friendly layout is
something more people have the tools to do. In fact, I would expect that
just about anyone capable of doing Android development could create a
G1-friendly copy of the docs if they sat down and tried. Rather than
simply dumping on the core Android team about what you feel is their
"pathetic" "horrid" work, you could have phrased your concerns in a way
that tries to recruit people to help fix the problem. If nobody
responded, that might suggest that having G1-friendly docs is not a high
priority for many people outside yourself; if others did respond, you
might get your G1-friendly docs faster than what the core Android team
can do.
--
Mark Murphy (a Commons Guy)
http://commonsware.com
_The Busy Coder's Guide to Android Development_ Version 2.0 Published!
--~--~---------~--~----~------------~-------~--~----~