4 ms·
> With React, you functionally describe how the UI looks in every possible state. That's how Qt works too (and the designer is prettier imho) : https://youtu.b
by jcelerier 9y ago
> With React, you functionally describe how the UI looks in every possible state.
That's how Qt works too (and the designer is prettier imho) : https://youtu.be/Ko3YPM_tStM?t=47 https://youtu.be/Ko3YPM_tStM?t=47
- tutuca 9y agoOk, then again... Qt is not "the nineties".
- jcelerier 9y agowell, the ide is more recent, but Qt was released in 1993 or something like this and the core concept did not change that much since then, it has just manifested itself in a simpler language than C++ with qml / qtquick.
- TuringTest 9y agoThe declarative QML makes all the difference when building a user interface programmatically. You could create interfaces in Qt in the nineties, but you couldn't create mockups of the different states and integrate them without writing the supporting code for those states by hand.
- pjmlp 9y agoDelphi, VB and C++ Builder surely are, and we could do a full application just by dragging components and setting properties, without a single line of code.
- realharo 9y agoThat doesn't look like what I was talking about. He basically has an entire new component for every possible state - and his state is just a single variable. That seems very wasteful if what you want to do is just to show a bunch of extra controls if a small part of the state changes. Later when he works with bindings, that's closer, but the expression still had to be written in as code, so no win there. Plus it's classic data-binding, where it can only affect pre-defined properties (usually of primitive types), but not the entire structure of the component.
- TuringTest 9y ago> That doesn't look like what I was talking about. He basically has an entire new component for every possible state - and the state here is just a single variable. With reactive programming being primarily functional, it should be relatively easy to refactor the output of a tool like this. You could split the states into its common components, maybe even using visual tools in the designer itself without having to touch the generated code. I don't know if this tool will be able to do that, but I've seen that approach used in mockup tools for rapid prototyping. The only part missing in those tools to allow the interface designer to build the interaction logic by themselves was a sane code generator. With a language like React, I believe the generated code will resemble something usable, which was impossible when UI designers generated imperative or object-oriented code.