2f88fad9ea
go.*: update gio to v0.10.0
...
Signed-off-by: Chris Waldon <christopher.waldon.dev@gmail.com >
2026-05-18 15:19:28 -04:00
74551d3253
go.*: update to gio v0.9.0
...
Signed-off-by: Chris Waldon <christopher.waldon.dev@gmail.com >
2025-09-16 08:41:55 -04:00
ab2d621e47
go.*: bump Go and dependencies
...
Signed-off-by: ddkwork
2025-05-05 19:53:28 +02:00
d1bccae359
go.mod,.builds: upgrade minimum Go version to 1.23
...
Remove a redundant package installation line while here.
Signed-off-by: Elias Naur <mail@eliasnaur.com >
2025-03-21 11:00:04 +01:00
03a1ada8ac
go.*: update to gio v0.8.0
...
Signed-off-by: Chris Waldon <christopher.waldon.dev@gmail.com >
2025-01-14 10:57:56 -05:00
eb9fbc797e
go.*: update to Gio v0.7.1
...
Signed-off-by: Chris Waldon <christopher.waldon.dev@gmail.com >
2024-07-16 20:39:39 -04:00
d0d7f84d0e
go.*: update to Gio v0.7.0
...
Signed-off-by: Chris Waldon <christopher.waldon.dev@gmail.com >
2024-06-17 13:29:39 -04:00
c9121dcb8c
go.*,gogio: update to Gio 0.6.0
...
Signed-off-by: Elias Naur <mail@eliasnaur.com >
2024-04-14 08:34:39 +02:00
78da7b9864
go.mod: bump Go to 1.19
...
Signed-off-by: Elias Naur <mail@eliasnaur.com >
2023-04-14 14:08:09 -06:00
ecebd405a7
gogio: implement custom rendering test
...
This commit adds an end to end test for the custom rendering
use-case. I confirmed that the new test failed when custom
rendering frame lifecycle was broken, and succeeds now.
However, the old X11 tests started failing when the new
one started passing. I'm not sure how they interfere with
one another, but I'm out of time to investigate.
Signed-off-by: Chris Waldon <christopher.waldon.dev@gmail.com >
2022-06-28 21:57:19 +02:00
6826ef0b64
all: initial import from gio main repository
...
Signed-off-by: Elias Naur <mail@eliasnaur.com >
2022-04-24 13:46:53 +02:00
Chris Waldon