There's also from runtime detection of API version, a la http://groups.google.com/group/android-developers/msg/887fbc62b6367fa9, which you could use to branch your code internally. Not that that's inherently cleaner, but it might work out that way for certain circumstances.
String On Oct 28, 11:18 am, jarkman <[email protected]> wrote: > We have an app which is very involved with contact data, and will need > to be ported to the new contacts APIs to work properly under 2.0. > > It looks like the change will affect quite a lot of code, so ideally > we would fork the project, make the right changes, and then have 1.6 > and 2.0 builds in the market. We would need to maintain both branches > for a few months, till 2.0 is widely deployed, then move forwards from > the new branch. > > We can't do that as long as the Market doesn't support multiple builds > per app, obviously. What else can we do ? > > There's reflection, of > course:http://android-developers.blogspot.com/2009/04/backward-compatibility... > which would let us build some kind of cross-version-compatible wrapper > for both contacts APIs. Is that really the only way ? Is anyone > solving the problem in any tidier ways ? > > Thanks, > > Richard --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
