基于文档的应用程序的 iPad ViewController 配置
我想知道对于我一直在计划的应用程序来说，视图控制器和视图的最佳配置是什么。从概念上讲，我想要布局应用程序的方式是使用初始加载器/浏览器视图，可能包含文档缩略图。当用户选择打开一个视图时，会出现一个新视图，该视图构成主要文档编辑模式。用户还可以选择打开包含替代文档编辑模式的第三个视图。
我认为这与 iPad 版 Pages 的工作方式非常相似，首先有一行文档缩略图可供选择，然后是主文字处理视图，并可从弹出窗口访问第三个页面设置视图。文档浏览器视图和两个文档编辑视图。
现在，我可以想到并尝试了几种不同的设置，但在每种情况下我都可以看到稍后会遇到的问题。所以说真的，我正在寻找有关配置的建议，您认为该配置可以使事情尽可能整洁和易于管理。
我希望这不是一个太开放的问题，我将非常感谢任何答案。
谢谢你，
I was wondering what would be the best configuration of view controllers and views for an app that I’ve been planning out. Conceptually, the way I would like to lay out the app is with an initial loader/browser view, likely with document thumbnails. When a user chooses to open one, a new view comes up that forms the main document-editing mode. The user can also choose to bring up a third view that contains an alternative document-editing mode.
I suppose this is very much like the way the Pages for iPad works, with first a row of document thumbnails to choose from, then the main word processing view, and accessible from a popover a third page setup view. Document browser view, and two document editing views.
Now, I can think of, and have been playing around with a few different set-ups, but in each case I can see problems that I’ll be running into later. So really, I’m looking for advice on a configuration that you think would keep things as neat and manageable as possible.
I hope this is not too open a question, and I would very much appreciate any answer.
Thank you,
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我可能会因为提出这样的建议而头部中弹，但无论如何我都会这样做：
在学习 iOS 编程时，我花了很多时间学习（就像大多数人一样 - 正如每个教程中所教授的那样） Planet）了解如何使用导航视图、工具栏以及所有有助于不同类型导航的标准类型视图。
在我一直在开发的最新应用程序中，我花了很多时间和挫败感试图弄清楚如何最好地描述我正在做的事情，而且还试图将其融入 iOS 框架用来实现这些东西的内容中。然后（当然）我陷入了尝试让事情做他们不应该做的事情 - 就像当导航视图不允许我使用“后退”按钮跳出我设置的导航层次结构时简而言之
- 当我不再担心所有这些不同类型的视图和控制器的具体细节 - 以及它们如何交互以及我应该如何做到这一点 - 并开始担心如何我希望我的应用程序能够工作——并且在通用视图、自定义工具栏等的基础上工作——整个想法变得更有意义。
就我而言，我喜欢 Mapquest 应用程序的外观和感觉 - 他们处理工具栏的方式，您可以从屏幕的顶部和底部打开和关闭工具栏 - 有按钮 - 可以切换到其他视图等因此，我开始使用“通用”视图来实现此功能 - 整个事情就完成了。
简而言之：
1 。我会决定您希望它的外观和功能
如果需要，使用第三方应用作为您的灵感
决定何时/何地/是否适用某些“标准”实践 - 并在何处/何时使用它们。
玩得开心！
-BKG
I will probibly get shot in the head for making a suggeston like this, but I'll make it anyway:
In learning iOS programming, I spent a lot of time studying (as most people do - and as is taught by every tutorial on the planet) on how to use Navigation Views, and toolbars, and all the standard type views that assist in different types of navigation.
On the latest app I have been working on - I spent a lot of time and frustration trying to figure out how to best characterize what I was doing - and moreso trying to fit it into what the iOS frameworks would use to implement this stuff. Then (of course) I got stuck trying get things to do what they weren't supposed to - like when a navigation view wouldn't let me use the "back" button to jump out of the navigation herirarchy I'd set-up, etc.
In short - when I stopped worrying about the specifics of what all these different types of views and controllers were - and how they interacted and how I was supposed to do it - and started worrying about how I wanted my application to work - and working from a basis of generic views, custom toolbars, etc - the whole think made a whole lot more sense.
In my case, I liked the look-and-feel of the Mapquest app - and they way it dealt with toolbars that your could open and close from the top and bottom of the screen - which had buttons - which could switch to other views etc. So I started using "generic" views to implement this functionality - and the whole entire thing clicked together.
So in-short:
1 . I'd decide how you want it to look and what you want it to do
Use a third-party app as your inspiration, if needed
Decide when/where/if some of the "standard" practices apply - and use them where/when they do.
Have fun!
-BKG