出自UXGuide.net

管理设置或配置选项

Managing Settings or Configuration Options

iPhone applications can offer settings that define preferred application behaviors or configuration options users can set to change some functionality of the application. Settings should represent information, such as an account name, that users set once and rarely (if ever) change. Users view application-specific settings in the built-in Settings application. Configuration options are values that users might want to change frequently, such as category types displayed in a list; configuration options should be available within the application itself.

iPhone应用程序可以提供用于定义应用程序行为的设置，或者是用于改变一些影响应用程序功能性的选项。设置应该表示一些信息，例如帐户的名称，用户只需设置一次，就很少会再去改动。用户在内置的设置应用程序设置中浏览特有的应用程序的设置。而配置选项, 用户可能会经常改变他们的值。比如，显示一个列表的类别，配置选项应该在应用程序当中即可使用(而不应该把它放置到内置的设置应用程序中)。

You should consider settings and options to be mutually exclusive. That is, you should not offer both settings and configuration options in your application.

你应该考虑到设置和选项是相互排斥的。也就是说，你不应该在你的应用程序中的同时提供设置和配置选项。

It’s best when iPhone applications do not ask users to specify any settings at all. Users can begin to use these applications right away without being asked to supply set-up information. To achieve this in your application, there are a few design decisions you can make:

不需要用户指定任何设置的iPhone应用程序，是最佳的。用户无需被要求提供初始设置信息，即可马上使用这些应用程序。你可以采纳以下这些设计决策达到这个目的：

• Focus your solution on the needs of 80 percent of your users. When you do this, the majority of users do not need to supply settings because your application is already set up to behave the way most users expect. If there is functionality that only a handful of users might want, or that most users might want only once, leave it out.

把你的解决方案集中在满足80%的用户的需求上。当你这样做时，大多数用户就不需要提供设置了，因为你的应用已经建立在大多数用户所期望的操作行为方式上。如果有些功能，只有一小部分的用户可能想要，或者大多数用户可能只需要用一次，那就要放弃它。

• Get as much information as possible from other sources. If you can use any of the information users supply in built-in application or device settings, query the system for these values; don’t ask users to enter them again.

尽可能多从其他来源获得更多信息。如果你可以从内置的应用程序或设备的设置中获得任何用户提供信息，那就从系统查询这些值；不要让用户再次重新输入。

• If you must ask for set-up information, prompt users to enter it within your application. Then, as soon as possible, store this information in your application’s settings. This way, users aren’t forced to quit your application and open Settings before they begin to benefit from your application. If users need to make changes to this information later, they can go to your application’s settings at any time.

如果你必须得到初始的设置信息，那么提示用户在你的应用程序里输入。然后，尽快的将这些信息保存在你的应用程序的设置中。这样，用户不会在还没开始感受你的应用程序的好处时,就被迫退出你的应用程序并打开设置。如果用户以后需要再次修改这些信息，他们可以在任何时候到应用程序的设置里修改。

It’s not possible for users to open the Settings application without first quitting your application, and you should not encourage them to take this action. There is no system-provided icon or control that supports this action, and it’s recommended that you avoid creating a custom icon or control that does. If you decide you must provide settings in your iPhone application, see “The Settings Bundle” in iPhone Application Programming Guide to learn how to support them in your code.

让用户无需先退出你的应用程序即可打开设置应用程序，那是不可能的，并且你不应该鼓励他们这样操作。系统没有提供任何的图标或控件来支持这一操作，并且也建议你不要创建自定义图标或控件的去支持。如果你确定必须为你的 iPhone 应用程序提供设置，请在 iPhone应用程序设计指南中参阅“设置绑定”，以了解如何在你的代码中实现它。

Unlike settings, configuration options are likely to be changed frequently as users choose to see information from new sources or in different arrangements. You can react dynamically to changes users make to these options, because users do not leave your application to access them.

与设置不同，配置选项经常性的被改变，比如当用户选择从新的来源或不同排列中察看资料。你可以提供动态反馈让用户作出选项，因为用户访问它们时并不会停止你的应用程序。

You can offer configuration options in the main user interface or on the back of^[1] a screen. To decide which technique makes sense, determine if the options represent primary functionality and how often users might want to set them.

你可以在主用户界面或在之外的屏幕里提供配置选项。你可通过考虑这个选项代表的功能的重要性，以及他可能被使用的频率次数来判断，使用哪种方式提供配置会更加合理。

For example, Calendar allows users to view their schedules by day, week, or month. These options could have been offered on the back of the screen, but viewing different parts of a calendar is primary functionality and users are likely to change their focus frequently.

例如，日历允许用户按天，周，月的方式浏览他们的日程。这些选项其实也是可以在其他之外的屏幕中提供，但翻看日历的不同部分是其首要功能，并且用户可能会频繁改变他们的关注点。（所以，这些选项应该在主用户界面中提供。）

On the other hand, the primary functionality of Weather is to display a city’s current conditions and 6-day forecast. Although it’s important to be able to choose whether temperatures are displayed in Celsius or Fahrenheit, users are not likely to change this option very often, so it would not make sense to put it in the main user interface. Offering the temperature-scale option on the back of the Weather screen makes it conveniently available, but not obtrusive.

另一方面，天气的主要功能是显示城市当前天气情况以及6日内的天气预测。尽管选择是在温度摄氏还是在华氏显示是很重要的，但是用户不太可能经常更改此选项，所以把它们放在主用户界面里是说不通的。在其他之外的屏幕中提供温度单位的选项,可以使人们方便地察看,而且唐突。

注释与引用

1. ^ iPhone的界面呈现为流动的卡片式的屏幕切换动画，这里所指的后面，指的是主屏幕之后的界面。

---