![]() The core extension point allows for registration of descriptor types, target types, launch object providers, and launch configuration providers. There are two extension points provided to allow plug-in developers to add their own content to the LaunchBar, one for core (launchBarContributions) and one for UI (launchBarUIContributions). Each descriptor has an active mode and active target. This is the service that manages the objects, including the current selection of active objects. The list of modes are determined from the ILaunchConfigurationType returned by the Launch Configuration Provider for the currently active Launch Descriptor and Launch Target. It is actually the platform debug ILaunchMode. This is the element shown in the left selector. Each provider supports a single launch configuration type. They also provide access to the type of the configuration without having to create one. Providers are registered to a given Launch Descriptor Type and Launch Target Type. This is the object that manages the creation and selection of ILaunchConfiguration used by the buttons and Descriptor edit gear. The Types interface the underlying target management system with the toolbar. Targets have Types which manage the creation and remove of Targets. It represents a machine that the launch will run on. This is the element shown in the right selector. Descriptors have a Type that watches for the creation and removal of Launch Objects and manages the creation and removal of Descriptors for those object. This is the element shown in the middle selector. Out of the box, we have support for ILaunchConfigurations and IProjects as things, but a provider can be added to provide other types of things. ![]() We've already introduced a few concepts but here's more detail on what they are and a few more that create the entire picture.Ī thing that can drive the launch. As such there needs to be enough information available to create good default launch configurations for the different tools people will want to launch from there. The main requirement for the LaunchBar is to make it unnecessary for the user to have to go to the launch configurations dialogs to create and set up launches. There is also an edit button on the target to change properties for the target, such as communication channel to get to it, etc. We'll go into more detail on this in the following sections. There is also a shortcut at the bottom of the Descriptor selector to manually create a new Launch Configuration. The edit button (the gear) on the Launch Descriptor allows the user to edit that launch configuration using the launch configuration editor. It is determined by the combination of descriptor type and target type. There is the concept of active Launch Configuration that is used by the buttons. It has three selectors (fancy custom combo dropdowns), and three buttons. ![]() ![]() The LaunchBar is a Tool Control that's inserted into the top trim bar of all workbench windows. Providers for CDT projects will be in the .cdt.core and .cdt.ui plug-ins. Implementation is in the .core and .ui plug-ins. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |