MVC 這三個字母大家都背得出來,但真正在自己專案裡落實分層,往往需要一次「痛過之後」的重構經驗。本文用一個 App 列表的小範例,示範同樣的功能如何分三次演進。
先說個比喻:一個人要吃五個包子才飽,不代表他可以直接從第五個開始吃。程式碼的優化也一樣,必須一步一步來,你才能理解每一步解決了什麼問題。
模型 YYappInfo
#import <Foundation/Foundation.h> @interface YYappInfo : NSObject @property (nonatomic, copy) NSString *name; @property (nonatomic, copy) NSString *icon; @property (nonatomic, strong, readonly) UIImage *img; - (instancetype)initWithDict:(NSDictionary *)dict; /** 工廠方法 */ + (instancetype)appInfoWithDict:(NSDictionary *)dict; @end
#import "YYappInfo.h"
@interface YYappInfo ()
{
UIImage *_img;
}
@end
@implementation YYappInfo
- (instancetype)initWithDict:(NSDictionary *)dict
{
if (self = [super init]) {
self.name = dict[@"name"];
self.icon = dict[@"icon"];
}
return self;
}
+ (instancetype)appInfoWithDict:(NSDictionary *)dict
{
return [[self alloc] initWithDict:dict];
}
- (UIImage *)img
{
_img = [UIImage imageNamed:self.icon];
return _img;
}
@end
視圖 YYappInfoView(xib 已連線)
#import <UIKit/UIKit.h> @interface YYappInfoView : UIView @property (strong, nonatomic) IBOutlet UIImageView *appInfoViewimg; @property (strong, nonatomic) IBOutlet UILabel *appInfoViewlab; @property (strong, nonatomic) IBOutlet UIButton *appInfoViewbtn; @end
控制器:什么都自己扛
- (void)viewDidLoad
{
[super viewDidLoad];
int totalloc = 3;
CGFloat appviewW = 80;
CGFloat appviewH = 90;
CGFloat margin = (self.view.frame.size.width - totalloc * appviewW) / (totalloc + 1);
int count = self.apps.count;
for (int i = 0; i < count; i++) {
int row = i / totalloc;
int loc = i % totalloc;
CGFloat appviewX = margin + (margin + appviewW) * loc;
CGFloat appviewY = margin + (margin + appviewH) * row;
YYappInfo *appinfo = self.apps[i];
// 從 xib 讀取視圖——這件事其實和控制器無關
NSArray *arryM = [[NSBundle mainBundle] loadNibNamed:@"appInfoxib"
owner:nil options:nil];
YYappInfoView *appinfoview = [arryM firstObject];
appinfoview.frame = CGRectMake(appviewX, appviewY, appviewW, appviewH);
// 逐一賦值——這是視圖自己的事
appinfoview.appInfoViewimg.image = appinfo.img;
appinfoview.appInfoViewlab.text = appinfo.name;
// 按鈕設定與事件綁定——同樣不該出現在這裡
appinfoview.appInfoViewbtn.tag = i;
[appinfoview.appInfoViewbtn addTarget:self
action:@selector(Click:)
forControlEvents:UIControlEventTouchUpInside];
[self.view addSubview:appinfoview];
}
}
-(void)Click:(UIButton *)btn
{
btn.enabled = NO;
YYappInfo *appinfo = self.apps[btn.tag];
UILabel *lab = [[UILabel alloc] initWithFrame:CGRectMake(60, 450, 200, 20)];
[lab setBackgroundColor:[UIColor lightGrayColor]];
[lab setTextAlignment:NSTextAlignmentCenter];
[lab setText:[NSString stringWithFormat:@"%@成功下載", appinfo.name]];
[self.view addSubview:lab];
lab.alpha = 1.0;
[UIView animateWithDuration:2.0 animations:^{
lab.alpha = 0;
} completion:^(BOOL finished) {
[lab removeFromSuperview];
}];
}
控制器同時在做:讀 plist、轉模型、載入 xib、算座標、賦值給子控制項、綁定事件、處理點擊邏輯。這已經不是「控制器」,而是「萬用鍋」。
觀察三個可優化點:賦值(66~67 行)、從 xib 讀取(61~62 行)、按鈕事件(69 行以後)——這三件事本質上都屬於視圖自己的職責。
視圖只對外開放一個資料接口
#import <UIKit/UIKit.h> @class YYappInfo; @interface YYappInfoView : UIView // 只對外開放一個資料接口 + (instancetype)appInfoViewWithappInfo:(YYappInfo *)appinfo; @end
#import "YYappInfoView.h"
#import "YYappInfo.h"
// 私有擴展:把 IBOutlet 屬性收到實作檔裡,對外隱藏
@interface YYappInfoView ()
@property (strong, nonatomic) IBOutlet UIImageView *appInfoViewimg;
@property (strong, nonatomic) IBOutlet UILabel *appInfoViewlab;
@property (strong, nonatomic) IBOutlet UIButton *appInfoViewbtn;
@property (strong, nonatomic) YYappInfo *appinfo;
@end
@implementation YYappInfoView
+ (instancetype)appInfoView
{
NSArray *arryM = [[NSBundle mainBundle] loadNibNamed:@"appInfoxib"
owner:nil options:nil];
return [arryM firstObject];
}
+ (instancetype)appInfoViewWithappInfo:(YYappInfo *)appinfo
{
YYappInfoView *appInfoView = [self appInfoView];
appInfoView.appinfo = appinfo;
return appInfoView;
}
// 資料一進來,視圖自己負責呈現
- (void)setAppinfo:(YYappInfo *)appinfoc
{
_appinfo = appinfoc; // 一定要保留原值,否則會遞迴
self.appInfoViewimg.image = appinfoc.img;
self.appInfoViewlab.text = appinfoc.name;
}
- (IBAction)Click
{
self.appInfoViewbtn.enabled = NO;
YYappInfo *appinfo = self.appinfo;
UILabel *lab = [[UILabel alloc] initWithFrame:CGRectMake(60, 450, 200, 20)];
[lab setBackgroundColor:[UIColor lightGrayColor]];
[lab setTextAlignment:NSTextAlignmentCenter];
[lab setText:[NSString stringWithFormat:@"%@成功下載", appinfo.name]];
[self.superview addSubview:lab];
lab.alpha = 1.0;
[UIView animateWithDuration:2.0 animations:^{
lab.alpha = 0;
} completion:^(BOOL finished) {
[lab removeFromSuperview];
}];
}
@end
控制器瞬間變乾淨
YYappInfo *appinfo = self.apps[i]; YYappInfoView *appinfoview = [YYappInfoView appInfoViewWithappInfo:appinfo]; appinfoview.frame = CGRectMake(appviewX, appviewY, appviewW, appviewH); [self.view addSubview:appinfoview];
讀 plist、字典轉模型的細節,外界根本不需要知道。讓模型自己提供一個「處理好的陣列」。
// YYappInfo.h + (NSArray *)appinfoarray;
// YYappInfo.m
+ (NSArray *)appinfoarray
{
NSString *path = [[NSBundle mainBundle] pathForResource:@"app.plist" ofType:nil];
NSArray *arrayM = [NSArray arrayWithContentsOfFile:path];
NSMutableArray *appinfoarray = [NSMutableArray array];
for (NSDictionary *dict in arrayM) {
[appinfoarray addObject:[YYappInfo appInfoWithDict:dict]];
}
return appinfoarray;
}
於是控制器的資料來源縮短成一行:
- (NSArray *)apps
{
if (!_apps) {
_apps = [YYappInfo appinfoarray];
}
return _apps;
}
這就是 MVC 的真正含義:不是三個資料夾,而是一條資料流的單向流動——模型供資料、視圖呈現、控制器居中協調。當你能指著某段程式碼說出「這件事為什麼不該放在這裡」,你就真的懂 MVC 了。