BlackBerry - 使用内容管理器进行多屏幕还是单屏幕？
我见过使用许多屏幕的项目，每个屏幕都有不同的布局和功能。
我见过只有一个屏幕的项目（如向导工作流程），其中内容在用户交互时发生变化（这似乎在向导中使用单个屏幕是合乎逻辑的）。
但我也见过一些项目（如游戏、信使或电话设置实用程序等应用程序）使用单个屏幕来实现不同的功能。
我可以看到在应用程序中使用单屏的优点：
- 保持相同的装饰设计和菜单或工具栏（也可以通过继承来实现）
- 在 ui 堆栈中保持单屏（可以通过弹出/推送屏幕来实现）
- 易于处理数据关于应用程序
您能说出单屏应用程序的其他优点/缺点吗？
什么时候使用这种方法比较好？
谢谢你！
I've seen projects which use many screens each one for different layout and functionality.
I've seen projects with only one screen (like wizard workflow) where content is changed on user interaction (and this seems to be logical to use single screen in wizards).
But also I've seen projects (apps like game or messenger or phone settings utility) which use single screen for different functionalities.
I can see such advantages of having single screen in app:
- keep same decoration design and menu or toolbar (which may be also achieved with inheritance)
- keep single screen in ui stack (which may be achieved by pop/push screen)
- easy to handle data over application
Can you tell other advantages/disadvantages of single screen app?
When its better to use this approach?
Thank you!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
对于我们来说，这取决于屏幕。我们有一些屏幕可以实现共同目标，例如带有列表控件或进度栏的弹出窗口。我们的大多数屏幕都是按功能分开的。我认为这有助于防止事情变得复杂。
我们确实重用了列表控件和树字段等的回调，其中特定控件的功能几乎总是相同的。
我也有一些同样的困惑，许多人建议使用单一类来限制设备上的占用空间，但其他人说，对于较新的设备，这并不重要。
For us it depends on the screen. We have some screens that achieve common goals such as a popup with a list control or a progress bar. Most of our screens are separated by functionality. I think that helps to prevent things from being convoluted.
We do reuse the callbacks for list controls and tree fields etc where the functionality of the particular control is almost always the same.
I have had some of the same confusion, many people suggest using single classes to limit the footprint on the device, but others say with newer devices it doesn't much matter.