new feature: m number marks work as mastered for active player and shows movements
This commit is contained in:
16
README.md
16
README.md
@@ -11,16 +11,18 @@ At the moment, an alpha version is undertaken, with these features:
|
||||
- The sqlite-database holds a growing number of piano-solo pieces, together with their exact catalogue-numbers and composers.
|
||||
- Prepared in this database is a table for users (pianists), that marks which of the pieces can be played.
|
||||
|
||||
### Application
|
||||
### Application and usage
|
||||
|
||||
- Create new users
|
||||
- Set an active user
|
||||
- Show the pieces stored in the database
|
||||
- (planned) Mark pieces as masterd for the active user
|
||||
- Create new users (`n username`)
|
||||
- Show users (`su`)
|
||||
- Set an active user (`a number_of_user`)
|
||||
- Show the pieces stored in the database (`s`)
|
||||
- Mark pieces as mastered for the active user (`m number_of_work`)
|
||||
- (planned) Show pieces by composer
|
||||
- (planned) Show movements throug pieces
|
||||
- (planned) Show movements through pieces
|
||||
|
||||
## Requirements
|
||||
|
||||
- Python 3.9 or higher
|
||||
- Enough disk space to hold the database
|
||||
- Enough disk space to hold the database
|
||||
- run `python builddb.py` to build the SQLite-database-file before running `python rep_cli.py`
|
||||
Reference in New Issue
Block a user