Re: [ptp-dev] PTP vs CDT main launch tab

["Randy M. Roberts" <rsqrd@xxxxxxxx>]

Wyatt,

I've implemented an extension point (EP) in PTP 2.0 to expand the
functionality of the launch configuration.  Every resource manager (RM)
plug-in will implement an extension for this EP that will provide both a
GUI component and a programmatic, logical component that deals with the
specific launch requirements for that RM.  The GUI component of the 
extension will be displayed on the Parallel tab of the launch
configuration.

If you want to take a look at it...

I've put in place the basic launch configuration extension point system
into the PTP_TRY_RMR_20070112 branch.

The object implementing the IRMLaunchConfigurationDynamicTab interface
does most of the work.

Take a look at the following files...

// The file that displays the dynamic launch configuration UI
org.eclipse.ptp.launch.ui.ParallelTab.java

// This file uses the dynamic tab to obtain IAttribute's
org.eclipse.ptp.launch.internal.AbstractParallelLaunchConfigurationDelegate.java

// The class used in the extension point.
// Extensions must extend this class.
// It is a factory to create tabs.
org.eclipse.ptp.launch.ui.extensions.AbstractRMLaunchConfigurationFactory.java

// The extension factory creates one of these, given a resource manager.
org.eclipse.ptp.launch.ui.extensions.IRMLaunchConfigurationDynamicTab.java

// Better to extend this class, then to use the interface
org.eclipse.ptp.launch.ui.extensions.AbstractRMLaunchConfigurationDynamicTab.java

// Preliminary ORTE implementations of this extension...
org.eclipse.ptp.orte.ui.rmLaunchConfiguration.ORTERMLaunchConfigurationDynamicTab.java
org.eclipse.ptp.orte.ui.rmLaunchConfiguration.ORTERMLaunchConfigurationFactory.java

The ORTE implementations are not yet hooked up to the
ORTEResourceManager, but there is enough there to get
the feeling for how it will work.

Regards,
Randy

On Mon, 2007-04-09 at 14:52 -0600, Greg Watson wrote:
> Wyatt,
> 
> The main differences between PTP and CDT launch are in how the  
> application and the debugger are started. These happen in completely  
> different ways for PTP and CDT. Also, we've disabled a lot of the  
> binary file checking to handle remote launching, since the executable  
> may not exist locally (or may be in a different location).
> 
> Having said that, if the same result can be achieved by extending  
> CDT's launch configuration then I would support that approach. Randy  
> may have a better idea of what would be required for 2.0 since he's  
> working on that at the moment.
> 
> Greg
> 
> On Apr 9, 2007, at 1:31 PM, wspear wrote:
> 
> > Greetings,
> >
> > Is there a reason the PTP's main launch configuration tab's  
> > implementation is so distinct from the CDT's?  For PTP 1.1 it seems  
> > like they both attempt to provide similar functionality and that  
> > the PTP tab could easily be an extension of the CDT tab.  The most  
> > significant differences seem to be that the CDT implements stricter  
> > control of binary-file selection and requires the inclusion of some  
> > CDT-specific packages.  Unless the current PTP main tab is  
> > necessarily different or PTP 2's main tab is going to have  
> > significantly different requirements I think I could submit a patch  
> > that merges them without too much difficulty.
> >
> > This is relevant to the TAU plugins in that I am altering the main  
> > tabs for the user to select a build configuration rather than a  
> > binary, since the plugins don't run preexisting executables  
> > anyway.  If the PTP's differences from the CDT are necessary I will  
> > extend the PTP tab separately, otherwise I'll reuse the extension I  
> > made to the CDT main tab.
> >
> > Thanks,
> > Wyatt
> > _______________________________________________
> > ptp-dev mailing list
> > ptp-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/ptp-dev
> 
> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev