即使差异不到 10%，您也会拆分 MVC 吗？
我的一些 UIViewController 由多个屏幕组成。我将这些 MVC 合并到一个 xib 中，因为屏幕上的差异大约只有 10%（一些不同的标签和按钮）。问题是我需要在屏幕上推送具体的 UIViewController 时显示具体的屏幕。因此，我在推送具体的 UIViewController 之前调用了诸如“显示 screen1 和隐藏 screen2”和“显示 screen2 并隐藏 screen1”之类的方法。现在，我知道为单独的屏幕使用单独的 MVC 会更清晰，但我对重复的东西有点恼火，所以只有在存在重大差异时我才会采取拆分操作。你如何处理这种情况？
Some of my UIViewControllers consist of several screens. I merged such each MVCs within one xib because the differences in screens were about 10% only (some different labels and buttons). The thing is I need to show concrete screen when pushing concrete UIViewController on screen. So, I have methods like "show screen1 and hide screen2" and "show screen2 and hide screen1" that I'm calling before pushing concrete UIViewController. Now, I know that having a separate MVC for separate screen would be more cleared but I'm a little bit annoyed about the duplicate stuff, so I'm taking an action to split only if there are major differences. How do you deal with such situations?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您不必为每个屏幕都有一个单独的 MVC — 这可能会变得非常混乱！一个控制器可以轻松拥有多个 UIView 出口，您可以在 IB 中连接这些出口并根据需要进行切换。但请记住，MVC 和其他范例是一种建议设计，旨在让您的生活更轻松，而不是法律。你不会因为不使用它而进入程序员地狱的第九层——最终，这取决于你。使用对您和您的应用程序有意义的任何内容！
You don't have to have a separate MVC for every screen—that can get very messy! A controller can easily have multiple UIView outlets that you can hook up in IB and switch around as needed. Remember though, that MVC and other paradigms are a suggested design to make your life easier, not a law. You won't go to the 9th layer of programmer's hell for not using it—in the end, it's up to you. Use whatever makes sense for you and your app!