如何在Swift中使用协议初始化UIView与UIViewController？

Great question! Building on the nibless view controller pattern you’ve started with, we can use protocols to abstract and reuse initialization logic across both UIViewController and UIView subclasses—no more repeating boilerplate code for every component. Let’s break this down step by step.

1. Protocol-Driven Nibless View Controllers #

First, let’s formalize the nibless initialization pattern into a protocol so any view controller can adopt it without duplicating code.

Step 1: Define the Protocol #

Create a protocol that enforces a nibless init method, then use an extension to provide the default implementation (and block nib-based initializers):

protocol NiblessViewControllerInitializable: UIViewController {
    init()
}

extension NiblessViewControllerInitializable {
    init() {
        self.init(nibName: nil, bundle: nil)
    }
    
    // Mark nib-based initializers as unavailable to prevent accidental use
    @available(*, unavailable, message: "Loading this view controller from a nib is unsupported.")
    required init?(coder: NSCoder) {
        fatalError("init(coder:) has not been implemented")
    }
    
    @available(*, unavailable, message: "Loading this view controller from a nib is unsupported.")
    override init(nibName nibNameOrNil: String?, bundle nibBundleOrNil: Bundle?) {
        super.init(nibName: nibNameOrNil, bundle: nibBundleOrNil)
    }
}

Step 2: Adopt the Protocol in Your View Controllers #

Now any view controller can conform to this protocol and get the nibless init for free—focus only on your custom logic:

class CustomViewController: NiblessViewControllerInitializable {
    override func viewDidLoad() {
        super.viewDidLoad()
        view.backgroundColor = .systemBlue
        // Add your custom setup here
    }
}

// Usage:
let vc = CustomViewController()

2. Protocol-Driven UIView Initialization #

For UIView, we can create a similar protocol to standardize initialization (and optionally disable xib loading).

Step 1: Define the View Initialization Protocol #

This protocol provides a default init() method, blocks xib-based initialization, and includes a setup hook for custom layout:

protocol ViewInitializable: UIView {
    init()
    func setupView()
}

extension ViewInitializable {
    init() {
        self.init(frame: .zero)
        setupView()
    }
    
    // Disable coder-based init if you don't want to support xibs
    @available(*, unavailable, message: "Loading this view from a nib is unsupported.")
    required init?(coder: NSCoder) {
        fatalError("init(coder:) has not been implemented")
    }
    
    // Default empty setup (override in subclasses for custom logic)
    func setupView() {}
}

Step 2: Adopt the Protocol in Your Views #

Conform your views to the protocol, then override setupView() to add your custom layout and configuration:

class CustomView: ViewInitializable {
    private let titleLabel = UILabel()
    
    func setupView() {
        backgroundColor = .systemGray5
        addSubview(titleLabel)
        
        // Auto layout setup
        titleLabel.translatesAutoresizingMaskIntoConstraints = false
        NSLayoutConstraint.activate([
            titleLabel.centerXAnchor.constraint(equalTo: centerXAnchor),
            titleLabel.centerYAnchor.constraint(equalTo: centerYAnchor)
        ])
        
        titleLabel.text = "Hello Protocol-Driven View!"
        titleLabel.font = .systemFont(ofSize: 16, weight: .medium)
    }
}

// Usage:
let customView = CustomView()

Key Benefits of This Approach #

• Code Reusability: No more copying the same nibless init boilerplate across every component.
• Enforced Consistency: All conforming types follow the same initialization pattern, preventing accidental nib loading.
• Cleaner Subclasses: Your custom components focus on their unique logic, not initialization overhead.

内容的提问来源于stack exchange，提问作者hisaac