update

.github/FUNDING.yml

@@ -0,0 +1,12 @@
+# These are supported funding model platforms
+
+github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: mpandroidchart
+open_collective: philippjahoda
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+otechie: # Replace with a single Otechie username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,37 @@
+<!---
+BEFORE YOU SUBMIT please read the following:
+
+Please search open/closed issues before submitting since someone might have asked
+the same thing before!
+
+If you have a support request or question please submit them on StackOverflow:
+  https://stackoverflow.com/questions/tagged/mpandroidchart
+using the tags `android` & `mpandroidchart`
+
+Please also look at the CONTRIBUTING file before opening an issue:
+  https://github.com/PhilJay/MPAndroidChart/blob/master/CONTRIBUTING.md
+
+Issues on GitHub are only related to problems with MPAndroidChart itself and we
+cannot answer support questions here. We will close your issue without a response.
+-->
+
+**Summary**
+<!-- A clear and concise description of what the bug is. -->
+
+**Expected Behavior**
+<!-- A clear and concise description of what you expected to happen. -->
+
+**Possible Solution**
+<!-- Not required, but suggest a fix/ reason for the bug, -->
+<!-- or ideas how to implement the addition or change -->
+
+**Device (please complete the following information):**
+ - Device: [e.g. Google Pixel]
+ - Android Version [e.g. 7.0]
+ - Library Version (e.g. 3.1.0-alpha)
+
+**Additional Context**
+<!-- Add any other context about the problem here.
+If you have source code demonstrating this bug, create a Gist:
+  https://help.github.com/articles/creating-gists/
+and link to it here. -->

.github/ISSUE_TEMPLATE/Bug_report.md

@@ -0,0 +1,44 @@
+---
+name: Bugs
+about: Create a bug report to help us improve
+
+---
+
+<!---
+BEFORE YOU SUBMIT please read the following:
+
+Please search open/closed issues before submitting since someone might have asked the same thing before!
+
+If you have a support request or question please submit them on StackOverflow:
+  https://stackoverflow.com/questions/tagged/mpandroidchart
+using the tags `android` & `mpandroidchart`
+
+Please also look at the CONTRIBUTING file before opening an issue:
+  https://github.com/PhilJay/MPAndroidChart/blob/master/CONTRIBUTING.md
+
+Issues on GitHub are only related to problems with MPAndroidChart itself and we cannot answer
+support questions here. We will close your issue without a response.
+-->
+
+**Summary**
+<!-- A clear and concise description of what the bug is. -->
+
+**Expected Behavior**
+<!-- A clear and concise description of what you expected to happen. -->
+
+**Possible Solution**
+<!-- Not required, but suggest a fix/ reason for the bug, -->
+<!-- or ideas how to implement the addition or change -->
+
+**Device (please complete the following information):**
+ - Device: [e.g. Google Pixel]
+ - Android Version [e.g. 7.0]
+ - Library Version (e.g. 3.1.0-alpha)
+
+**Additional Context**
+<!-- Add any other context about the problem here.
+If you have source code demonstrating this bug, create a Gist:
+  https://help.github.com/articles/creating-gists/
+and link to it here. -->
+
+ADD A REWARD using [Speed](speedoss.com) to SOLVE this issue QUICKLY and SUPPORT this project.

.github/ISSUE_TEMPLATE/Feature_request.md

@@ -0,0 +1,34 @@
+---
+name: Feature Request
+about: Suggest an idea for this project
+
+---
+
+<!---
+BEFORE YOU SUBMIT please read the following:
+
+Please search open/closed issues before submitting since someone might have asked the same thing before!
+
+If you have a support request or question please submit them on StackOverflow:
+  https://stackoverflow.com/questions/tagged/mpandroidchart
+using the tags `android` & `mpandroidchart`
+
+Please also look at the CONTRIBUTING file before opening an issue:
+  https://github.com/PhilJay/MPAndroidChart/blob/master/CONTRIBUTING.md
+
+Issues on GitHub are only related to problems with MPAndroidChart itself and we cannot answer
+support questions here. We will close your issue without a response.
+-->
+
+**Is your feature request related to a problem? Please describe.**
+<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
+
+**Describe the solution you'd like**
+<!-- A clear and concise description of what you want to happen. -->
+
+**Describe alternatives you've considered**
+<!-- A clear and concise description of any alternative solutions or features you've considered. -->
+
+**Additional context**
+<!-- Add any other context or screenshots about the feature request here. -->
+ADD A REWARD using [Speed](speedoss.com) to SOLVE this issue QUICKLY and SUPPORT this project.

.github/ISSUE_TEMPLATE/Support_help.md

