removing launch configurations - programmatically

[subs]

Hi,

I have created a plugin with my own launch configurations for debug and run. Is
it possible to remove (or replace with my own delegate) the default
configurations ("C/C++ Local Application", "C/C++ Postmortem Debugger" and
"C/C++ Attach top Local Application") as these make no sense in my toolchain.

I wish to remain a 'pure' plugin so would like to do this either
programmatically or through plugin.xml rather than by changing and shipping my
own CDT.

Any pointers as to how I might achieve this?

Thanks

[W***@public.gmane.org]

You can hide them using capabilities. Add something like this to your
plugin.xml:

<extension
point="org.eclipse.ui.activities">

<activity
name="Unused CDT UI"
description="These UI elements from CDT are not used and
have been hidden using this capability"
id="com.yourcompany.cdtactivity">
</activity>

<!-- The following UI elements are from org.eclipse.cdt.launch -->
<activityPatternBinding
activityId="com.yourcompany.cdtactivity"

pattern="org.eclipse.cdt.launch/org.eclipse.cdt.launch.localCLaunch">
</activityPatternBinding>

<activityPatternBinding
activityId="com.yourcompany.cdtactivity"

pattern="org.eclipse.cdt.launch/org.eclipse.cdt.launch.localAttachCLaunc
h">
</activityPatternBinding>

<activityPatternBinding
activityId="com.yourcompany.cdtactivity"

pattern="org.eclipse.cdt.launch/org.eclipse.cdt.launch.coreFileCLaunch">
</activityPatternBinding>

<activityPatternBinding
activityId="com.yourcompany.cdtactivity"

pattern="org.eclipse.cdt.launch/org.eclipse.cdt.debug.ui.localCShortcut"
</activityPatternBinding>
</extension>


They will be hidden by default, but can be enabled from the Capabilities
pref.

Thanks,
Warren


-----Original Message-----
From: cdt-debug-dev-bounces-j9T/***@public.gmane.org
[mailto:cdt-debug-dev-bounces-j9T/***@public.gmane.org] On Behalf Of ext subs
Sent: Tuesday, January 15, 2008 5:40 AM
To: CDT Debug developers list
Subject: [cdt-debug-dev] removing launch configurations -
programmatically

Hi,

I have created a plugin with my own launch configurations for debug and
run. Is it possible to remove (or replace with my own delegate) the
default configurations ("C/C++ Local Application", "C/C++ Postmortem
Debugger" and "C/C++ Attach top Local Application") as these make no
sense in my toolchain.

I wish to remain a 'pure' plugin so would like to do this either
programmatically or through plugin.xml rather than by changing and
shipping my own CDT.

Any pointers as to how I might achieve this?

Thanks
--
Derek

[subs]

Brilliant - exactly what I wanted.

Thanks

Post by W***@public.gmane.org
You can hide them using capabilities. Add something like this to your
<extension
point="org.eclipse.ui.activities">
<activity
name="Unused CDT UI"
description="These UI elements from CDT are not used and
have been hidden using this capability"
id="com.yourcompany.cdtactivity">
</activity>
<!-- The following UI elements are from org.eclipse.cdt.launch -->
<activityPatternBinding
activityId="com.yourcompany.cdtactivity"
pattern="org.eclipse.cdt.launch/org.eclipse.cdt.launch.localCLaunch">
</activityPatternBinding>
<activityPatternBinding
activityId="com.yourcompany.cdtactivity"
pattern="org.eclipse.cdt.launch/org.eclipse.cdt.launch.localAttachCLaunc
h">
</activityPatternBinding>
<activityPatternBinding
activityId="com.yourcompany.cdtactivity"
pattern="org.eclipse.cdt.launch/org.eclipse.cdt.launch.coreFileCLaunch">
</activityPatternBinding>
<activityPatternBinding
activityId="com.yourcompany.cdtactivity"
pattern="org.eclipse.cdt.launch/org.eclipse.cdt.debug.ui.localCShortcut"
</activityPatternBinding>
</extension>
They will be hidden by default, but can be enabled from the Capabilities
pref.
Thanks,
Warren
-----Original Message-----
Sent: Tuesday, January 15, 2008 5:40 AM
To: CDT Debug developers list
Subject: [cdt-debug-dev] removing launch configurations -
programmatically
Hi,
I have created a plugin with my own launch configurations for debug and
run. Is it possible to remove (or replace with my own delegate) the
default configurations ("C/C++ Local Application", "C/C++ Postmortem
Debugger" and "C/C++ Attach top Local Application") as these make no
sense in my toolchain.
I wish to remain a 'pure' plugin so would like to do this either
programmatically or through plugin.xml rather than by changing and
shipping my own CDT.
Any pointers as to how I might achieve this?
Thanks
--
Derek
_______________________________________________
cdt-debug-dev mailing list
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
_______________________________________________
cdt-debug-dev mailing list
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev