导航问题 [英] Navigation Questions

问题描述

我们正在开发一个应用程序，用于将现有的iPad应用程序转换为Metro。在iPad应用程序中，在横向模式下，导航栏位于左侧，右侧包含内容框架。要添加导航支持，
我们正在探索4个选项：

We are working on an application where we are converting an existing iPad application to Metro. In the iPad application, in landscape mode, the navigation bar is on the left-hand side and the right side contains the content frame. To add navigation support, we are exploring 4 options:

1。在中心屏幕上，为每个导航项添加切片。用户可以导航回集线器以选择不同的视图。

1. On the hub screen, add tiles for each of the navigation items. User can navigate back to the hub to select a different view.

2。在顶部导航栏中添加导航项（缩略图）。

2. Add the navigation items in the top navigation bar (as thumbnails).

3。在每个视图页面上添加标题菜单以在视图之间切换。

3. Add a header menu on each view page to switch between views.

4。添加导航弹出窗口。这类似于iOS实现;但是，飞出会覆盖内容视图，用户可以在需要时隐藏/显示。屏幕上会一直显示一个按钮，当点击该按钮时，将显示导航飞出的
。如果用户单击弹出窗口中的关闭按钮或进行选择，则弹出窗口将消失。

4. Add a navigation fly-out. This is similar to the iOS implementation; however, the fly-out would be overlay the content view and the user could hide/show when needed. A button would be constantly available on the screen, which when clicked, would display the navigation fly-out. If the user clicks the close button in the fly-out or makes a selection, the fly-out would disappear.

我已经看到了前3个选项的示例应用程序和/或书面指导。我没有看到最后一个选项。我知道你不想在屏幕上显示任何与内容无关的东西，所以我的直觉是它不是最好的做法。风味
是删除按钮但添加底部应用程序栏选项以显示弹出窗口。如果您在顶部应用程序栏中包含导航选项，则只需少1次点击即可实现该选项。

I have seen example applications and/or written guidance on the first 3 options. I have not seen anything on the last option. I know you do not want to display anything on the screen not related to content so my gut is it is not a best practice. A flavor is to remove the button but add an bottom application bar option to display the fly-out. If you include the navigation options in the top application bar, that option could be achieved in 1 fewer clicks.

所以问题包括：

1。 ＃4是否违反最佳做法？

1. Does #4 go against best practices?

2。可以实现多个导航选项吗？我们可以实施选项＃1，＃2和＃3吗？

2. Is it ok to implement multiple navigation options? Could we implement options #1, #2, and #3?

推荐答案

史蒂夫，

选项4会违反Chrome之前的内容最佳做法。 你不会想要一个持久的按钮。

Option 4 would violate best practices of Content before Chrome.  You would not want a persistant button.

你可以使用app bar和tiles（Ala IE）或你今天在其他Metro风格应用中看到的方法之一。

You could use the app bar and tiles (Ala IE) or one of the methods you see in other Metro style apps today.

我认为多种导航选项可能会让您的用户感到困惑。 您认为您的应用最适合的导航方式是：
http://msdn.microsoft.com/en-us/library/windows/apps/hh761500.aspx 功能Hierarchial还是Flat？

I would think multiple navigation options that do all the same may confuse your user.  What style of navigation do you think your app would be served best by: http://msdn.microsoft.com/en-us/library/windows/apps/hh761500.aspx  Hierarchial or Flat?

-Jeff

这篇关于导航问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！