WX is focused more on building traditional UI: windows, buttons, etc. It does support using OpenGL, a drawing toolkit, in its UIs. The interface is super awkward in Elixir, as you have noted.
It currently is, but it sounded like a move to NIFs is planned.
Like everyone else, excited for this project. Has there been any updates since? Watched this talk a couple of months ago and sort of forgot about it until now. Would love to tinker with it
@Rob-bie: It’s latest available info that I have found:
https://twitter.com/BoydMulterer/status/931164507761655808
Few hours ago was made an interesting meetup.
https://twitter.com/BoydMulterer/status/965842957554167809
but maybe @boydm can give a small update..
Finally some big news! Scenic (name of new UI Framework) will be officially announcement by @boydm at ElixirConf which will happen in 4-7 September in Bellevue, WA (USA). Hope code will be ready to share and contribute soon too!
https://twitter.com/ElixirConf/status/1012789550488440833
https://twitter.com/BoydMulterer/status/1012790243852861440
Love to see the interest. Was just reading the above thread…
Think of it is that it is a retained-mode model specifically designed to take advantage of OTP.
All UI scenes are GenServers. Scenes can reference (embed) other scenes. Input is all message passing/filtering/handling. This also means that developers can build “components”, which are just scenes/GenServers that can be reused by other devs. Nice for extensibility.
Drivers (rendering) are abstracted away from the scenes so that they can be swapped to run on different hardware without re-writing the UI logic. This allows me to run my app on Mac to debug, change a target, and build firmware for a raspberry on Nerves. Everything looks and works the same across the two.
The driver model has also been really good for getting remoting working. More on that later…
A big thing I’m going for is reliability. Devices in the field are going to encounter errors, whether it be code, unexpected data, malfunctioning sensors or whatever. This was harder to get right than I expected, but now any piece of UI can crash and things recover sensibly into a good state.
Multiple people have said they can tell it looks like something someone with game experience would make. Partly that was to get my dependencies down to just OGL. But also because transforms are just a great way to manipulate things.
As far as overall status goes, I’ve stopped adding features and am now focused on the large amount of supporting things around it. (Including stripping out the code from various dead-ends and experiments). I want the API to be pretty stable before it goes out to lots of people.
