Android Website Gripes...

by Bill Zimmerly » Fri, 06 Mar 2009 21:35:21 GMT


Sponsored Links
 I love Android and think that Google and their partners in the OHA did
a real bang-up job in creating the platform. (Kudos of course to GNU,
Linus T, Richard S, et al. as well!)

But what really gripes me is how lousy the official Android web sites
look ... ON ANDROID!!

The frame-based site is really difficult to navigate and the online
documentation is horrid on my T-Mobile G1.

Can't Google please address this problem and make the documentation at
least readable on the platform that it is meant to document?

--~--~---------~--~----~------------~-------~--~----~



Android Website Gripes...

by Mark Murphy » Fri, 06 Mar 2009 21:48:14 GMT


 


You are welcome to file an issue at  http://b.android.com .

You are also welcome to rework that documentation into a format that is
friendlier for whatever environment you wish to view it on.

-- 
Mark Murphy (a Commons Guy)
 http://commonsware.com 
Android Training in Sweden --  http://www.sotrium.com/training.php 

--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Android Website Gripes...

by Bill Zimmerly » Fri, 06 Mar 2009 22:17:32 GMT


 


Thanks for the link, Mark, I'll check it out.

By the way, here is a great example of what I meant. Just point your
Android browser to this page and then spend a minute or two running
your finger back and forth across the page in order to try and read
it...

 http://developer.android.com/guide/basics/what-is-android.html 

On mine, for example, the actual text on the right side was somehow
"crunched" into an unreadable form that was about 3 characters wide.

I don't think what I'm complaining about is that unreasonable.

Furthermore, there are times (like when I was waiting for a little
more than an hour in my local Dentist's waiting room) when I would
like to study the Android documentation on the G1. It's pretty
pathetic that this can't be done because the Safari/Webkit browser
can't properly render the site like it can so many others.

--~--~---------~--~----~------------~-------~--~----~



Android Website Gripes...

by Mark Murphy » Fri, 06 Mar 2009 22:41:15 GMT


 


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!

--~--~---------~--~----~------------~-------~--~----~



Android Website Gripes...

by Bill Zimmerly » Fri, 06 Mar 2009 22:44:29 GMT


 Aha! The solution!!!

Menu / More / Settings / Enable Javascript

...uncheck it so that Javascript can't run.

This makes the Android documentation much more comfortably readable on
the G1.

--~--~---------~--~----~------------~-------~--~----~



Android Website Gripes...

by Mark Murphy » Fri, 06 Mar 2009 22:49:50 GMT


 


Cool!

-- 
Mark Murphy (a Commons Guy)
 http://commonsware.com 
_The Busy Coder's Guide to Android Development_ Version 2.0 Published!

--~--~---------~--~----~------------~-------~--~----~



Android Website Gripes...

by Bill Zimmerly » Fri, 06 Mar 2009 23:05:58 GMT


 


The crunched up text was the tip I needed. Since it dynamically
changed the look of the site, I figured that it must be a bug or
something in the JavaScript code.

--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. How to check the Foreground Process from a Service

Does anyone know how to, or if it's even possible to check the
(foreground process/top of the activity stack) from a service?

-- 

2. So can we use Directions API or not in Android?

I would love to be able to use the Directions API in my Android app,
but I'm confused by the information in the Directions API
documentation: http://code.google.com/apis/maps/documentation/directions/
so the short form of my question is: can Android apps use the Google
Directions API?

It clearly states the intended audience includes mobile developers.
But it also states that you're limited to 2500 requests per day. Does
this mean my app, if deployed to thousands of devices, is in total
restricted to 2500 requests per day? How could the Google server tell
anyway? Based on IP address? In which case I may be okay. The docs
also say no API key is required so again it would seem the Google
servers have nothing to use to accumulate a counter of requests per
day. Still, I don't want to be in violation of any Google Terms of
Service.

So is it okay or not? Thanks in advance.

- dave

-- 

3. Odd size Dell Aero screen: 360x640 px

4. Native crash (SIGSEGV) in open gl texture load

5. Using HttpClient

6. avira premium security 2010

7. Maybe you can use this