Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/gouri-panda/xplayer

This is a simple Media player application where the user sees his/her videos, images, and audio.
https://github.com/gouri-panda/xplayer

android coroutines-android hacktoberfest hactoberfest2019 hactoberfest2020 java kotlin kotlin-android media-player mediaservices room-persistence-library viewmodel

Last synced: about 14 hours ago
JSON representation

This is a simple Media player application where the user sees his/her videos, images, and audio.

Awesome Lists containing this project

README

        




XPlayer


XPlayer (work-in-progress ⛏⛏⛏)



A Multimedia application where the user can run Videos, Images & Audio

XPlayer is a **work-in-progress**. This is a simple Media player application where the user sees his/her videos, images and audio.
It is still in its early stages of development; It is under heavy development.

# Setting up the project
**1.** Fork [this](https://github.com/gouri-panda/XPlayer) repository.

**2.** Clone your forked copy of the project.

```
git clone --depth 1 https://github.com//Automatic-attendance-management-system.git
```

**3.** Navigate to the project directory :file_folder: .

```
cd XPlayer
```

**4.** Add a reference(remote) to the original repository.

```
git remote add upstream https://github.com/gouri-panda/XPlayer
```

**5.** Check the remotes for this repository.

```
git remote -v
```

**6.** Always take a pull from the upstream repository to your master branch to keep it at par with the main project(updated repository).

```
git pull upstream master
```

**7.** Create a new branch.

```
git checkout -b
```

**8.** Add your changes to the Project.

**9.** Track your changes :heavy_check_mark: .

```
git add .
```

**10.** Commit your changes .

```
git commit -m "Relevant message"
```

**11.** Push the committed changes in your feature branch to your remote repo.

```
git push -u origin
```

**12.** To create a pull request, click on `compare and pull requests`. Please ensure you compare your feature branch to the desired branch of the repo you are supposed to make a PR to.

**13.** Add appropriate title and description to your pull request explaining your changes and efforts done.

**14.** Click on `Create Pull Request`.

# Libraries used
* [Jetpack Legacy](https://developer.android.com/jetpack/androidx/releases/legacy)
* [Jetpack Navigation](https://developer.android.com/jetpack/androidx/releases/navigation)
* [Jetpack Lifecycle](https://developer.android.com/jetpack/androidx/releases/lifecycle)
* [Jetpack Core](https://developer.android.com/jetpack/androidx/releases/core)
* [Jetpack Appcompat](https://developer.android.com/jetpack/androidx/releases/appcompat)
* [Jetpack Constraintlayout](https://developer.android.com/jetpack/androidx/releases/constraintlayout)
* [Jetpack Localbroadcastmanager](https://developer.android.com/jetpack/androidx/releases/localbroadcastmanager)
* [Jetpack Room](https://developer.android.com/jetpack/androidx/releases/room)
* [Jetpack RecyclerView](https://developer.android.com/jetpack/androidx/releases/recyclerview)
* [Material](https://material.io/develop/android/docs/getting-started)

* [Exoplayer](https://github.com/google/ExoPlayer)
* [RxJava](https://github.com/ReactiveX/RxJava)
* [Kotlin](https://kotlinlang.org/docs/reference/using-gradle.html)
* [Kotlin Coroutines](https://github.com/Kotlin/kotlinx.coroutines)
* [Glide](https://github.com/bumptech/glide)
* [LeakCanary](https://github.com/square/leakcanary)

* [JUnit](https://github.com/junit-team/junit4/wiki/Use-with-Gradle)
* [Espresso](https://developer.android.com/training/testing/espresso/setup)

# Contribution Guidelines

* Write clear meaningful git commit messages (Do read [this](https://chris.beams.io/posts/git-commit/)).

* Make sure your PR's description contains GitHub's special keyword references that automatically close the related issue when the PR is merged. (Check [this](https://github.blog/2013-05-14-closing-issues-via-pull-requests/) for more info)

* When you make very minor changes to a PR of yours (like for example fixing a text in button, minor changes requested by reviewers) make sure you squash your commits afterward so that you don't have an absurd number of commits for a very small fix. (Learn how to squash at [here](https://davidwalsh.name/squash-commits-git))

* When you're submitting a PR for a UI-related issue, it would be really awesome if you add a screenshot of your change or a link to a deployment where it can be tested out along with your PR. It makes it very easy for the reviewers and you'll also get reviews quicker.

## Don't forget to leave a 🌟 if you like this repo