News for hackers. Stuff that matters.
Re:Minimum Viable Declarative GUI in C++ by lazypenguin on Tuesday March 22, 2022 @08:40PM (#30773469)
In my experience, declaring the UI is not the hard part. Iterating 100s of times with minor tweaks to get the final appearance right is what usually kills me. Using something like this would requires a continuous edit,compile,run cycle that would start hurting once compile times reach >5 seconds. For all its faults, I really appreciate that web development comes with a console to inspect data and way to edit the widgets in real time and get immediate feedback.
Re:Minimum Viable Declarative GUI in C++ by jdswain on Tuesday March 22, 2022 @09:50PM (#30773944)
Like the original NeXT AppKit, where the UI was built from objects in memory, then stored on disk as archived objects. The objects could be manipulated with InterfaceBuilder and live tested. These concepts seem to have been lost along the way, to the point where they are not a part of modern NeXT->Mac->iOS development.

But also they got harder to implement as UI's got more complex.

Re:Minimum Viable Declarative GUI in C++ by drEv0 on Wednesday March 23, 2022 @12:34AM (#30774987)
> stored on disk as archived objects

This at least is still the case for iOS.

> The objects could be manipulated with InterfaceBuilder and live tested.

Is this anything like the new live previews with Canvas? I've only ever done iOS development but if this is the case that is amazing.

Re:Minimum Viable Declarative GUI in C++ by jcelerier on Tuesday March 22, 2022 @09:53PM (#30773959)
Fast iteration times and iterative feedback are exactly the topic of my other project Lafajol: https://youtu.be/fMQvsqTDm3k ; adding support for the UI thing is in-progress but so far I have compilation times around the 200ms mark for the kind of UI I target
Re:Minimum Viable Declarative GUI in C++ by algo_trader on Wednesday March 23, 2022 @06:25AM (#30776940)
2 quick questions:

Q1: is it mostly iterating to get precise visuals to get specific behaviours?

Q2: is the toolchain/compiler/webpack turnaround speed a major factor?

Re:Minimum Viable Declarative GUI in C++ by CyberRabbi on Tuesday March 22, 2022 @09:06PM (#30773660)
That’s a great requirement for any C++ GUI library. It must support a runtime GUI model. Ideally it would seamlessly support a compile-time model as well but I’m not sure there is a strong argument for the increased complexity in that case.
Re:Minimum Viable Declarative GUI in C++ by thechao on Tuesday March 22, 2022 @09:19PM (#30773754)
I always thought that "array of ints" was a greatly unappreciated concept for declarative ... anything. They can be easily hot reloaded, they compile fast, and they're not terrible. OTOH, you'd just be reinventing the Lisp-wheel but in ints.