I do fully agree with the process, but apparently, with these requirements (supporting x to honeycomb), we are cornered with using build targets *above* the minSdk level which is really begging for troubles.
Google dropped the ball at the last hurdle. If the XML code for tablets (showAsAction, for example) would have compiled with lower SDKs, we could have kept "low" build targets and be sure that the application will run and compile from the low end of the supported range. This is still a liability at runtime, but we can exclude it from loading with resource qualifiers. This way, and with the compatibility package, developpers would have developed 3.0 compatible application much easier and much safer as well. This is really disapointing. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
