4 ms·

There was a reason why we moved away from this. Everything is code, the UIs for creating such interfaces are just abstractions. The code generated by those no-c

There was a reason why we moved away from this. Everything is code, the UIs for creating such interfaces are just abstractions. The code generated by those no-code approaches to interface design was horrible and would break down quite fast in larger projects. Maintainability for such interfaces was non-existent. I think just regretting an old feature long gone without proper context is dangerous. If we are to bring back those approaches we have to keep in mind exactly why they went away in the first place.

vintagedave 3y ago
> Everything is code, the UIs for creating such interfaces are just abstractions. The code generated by those no-code approaches to interface design... I'm not sure you're replying to the same thing. I never used VB much, but Delphi was not and is not no-code. In fact it emphasised using libraries a lot ('components' in its terms are classes provided by libraries) and the UI had a text description, which was streamed and created at runtime. Delphi today could indeed create something doing this just as fast, and you wouldn't draw a trackbar and hope it's recognised in the image by the AI... you'd drop an actual trackbar.
protomolecule 3y ago
That's not how VB6 or Delphi work. Delphi's visual editor allows you to position, link together and configure visual and non-visual components in design time, automatically serializes all the components into text file and in runtime your program deserializes these components from the resource embedded in the program's binary file. It also allows you to create handlers for events like OnButtonClicked or OnDBConnectionOpened where the usual arbitrarily complex programming happens. The first result from google showing what this looks like: https://www.youtube.com/watch?v=AyWm24ekSVM https://www.youtube.com/watch?v=AyWm24ekSVM
insanitybit 3y ago
I don't use these tools (I do backend dev), so perhaps I'm mistaken, but the benefits here are, I assume, a) For UX people who have minimal programming knowledge but need to produce mockups. b) For people like me who might want a basic UX to start with for demo purposes.
- deleted 3y ago
  [deleted]

vintagedave 3y ago

> Everything is code, the UIs for creating such interfaces are just abstractions. The code generated by those no-code approaches to interface design... I'm not sure you're replying to the same thing. I never used VB much, but Delphi was not and is not no-code. In fact it emphasised using libraries a lot ('components' in its terms are classes provided by libraries) and the UI had a text description, which was streamed and created at runtime. Delphi today could indeed create something doing this just as fast, and you wouldn't draw a trackbar and hope it's recognised in the image by the AI... you'd drop an actual trackbar.

protomolecule 3y ago

That's not how VB6 or Delphi work. Delphi's visual editor allows you to position, link together and configure visual and non-visual components in design time, automatically serializes all the components into text file and in runtime your program deserializes these components from the resource embedded in the program's binary file. It also allows you to create handlers for events like OnButtonClicked or OnDBConnectionOpened where the usual arbitrarily complex programming happens. The first result from google showing what this looks like: https://www.youtube.com/watch?v=AyWm24ekSVM https://www.youtube.com/watch?v=AyWm24ekSVM

insanitybit 3y ago

I don't use these tools (I do backend dev), so perhaps I'm mistaken, but the benefits here are, I assume, a) For UX people who have minimal programming knowledge but need to produce mockups. b) For people like me who might want a basic UX to start with for demo purposes.

deleted 3y ago
[deleted]