There are some subtle differences between the Fragment compatability library and the native Fragment support in Android 3.0. For example, the setCustomAnimations() method on FragmentTransaction can use the new ObjectAnimator in Android 3.0 (see android.R.animator), but must use the older anim transitions pre-3.0 (see android.R.anim).
- dave On Mar 9, 7:54 pm, Mark Murphy <mmur...@commonsware.com> wrote: > On Mon, Mar 7, 2011 at 5:35 PM, Neal Sanche <thorins...@gmail.com> wrote: > > I guess I just wanted to ask if, when this compatibility library was > > developed, the design intent was to allow applications to run on > > Android 1.6 -> Android 3.0 inclusive without needing to change the > > code? > > Yes, that was the intent. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > Android Training Worldwide:http://commonsware.com/training -- 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 android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
