Tags
This article will look at how SwiftUI's approach to declarative views compares to CwlViews, why the two approaches differ and what Apple changed to make this possible. I'll end with some thoughts about how this will affect macOS and iOS development.
In this article, I'll look at the the biggest problem with non-declarative views and how frameworks have slowly become more declarative, over time. I'll take a guess at what approach a declarative view framework from Apple might use – although keep in mind, I have zero insider knowledge and there's only a month before WWDC proves how wrong I am.
CwlViews is a library that offers declarative construction for all common iOS and macOS view and application objects. The result hides many of the busywork tasks that consume much of Cocoa application programming, leaving behind a highly concise, declaratively constructed, view-state driven, reactively connected experience.
The upcoming CwlViews library offers a syntax for constructing views that has a profound effect on the Cocoa applications, making them naturally 'unidirectional' and eliminating the need for `UIViewController` subclasses. In this article, I look at what the Cocoa application design pattern becomes if we take away the need for a controller.
In this article, I look at constructing Cocoa views in code using a unique syntax that offers dynamic and constant options with no syntactic overhead, support for parameters inherited through the class hierarchy, support for large numbers of optional parameters without needing to push unused parameters onto the stack, avoidance of parentheses, and avoiding the need to specify types – all while remaining completely typesafe.
I present a small file for handling layout, similar to UIStackView or NSStackView but built around efficient Swift syntax and the aim of composing full layouts as a single expression.
In this article, I’ll look at a little theory and history behind the primary application design pattern used in Cocoa. I’ll discuss the key shortcoming of Cocoa’s Model-View-Controller approach, Apple’s aborted efforts to address this shortcoming and wonder from where the next major improvements will come.
Just a little helper class that I use to round off the rough edges when dealing with Cocoa's key-value observing.
In my first truly 'Cocoa' article since restarting Cocoa with Love, I'll talk about presenting errors to the user. In particular, ensuring that errors we didn't expect or plan for are presented in a manner that allows error reporting by users and easier bug fixing.
