Skip to content
Bringing futuresimple's floating-action-button library into 2018
Branch: dev
Clone or download
MSF-Jarvis Dependency updates
Kotlin 1.3.30

Signed-off-by: Harsh Shandilya <msfjarvis@gmail.com>
Latest commit db09878 Apr 15, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
ci Introduce style checking into CI repertoire Jan 5, 2019
gradle/wrapper Update gradle to 5.2.1 Mar 4, 2019
library Cleanup Mar 19, 2019
sample Cleanup Mar 19, 2019
screenshots Add info about labels to readme Dec 30, 2014
.gitignore library: Implement properties based signing config May 27, 2018
.travis.yml
LICENSE.txt Fill placeholders in LICENSE.txt Feb 9, 2015
README.md README: Add JitPack badge Jan 8, 2019
build.gradle.kts Dependency updates Apr 15, 2019
changelog.md Bump version to 3.0.0 Jan 8, 2019
gradle.properties
gradlew Dependency updates Feb 14, 2019
gradlew.bat Dependency updates Feb 14, 2019
settings.gradle Cleanup and reintroduce sample project Aug 15, 2018

README.md

FloatingActionButton

Yet another library for drawing Material Design promoted actions

Features

  • Support for normal 56dp and mini 40dp buttons.

    Demo

  • Customizable background colors for normal and pressed states and icon drawable.

    Demo

  • Convenience LabeledFloatingActionButton with customizable icon and background.

  • FloatingActionsMenu which can be expanded/collapsed to reveal multiple actions.

    Demo

  • Optional labels for buttons in FloatingActionsMenu.

    Demo

Usage

Configure the JitPack repository:

repositories {
    maven {
        url "https://jitpack.io"
     }
}

Just add the dependency to your build.gradle:

dependencies {
    implementation("com.github.MSF-Jarvis:floating-action-button:2.1.2")
}

To see how the buttons are added to your xml layouts, check the sample project.

Caveats

The API is extremely limited at the moment. It solves few select use cases in the app I'm working on.

Unlike some other FloatingActionButton libraries this library doesn't implement "quick return" pattern, i.e. hiding the button on scrolling down and showing it on scrolling up. That's intentional, I think that should be responsibility of another component, not the button itself.

This library is minSdkVersion=21 and if that changes, the version number will be increased, not decreased. It means that Honeycomb, Gingerbread or - gods forbid - Froyo, won't ever be supported. I won't even consider merging pull requests fully implementing support for older versions. We need to move on as Android community and focus on delivering value for 95% of users of modern Android OS instead of jumping through burning hoops to support ancient devices with ancient OS.

Credits

I used FloatingActionButton library by Oleksandr Melnykov as a base for development.

License

Copyright (C) 2014 Jerzy Chalupski
Copyright (C) 2018-2019 Harsh 'MSF-Jarvis' Shandilya

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.
You can’t perform that action at this time.