dialogs造句

Visually differentiate modeless dialogs from modal dialogs.

The writer is not very good at writing dialogs.

Never use transitory dialogs as error messages or confirmations.

Before tabbed dialogs, the problem was often clumsily solved with expanding and cascading dialogs, which we’ll discuss shortly.

The SampleApp defines a callback to handle the success or failure for login requests, for logout dialogs, for post to wall dialogs and for get friends requests.

These dialogs pop up like weeds in most programs and should, like error dialogs, be eliminated in favor of more useful idioms.

The navigation paths to these dialogs are depicted in Figures 8 and 9.

In modal dialogs, the Cancel button means, “Abandon my input and close the dialog.”

Thankfully, cascading dialogs have been falling from grace, but examples can still be found.

There’s no reason for users to be subjected to dialogs like these.

You can think of property dialogs as control panels with exposed configuration controls for the selected object.

Two solutions for better modeless dialogs We offer two design strategies for improving modeless dialogs. The first one is easy to swallow, a stopgap for common predicaments. The second one is more radical; an evolutionary step forward.

These dialogs parallel a complex procedure that is “normally” used to manage a feature of the program.

This time, select the USERID attribute, and click OK on each of the dialogs to close them.

The concepts of modal and modeless dialogs are derived from programmers’ terms. They affect our design, but we must also examine dialogs from a goal-directed point of view.

A number of years back, tabbed dialogs quickly became an established standard in the world of commercial software.

Some dialogs say Close, some say Apply, some use Done, while others use Dismiss, Accept, Yes, and even OK.

Now this is a standard idiom, as well known as the menu bar, where buttons move from traditional dialogs to toolbars.

Put this information into main application windows in the form of RVMF and see how many dialogs you can eliminate from routine use!

Although the sections on SWT and JFace are brief, as I noted earlier, subsequent chapters on other technologies provide ample detail regarding views, editors, actions, and dialogs.

We aim to keep anything related to the model under the models package and any dialog-related classes under the dialogs package.

Menu items and dialogs, when they are translated, need to be considered holistically. It is important to make sure that translated interfaces remain coherent as a whole.

If a transient application performs more than just a single function, the interface should communicate this visually and unambiguously and provide immediate access to all functions without the addition of windows or dialogs.

In general, modal dialogs are the easiest for users (and designers) to understand. The operation of a modal dialog is quite clear, saying to users, “Stop what you are doing and deal with me now.

If you find your program requiring cascading dialogs for anything other than really obscure stuff that your users won’t generally need, you should take another look at your interaction framework—you may find some severe structural flaws.

我们打算将与模型相关的所有内容都放在models包中，而与对话框相关的所有类都放在dialogs包下。

Hot: Engaging in conversations: that people spend more time using social media than using email reveals that people want dialogs, and there are many new ways they prefer to have them.

Much of the confusion creeps into the situation because users are so familiar with the behavior of modal dialogs. A modal dialog can adjust itself for the current selection at the instant it was summoned. It can do this with assurance that the selection won’t change during its lifetime. Conversely, the selection is quite likely

The use of tabbed screen areas is a space-saving mechanism and is sometimes necessary to fit all the required information and functions in a limited space. (Settings dialogs are a classic example here. We don’t think anyone is interested in seeing all of the settings for a sophisticated application laid bare in a single view.)

Modeless dialogs are conventionally free-floating windows, which allows users to position them on the screen wherever they like, but it also results in window-management excise. It is no user’s goal to reposition windows—all work done in the service of this is excise.

On a positive note, many domain or application objects with numerous properties can now have correspondingly rich property dialog boxes without making those boxes excessively large and crowded with controls (see Figure 24-8 for an example). Many function dialogs that were previously jam-packed with controls now make better use o