@@ -0,0 +1,27 @@
+---
+name: Support
+about: I need help!
+
+---
+
+# *STOP RIGHT THERE!*
+
+Issues are ***NOT*** for getting help, only for reporting bugs and feature requests.
+
+Search open and closed issues to see if your question already has an answer. However, **do not create a new issue.**
+
+Instead, do the following:
+
+1. Download the [Example App](https://play.google.com/store/apps/details?id=com.xxmassdeveloper.mpchartexample) and check out the [source code](https://github.com/PhilJay/MPAndroidChart/tree/master/MPChartExample/src/com/xxmassdeveloper/mpchartexample). 90% of the time there is an example that does exactly what you are trying to do.
+
+1. Look at the [Wiki](https://github.com/PhilJay/MPAndroidChart/wiki) for the official documentation for MPAndroidChart. You can also browse the [javadoc](https://jitpack.io/com/github/philjay/mpandroidchart/v3.1.0-alpha/javadoc/) for a more detailed tutorial of the API.
+
+1. Go to [StackOverflow](https://stackoverflow.com/questions/tagged/mpandroidchart) and ask your questions there. The community will be much more helpful and willing to offer guidance.
+
+
+### You have been warned!
+
+From now on, any issues asking for help will get closed with a link to this file.
+
+### Additional Context
+ADD A REWARD using [Speed](speedoss.com) to SOLVE this issue QUICKLY and SUPPORT this project.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,15 @@
+## PR Checklist:
+- [ ] I have tested this extensively and it does not break any existing behavior.
+- [ ] I have added/updated examples and tests for any new behavior.
+- [ ] If this is a significant change, an issue has already been created where the problem / solution was discussed: [N/A, or add link to issue here]
+       <!-- If you'd like to suggest a significant change, please
+            create an issue to discuss those changes and gather
+            feedback BEFORE submitting your PR. -->
+
+
+## PR Description
+<!-- Describe Your PR Here! -->
+
+<!-- What does this add/ remove/ fix/ change? -->
+
+<!-- WHY should this PR be merged into the main library? -->

.gitignore

@@ -11,6 +11,12 @@
 # generated files
 bin/
 gen/
+generated/
+docs/
+finalOutput/
+projectFilesBackup/
+
+build.xml
 
 # Local configuration file (sdk path, etc)
 local.properties
@@ -37,3 +43,5 @@ build/
 
 # maven
 target/
+
+.DS_Store

CONTRIBUTING.md

@@ -0,0 +1,66 @@
+> ### Notice
+> *Before you continue, this is the* **ANDROID** *library. If you have an* **iOS** *device, please go here instead*:
+> 
+> – https://github.com/danielgindi/Charts
+> 
+> They might tell you to come back here, if they do, listen to them and ignore this notice.
+
+# How to contribute
+
+Bug-fixes and features often come from users of the MPAndroidChart library and improve it greatly. We want to keep it as easy as possible to contribute changes that improve the experience for users all around the world. There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
+
+## Creating Issues
+
+There are two main issue templates, one for bugs and another for feature requests. Please use them! You're issue will be much easier to understand, and bugs easier to fix, if you follow the templates. If your issue doesn't fit into those, just use the generic template.
+
+Search existing [issues] to see if your bug has already been reported or if a feature request already exists. Don't forget to remove `is:open` so you see all the issues! If you find that one already exists, use reactions to show how much you care!
+
+## Making Pull Requests
+
+Careful! If you fail to follow these guidlines, you're pull request may be closed, *even if it's really awesome*. 
+
+  0. **Search** open [pull requests] AND existing [issues] to make sure what you want to do isn't already being worked on or already has an open pull request.
+  1. **Fork** the repository
+  1. **Create** a new branch based on `master`, and name it according to your changes
+  1. **Add** your commits, they MUST follow the [Commit Style](#commit-style) below
+  1. **Test** your changes by actually running the example app, or create a new example
+  1. **Create** a pull request, following the auto-generated template
+  1. ???
+  1. Profit :money_with_wings:
+
+You are encouraged to use [GitHub Desktop] to inspect your code changes before committing them. It can reveal small changes that might have gone unnoticed, and would be requested for removal before merging.
+
+Check out [#3975](https://github.com/PhilJay/MPAndroidChart/pull/3975) for an example of a good-made-better pull request.
+
+## Commit Style
+
+  * **Make commits of logical units**  
+  Don't load your commits with tons of changes, this makes it hard to follow what is happening. However, if you have done a lot of work, and there are commits and merges all over the place, squash them down into fewer commits.
+
+  * **Conform to the code style**  
+  It's easy, just look around!
+
+  * **Write good commit messages**  
+  You may prefer [Tim Pope's style], you might like the [commitizen-friendly] way. Regardless of the color you pick, you MUST stay within the lines!  
+  ```
+The commit title CANNOT exceed 50 characters
+
+The body of the message comes after an empty new line, and describes the
+changes more thoroughly. If the change is obvious and self-explanatory
+from the title, you can omit the body. You should describe all changes
+if many were made, or maybe some trickery that only code wizards can
+understand.
+
+Be polite and wrap your lines to 72 characters, but if you prefer going
+to 100 characters then I guess we can't stop you.
+```
+
+## Final Notes
+
+Thanks for reading the contributing file! Have some cake! :cake:
+
+[issues]: https://github.com/PhilJay/MPAndroidChart/issues
+[pull requests]: https://github.com/PhilJay/MPAndroidChart/pulls
+[GitHub Desktop]: https://desktop.github.com/
+[Tim Pope's style]: https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
+[commitizen-friendly]: https://github.com/commitizen/cz-cli

LICENSE

@@ -0,0 +1,13 @@
+   Copyright 2020 Philipp Jahoda
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this software 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.

MPChartExample/.gitignore

@@ -1 +1,2 @@
 /build
+/release