iOS4 Built in SwiftUI
github.com
iOS4 Built in SwiftUI
1–10 of 45 posts
Re: iOS4 Built in SwiftUI
#2Would be nice if it share some screenshots
Re: iOS4 Built in SwiftUI
#3Would be nice if it share some screenshots
Adding screenshots would probably get the repo DCMA'ed by Apple for infringing their Copyright
Re: iOS4 Built in SwiftUI
#4iOS was and always will be a social construct. The ideas of NexTStep pre-date the 90s but certainly weren't new in 2010.
Re: iOS4 Built in SwiftUI
#5Screenshots: https://imgur.com/a/JNVaFBI
Re: iOS4 Built in SwiftUI
#6This file is insane: https://github.com/zzanehip/The-OldOS-Project/blob/master/Ol...
I hate to say it but SwiftUI is tricky to write for very complex user interface...the one in that file is a nightmare imo.
Re: iOS4 Built in SwiftUI
#7This file is insane: https://github.com/zzanehip/The-OldOS-Project/blob/master/Ol... I hate to say it but SwiftUI is tricky to write for very complex user interface...the one in that file is a nightmare imo.
Compared to the equivalent standard code to implement that UI?
Re: iOS4 Built in SwiftUI
#8This is great! While I really do like the flat UI design trend, I sure do miss skeuomorphism in UI design. I underestimated the nostalgia that seeing this original design would stir up in me.
Re: iOS4 Built in SwiftUI
#9This file is insane: https://github.com/zzanehip/The-OldOS-Project/blob/master/Ol... I hate to say it but SwiftUI is tricky to write for very complex user interface...the one in that file is a nightmare imo.
Compared to the equivalent standard code to implement that UI?
Did you look at the file? Yes, comparatively using a non-declarative approach would render much simpler code. Perhaps the author is not writing SwiftUI proficiently? Having used SwiftUI myself I would argue that this is not the case.
Re: iOS4 Built in SwiftUI
#10Earlier quoted context omitted.
Compared to the equivalent standard code to implement that UI?
Did you look at the file? Yes, comparatively using a non-declarative approach would render much simpler code. Perhaps the author is not writing SwiftUI proficiently? Having used SwiftUI myself I would argue that this is not the case.
It reminds me of why I am not a big fan of Flutter either. Not a fan of the deep nesting which both SwiftUI and Flutter needs to do for even moderately complex UIs.