blob: faef14aacd67eee297bd60618b905153d8322618 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<?NLS TYPE="org.eclipse.help.contexts"?>
<contexts>
<!-- Actions -->
<context id="open_manifest">
<description>This action opens the manifest files contained in the selected plug-in project(s).</description>
</context>
<context id="organize_manifest">
<description>This action organizes and cleans up the manifest files contained in the selected plug-in project(s).</description>
<topic label="Organizing Manifest Files" href="guide/tools/pde_actions/organize_manifests.htm"/>
</context>
<context id="update_classpath">
<description>PDE computes the classpath of this project by looking for dependencies in the workspace and enabled external plug-ins and fragments.</description>
<topic label="Updating Classpaths" href="guide/tools/pde_actions/update_classpaths.htm"/>
</context>
<context id="open_dependencies">
<description>This command opens the Dependencies view to show all the plug-ins needed to run the selected plug-in.</description>
<topic label="Dependencies page" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
</context>
<context id="find_references">
<description>This command searches for all the plug-ins that directly depend on the selected plug-in and all the fragments which target it.</description>
<topic label="Dependencies page" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
<topic href="concepts/fragment.htm" label="Fragments"/>
</context>
<context id="create_plugin_jars">
<description>This command builds an Ant script which can then be used to build an executable version of the plug-in.</description>
<topic href="guide/tools/export_wizards/export_plugins.htm" label="Export plug-in"/>
<topic label="Build configuration" href="guide/tools/editors/manifest_editor/build.htm"/>
<topic label="Deploying a plug-in" href="tasks/ui_export_install_into_host.htm"/>
</context>
<context id="create_fragment_jars">
<description>This command builds an Ant script which can then be used to build an executable version of the fragment.</description>
<topic label="Generating Ant Scripts" href="tasks/pde_feature_generating_ant.htm"/>
<topic label="Build configuration" href="guide/tools/editors/manifest_editor/build.htm"/>
<topic label="Deploying a plug-in" href="tasks/ui_export_install_into_host.htm"/>
</context>
<context id="create_feature_jars">
<description>This command builds an Ant script which can then be used to build a feature.</description>
<topic label="Features" href="concepts/feature.htm"/>
<topic label="Build configuration" href="guide/tools/editors/manifest_editor/build.htm"/>
</context>
<context id="migrate_action">
<description>This command migrates Eclipse 3.4 plug-ins and fragments to comply with Eclipse 3.5 guidelines.</description>
<topic label="FAQ" href="../org.eclipse.platform.doc.isv/porting/3.5/faq.html" />
<topic label="Incompatibilities" href="../org.eclipse.platform.doc.isv/porting/3.5/incompatibilities.html" />
<topic href="../org.eclipse.platform.doc.isv/porting/3.5/recommended.html" label="Recommended"/>
</context>
<context id="image_browser_view">
<description>The Plug-in Image Browser view displays information about images found in plug-ins in the target platform, running application or workspace.</description>
<topic href="guide/tools/views/image_browser_view.htm" label="Plug-in Image Browser"/>
</context>
<context id="build_site">
<description>This command builds all the features and plug-ins contained in this site.</description>
<topic href="concepts/update_site.htm" label="Update Site"/>
<topic label="Update Site Editor" href="guide/tools/editors/site_editor/site_editor.htm"/>
<topic label="Building plug-ins and features using update site editor" href="guide/tools/project_wizards/new_update_site_project.htm"/>
</context>
<context id="preview_schema">
<description>This command transforms and renders the schema into HTML format.</description>
<topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
<topic label="Creating an extension point schema" href="guide/tools/editors/manifest_editor/extension_points.htm"/>
<topic label="Extension point schema editor" href="guide/tools/editors/schema_editor/editor.htm"/>
</context>
<context id="history_action">
<description>Choose this previously shown plug-in dependency, to open it again.</description>
</context>
<context id="history_list_action">
<description>Choose to open a dialog with all previously shown plug-in dependencies.</description>
</context>
<context id="target_export_wizard">
<description>Use this wizard to export the contents of the current target platform to a directory. All plug-ins included in the target platform will be copied to the destination directory.</description>
<topic href="guide/tools/export_wizards/export_target.htm" label="Target Export"/>
</context>
<!-- Dialogs -->
<context id="fragment_add_target">
<description>This wizard allows you to select the target plug-in for your fragment.</description>
<topic href="concepts/fragment.htm" label="Fragment"/>
<topic label="Fragment Project" href="guide/tools/project_wizards/new_fragment_project.htm"/>
<topic href="guide/tools/project_wizards/fragment_content.htm" label="Fragment Content"/>
<topic href="guide/tools/project_wizards/fragment_structure.htm" label="Fragment Structure"/>
</context>
<context id="schema_type_restriction">
<description>This wizard allows you to define the possible values for the selected attribute.</description>
<topic label="Extension point schema" href="guide/tools/editors/manifest_editor/extension_points.htm"/>
<topic label="Extension point schema editor" href="guide/tools/editors/schema_editor/editor.htm"/>
<topic label="Extension point schema definition page" href="guide/tools/editors/schema_editor/page_schema_definition.htm"/>
<topic label="Extension point schema overview page" href="guide/tools/editors/schema_editor/page_schema_overview.htm"/>
</context>
<context id="new_restriction_dialog">
<description>This wizard allows you to define a new possible value for the selected attribute.</description>
<topic label="Extension point schema" href="guide/tools/editors/manifest_editor/extension_points.htm"/>
<topic label="Extension point schema editor" href="guide/tools/editors/schema_editor/editor.htm"/>
<topic label="Extension point schema definition page" href="guide/tools/editors/schema_editor/page_schema_definition.htm"/>
<topic label="Extension point schema overview page" href="guide/tools/editors/schema_editor/page_schema_overview.htm"/>
</context>
<context id="filtered_schema_attribute_selection_dialog">
<description>This dialog allows you to select which attribute of which extension point the current identifier will be based on.</description>
<topic label="Extension point schema" href="guide/tools/editors/manifest_editor/extension_points.htm"/>
<topic label="Extension point schema editor" href="guide/tools/editors/schema_editor/editor.htm"/>
<topic label="Extension point schema definition page" href="guide/tools/editors/schema_editor/page_schema_definition.htm"/>
<topic label="Extension point schema overview page" href="guide/tools/editors/schema_editor/page_schema_overview.htm"/>
</context>
<context id="search_page">
<description>On this page, you can search for references to and declarations of plug-ins, fragments and extension points.
The search can be extended beyond workspace resources to include external plug-ins. </description>
</context>
<context id="plugin_selection">
<description>This dialog allows you to select a plug-in.</description>
<topic href="concepts/plugin.htm" label="Plug-in"/>
</context>
<context id="feature_selection">
<description>This dialog allows you to select a feature by typing either a feature ID, or a plug-in ID.
If a plug-in ID is entered, then all features containing matching plug-ins will be revealed.
Wildcards '?' and '*' are supported. </description>
<topic href="concepts/feature.htm" label="Feature"/>
</context>
<context id="product_configuration_selection">
<description>This dialog allows you to select a product configuration to export.</description>
<topic label="Product Export" href="guide/tools/export_wizards/export_product.htm"/>
</context>
<context id="execution_environment_selection">
<description>This dialog allows you to select one or more execution environment.</description>
<topic label="Plug-in Overview" href="guide/tools/editors/manifest_editor/overview.htm"/>
</context>
<context id="import_packages">
<description>This dialog allows you to add one or more packages to the list of packages imported by your bundle.</description>
<topic label="Dependencies" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
</context>
<context id="imported_package_properties">
<description>This dialog allows you to specify version rules, and whether the dependency on the selected package is optional or not.</description>
<topic label="Dependencies" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
</context>
<context id="export_packages">
<description>This dialog allows you to add one or more packages to the list of packages exported by your bundle.</description>
<topic label="Runtime" href="guide/tools/editors/manifest_editor/runtime.htm" />
</context>
<context id="package_selection">
<description>This dialog allows you to select one or more packages to export.</description>
<topic label="Runtime" href="guide/tools/editors/manifest_editor/runtime.htm" />
</context>
<context id="exported_package_properties">
<description>This dialog allows you to declare a version number for the selected package.</description>
<topic label="Runtime" href="guide/tools/editors/manifest_editor/runtime.htm" />
</context>
<context id="imported_plugin_properties">
<description>This dialog allows you to edit the properties of a plug-in dependency.</description>
<topic label="Dependencies" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
</context>
<context id="browse_extension_points_schemas">
<description>This dialog lists all the extension points schema defined in the current plug-in project.</description>
<topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
<topic label="Extension point schema" href="guide/tools/file_wizards/new_schema.htm"/>
</context>
<context id="container_selection">
<description>This dialog allows you to select the project or folder in which you want to store your extension point schema.</description>
<topic label="Extension point schema" href="guide/tools/file_wizards/new_schema.htm"/>
</context>
<context id="jar_selection">
<description>This dialog allows you to select a JAR archive to add to your library plug-in.</description>
</context>
<context id="add_library">
<description>This dialog allows you to select a library or a folder of your plug-in project and add it to your plug-in classpath.</description>
<topic label="Runtime" href="guide/tools/editors/manifest_editor/runtime.htm#classpath" />
</context>
<context id="new_library">
<description>This dialog allows you to declare a new library to add to your plug-in classpath.</description>
<topic label="Runtime" href="guide/tools/editors/manifest_editor/runtime.htm#classpath" />
</context>
<context id="unused_imports_dialog">
<description>This dialog lists every unused or redundant entry in the list of required plug-ins and imported packages, and offers to remove them.</description>
<topic label="Plug-in dependencies" href="guide/tools/editors/manifest_editor/dependencies.htm" />
<topic label="Dependency analysis" href="guide/tools/editors/manifest_editor/dependencies.htm#dependency_analysis" />
</context>
<context id="launcher_application_selection">
<description>This dialog allows you to select an application to launch.</description>
<topic label="Eclipse Application Launcher" href="guide/tools/launchers/eclipse_application_launcher.htm" />
</context>
<context id="command_composer_dialog">
<description>This dialog allows you to select an executable command among the ones of your development environment.
If the selected command has parameters, you are able to edit their values.</description>
<topic label="Simple Cheat Sheet Editor" href="guide/tools/editors/simple_cs_editor/editor.htm" />
<topic label="Command Section" href="guide/tools/editors/simple_cs_editor/section_command-details.htm" />
</context>
<context id="loop_dialog">
<description>This dialog lists all the cycles detected in the dependency graph of the selected plug-in.</description>
<topic label="Plug-in dependencies" href="guide/tools/editors/manifest_editor/dependencies.htm" />
</context>
<context id="rename_dialog">
<description>This dialog allows you to rename the selected element.</description>
</context>
<context id="new_cs_category_name_dialog">
<description>This dialog allows you to create a new problem domain category for the cheat sheet being registered.</description>
<topic label="Register Cheat Sheet Wizard" href="guide/tools/editors/simple_cs_editor/wizard_register-cheat-sheet.htm" />
</context>
<context id="plugin_import_finish_dialog">
<description>This dialog shows a list of plug-ins for which import was not possible (probably because they already exist in read-only projects of your workspace).</description>
</context>
<context id="plugin_import_overwrite_dialog">
<description>This dialog opens when one or more plug-ins being imported already exist in the workspace. Any projects that are checked in this dialog will be deleted when finish is pressed. The imported plug-ins will use their id as the project name, but if a project with that name exists in the workspace a new project name that includes the version will be used.</description>
</context>
<context id="spy_dialog">
<description>This dialog, called the "Plug-in Spy", allows you to introspect your environment and retrieve information about your current context (active page, active selection, ...).</description>
</context>
<context id="filtered_plugin_artifacts_dialog">
<description>This dialog lists every plug-in, extension, extension point and exported package accessible in your development environment.
You can select any item to open it in an editor.</description>
</context>
<!-- START: Launchers -->
<context id="launcher_basic">
<description>This page allows you to set the basic program arguments to run the configuration.</description>
<topic label="Eclipse Application Launcher Main Tab"
href="guide/tools/launchers/eclipse_main.htm"/>
<!-- Note: This context ID is shared between the Eclipse Application Launcher Main tab
and JUnit Plug-in Test Launcher Main tab. Limitation at this point which
may cause confusion
-->
</context>
<context id="launcher_advanced">
<description>This page allows you to run your configuration with only a subset of the plug-ins.</description>
<topic label="Eclipse Application Launcher Plug-ins Tab"
href="guide/tools/launchers/plugins.htm"/>
<!-- Note: This context ID is shared between the Eclipse Application Launcher Plug-ins tab
and Equinox OSGi Framework Launcher Plug-ins tab. Limitation at this point which
may cause confusion
-->
</context>
<context id="launcher_tracing">
<description>This page allows you to use tracing flags that will cause tracing information to be printed to the standard output (or the console view) when you run the configuration.</description>
<topic label="Launcher Tracing Tab"
href="guide/tools/launchers/tracing.htm"/>
<!-- Note: Shared context ID between all Launchers that have a Tracing Tab -->
</context>
<context id="launcher_configuration">
<description>This page allows you to specify the plug-ins that are to be automatically installed, and optionally started, by the runtime.</description>
<topic label="Eclipse Application Launcher Configuration Tab"
href="guide/tools/launchers/configuration.htm"/>
<!-- Note: This context ID is shared between the Eclipse Application Launcher Configuration tab
and JUnit Plug-in Test Launcher Configuration tab. Limitation at this point which
may cause confusion
-->
</context>
<context id="plugin_status_dialog">
<description>This dialog lists every unresolvable plug-in in your launch configuration, and the corresponding unsatisfied constraint(s).</description>
<topic label="Eclipse Application Launcher" href="guide/tools/launchers/eclipse_application_launcher.htm" />
</context>
<!-- END: Launchers -->
<context id="history_list_dialog">
<description>A dialog for re-opening previously viewed plug-in dependencies.</description>
</context>
<!-- START: Editors -->
<!-- Plugin Manifest Editor -->
<context id="manifest_source_page">
<description>This page allows you to edit the file content directly.</description>
</context>
<context id="manifest_plugin_overview">
<description>The Overview page shows you the plug-in at a glance.</description>
<topic href="concepts/plugin.htm" label="Plug-in"/>
<topic label="Plug-in Overview" href="guide/tools/editors/manifest_editor/overview.htm"/>
</context>
<context id="manifest_plugin_dependencies">
<description>The Dependencies page shows the dependencies that your plug-in has on other plug-ins.</description>
<topic label="Dependencies" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
</context>
<context id="manifest_plugin_runtime">
<description>The Runtime page shows information about the plug-in's runtime libraries. This includes the plug-in classpath (if resources are not at the root of the plug-in) as well as what packages the plug-in exports. Visibility restrictions can be set on the exported packages to limit usage by downstream users.</description>
<topic label="Runtime" href="guide/tools/editors/manifest_editor/runtime.htm" />
</context>
<context id="manifest_plugin_extensions">
<description>The Extensions page shows all the extensions used by your plug-in.</description>
<topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
<topic label="Extensions" href="guide/tools/editors/manifest_editor/extensions.htm" />
</context>
<context id="manifest_plugin_ext_points">
<description>The Extension points page shows all the extension points declared by the plug-in.</description>
<topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
<topic label="Extension Points" href="guide/tools/editors/manifest_editor/extension_points.htm" />
</context>
<context id="manifest_fragment_overview">
<description>The Overview page shows you the fragment at a glance.</description>
<topic label="Plug-in Overview" href="guide/tools/editors/manifest_editor/overview.htm"/>
</context>
<context id="manifest_fragment_dependencies">
<description>The Dependencies page shows the dependencies that your fragment has on other plug-ins.</description>
<topic label="Dependencies" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
</context>
<context id="manifest_fragment_runtime">
<description>The Runtime page shows information about the fragment's runtime libraries.</description>
<topic label="Runtime" href="guide/tools/editors/manifest_editor/runtime.htm" />
</context>
<context id="manifest_fragment_extensions">
<description>The Extensions page shows all the extensions used by your fragment.</description>
<topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
<topic label="Extensions" href="guide/tools/editors/manifest_editor/extensions.htm" />
</context>
<context id="manifest_fragment_ext_points">
<description>The Extension points page shows all the extension points declared by the fragment.</description>
<topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
<topic label="Extension Points" href="guide/tools/editors/manifest_editor/extension_points.htm" />
</context>
<context id="build_page">
<description>This editor is used to edit the build configuration for a plug-in, fragment or a feature.</description>
<topic label="Build" href="guide/tools/editors/manifest_editor/build.htm"/>
</context>
<context id="build_add_library_dialog">
<description>This dialog allows you to add a new library to build. You can either select a library already declared in your plug-in classpath, or declare a new library.</description>
<topic label="Build" href="guide/tools/editors/manifest_editor/build.htm"/>
</context>
<context id="folder_add_selection">
<description>This dialog allows you to add a new source folder for the selected library. The content of this folder will be compiled into the library.</description>
<topic label="Build" href="guide/tools/editors/manifest_editor/build.htm"/>
</context>
<!-- Extension Point Schema Editor -->
<context id="schema_editor_main">
<description>This editor creates a schema for an extension point, to which all extensions extending this point must conform.</description>
<topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
<topic label="Extension point schema" href="guide/tools/editors/manifest_editor/extension_points.htm"/>
<topic label="Extension point schema editor" href="guide/tools/editors/schema_editor/editor.htm"/>
<topic label="Extension Point schema definition page" href="guide/tools/editors/schema_editor/page_schema_definition.htm"/>
<topic label="Extension Point schema overview page" href="guide/tools/editors/schema_editor/page_schema_overview.htm"/>
</context>
<context id="schema_editor_doc">
<description>Documentation for the use of this extension point is entered on this page.</description>
<topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
<topic label="Extension point schema" href="guide/tools/editors/manifest_editor/extension_points.htm"/>
<topic label="Extension point schema editor" href="guide/tools/editors/schema_editor/editor.htm"/>
<topic label="Extension Point schema definition page" href="guide/tools/editors/schema_editor/page_schema_definition.htm"/>
<topic label="Extension Point schema overview page" href="guide/tools/editors/schema_editor/page_schema_overview.htm"/>
</context>
<!-- Feature Editor -->
<context id="manifest_feature_overview">
<description>This page shows general information about the feature.</description>
<topic label="Feature Overview" href="guide/tools/editors/feature_editor/overview.htm"/>
</context>
<context id="manifest_feature_info">
<description>This page is used to edit the required description, license and copyright information.</description>
<topic label="Feature Information" href="guide/tools/editors/feature_editor/information.htm"/>
</context>
<context id="manifest_feature_content">
<description>This page shows the list of plug-ins and fragments that are included in the feature.</description>
<topic label="Included Plug-ins" href="guide/tools/editors/feature_editor/plugins.htm"/>
</context>
<context id="manifest_feature_advanced">
<description>This page lists all features included in this feature</description>
<topic label="Included Features" href="guide/tools/editors/feature_editor/included_features.htm"/>
</context>
<context id="manifest_feature_dependencies">
<description>This page lists all plug-ins and features that need to be installed before installing this feature. </description>
<topic label="Feature Dependencies" href="guide/tools/editors/feature_editor/dependencies.htm"/>
</context>
<context id="manifest_feature_installation">
<description>This page details installation options</description>
<topic label="Feature Installation" href="guide/tools/editors/feature_editor/installation.htm"/>
</context>
<context id="feature_synchronize_versions">
<description>The versions of the plug-ins and fragments should be synchronized with that of the packaged feature.</description>
<topic label="Feature Overview" href="guide/tools/editors/feature_editor/overview.htm"/>
</context>
<!-- Site Editor -->
<context id="manifest_site_overview" >
<description>This page shows the general information about the update site.</description>
<topic label="Setting up an update site project" href="guide/tools/project_wizards/new_update_site_project.htm"/>
<topic label="Building plug-ins and features using update site editor" href="guide/tools/editors/site_editor/site_editor.htm"/>
</context>
<context id="manifest_site_build">
<description>This page allows you to configure how this site will be built from features and plug-ins in the workspace.</description>
<topic label="Setting up an update site project" href="guide/tools/project_wizards/new_update_site_project.htm"/>
<topic label="Building plug-ins and features using update site editor" href="guide/tools/editors/site_editor/site_editor.htm"/>
</context>
<context id="manifest_site_features">
<description>This page lists all the features visible to the user when connecting to this site.</description>
<topic label="Setting up an update site project" href="guide/tools/project_wizards/new_update_site_project.htm"/>
<topic label="Building plug-ins and features using update site editor" href="guide/tools/editors/site_editor/site_editor.htm"/>
</context>
<context id="manifest_site_archives">
<description>This page lists all the archive mappings in this site.</description>
<topic label="Setting up an update site project" href="guide/tools/project_wizards/new_update_site_project.htm"/>
<topic label="Building plug-ins and features using update site editor" href="guide/tools/editors/site_editor/site_editor.htm"/>
</context>
<!-- Product Editor -->
<context id="overview_page">
<description>This page allows you to specify general information about the product, as well as test and export it.</description>
<topic href="concepts/product.htm" label="Product"/>
<topic label="Product Overview Page" href="guide/tools/editors/product_editor/overview.htm"/>
</context>
<context id="configuration_page">
<description>Select plug-ins or features belonging to the product. Optionally specify custom config.ini file, or program arguments.</description>
<topic label="Product Configuration Page" href="guide/tools/editors/product_editor/configuration.htm"/>
</context>
<context id="launching_page">
<description>Information on this page controls the native launcher properties and arguments for the product.</description>
<topic label="Product Launching Page" href="guide/tools/editors/product_editor/launching.htm"/>
</context>
<context id="branding_page">
<description>Information on this page controls branding of the product.</description>
<topic label="Product Branding Page" href="guide/tools/editors/product_editor/branding.htm"/>
</context>
<context id="splash_page">
<description>This page allows you to create and customize a splash screen for the product.</description>
<topic label="Product Splash Page" href="guide/tools/editors/product_editor/splash.htm"/>
</context>
<!-- Simple Cheat Sheet Editor -->
<context id="simple_cs_editor">
<description>This editor allows you to compose a simple cheat sheet, which presents a set of steps to help the user complete a certain task.</description>
<topic label="Simple Cheat Sheet Editor" href="guide/tools/editors/simple_cs_editor/editor.htm"/>
</context>
<!-- Composite Cheat Sheet Editor -->
<context id="composite_cs_editor">
<description>This editor allows you to compose a composite cheat sheet, which presents a set of tasks (represented by simple cheat sheets) to help the user achieve an overarching goal.</description>
<topic label="Composite Cheat Sheet Editor" href="guide/tools/editors/composite_cs_editor/editor.htm"/>
</context>
<!-- Register Cheat Sheet Wizard -->
<context id="register_cs">
<description>This wizard allows you to register a simple or composite cheat sheet with the Eclipse workbench to make it accessible through the Help menu.</description>
<topic label="Register Cheat Sheet Wizard" href="guide/tools/editors/simple_cs_editor/wizard_register-cheat-sheet.htm"/>
</context>
<!-- Category Editor -->
<context id="category_editor">
<description>This editor is used to modify category definition files that are used to generate categories when exporting.</description>
<topic label="Category Editor" href="guide/tools/editors/category_editor/definition_page.htm"/>
<topic label="New Category Definition" href="guide/tools/file_wizards/new_category.htm"/>
<topic label="Feature Export" href="guide/tools/export_wizards/export_features.htm"/>
</context>
<context id="category_file_page">
<description>This wizard allows you to create a new category file used to generate categories when exporting.</description>
<topic label="New Category Definition" href="guide/tools/file_wizards/new_category.htm"/>
<topic label="Category Editor" href="guide/tools/editors/category_editor/definition_page.htm"/>
<topic label="Feature Export" href="guide/tools/export_wizards/export_features.htm"/>
</context>
<!-- Table of Contents Editor -->
<context id="toc_editor">
<description>This editor creates a Help table of contents, which allows you to organize how documentation is displayed to users of an Eclipse product.</description>
<topic label="Table of Contents Editor" href="guide/tools/editors/toc_editor/editor.htm"/>
</context>
<context id="register_toc">
<description>This wizard allows you to register a Help table of contents with the project's plugin.xml file.</description>
<topic href="guide/tools/editors/toc_editor/editor.htm" label="Table of Contents Editor"/>
</context>
<context id="target_editor" title="Target Definition Editor">
<description>The Target Definition Editor is used to edit target definition files in the workspace, which should end with the extension &quot;.target&quot;. Target definition files can be created using the New Target Definition Wizard or by moving them to the workspace on the Target Platform Preference Page.</description>
<topic href="guide/tools/editors/target_editor/target_editor.htm" label="Target Definition Editor"/>
<topic href="guide/tools/editors/target_editor/definition_page.htm" label="Target Definition Editor Definition Page"/>
<topic href="guide/tools/editors/target_editor/content_page.htm" label="Target Definition Editor Content Page"/>
<topic href="guide/tools/editors/target_editor/environment_page.htm" label="Target Definition Editor Environment Page"/>
<topic href="concepts/target.htm" label="Target Platform"/>
</context>
<!-- Children of the PDEFormPage -->
<!-- PLACE HOLDER -->
<context id="target_editor_environment_page" title="Target Definition Editor Environment Page">
<description>The Enviroment Page in the Target Definition Editor is used to edit many settings in the definition affecting how the target will be compiled and run.</description>
</context>
<!-- PLACE HOLDER -->
<context id="target_editor_definition_page" title="Target Definition Editor Definition Page">
<description>The Definition Page in the Target Definition Editor is used to edit the most important settings in a target definition file. The Target Name is used to display your targets on the Target Platform Preference Page. The Locations section is used to add locations that contain plug-ins and works the same as the Location Tab on the Edit Target Wizard.</description>
</context>
<context id="target_editor_content_page" title="Target Definition Editor Content Page">
<description>The Content Page in the Target Definition Editor is used to view and edit the set of plug-ins to be included in the target definition when set as the active target platform. The definition must contain one or more locations containing plug-ins and the definition must be resolved to edit the content. Only the plug-ins that are checked on this page will be included in the target. There are multiple options available to filter and sort the list to quickly check what you require.</description>
</context>
<!-- END: Editors -->
<!-- end Children of the PDEFormPage -->
<!-- START: Preference pages -->
<!-- Plug-in Development -->
<!-- one to one mapping -->
<context id="main_preference_page" >
<description>This page allows you to set Plug-in Development Environment general settings.</description>
<topic label="General Plug-in Development Preferences" href="guide/tools/preference_pages/plug_in_development.htm"/>
<topic label="PDE Preferences" href="guide/tools/preference_pages/preferences.htm"/>
</context>
<!-- Compilers -->
<!-- one to one mapping -->
<context id="compilers_preference_page" >
<description>This page allows you to specify the severity of reported errors and warnings in the manifest, plugin.xml and build.properties files.</description>
<topic label="Compilers Preferences" href="guide/tools/preference_pages/compilers.htm"/>
<topic label="Plug-in Compiler Preferences" href="guide/tools/preference_pages/plugin_compiler.htm"/>
<topic label="Extension Point Schema Compiler Preferences" href="guide/tools/preference_pages/schema_compiler.htm"/>
<topic label="Feature and Update Site Compiler Preferences" href="guide/tools/preference_pages/feature_compiler.htm"/>
<topic href="guide/tools/preference_pages/preferences.htm" label="PDE Preferences"/>
</context>
<!-- Editors -->
<!-- one to one mapping -->
<context id="editor_preference_page" >
<description>This page allows you to configure the behavior and presentation of PDE editors.</description>
<topic label="Editors Preferences" href="guide/tools/preference_pages/editors.htm"/>
<topic href="guide/tools/preference_pages/preferences.htm" label="PDE Preferences"/>
</context>
<!-- OSGi Frameworks -->
<!-- one to one mapping -->
<context id="osgi_preference_page" >
<description>This page allows you to manage the OSGi Framework settings.</description>
<topic label="OSGi Frameworks Preferences" href="guide/tools/preference_pages/osgi_frameworks.htm"/>
<topic href="guide/tools/preference_pages/preferences.htm" label="PDE Preferences"/>
</context>
<!-- Target Platform -->
<!-- one to one mapping -->
<context id="target_platform_preference_page" >
<description>This page allows you to manage a set of target definitions and select one as the active target platform. A target definition consists of a set of plug-ins and environment settings. The active target platform is used to build and launch your workspace plug-ins.</description>
<topic href="guide/tools/preference_pages/target_platform.htm" label="Target Platform Preferences"/>
<topic href="concepts/target.htm" label="Target Platform"/>
<topic href="guide/tools/target_shared/new_target_wizard.htm" label="New Target Wizard"/>
<topic href="guide/tools/target_shared/edit_target_wizard.htm" label="Edit Target Wizard"/>
<topic href="guide/tools/target_shared/move_target_wizard.htm" label="Move Target Wizard"/>
<topic href="guide/tools/editors/target_editor/target_editor.htm" label="Target Editor"/>
<topic href="guide/tools/preference_pages/preferences.htm" label="PDE Preferences"/>
</context>
<!-- END: Preference pages -->
<!-- Property pages -->
<context id="plugin_development_property_page">
<description>Parent property page for the other pde property pages. Allows you to modify how the manifest editor is displayed for your project.</description>
</context>
<context id="selfhosting_property_page">
<description>This page allows you to exclude certain class folders from the project's classpath.</description>
<topic href="guide/tools/preference_pages/runtime_classpath_properties.htm" label="Runtime Classpath"/>
</context>
<context id="compilers_property_page">
<description>This page allows you to specify the behavior of the various manifest compilers. The settings are identical to the Compilers Preference Page, but will only apply to a single project.</description>
<topic label="Plug-in Compiler Preferences" href="guide/tools/preference_pages/plugin_compiler.htm"/>
</context>
<!-- START: Views -->
<context id="plugins_view">
<description>The Plug-in View show the plug-ins and fragments that will be passed to the runtime workbench when running or debugging. If simple self-hosting is used, the view allows you to browse external plug-ins that are not part of the workspace.</description>
<topic label="Plug-ins" href="guide/tools/views/plugins.htm"/>
</context>
<context id="dependencies_view">
<description>The Dependencies view shows all the plug-ins required to run the selected plug-in.</description>
<topic label="Plug-in Dependencies" href="guide/tools/views/plugin_dependencies.htm"/>
</context>
<context id="registry_view">
<description>The Plug-in Registry view shows a read-only view of the plug-in registry of the running platform.</description>
<topic label="Plug-in Registry" href="guide/tools/views/plugin_registry.htm"/>
</context>
<!-- END: Views -->
<!-- Wizard pages -->
<!-- PLACE HOLDER -->
<context id="externalize_strings_page">
<description>This page allows you to extract translatable strings and store them in a properties file for multi-language support.</description>
<topic label="Externalizing Strings" href="guide/tools/pde_actions/externalize_strings.htm"/>
</context>
<!-- PLACE HOLDER -->
<context id="xhtml_conversion_page">
<description>This page allows you to convert existing help files into XHTML</description>
</context>
<!-- PLACE HOLDER -->
<context id="convert_preferences_page">
<description>This page allows you to convert preferences from an Eclipse Preferences (*.epf) file into plugin_customization file settings.</description>
</context>
<!-- START: New Project Creation Wizard pages -->
<!-- New Plug-in Project -->
<context id="new_project_structure_page">
<description>This wizard helps you create a new plug-in project. If the plug-in is to contain resources only, create a simple project. Otherwise, create a Java project.</description>
<topic label="Plug-in Project Structure"
href="guide/tools/project_wizards/plugin_structure.htm"/>
</context>
<context id="new_project_required_data">
<description>Data entered on this page is used to customize the generated manifest file and top level plug-in Java class.</description>
<topic label="Plug-in Content"
href="guide/tools/project_wizards/plugin_content.htm"/>
</context>
<context id="new_project_code_gen_page">
<description>For a quick start, use the code generation wizards to create a plug-in project containing a working extension. You can customize a plug-in to contain any combination of the available extension templates by choosing the 'Custom Plug-in Wizard' option.</description>
<topic label="Templates"
href="guide/tools/project_wizards/plugin_templates.htm"/>
</context>
<!-- New Fragment Project -->
<context id="new_fragment_structure_page">
<description>This wizard helps you create a new fragment project. If the fragment is to contain resources only, create a simple project. Otherwise, create a Java project.</description>
<topic label="Fragment Project Structure"
href="guide/tools/project_wizards/fragment_structure.htm"/>
</context>
<context id="new_fragment_required_data">
<description>This page specifies the fragment's target plug-in and other data required to generate the fragment's manifest file.</description>
<topic label="Fragment Content"
href="guide/tools/project_wizards/fragment_content.htm"/>
</context>
<!-- Plug-in From Existing JAR Archives Project -->
<context id="new_library_plugin_jar_page">
<description>This wizard helps you create a new plug-in project from existing JAR archives. Use this page to specify archives to be included in the plug-in. The buttons allow adding JAR archives from the workspace or the file system.</description>
<topic label="Plug-in From Existing JAR Archives"
href="guide/tools/project_wizards/plugin_from_archives.htm"/>
</context>
<context id="new_library_plugin_structure_page">
<description>This wizard helps you create a new plug-in project from existing JAR archives. Data entered on this page is used to customize the generated manifest file.</description>
<topic label="Plug-in From Existing JAR Archives"
href="guide/tools/project_wizards/plugin_from_archives.htm"/>
</context>
<context id="new_feature_main">
<description>This wizard creates a new feature project that can be used to package plug-ins.</description>
<topic label="Features" href="concepts/feature.htm"/>
<topic label="Setting up a feature project" href="guide/tools/project_wizards/new_feature_project.htm"/>
<topic href="guide/tools/editors/feature_editor/feature_editor.htm" label="Feature editor"/>
</context>
<!-- New Feature Project -->
<context id="new_feature_data">
<description>This page specifies basic data about the feature.</description>
<topic label="Feature Project"
href="guide/tools/project_wizards/new_feature_project.htm"/>
</context>
<context id="new_feature_referenced_plugins">
<description>The plug-ins and fragments selected on this page will be packaged in the feature.</description>
<topic label="Feature Project"
href="guide/tools/project_wizards/new_feature_project.htm"/>
</context>
<!-- New Feature Patch -->
<context id="new_patch_main">
<description>This wizard creates a patch to an existing feature.</description>
<topic label="Features" href="concepts/feature.htm"/>
<topic label="Setting up a feature project" href="guide/tools/project_wizards/new_feature_project.htm"/>
</context>
<context id="new_patch_data">
<description>This page specifies basic data about the patch and the feature it targets.</description>
<topic label="Feature Patch"
href="guide/tools/project_wizards/new_feature_patch.htm"/>
</context>
<context id="new_patch_referenced_plugins">
<description>The plug-ins and fragments selected on this page will be packaged in the patch.</description>
<topic label="Features" href="concepts/feature.htm"/>
<topic label="Setting up a feature project" href="guide/tools/project_wizards/new_feature_project.htm"/>
</context>
<!-- New Update Site Project -->
<context id="new_site_main">
<description>This wizard creates an update site project where you can publish features for the Update Manager to find.</description>
<topic label="Update Site Project"
href="guide/tools/project_wizards/new_update_site_project.htm"/>
</context>
<!-- END: New Project Creation Wizard pages -->
<!-- START: New File Creation Wizard pages -->
<!-- New Extension Point Schema -->
<context id="new_schema">
<description>All extensions that extend the specified extension point will be validated against this schema.</description>
<topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
<topic label="Extension point schema" href="guide/tools/editors/schema_editor/editor.htm"/>
<topic href="guide/tools/editors/manifest_editor/extension_points.htm" label="Extension Points Page"/>
</context>
<!-- New Product Configuration -->
<context id="product_file_page">
<description>This page allows you to create a new product configuration and initialize its content.</description>
<topic label="Product Configuration"
href="guide/tools/file_wizards/new_product_config.htm"/>
</context>
<!-- New Cheat Sheet -->
<context id="cheat_sheet_page">
<description>This page allows you to create a new cheat sheet.</description>
<topic label="Cheat Sheet"
href="guide/tools/file_wizards/new_cheat_sheet.htm"/>
</context>
<!-- New Target Definition -->
<context id="target_definition_page">
<description>This page allows you to create a new target definition. A target definition specifies all aspects of a target - including its location, constituent plug-ins and environment.</description>
<topic label="Target Definition"
href="guide/tools/file_wizards/new_target_definition.htm"/>
</context>
<!-- New Table of Contents -->
<context id="toc_page">
<description>This page allows you to create a new table of contents.</description>
<topic label="Table of Contents" href="guide/tools/file_wizards/new_toc.htm"/>
</context>
<!-- New Context Help -->
<context id="new_context_help_page">
<description>This page allows you to create a new Context Help file.</description>
<topic label="Context Help" href="guide/tools/file_wizards/new_ctx_help.htm"/>
</context>
<!-- END: New File Creation Wizard pages -->
<context id="converted_projects">
<description>Select Java projects to which you want to add PDE capabilities.
If the selected project does not contain a manifest file, PDE will generate a generic one.</description>
<topic label="Converting existing projects" href="guide/tools/pde_actions/convert_projects.htm"/>
</context>
<context id="migrate_3_0">
<description>All pre-3.0 plug-ins must be migrated using this wizard to update their list of dependencies and add the 3.0 processing instruction.</description>
</context>
<!-- START: New Import Wizard pages -->
<!-- Plugins and Fragments -->
<context id="plugin_import_first_page">
<description>This wizard allows you to import plug-ins into the workspace. Plug-ins can be imported from the current target, any other target definition or a local directory. The next page of the wizard will allow you to choose which plug-ins to import. You can either select from a list of all plug-ins at the source location or select based on the requirements of plug-ins already in your workspace. Plug-ins can be imported in four different formats. Binary projects will contain the compiled plug-in code and will have attached source, but the source cannot be edited. Binary projects with linked content will use linked files instead of copying the plug-in contents into the project. Projects with source folders will attempt to extract source from the imported plug-in to make an editable project. Projects from a repository will look for a special entry in the plug-in manifest that specifies a repository (such as a CVS location) so that source can be checked out.</description>
<topic label="Plug-in Import"
href="guide/tools/import_wizards/import_plugins.htm"/>
</context>
<context id="plugin_import_second_page">
<description>This list shows the plug-ins and fragments found in the location specified on the previous page.</description>
<topic label="Plug-in Import"
href="guide/tools/import_wizards/import_plugins.htm"/>
</context>
<context id="plugin_import_express_page">
<description>For each one of the selected plug-ins, the wizard will import all its pre-requisites that do not already exist as shared projects in the workspace.</description>
<topic label="Plug-in Import"
href="guide/tools/import_wizards/import_plugins.htm"/>
</context>
<!-- Features -->
<context id="feature_import_first_page">
<description>This page defines the location from which the features will be imported into the workspace. This wizard should only be used in conjunction with feature-based self-hosting.</description>
<topic label="Feature Import"
href="guide/tools/import_wizards/import_wizards.htm"/>
</context>
<context id="feature_import_second_page">
<description>This list shows the features found in the location specified on the previous page.</description>
<topic label="Feature Import"
href="guide/tools/import_wizards/import_wizards.htm"/>
</context>
<!-- END: New Import Wizard pages -->
<context id="template_selection">
<description>Customize the plug-in by choosing one or more template extensions.</description>
</context>
<context id="template_editor">
<description>This template creates a sample XML editor with basic editing capabilities, syntax highlighting, etc.</description>
</context>
<context id="template_hello_world">
<description>This template creates a sample action set that adds a menu to the menu bar and a button to the toolbar.</description>
</context>
<context id="template_help">
<description>This template creates a sample Help Table of Contents.</description>
</context>
<context id="template_intro">
<description>This template creates a sample intro for product.</description>
</context>
<context id="template_multipage_editor">
<description>This template creates a multi-page editor that works on files with the chosen extension.</description>
</context>
<context id="template_new_wizard">
<description>This template creates a wizard that can create a new file in the workspace</description>
</context>
<context id="template_popup_menu">
<description>This template adds a popup menu to the specified target object.
The menu will appear in all views where an object of the specified type is selected.</description>
</context>
<context id="template_preference_page">
<description>This template creates a page that is contributed to the Preferences.</description>
</context>
<context id="template_property_page">
<description>This template adds a property page to a resource that matches the specified filter, and will appear in the Properties dialog for that resource.</description>
</context>
<context id="template_view">
<description>This template creates a workbench view and is contributed to the Workbench by creating a category.</description>
</context>
<context id="template_universal_welcome">
<description>This template creates a contribution to the Universal Welcome in the section of your choice. For this to work, your product must use Universal Welcome.</description>
</context>
<context id="template_builder">
<description>This template creates an incremental project builder and a project nature. A popup action on the project configures or unconfigures the nature.</description>
</context>
<context id="manifest_add_dependencies">
<description>This wizard allows you to add plug-ins as dependencies to your plug-in.
Use the filter to accelerate your search for the plug-ins.</description>
<topic label="Dependencies page" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
<topic label="Creating a plug-in project" href="guide/tools/project_wizards/new_plugin_project.htm"/>
</context>
<context id="add_extensions_main">
<description>This wizard allows you to add an extension to one of the available extension points.
You can also create a working template extension from the list of available templates.</description>
<topic href="guide/tools/editors/manifest_editor/new_extension_wizard.htm" label="New Extension Wizard"/>
<topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
<topic href="guide/tools/editors/manifest_editor/extensions.htm" label="Extensions Page"/>
<topic label="Dependencies page" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
<topic label="Extension point schema" href="guide/tools/editors/schema_editor/editor.htm"/>
</context>
<context id="add_extensions_schema_based">
<description>This wizard allows you to extend one of the available extension points. To be able to extend an extension point, your plug-in has to import the plug-in where the point is declared.</description>
<topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
<topic href="guide/tools/editors/manifest_editor/new_extension_wizard.htm" label="New Extension Wizard"/>
<topic href="guide/tools/editors/manifest_editor/extensions.htm" label="Extensions Page"/>
<topic label="Dependencies page" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
<topic label="Extension point schema" href="guide/tools/editors/schema_editor/editor.htm"/>
</context>
<context id="project_selection_dialog">
<description>This dialog is used to select a plug-in project to configure specific settings for.</description>
<topic href="guide/tools/preference_pages/compilers.htm" label="Compilers Preferences"/>
<topic href="guide/tools/preference_pages/plugin_compiler.htm" label="Plug-in Compiler Preferences"/>
</context>
<context id="java_attribute_wizard_page">
<description>This wizard allows you to create a new Java class or select an existing one.</description>
</context>
<context id="feature_portability_wizard">
<description>This wizard allows you to add constraints to ensure that your feature is not installed or shown in a context that does not match these constraints.</description>
<topic label="Feature manifest editor" href="guide/tools/editors/feature_editor/feature_editor.htm"/>
</context>
<!-- START: Export Wizards -->
<context id="plugin_export_wizard" >
<description>This wizard builds and exports the selected plug-ins and/or fragments into the specified location.</description>
<topic label="Plug-in Export" href="guide/tools/export_wizards/export_plugins.htm"/>
<topic href="guide/tools/export_wizards/export_features.htm" label="Feature Export"/>
<topic href="tasks/ui_export_install_into_host.htm" label="Export and Install into Running Host"/>
</context>
<context id="feature_export_wizard">
<description>This wizard builds and exports the selected features and the associated plug-ins into the specified location.</description>
<topic label="Feature Export" href="guide/tools/export_wizards/export_features.htm"/>
<topic href="guide/tools/export_wizards/export_plugins.htm" label="Plug-in Export"/>
<topic href="tasks/ui_export_install_into_host.htm" label="Export and Install into Running Host"/>
</context>
<context id="product_export_wizard">
<description>This page allows you to export a product to a destination outside the Eclipse workspace</description>
<topic href="concepts/product.htm" label="Product"/>
<topic label="Product Export" href="guide/tools/export_wizards/export_product.htm"/>
</context>
<!-- END: Export Wizards -->
<context id="plugins_container_page">
<description>This page shows you the actual classpath entries that are managed by this dynamic classpath container. In case one of the library entries does not have source associated, you can add source by selecting 'Attach Source...' button.</description>
</context>
<!-- new help contents, need to be completed -->
<context id="advanced_plugin_export_page">
<description>This page allows signing the JARs for added security.
If present, the JNLP option allows generation of manifests for Java Web Start deployment.</description>
</context>
<context id="cross_platform_export_page">
<description>When exporting for multiple platforms, select the desired target platforms on this page. A directory will be created for each selection.</description>
</context>
<context id="library_plugin_jars">
<description>Add JAR archives to include in the new plug-in. JAR files can be imported from existing workspace projects, or external directories. </description>
</context>
<context id="plugin_working_set">
<description>Create a new working set by selecting plug-ins or fragments that will belong to it.</description>
</context>
<context id="product_definitions_wizard_page">
<description>This wizard creates a new product extension. A product must be assoicated with an application.</description>
<topic href="concepts/product.htm" label="Product"/>
</context>
<context id="project_names_page">
<description>Specify project name.</description>
</context>
<context id="required_plugins_container_page">
<description>The Plug-in Dependencies container is a read-only container managed by PDE. This page shows the classpath entries that the container resolves to for this particular plug-in project.</description>
<topic label="Access Restrictions" href="guide/tools/editors/manifest_editor/access_rules.htm"/>
</context>
<context id="review_page">
<description>Review details of the selected sample.</description>
</context>
<context id="selection_page">
<description>Select the samples to create.</description>
</context>
<!-- Wizards -->
<!-- Editor Outline -->
<context id="outline_sort_action">
<description>This action sorts elements in the Outline View.</description>
</context>
<!-- END Editor Outline -->
<context id="ctx_help_editor" title="Context Help Editor">
<description>This editor creates a context help XML file, which allows you to create and edit dynamic help entries.</description>
<topic href="guide/tools/editors/ctx_help_editor/ctx_help_editor.htm" label="Context Help Editor"/>
</context>
<!-- Target related contexts -->
<context id="target_platform_state" title="Target Platform State View">
<description>The Target Platform State view shows the current status of the resolver state in PDE.</description>
<topic href="guide/tools/views/target_platform_state.htm" label="Target Platform State View"/>
</context>
<context id="new_target_wizard" title="New Target Wizard">
<description>This wizard creates a new target definition that will be added to the Target Platform Preference Page. There are several options to initialize your target definition with data. The new target definition will be saved in the Eclipse preferences, to create a target definition in your workspace use the New Target Definition File Wizard.</description>
<topic href="guide/tools/target_shared/new_target_wizard.htm" label="New Target Wizard"/>
</context>
<context id="edit_target_wizard" title="Target Definition Wizard">
<description>This wizard is used to edit target definitions. It is opened when a target definition on the Target Platform Preference Page is edited or a new definition is created. This wizard provides the same functionality as the Target Editor.</description>
<topic href="guide/tools/target_shared/edit_target_wizard.htm" label="Edit Target Wizard"/>
<topic href="guide/tools/target_shared/edit_target_arguments_tab.htm" label="Argument Tab"/>
<topic href="guide/tools/target_shared/edit_target_content_tab.htm" label="Content Tab"/>
<topic href="guide/tools/target_shared/edit_target_environment_tab.htm" label="Environment Tab"/>
<topic href="guide/tools/target_shared/edit_target_implicit_tab.htm" label="Implicit Dependencies Tab"/>
<topic href="guide/tools/target_shared/edit_target_locations_tab.htm" label="Locations Tab"/>
</context>
<context id="edit_target_wizard_locations_tab" title="Target Definition Wizard Locations Tab">
<description>The Location Tab in the Edit Target Wizard is used to set the locations that provide the plug-ins included in the target definition. There are several types of locations, allowing for definitions to be constructed in different styles.</description>
</context>
<context id="edit_target_wizard_argument_tab" title="Target Definition Wizard Arguments Tab">
<description>The Arguments Tab in the Edit Target Wizard is used to set the default program and vm arguments for new PDE launch configurations.</description>
</context>
<context id="edit_target_wizard_content_tab" title="Target Definition Wizard Content Tab">
<description>The Content Tab in the Edit Target Wizard is used to set a subset of plug-ins to include in the target platform. The tab displays a list of all plug-ins available in the target definition&apos;s locations. Only the plug-ins checked on this tab will be included. There are multiple ways to organize and filter the list.</description>
</context>
<context id="edit_target_wizard_environment_tab" title="Target Definition Wizard Environment Tab">
<description>The Environment Tab in the Edit Target Wizard is used to set environment settings that affect how a target is compiled and run. The environment settings can also be edited on the Environment Page of the Target Editor.</description>
</context>
<context id="edit_target_wizard_implicit_tab" title="Target Definition Wizard Implicit Dependencies Tab">
<description>The Implicit Tab in the Edit Target Wizard is used to set the implicit dependencies of the target. Any plug-in marked as an implicit dependency will always be added as a required plug-in when PDE determines requirements. Implicit dependencies can also be edited on the Environment Page of the Target Editor.</description>
</context>
<context id="implicit_dependencies_selection_dialog" title="Implicit Dependencies Selection Dialog">
<description>The Implicit Dependencies Selection Dialog allows you to browse through the plug-ins in your target and add one or more of them as implicit dependencies.</description>
<topic href="guide/tools/target_shared/implicit_plugin_selection_dialog.htm" label="Implicit Dependencies Selection Dialog"/>
</context>
<context id="move_target_wizard" title="Move Target Wizard">
<description>This wizard moves a target definition stored in the Eclipse preferences to a file in the workspace. This wizard is accessed by pressing Move on the Target Platform Preference Page. You must choose a project or directory to create the file in and a filename. Target definition files must end in the file extension &quot;.target&quot;.</description>
<topic href="guide/tools/target_shared/move_target_wizard.htm" label="Move Target Definition"/>
</context>
<context id="import_arguments_dialog" title="Import Arguments">
<description>The Import Arguments dialog is used to copy the arguments used in installations in your target. Often, if you have an Eclipse installation in your target that requires certain vm arguments to launch, you will require the same arguments to launch.</description>
<topic href="guide/tools/target_shared/import_arguments_dialog.htm" label="Import Arguments"/>
</context>
<context id="add_location_wizard" title="Add Location Wizard">
<description>The Add Location Wizard is opened from the Location Tab or the Definition Page. It is used to add a new location to a target definition. On the first page you must select a type of location to add.</description>
<topic href="guide/tools/target_shared/location_add_wizard.htm" label="Add Location Wizard"/>
</context>
<context id="location_add_directory_wizard" title="Add Directory Location Wizard">
<description>The Directory Location Wizard is used to create and edit directory locations in target definitions.</description>
<topic href="guide/tools/target_shared/location_edit_directory_wizard.htm" label="Directory Location Wizard"/>
</context>
<context id="location_edit_directory_wizard" title="Edit Directory Location Wizard">
<description>The Directory Location Wizard is used to create and edit directory locations in target definitions.</description>
<topic href="guide/tools/target_shared/location_edit_directory_wizard.htm" label="Directory Location Wizard"/>
</context>
<context id="location_preview_wizard" title="Preview Contents">
<topic href="guide/tools/target_shared/location_preview.htm" label="Preview Location Contents"/>
</context>
<context id="location_add_feature_wizard" title="Add Feature Locations Wizard">
<description>The Add Feature Locations Wizard is opened from the Add Location Wizard. Select a folder containing features (it can also contain a folder called &quot;features&quot;). All features found in the directory will be adde to the list. Check the features you want to add to your target. When Finish is pressed locations will be added to your target for each selected feature. The plug-ins in the features will be added to your target.</description>
<topic href="guide/tools/target_shared/location_add_features_wizard.htm" label="Add Feature Locations Wizard"/>
</context>
<context id="location_edit_feature_wizard" title="Edit Feature Location Wizard">
<description>The Edit Feature Location Wizard allows you to view the details of a feature location in your target definition.</description>
<topic href="guide/tools/target_shared/location_edit_feature_wizard.htm" label="Edit Feature Location Wizard"/>
</context>
<context id="location_add_installation_wizard" title="Add Installation Location Wizard">
<description>The Installation Location Wizard is used to create and edit installation locations in target definitions.</description>
<topic href="guide/tools/target_shared/location_edit_installation_wizard.htm" label="Installation Location Wizard"/>
</context>
<context id="location_edit_installation_wizard" title="Edit Installation Location Wizard">
<description>The Installation Location Wizard is used to create and edit installation locations in target definitions.</description>
<topic href="guide/tools/target_shared/location_edit_installation_wizard.htm" label="Installation Location Wizard"/>
</context>
<context id="location_add_site_wizard" title="Add Software Site Location Wizard">
<description>The Software Site Location Wizard is used to create and edit software site locations in target definitions.</description>
<topic href="guide/tools/target_shared/location_edit_site_wizard.htm" label="Software Site Location Wizard"/>
</context>
<context id="location_edit_site_wizard" title="Edit Software Site Location Wizard">
<description>The Software Site Location Wizard is used to create and edit software site locations in target definitions.</description>
<topic href="guide/tools/target_shared/location_edit_site_wizard.htm" label="Software Site Location Wizard"/>
</context>
<context id="launcher_osgi_framework" title="OSGi Framework Configuration">
<description>The OSGi Framework launches an OSGi runtime with bundles from the workspace and target platform.</description>
<topic href="guide/tools/launchers/equinox_launcher.htm" label="OSGi Framework Launcher"/>
</context>
<context id="launcher_eclipse_application" title="Eclipse Application Configuration">
<description>The Eclipse Application launcher runs or debugs plug-ins by launching a separate Eclipse application.</description>
<topic href="guide/tools/launchers/eclipse_application_launcher.htm" label="Eclipse Application Launcher"/>
</context>
<context id="launcher_junit_plugin" title="Junit Plug-in Test Configuration">
<description>The JUnit Plug-in Test Launcher runs JUnit Plug-in tests in a launched Eclipse application.</description>
<topic href="guide/tools/launchers/junit_launcher.htm" label="JUnit Plug-in Test Launcher"/>
</context>
<!-- END Target related contexts -->
</contexts>