Themes and skins extension points.
主题和皮肤扩展点。
These extension points are basically programming interfaces.
这些扩展点是基本编程接口。
Extend the extension points needed for the desired functionality.
扩展目标功能所需的扩展点。
Think of extension points as events that cause a plug-in to be loaded.
可以把扩展点看作引发插件被装入的事件。
Plugin.xml, which defines the extension points to which it contributes
定义它所实现的扩展点
An example of using extension points in Eclipse is the Preferences window.
使用Eclipse中扩展点的一个示例是Preferences窗口。
This feature has proven very useful in leaving extension points in schemas.
该特性已被证实对于在模式中留下扩展点非常有用。
Three extension points are used to contribute to the tabbed properties view.
选项卡式属性视图使用了3个扩展点。
The concept of extension points is the key to understanding how Eclipse works.
扩展点的概念是理解eclipse工作原理的关键。
You can use defined extension points to customize the default themes and skins.
您可以使用定义的扩展点来自定义缺省的主题和皮肤。
The model of extension points in Eclipse is different from basic OSGi services.
Eclipse中扩展点的模型不同于基本的OSGi服务。
You contribute to three of these extension points to create the BuddyNote plug-in
您将添加其中三种扩展点来创建BuddyNote 插件
It also provides extension points for customizing how application state is managed.
它也提供了定制应用状态管理的扩展点。
Provides links to collaboratively built dynamic contents from these extension points.
提供链接，以协作方式从这些扩展点构建动态内容。
The plug-in manifest captures which LPEX extension points your client plug-in will use.
插件清单捕获客户端插件将使用哪些LPEX扩展点。
For the answer to these questions, select the extension points that your plug-in extends.
为了回答这些问题，请选择您的插件所扩展的扩展点。
Each dependency can have multiple extension points based on the functions they control.
每个依赖关系都具备多个扩展点，这些扩展点的基础就是其所控制的功能。
Extension points allow you to create menu items, toolbar buttons, panels and dialog boxes.
扩展接口允许你创建菜单项、工具条按钮、面板和对话框。
Like every other aspect of the Eclipse platform, builders are defined through extension points.
正如eclipse平台的其它各方面一样，构建器是通过扩展点定义的。
This is acceptable as long as the extension generator and handler extension points reflect this.
只要扩展生成器和处理程序扩展点反映这一点，就是可以接受的。
Bundle extension points are owned by the defining bundle; other bundles simply contribute to them.
绑定包扩展点由定义绑定包拥有；其他绑定包只对这些点做贡献。
However, as an analogy: extension points are like electrical sockets and extensions are like plugs.
但是，打个比方的话：所谓的扩展点就像是一个用电的插座而扩展就是那个插头。
Developers can define their own extension points and that in turn creates a new custom metadata tag.
开发者可以定义自己的扩展点，这些扩展点会创建新的客户化元数据标签。
Wildcards play a key role in defining extension points in schemas, and are the focus of this article.
通配符在定义模式中的扩展点方面扮演着重要角色，是本文关注的焦点。
Plug-ins can define extension points, well-defined places where other plug-ins can add functionality.
插件可以定义扩展点、定义良好的位置，其他插件可以在这些位置添加功能。
You can also quickly see and query the available extension and extension points for these plug-ins too.
你还能很快看到并查询这些插件的可用扩展及扩展点。
Extension points are defined on host plug-ins, whereas extensions are declared by the extender plug-ins.
扩展点是在主插件上定义的，而扩展是由扩展器插件声明的。
This article explains some of these artifacts through examples and relevant listings of extension points.
本文通过一些示例和相关扩展点列表解释了其中一些工件。
Now this is only an example and using extension points for this concept is probably not the best approach.
现在这只是一个示例，并且使用针对此概念的扩展点可能不是最好的方法。
Where the static method is rendered in HTML, these extension points are hyperlinks from inside the method.
静态方法以HTML形式呈现，这些扩展点是方法内部的超链接。
应用推荐