Fragment with multiple backstack

As far as I understand, every Fragment has its own backstack, and this is shared with all the fragments that belongs to the FragmentActivity. Suppose you have to manage multiple tabs, and every tab could navigate through multiple fragment. Suppose you want to "record" the navigation history for every tab so switching between fragments will allow you to return to the fragment you were viewing. Is it possible to achieve? Do I need to link every tab to an fragment activity? In this case how can be the switching between FragmentActivity managed?

Solution 1:

There is no "standard" way of going about this, because this design style is discouraged. However, I found a way to make it work: You will design your navigation manually.

Your application should have one Activity, a FragmentActivity. It has a FragmentTabHost that will hold each of your TabFragments.

TabFragment is the abstract class I created to represent your tab in the TabSpec. It will manage the navigation and swapping of fragments WITHIN the tab.

Then, the individual Fragments you create can be swapped within the TabFragment object. Here is the code:

The Activity

    public class MainActivity extends FragmentActivity {

            private FragmentTabHost tabHost;

//(TabFragment)s will set this property when created so the Activity can communicate with it
            public TabFragment activeFragment;

            @Override
            public void onCreate(Bundle savedInstanceState){
                super.onCreate(savedInstanceState);
                setContentView(R.layout.main);

        //create tabHost based on .xml layout
                tabHost = (FragmentTabHost)findViewById(R.id.tabhost);
                tabHost.setup(this, getSupportFragmentManager(), R.id.tabcontent);

        //add each of your tabs to the tabHost. These are all (TabFragment)s
                tabHost.addTab(tabHost.newTabSpec("New Tab").setIndicator("New Tab"),
                      ExampleTabFragment.class, null);
            }

    /*override the onBackPressed method, so that your application does not close every 
time the user navigates back. Instead, calls the activeFragment to determine behavior*/
            @Override
            public void onBackPressed() {
                activeFragment.onBackPressed();
            }

    //method for TabFragment to call when the user navigates out of the app
            public void close(){
                super.onBackPressed();
            }
        }

TabFragment

    public abstract class TabFragment extends Fragment {

        @Override
        public void onResume(){

//sets the property in the Activity so we can reference this from it.
            ((MainActivity) getActivity()).activeFragment=this;
            super.onResume();
        }

//this will be the method called when the back button is pressed. It will navigate.
        public abstract void onBackPressed();

    }

Instance of TabFragment Inside an instance of a TabFragment should be a FrameLayout to which child Fragments can be attached. The first time the tab is clicked, it will launch the Fragment specified in onCreate(). After switching back to it from another tab, it will resume whatever Fragment was last displayed. The onBackPressed() method should be used to navigate back through the fragments if hierarchical navigation is desired. I used a byte property (tabContentIndex) to determine how to navigate. The Fragments can swap themselves for other Fragments if you add a constructor that takes and instance of this TabFragment. They will do this by accessing the start(Example)Fragment() methods. Remember that the 'back' button must eventually exit the app.

public class NewTrailTabContent extends TabFragment {

    //to determine what child Fragment is active
    byte tabContentIndex;

    @Override
    public View onCreateView(LayoutInflater inflater, ViewGroup container,
            Bundle savedInstanceState) {

//a simple FrameLayout in this case. Child Fragments will be attached.
        return inflater.inflate(R.layout.example_fragment, container,
                false);
    }

    @Override
    public void onCreate(Bundle savedInstanceState) {

//The tab starts with this Fragment
        startDiologFragment();
        super.onCreate(savedInstanceState);
    }

    public void startExampleFragment(){

/*Fragment's constructor allows us to reference the parent to navigate. In effect, this 
Fragment will be able to call these navigation methods.*/
        ExampleFragment newFragment = new ExampleFragment(this);
        FragmentManager fragmentManager = getChildFragmentManager();
        FragmentTransaction fragmentTransaction = fragmentManager
                .beginTransaction();

//this Resource is the FrameLayout
        fragmentTransaction.replace(R.id.example_contentpane,
                newFragment);
        fragmentTransaction.commit();

//this is set so the onBackPressed() method knows how to operate.
        tabContentIndex =0;
    }

    public void startTestFragment(){

        Fragment testFragment = new TestFragment(this);
        FragmentManager fragmentManager = getChildFragmentManager();
        FragmentTransaction fragmentTransaction = fragmentManager
                .beginTransaction();
        fragmentTransaction.replace(R.id.example_contentpane,
                testFragment);
        fragmentTransaction.commit();

//different contentIndex
        tabContentIndex = 1;
    }

//this method called by the Activity
    @Override 
    public void onBackPressed() {

//this will close the app because we are at the top of the hierarchy
        if(tabContentIndex==0){
            ((MainActivity)getActivity()).close();

//this will switch to the original content fragment.
        }else if(tabContentIndex==1||tabContentIndex==2){
            startExampleFragment();
        }
    }
}

Solution 2:

Thats not really a good navigation method. I would recommend you. Look at the Android Design patterns and re think your flow.

But yes, without writing your own FragmentManager you would need to have multiple FragmentActivities

Look at using TaskStacks But this would only really work on HoneyComb. Thus I would recommend rethinking your navigation OR only build a HC+ app.

I know im not giving you much code to really sove your problem. But have a good read of Android Navigation It explains temporal and ancestral navigation, which was 'officially' added as of Android 3.0+