All Projects → patloew → Navigationviewfragmentadapters

patloew / Navigationviewfragmentadapters

Licence: other
A small library containing two adapters which allow for easy fragment management with a NavigationView.

Programming Languages

java
68154 projects - #9 most used programming language

Projects that are alternatives of or similar to Navigationviewfragmentadapters

React Native Actions Sheet
A Cross Platform(Android & iOS) ActionSheet with a flexible api, native performance and zero dependency code for react native. Create anything you want inside ActionSheet.
Stars: ✭ 412 (+564.52%)
Mutual labels:  drawer
Spinmenu
轮盘样式的 Fragment 选择菜单,可转动轮盘切换 Fragment
Stars: ✭ 903 (+1356.45%)
Mutual labels:  fragments
React Apollo Decorators
Better decorators for Apollo and React
Stars: ✭ 39 (-37.1%)
Mutual labels:  fragments
Materialdrawerkt
A Kotlin DSL wrapper around the mikepenz/MaterialDrawer library.
Stars: ✭ 508 (+719.35%)
Mutual labels:  drawer
Kydrawercontroller
Side Drawer Navigation Controller similar to Android
Stars: ✭ 632 (+919.35%)
Mutual labels:  drawer
Flowingmenu
Interactive view transition to display menus with flowing and bouncing effects in Swift
Stars: ✭ 946 (+1425.81%)
Mutual labels:  drawer
Drawer Behavior
Drawer behavior is a library that provide an extra behavior on drawer, such as, move view or scaling view's height while drawer on slide.
Stars: ✭ 394 (+535.48%)
Mutual labels:  drawer
Smsretrieverapimaster
Automatic SMS Verification with the SMS Retriever API
Stars: ✭ 48 (-22.58%)
Mutual labels:  fragments
Youtubeux
With MVVM Architecture pattern using Android Architecture Components This is a sample app demonstrating Youtube player animation using constraint layout
Stars: ✭ 823 (+1227.42%)
Mutual labels:  fragments
Duo Navigation Drawer
A flexible, easy to use, unique drawer library for your Android project.
Stars: ✭ 986 (+1490.32%)
Mutual labels:  drawer
Kotlinextensions.com
A handy collection of most commonly used Kotlin extensions to boost your productivity.
Stars: ✭ 522 (+741.94%)
Mutual labels:  fragments
Fern.vim
🌿 General purpose asynchronous tree viewer written in Pure Vim script
Stars: ✭ 552 (+790.32%)
Mutual labels:  drawer
Openlauncher
Customizable and Open Source Launcher for Android
Stars: ✭ 945 (+1424.19%)
Mutual labels:  drawer
Shatter
代替fragment的轻量级解耦类,拥有和activity完全一致的生命周期
Stars: ✭ 451 (+627.42%)
Mutual labels:  fragments
Simple Stack
[ACTIVE] Simple Stack, a backstack library / navigation framework for simpler navigation and state management (for fragments, views, or whatevers).
Stars: ✭ 1,012 (+1532.26%)
Mutual labels:  fragments
Puzzle Js
⚡ Micro frontend framework for scalable and blazing fast websites.
Stars: ✭ 398 (+541.94%)
Mutual labels:  fragments
React Apollo Defragment
💿 Automatic query defragmentation based on React trees.
Stars: ✭ 14 (-77.42%)
Mutual labels:  fragments
Material About Library
Makes it easy to create beautiful about screens for your apps
Stars: ✭ 1,099 (+1672.58%)
Mutual labels:  fragments
Treedrawer
treedrawer is a Go module for drawing trees on the terminal.
Stars: ✭ 43 (-30.65%)
Mutual labels:  drawer
Blog Fragments 2017
Blog post regarding android fragments in 2017. Sample includes fragment-less architecture
Stars: ✭ 34 (-45.16%)
Mutual labels:  fragments

NavigationViewFragmentAdapters

Build Status Download API

A small library containing two adapters which allow for easy fragment management with a NavigationView or BottomNavigationView.

The library handles replacing the fragments and saving/restoring the fragment state, including showing the right fragment when opening an app again after it was killed.

Usage

First, decide which adapter suits your use case better.

The NavigationViewFragmentAdapter detaches fragments after another menu item is selected. This means that each Fragment for a menu item is kept in memory, but there is no overhead for recreating when it is attached again.

The NavigationViewStateFragmentAdapter saves the state and removes the fragment after another menu item is selected. This means that only the fragment for the current menu item is kept in memory, but there is overhead for recreating other fragments when they are selected again.

After you decided, create your adapter implementation:

private class MyNavigationViewAdapter extends NavigationViewFragmentAdapter {

    public MyNavigationViewAdapter(FragmentManager fragmentManager, @IdRes int containerId, @IdRes int defaultMenuItemId, Bundle savedInstanceState) {
        super(fragmentManager, containerId, defaultMenuItemId, savedInstanceState);
    }

    @NonNull
    @Override
    public Fragment getFragment(@IdRes int menuItemId) {
        switch (menuItemId) {
            case R.id.navitem_1:
                return SampleFragment.newInstance("Fragment 1");
            case R.id.navitem_2:
                return SampleFragment.newInstance("Fragment 2");
            case R.id.navitem_3:
                return SampleFragment.newInstance("Fragment 3");
            default:
                return SettingsFragment.newInstance();
        }
    }
}

Now, create an instance and attach it to your NavigationView in your Activity onCreate():

adapter = new MyNavigationViewAdapter(getSupportFragmentManager(), R.id.container, R.id.navitem_1, savedInstanceState);
adapter.attachTo(navigationView);

Also, don't forget to call adapter.onSaveInstanceState() in your Activity onSaveInstanceState().

Now you have your navigation drawer or bottom navigation view up and running, including state saving of the fragments.

Advanced Usage

OnNavigationItemSelectedListener

An additional OnNavigationItemSelectedListener can be provided via setNavigationItemSelectedListener(). This can be used to add behavior after the fragment transaction was commited. If you just want to close the drawer, the lib includes a CloseDrawerNavigationItemSelectedListener.

Back Stack

There are cases when some menu items (e.g. settings) should not simply replace the current fragment, but also be added to the back stack. To do this, override shouldAddToBackStack() in your adapter:

@Override
public boolean shouldAddToBackStack(@IdRes int menuItemId) {
    return menuItemId == R.id.navitem_settings;
}

Custom Actions

If you don't want to handle fragments when a menu item is selected (e.g. to start an Activity), you can override shouldHandleMenuItem() in your adapter:

@Override
public boolean shouldHandleMenuItem(@IdRes int menuItemId) {
    return menuItemId != R.id.navitem_sample_activity;
}

Don't forget to set an additional OnNavigationItemSelectedListener via setNavigationItemSelectedListener(), where you have to handle these menu items:

adapter.setNavigationItemSelectedListener(new CloseDrawerNavigationItemSelectedListener(drawerLayout) {
    @Override
    public boolean onNavigationItemSelected(MenuItem item) {
        if(item.getItemId() == R.id.navitem_sample_activity) {
            startActivity(new Intent(MainActivity.this, SampleActivity.class));
        }

        return super.onNavigationItemSelected(item);
    }
});

Animations

You can provide custom animations for your fragment transactions via setCustomAnimations(). Separate animations can be set for when you add the transaction to the back stack via setBackStackCustomAnimations().

Sample

A basic sample app with example Activities for both adapters is available in the sample project.

Setup

The library is available on jCenter. Add the following to your build.gradle:

dependencies {
    compile 'com.patloew.navigationviewfragmentadapters:adapters:0.3.0'
}

License

Copyright 2016 Patrick Löwenstein

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].