having the same problem here, so 2.0 not backward compatible with 1.5?
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
I have the same question.
1.5 compiler is having problem with the new layout directories that I
need for 1.6 and 2.0
how can I support 1.5, 1.6 and 2.0 at the same time?
On Nov 3, 9:50 pm, sdphil phil.pellouch...@gmail.com wrote:
i need my app to support1.5and above.
i noticed that if I
i think what this boils down to, is that you need to build everything
with 2.0 SDK, and then just make sure you're not using any APIs from
versions you don't want. And you will want to abstract away calls you
don't have using reflection. Simply doing something like if (version
= 2.0) then
indeed, but don't use reflection, instantiate OS-dependent classes
which implement a common interface by *name*. this breaks the class
loading chain.
reflection == last resort, IMHO
At 6:01 PM -0800 11/17/09, sdphil wrote:
i think what this boils down to, is that you need to build
If I have layout-xxx folders, compilation in 1.5 would just fail.
how can I deal with that? I don't think reflection would help.
On Nov 17, 6:12 pm, Jason Proctor jason.android.li...@gmail.com
wrote:
indeed, but don't use reflection, instantiate OS-dependent classes
which implement a common
5 matches
Mail list logo
