我应该将特定于类的类型从我的模型返回到我的控制器吗?

时间:2016-04-25 13:43:29

标签: ios swift model-view-controller

我正在创建一个锻炼跟踪应用程序来学习Swift和iOS开发。我从大学毕业后的15年多来都没有编写代码,所以我对这个MVC的新东西不熟悉。欢迎任何指导,但具体而言,我对如何在模型和控制器之间进行通信的最佳实践提出疑问。

我的模特(课程名称"练习"下面)有自己的类型(例如," Weights"," Reps"),返回感觉不对那些类型回到我的控制器来构建视图。我的直觉是对的吗?我应该将这一级抽象得更高,以便控制器请求值而不是特定于类的数据结构吗?或者这对MVC来说是完全正常的吗?

以下是一些代码,用于演示我现在正在做的事情,这感觉不对。有问题的错误部分在configureView()。

模特:

class Exercise {

    var name = "placeholder name"
    var formNotes = "placeholder notes"
    private var repLog: [repLogEntry] = []
    private var currentWeights = Weights(warmup25: 0, warmup50: 0, heavy: 0)

    init() {
        // some test data
        name = "Squat"
        formNotes = "Grasp the bar 1 inch outside knurling\nPull bar apart while squeezing shoulders back"
        self.recordExercise("16-04-20", weight: 135, reps: Reps(firstSet: 10, secondSet: 8))
        self.recordExercise("16-04-22", weight: 135, reps: Reps(firstSet: 11, secondSet: 9))
        self.setWeights(135)


    }

    // data to be recorded
    private struct repLogEntry {
        var date: String
        var weight: Int
        var reps: Reps

    }

    // reps always come in pairs
    struct Reps {
        var firstSet: Int
        var secondSet: Int
    }

    // weights of the exercise
    struct Weights {
        var warmup25: Int
        var warmup50: Int
        var heavy: Int
    }

    func recordExercise(date: String, weight: Int, reps: Reps) {
        let newRepLogEntry = repLogEntry(date: date, weight: weight, reps: reps)
        repLog.append(newRepLogEntry)
    }

    func setWeights(newWeight: Int) {
        currentWeights.heavy = newWeight
        currentWeights.warmup25 = Int(Double(newWeight) * 0.25)
        currentWeights.warmup50 = Int(Double(newWeight) * 0.50)
    }

    func getCurrentWeights() -> Weights {
        return currentWeights
    }

    func getLastWorkoutReps() -> Reps {
        return repLog.last!.reps
    }

    func getLastWorkoutDate() -> String {
        return repLog.last!.date
    }

    func getLastWorkoutWeight() -> Int {
        return repLog.last!.weight
    }  
}

和控制器:

class DetailViewController: UIViewController {

    @IBOutlet weak var detailDescriptionLabel: UILabel!

    @IBOutlet weak var label: UILabel?

    let Squat = Exercise()

    var detailItem: AnyObject? {
        didSet {
            // Update the view.
            self.configureView()
        }
    }

    func configureView() {
        // Update the user interface for the detail item.
        if let detail = self.detailItem {
            if let label = self.detailDescriptionLabel {
                label.text = detail.valueForKey("timeStamp")!.description
            }
        }

        let currentWeights = Squat.getCurrentWeights()
        let exerciseName = Squat.name
        let formNotes = Squat.formNotes
        let warmup25Text = String(currentWeights.warmup25)
        let warmup50Text = String(currentWeights.warmup50)
        let heavyText = String(currentWeights.heavy)
        let lastWorkoutReps = Squat.getLastWorkoutReps()
        let lastWorkoutDate = Squat.getLastWorkoutDate()
        let lastWorkoutWeight = Squat.getLastWorkoutWeight()

        label?.text = "\(exerciseName)\nWarmup (25%): \(warmup25Text)\nWarmup (50%): \(warmup50Text)\nHeavy (100%): \(heavyText)\n\(lastWorkoutDate) Reps @\(lastWorkoutWeight): \(lastWorkoutReps.firstSet) and \(lastWorkoutReps.secondSet)\n\nForm Notes:\n\(formNotes)"

    }

    override func viewDidLoad() {
        super.viewDidLoad()
        // Do any additional setup after loading the view, typically from a nib.
        self.configureView()
    }

    override func didReceiveMemoryWarning() {
        super.didReceiveMemoryWarning()
        // Dispose of any resources that can be recreated.
    }
}

1 个答案:

答案 0 :(得分:1)

对于MVC,你正在做的事情是“很好”。你有模型,视图和控制器的分离,控制器正在模型和视图之间进行调解。

在MVC中,Controller通常管理视图上的所有数据布局以及视图上的所有用户交互,因此它可能变得庞大而混乱。有时您会将模型传递给View并让View自行配置,这会使Controller变得更简单,但MVC并不好。

您可以考虑使用MVVM - 模型视图ViewModel - 这是MVC的扩展。基本上,它采用如何从Controller中显示Model数据并将其放入ViewModel的逻辑,ViewModel提供给View以供其自行配置。这简化了Controller,但也使View与模型隔离开来。

因此,您的ViewModel将拥有您的text = "\(exerciseName...代码,但就是这样。它只知道如何获取Model对象并生成应该显示的文本。它不知道它将在何处显示。 View使用此ViewModel进行配置,因此它可以获取所需的数据,但不知道它来自何处。 Controller是创建ViewModel并将其传递给View的中间人。