This repository has been created to version control my score keeper applicaiton intended to be submitted. Project is for Udacity's "Android Basics Nanaodegree by Google" nanodegree program. This project is number 2/11.
This project is a chance for you to combine and practice everything you learned in this section of the Nanodegree program. You will be making an app that allows a user to keep track of points within a game.
The goal is to create an Score Keeper app which gives a user the ability to keep track of the score of two different teams playing a game of your choice. To build this project, you can follow along with the practice set and customize the Court Counter app to track scores from a different sport.
This project is about combining various ideas and skills we’ve been practicing throughout the course. They include:
- Adding button code to your app
- Updating views
- Properly scoping variables
- Finding views by their ID
CRITERIA | MEETS SPECIFICATIONS |
---|---|
Game Chosen | The chosen game has either multiple amounts of points that can be scored, as in american football, or multiple important metrics to track, such as fouls, outs, and innings in baseball. |
Overall layout | App is divided into two columns, one for each team. |
Column contents | Each column contains a large TextView to keep track of the current score for that team. Optionally, a second TextView to track another important metric such as fouls can be added. |
Score buttons | Each column contains multiple buttons. The buttons must track either:
|
Reset button | The layout contains a ‘reset’ button. |
Best Practices | The code adheres to all of the following best practices:
|
CRITERIA | MEETS SPECIFICATIONS |
---|---|
Errors | The code runs without errors. |
Score Button Function | Each score button updates the score TextView in its column by adding the correct number of points. |
Reset Button Function | The reset button resets the scores on both of the score TextViews. |
CRITERIA | MEETS SPECIFICATIONS |
---|---|
Naming Conventions | "Any classes are named after the object they represent.All variables are named by their intended contents. All methods are named by their intended effect or in the style required by a callback interface." |
Code Style | "There are no unnecessary blank lines.One variable is declared per declaration line. The code within a method is indented with respect to the method declaration line." |