←back to thread

Visual Basic 6 IDE recreated in C#

(github.com)
377 points porterde | 1 comments | 14 Nov 24 21:47 UTC | HN request time: 0.211s | source
Show context
wiseowise ◴[14 Nov 24 22:51 UTC] No.42142078[source]▶
Still don't understand how we went from this to modern GUI toolkits.

It looks and works so intuitively.

replies(14): >>42142147 #>>42142252 #>>42142509 #>>42142582 #>>42142873 #>>42143270 #>>42143473 #>>42145120 #>>42145467 #>>42146571 #>>42147144 #>>42147616 #>>42148647 #>>42155384 #
Onavo ◴[14 Nov 24 22:58 UTC] No.42142147[source]▶
The answer is simple, mobile and relative layouts. GUI builders are easy when you can just use absolute positioning for everything (see Retool and the dozens of Retool clones). They become insanely complex when you can't.
replies(5): >>42142262 #>>42142267 #>>42142329 #>>42142436 #>>42145326 #
ok123456 ◴[14 Nov 24 23:12 UTC] No.42142262[source]▶
Windows Forms didn't use absolute positioning for everything. You could anchor things relatively to other controls or components. You would test how things behave when you maximize and resize windows, similar to how Devtools tests reactive designs now.

If it were a very simple window or dialog that always showed the same amount of information, you would disable maximize, resize, and position it absolutely. This allowed you to add "reactivity" incrementally instead of forcing everything to be reactive up front.

replies(1): >>42143422 #
1. epcoa ◴[15 Nov 24 02:24 UTC] No.42143422[source]▶
> You could anchor things relatively to other controls or components.

I don’t believe this was a feature that came out of the box in VB6. There is Control.Anchor in WinForms that is post VB6.