Each web UI plug-in contributes component-specific web pages and scripts to an extension point.
每个WebUI插件向某个扩展点提供组件特定的网页和脚本。
For the MySQL example, the update site will provide one feature that includes the domain and UI plug-in.
对于MySQL范例，更新站点将会提供一个特性，它包含了域和UI插件。
Before code can be added to our actions, we need to tell this UI plug-in about the corresponding core plug-in, otherwise it won't have access to HSQLDB classes.
在能够给我们的操作添加代码之前，我们需要将这种UI插件与相应的核心插件区别开来，否则它将不能访问HSQLD b类。
The contribution of an action set to the org.eclipse.ui.actionSets extension point implicitly depends on the defining plug-in, the Workbench UI plug-in (org.eclipse.ui).
对 org.eclipse.ui.actionSets扩展点动作设置的贡献隐式地依赖于定义插件，即Workbench UI 插件（org.eclipse.ui）。
However, after the release of this consolidated UI plug-in, developers who were trying to use it in their own code had comments (or complaints) that the code, while good, was all very different.
然而，在这个合并的UI插件发布之后，尝试在自己的代码中使用该插件的开发人员认为(或抱怨)它虽然很好，但彼此的差别过大。
Figures 3 and 4 show more formally where additional plug-ins can display their contributed UI elements in the main window. The scope of these UI changes can be large or small.
图3和图4更为正式地展示了附加插件在主窗口中呈现的UI元素，这些 UI变化的范围可大可小。
This was a very clever and important plug-in for UI developers, as it made working with dynamic pages as easy as working with static ones.
对UI开发人员而言，这是一个非常智能、重要的插件，因为使得处理动态页面就像处理静态页面一样简单。
Placing a single component view in each plug-in resolves whatever confusion may result from having properties from several components display when referring to a single one in the CAE UI.
当在CAEUI中只引用一个组件视图时，显示来自不同组件的属性可能会造成混乱，但在每个插件中仅放置一个组件视图能够解决这个问题。
This UI should also provide some way for users to select a plug-in whose dependency chain they want to observe.
这个UI还应该为用户提供一些方法来选择希望解析其依赖性的插件。
When you write a plug-in application, you provide implementation code that WSRR executes every time one of the interface methods is called (directly through an API or indirectly through the UI).
当您编写一个插件应用程序时，需要提供实现代码，每当（直接通过API或间接通过 UI）调用接口方法时，WSRR 都会执行该实现代码。
The UI library actually started as several different plug-ins "back in the day" ("the day" meaning late 2007, which is decades ago in terms of jQuery).
这个UI库在最初的时候（即 2007 年年末）仅是几个不同的插件。
The UI elements that need globalization include menu, toolbar, dialog, splash screen, welcome page, plug-in and product information, and the standard Eclipse UI elements.
需要进行全球化的UI元素包括菜单、工具栏、对话框、闪屏、欢迎页面、插件和产品信息，以及标准的Eclipse UI 元素。
JQuery Cookie, another plug-in, can be added to jQuery UI Tabs so that the browser "remembers" the most recently selected TAB the next time the user returns to your page.
jQueryCookie是另一个插件，可以把它添加到jQueryUITabs中，让浏览器在用户下一次访问页面时“记住”最近选择的选项卡。
Figure 4 shows a chat UI that has several plug-in enhancements, such as an icon to launch conversations through voice chat, using voice Over Internet Protocol (VoIP).
图4展示了一个具有若干插件功能增强的聊天ui，例如，其中的一个图标利用VoiceOverInternetProtocol (VoIP)，可启动该图标进行语音聊天。
Like the rest of a Jazz component, a component's web UI is developed as an Eclipse plug-in that runs on the Jazz server.
与Jazz组件的其他部分一样，组件的WebUI被开发为在Jazz服务器上运行的Eclipse插件。
Depending on the extension point that it's extending, the plug-in can be anything from UI only, to no UI, and everything in between.
根据插件所扩展的扩展点不同，插件可以是从只有UI，到没有UI，以及介于两者之间的任何情况。
You'll see a real-world example of how to develop such a plug-in, considering API and user interface (UI) issues, and also how to evaluate alternative ways to bring desired functionality to a user.
您将看到一个现实世界中的例子，目的是说明如何在考虑到API和用户接口（UI）的情况下开发这类插件，以及如何评估可供选择的方法以给用户带来所需要的功能。
To demonstrate how you can use FIT in an Eclipse environment, I used the Extended FIT Eclipse plug-in, which provides a simple user interface (UI) for loading FIT input and output files.
为了演示如何在Eclipse环境中使用FIT，我使用了Extended FIT Eclipse插件，它提供了一个简单的用户界面 (UI)，用于加载 FIT输入和输出文件。
Open the plug-in editor of the UI project (double-click the plugin.xml) and go to the Extensions TAB.
打开UI项目的插件编辑器(双击plugin . xml)并切换至extensions项。
In the next window (shown in figure 7), deselect the plug-in option "This plug-in will make contributions to the UI."
在下一个窗口(如图7所示)中取消选择“Thisplug - inwillmake contributionsto the UI”。
You can now launch JUnit Plug-in tests in a non-UI thread.
你现可以在非ui线程中启动JunitPlug - in测试。
Notice that the option "This plug-in will make contributions to the UI" is selected.
请注意，应该选中选项“This plug - inwillmake contributions to the UI”。
In the Options area, clear the This plug-in will make contributions to the UI check box.
在Options区域，清除This plug - inwillmake contributions tothe UI复选框。
It is a carte Blanche request to the workbench UI to activate a plug-in once the workbench window is opened, bypassing the deferred load strategy.
当工作台窗口打开时它可以全权要求WorkbenchUI激活插件，而不受延迟加载策略限制。
Make sure that the option for "This plug-in will make contributions to the UI" is selected, and then click Finish.
确保选中 “This plug-inwillmake contributions totheUI” 选项，然后单击 Finish。
Deselect the "This plug-in will make contributions to the UI" option.
取消对“This plug - inwillmakecontributionstotheUI”选项的选定。
Deselect the "This plug-in will make contributions to the UI" option.
取消对“This plug - inwillmakecontributionstotheUI”选项的选定。
应用推荐