ovenpasta

11 ms·

1.
by ovenpasta 22d ago
I think depends on the use case, CSS styling, Ada, static self contained executable, portability, simplicity. I'm curious what people think about this, I'm happy with it and use it for my own projects so I thought it would be usef
2.
by ovenpasta 23d ago
Thanks! The real work is done in the Adi2 widget engine. Take a look at: https://github.com/ovenpasta/adi2/blob/master/src/adi-widget... https://github.com/ovenpasta/adi2/b
3.
by ovenpasta 23d ago
Thanks! You can watch the talk at Ada Developers Workshop Vasteras 2026, where I explain some of your questions: https://www.youtube.com/watch?v=d-RISfK9Sy8 I should write more details in the repo's README file. Basica
4.
by ovenpasta 23d ago
I agree on the repetitions those need cleanup. Regarding filenames, it is a GNAT convention (the GCC's ada compiler) where we need to have the package name on it separated by -
5.
by ovenpasta 23d ago
The XML is just a layer, it gets compiled to normal code that creates / operates on the widget tree. On any user input callbacks are just Ada code that can again apply changes to widgets, like states, or add / remove widgets or se
6.
by ovenpasta 23d ago
Hi! Interesting! Your frameworks seems to be a kind of web browser, with dynamic content. Adi2 takes a different approach. Your entire app is static code. Every widget, every style is built at compile time. No interpreters or parsers at run
7.
by ovenpasta 23d ago
Author here, the library itself is pure Ada, the XML UI is just a convenience layer on top of it, there is a code generator that picks it and writes ada packages. happy to hear better alternatives!
8.
Show HN: A Modern GUI Library for Ada: CSS Styling, XML UI, SDL3(github.com)
59 points by ovenpasta 23d ago|26 comments