update the README.md

README.md

@@ -1,17 +1,33 @@
 # Hello Contest
+
+[![CI-Build](https://github.com/ftl/hellocontest/actions/workflows/ci.yml/badge.svg)](https://github.com/ftl/hellocontest/actions/workflows/ci.yml)
+
 A simple HF contest log for Linux, written in Go using [gotk3](https://github.com/gotk3) for the UI. As I'm using this only for CW contests on HF, the program might not be very useful for other modes or higher frequencies. Anyway, here are some highlights:
 
-* Calculate points, multis, and score per band and overall. The calculation rules can be changed in the settings dialog (File > Settings, Ctrl+.).
+* Calculate points, multis, and score per band and overall. The calculation is done using the [conval](https://github.com/ftl/conval) library. You can select the contest definition in the settings dialog (File > Settings).
+* Show the current rate of QSOs, points, and multis in a comprehensive graphic.
 * Export the logbook as [Cabrillo](https://wwrof.org/cabrillo/), [ADIF](http://adif.org), CSV, or call history.
 * Get additional information about the entered callsign from the [DXCC](http://www.country-files.com) and [super check partial](http://supercheckpartial.com) databases, or a call history file.
 * Use a call history file from a former contest to predict the exchange for the currently entered callsign.
+* Use a dx cluster or a local CW skimmer and show the spotted stations in a spot list (or even the spectrum view of your radio, if it supports the [TCI protocol](https://github.com/maksimus1210/TCI)).
+* Define different CW macros for the running and the search&pounce working mode.
 * Use the [TCI protocol](https://github.com/maksimus1210/TCI), the [Hamlib daemon](https://github.com/Hamlib/Hamlib), or the [cwdaemon](https://github.com/acerion/cwdaemon) to transmit CW macros.
-* Define different macros for running and search&pounce working mode.
 * Connect to your transceiver through the [TCI protocol](https://github.com/maksimus1210/TCI) or the [Hamlib network protocol](https://github.com/Hamlib/Hamlib) to keep the band and mode information in sync.
 
-I use this little project mainly as training ground to learn how to develop a desktop application in Go and to improve my Go-Fu.
-
 ## Build
+Build hellocontest using the included Makefile by simply running
+
+```
+make
+```
+
+The following libraries are required:
+
+* libgtk-3-0
+* libgtk-3-dev
+* libpango-1.0-0
+* libpango1.0-dev
+* libpangocairo-1.0-0
 
 ### gtk+3.0
 To build the software on your system with the gotk3 library, you may need to set a tag with the version number of gtk+3.0 that is installed on your system:
@@ -28,7 +44,7 @@ go build -tags gtk_3_22
 Hellocontest uses Google's [protocol buffers](https://developers.google.com/protocol-buffers/) to define the data format of the log data stored on disk. The proto definition of the data format resides in the `core/pb` package. This package also contains the generated Go code to access the binary logbook data according to the proto definition. If you make any changes to the proto definition, you need to regenerate this code. The code generation is done using Google's `protoc` compiler for protocol buffers (see Google's [documentation on protocol buffers](https://developers.google.com/protocol-buffers/) for more information about how to install this tool). To run the code generation simply execute 
 
 ```
-go generate ./core/pb
+make generate
 ```
 
 This will generate the Go code to access the binary data in the logbook files into the `core/pb` package.