We do generate a few other Activities (TabActivity and
PreferencesActivity), but we have the xml data for them. I looked but
never found a xml specification for Google's proprietary APIs. That
means we have to either:
1) Generate an activity subclass, and make changes to it by hand.
2) Generate our own version of the xml data through reflection.
3) Just generate the subclass through reflection.
The main problem with the last two is that we can only look at one API
level at a time. It's doable, but it would take a decent amount of
work (e.g., generating our own xml for each level).
I would say go with #1 for now...until someone wants to invest the
time into #2.