Re:We need visual programming. No, not like that
by ryandrake on Monday July 15, 2024 @11:18AM
(#40968621)
Mixes Well is an understatement. I couldn't imagine writing any more than a simple toy app without it. I've experimented with building an iOS UI purely in code, and while it is possible, it is a painful, masochistic, and slow way to develop.
Re:We need visual programming. No, not like that
by nottorp on Monday July 15, 2024 @04:00PM
(#40970998)
The idea is to do everything trivial via the interface builder thing of the platform but not get limited by it when you want to customize the last 10%
> any change made in the editor immediately updates the code, any change in code immediately updates the editor.
Delphi memories :)
> That said, in my experience at least, this editor falls over quite often if you do that.
Not-Delphi memories.
Apple has two UI frameworks, UIKit and SwiftUI, and Xcode's Interface Builder handles each differently. The Interface Builder for each is built into Xcode, but the UI they present when editing is quite different — I'm unclear if they're both officially called "Interface Builder" or if people like me stuck with the same name for the new one because it's a thing for building interfaces.
The older system is UIKit, where Interface Builder produces some XML files — .xib or .storyboard — and once those are loaded, they result in objects which are fully manipulable in code.
The newer system, SwiftUI, the source code is the source-of-truth for a WYSIWYG editor — any change made in the editor immediately updates the code, any change in code immediately updates the editor. That said, in my experience at least, this editor falls over quite often if you do that.