Mobile App Development 2021W Lecture 4: Difference between revisions
No edit summary |
|||
Line 4: | Line 4: | ||
==Notes== | ==Notes== | ||
Historical articles referenced in class: | |||
* [https://www.dougengelbart.org/content/view/209/448/ The Mother of All Demos] | |||
* [https://en.wikipedia.org/wiki/Xerox_Alto Xerox Alto] | |||
* [https://en.wikipedia.org/wiki/Apple_Lisa Apple Lisa] | |||
* [https://en.wikipedia.org/wiki/ResEdit ResEdit] | |||
* [http://www.kevra.org/TheBestOfNext/page570/page571/page571.html NeXT development tools] | |||
<pre> | <pre> |
Revision as of 21:00, 20 January 2021
Video
Video from the lecture given on January 20, 2021 is now available.
Notes
Historical articles referenced in class:
Lecture 4 ------------ * nested views * UIkit * Apple-centered history of GUIs - mother of all demos (Englebart, 1968) - Xerox Alto - Lisa - Macintosh - NeXT - MacOS X - iPhone Why not just use HTML/CSS everywhere, instead of SwiftUI? - because then you need an entire web renderer to create the interface! - web rendering engines are BEASTS - only 3 left Webkit (Apple) Blink (Google, fork of Webkit) Gecko (Mozilla) Microsoft had Trident, but they gave up and adopted Blink for Edge UIkit is for iOS, AppKit is for MacOS - storyboard is the way you make these interfaces SwiftUI is for both MacOS and iOS SwiftUI is really a domain-specific language for building interfaces, built using Swift - some rules of regular swift apply, but many don't - really need to switch modes when doing SwiftUI - only use SwiftUI components in Views, not elsewhere