Android studio (return new InboxFragment)

This is a frustrating thing about working with the ViewPager. :-/

First things first: there are two versions of all the Fragment classes: android.app fragments and android.support.v4.app. fragments. Regular fragments (android.app) can be used from API version 3.0 and beyond. The support versions (android.support.v4.app) are backwards compatible with older versions of Android (before version 3.0).

The Ribbt app is targeting 4.0 and beyond. However, the ViewPager comes from the support library and requires the older version of the Fragment classes.

So the solution is to make sure that InboxFragment and FragmentPagerAdapter both have import statement for the support versions, not the regular versions.

InboxFragment.java and FriendsFragment.java:

import android.support.v4.app.ListFragment;

FragmentPagerAdapter:

import android.support.v4.app.Fragment;
import android.support.v4.app.FragmentManager;
import android.support.v4.app.FragmentPagerAdapter;

After trailing the internets dark corners and looking deep into other peoples codes I found a repetitive solution ... but I'm not sure if this will effect the flow of our project... is this an acceptable edit or will it mess things up ?

public class MainActivity extends FragmentActivity implements ActionBar.TabListener

I'm going to carry on with the lesson now but I'm hoping I haven't messed it up .

John

Ha!

This code should have been generated for you, but it's easy to mix it up for one reason or another. Instead of getFragmentManager() it should be getSupportFragmentManager(), like this:

// Create the adapter that will return a fragment for each of the three
// primary sections of the app.
mSectionsPagerAdapter = new SectionsPagerAdapter(this, getSupportFragmentManager());

There is generally a 1 to 1 conversion between regular and support versions like this. :)

Just a quick note, the latest version of Eclipse (w/ Android SDK 22.6.2) also automatically includes fragments, and the same adjustments needed for Android Studio also work in Eclipse.

Oh the joys of coding.... what have I got myself into here, I wouldn't mind a 1 on 1 conversation with this Fragment Manager myself :0)

I knew that "android studio" would have some bugs, but not an ant farm worth of them ! Thanks for your time helping me with this issue "obi BEN kenobi" but that last fix didn't seem to do it. now I get an error :-

error: cannot find symbol method getSupportFragmentManager()

the quick-fix is asking me if I want to :- Create Getter. Create Property. Create Method "getSupportFragmentManager"

Ive tried shouting at the dog and that didn't seem to work, but I got some satisfaction :0)

Thanks again for your time Ben it is much appreciated .

I ran into similar issues with the code at this point, using Android Studio. My java jargon isn't up to snuff, but I think the issue has to do with the difference between how Eclipse builds the initial project versus the gradle build.

The Android Studio version of this project, following all of the same steps, uses the term PlaceholderFragments instead of Dummy Fragments, and some of the code that needs to be moved from the MainActivity class to SectionsPagerAdapter is not in quite the same order as the Eclipse version which makes the copy+paste portion of this project moderately complicated. I wish I could post the code for comparison, but I was so flustered trying to fix the code that by the time I had cleaned up all the errors Control+Z was out of the question. I can concur with John though that the original MainActivity class extends Activity rather than FragmentActivity. The errors were much more manageable after catching that snafu.

It wasn't too painful to fix up the errors and having watched subsequent videos in the project, the directions seem to work smoothly other than this issue.

Ben: It may already exist and I just can't find it, but you might consider adding alternate instructions for those of us making the leap to Android Studio. Not necessarily a video, but maybe a warning in the notes section. The step where everything gets nasty in Android Studio is "Modifying Tabs from the Template."

I don't know but I still get thrown the same error at new InboxFragment(). Tried everything. Here's my code:

package com.seyekuyinu.ribbit;

import java.util.Locale;

import android.app.Fragment; import android.app.FragmentManager; import android.content.Context; import android.support.v13.app.FragmentPagerAdapter;

public class SectionsPagerAdapter extends FragmentPagerAdapter {

protected Context mContext;

public SectionsPagerAdapter(Context context, FragmentManager fm) {
    super(fm);
    mContext = context;
}

@Override
public Fragment getItem(int position) {
    // getItem is called to instantiate the fragment for the given page.
    // Return a PlaceholderFragment (defined as a static inner class
    // below).
    return new InboxFragment();
}

@Override
public int getCount() {
    // Show 2 total pages.
    return 2;
}

@Override
public CharSequence getPageTitle(int position) {
    Locale l = Locale.getDefault();
    switch (position) {
    case 0:
        return mContext.getString(R.string.title_section1).toUpperCase(l);
    case 1:
        return mContext.getString(R.string.title_section2).toUpperCase(l);
    }
    return null;
}

}

Well I thought I was up and running but after inserting those imports into the relevant classes I now have a problem in the MainActivity ..... mSectionsPagerAdapter = new SectionsPagerAdapter(getFragmentManager());

where the (getFragmentManager()) seems to be the problem. what should I cast here ?

please help me Ben your my only hope :0)

all is well thanks for the guidance .

John

Phew, with Android Studio that was a tough one to workaround....Persistence Pays :-)

I picked and chose several of the ideas. The changing Activity to FragmentActivity seems to have done the job. However, I cannot say all of this is registering.

Make sure the class is under the right package! it fixed my problems