| |
![zoujiaqing's Gravatar profile Gravatar of zoujiaqing](//www.gravatar.com/avatar/825e77d9ccc7d95e1dba6ac64e894d67?d=identicon&s=32) | Posted by zoujiaqing in reply to Ikey Doherty | Permalink Reply |
|
zoujiaqing ![zoujiaqing's Gravatar profile Gravatar of zoujiaqing](//www.gravatar.com/avatar/825e77d9ccc7d95e1dba6ac64e894d67?d=identicon&s=80)
Posted in reply to Ikey Doherty
| On Saturday, 25 March 2023 at 10:03:29 UTC, Ikey Doherty wrote:
> Most of the time I've been a backend engineer. However at times I do need to write an app, and usually I go with Gtk.
However, I'm a bit concerned that gtk-d seems .. well, catatonic. DWT also appears to be beyond life support.
We all know Rust has iced-rs, which due to the design of Rust has had to adopt the Elm paradigm.
D, with features that honestly don't need reiterating, could trivially manage OOP, ECS, mixins...
Is there general interest in UI within the D community? And is there enough to have our own toolkit, or would we be better placed to contribute to the likes of gtk-d?
I have a selfish interest in this, hence asking. While spinning a ui toolkit isn't hard, doing it properly can be (accessibility)
skiad is a binding to mono/SkiaShar.
skiad has a great api.
A UI framework like AvaloniaUI or like Flutter can be created based on skiad.
https://github.com/gearui/skiad
|