I've created a swipe view with tabs as described in the android documentation several times before. In fact, stepping through the Eclipse project wizard pretty much sets you up with the basic ui using a ViewPager.
My question is this:
The application I'm building will only be supporting as far back as Android 4.0 (API level 14). So, I was considering ditching the support package altogether. However, I couldn't seem to find an example of a Swipe View with Tabs not using the ViewPager (which is only available in the support package).
Is there an api level 14&> equivalent to the ViewPager and could someone give me a working example of how to implement a Swipe View with Tabs interface without using the support library.
Otherwise, could someone give a good argument as to why I shouldn't even bother, use the support package and just be happy.
Edit: What I'm looking for is an authoritative answer regarding support library specific functionality such as the ViewPager. Are these features going to eventually be merged into the core API? Or will we continue to have to include the support package for these types of functionality? Please be specific with API versions and timelines.
Edit-1/15: I'm updating this question to stop the 'Me Too' answers I'm getting. At the time of the original posting of this question, the Android Developer documentation was much more vague on the purpose of the support libraries as they relate to functionality not included in the core SDK. They have since updated their docs to clarify things:
The Android Support Library package is a set of code libraries that provide backward-compatible versions of Android framework APIs as well as features that are only available through the library APIs.
This certainly clears things up a bit and notifies developers to not expect things like the ViewPager to ever be rolled into the core SDK functionality. I've accepted the answer which was the most relevant to the issue I was having. That is how to add support package functionality to an existing project w/o having to significantly change the codebase.