aboutsummaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authorfaiface <faiface2202@gmail.com>2019-05-04 17:58:06 +0200
committerfaiface <faiface2202@gmail.com>2019-05-04 17:58:06 +0200
commit7f27d8ee626eafe24c1a540bd70ad12c34745856 (patch)
tree8f20932ced2295b7f5c83219bf05afdac1b5380d /README.md
parent587632a9da4feda83215efb563df464ec33e0993 (diff)
downloadgui-7f27d8ee626eafe24c1a540bd70ad12c34745856.zip
README: add a 'main idea of concurrent GUI' paragraph
Diffstat (limited to 'README.md')
-rw-r--r--README.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/README.md b/README.md
index 80ffdc8..c317b3a 100644
--- a/README.md
+++ b/README.md
@@ -30,7 +30,9 @@ Why the hell has no one made a concurrent GUI in Go yet? I have no idea. Go is a
**So, how does this work?**
-There's [`Env`](https://godoc.org/github.com/faiface/gui#Env0), short for _environment_:
+The main idea is that different components of the GUI (buttons, text fields, ...) run concurrently and communicate using channels. Furthermore, they receive events from an object called _environment_ and can draw by sending draw commands to it.
+
+Here's [`Env`](https://godoc.org/github.com/faiface/gui#Env0), short for environment:
```go
type Env interface {