| Are you using ptp_5_0 branch or HEAD? I only checked the changes into ptp_5_0.
Greg On Aug 2, 2011, at 6:51 PM, Wyatt Spear wrote: Just ptp.launch? I'm not seeing any difference.=Wyatt On Tue, Aug 2, 2011 at 3:47 PM, Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
Wyatt,
Update the ptp.launch plugin and the message should go away.
Greg On Aug 2, 2011, at 6:10 PM, Wyatt Spear wrote: Ah, sorry Greg, I should have mentioned I already had most of the ETFW-side changes in place. What I was missing was the .launchDelegates extension point... switching over to that lets me use my own delegate while using the standard PTP launch type. Unfortunately when I do this my launch configurations have the error
"Multiple launchers available - select one to continue"
but there is nothing in the configuration panes to change to fix it. I tried both your patch and just adding the .launchDelegates fix to the changes I implemented and it shows up in both cases.
=Wyatt On Tue, Aug 2, 2011 at 11:53 AM, Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
Wyatt,
It turned out to be a bit trickier than I though. I've opened bug 353633 and attached a patch. Can you try this out and make sure it looks ok?
Also, I've only changed the parallel launch. I'm not sure what you want to do about the "Performance Analysis" launch.
Thanks, Greg
On Aug 1, 2011, at 7:41 PM, Wyatt Spear wrote: Yes, that's what I was doing, but it looks like the type provides the delegate. I don't see anyway to use the ptp type without using its delegate.
=Wyatt On Mon, Aug 1, 2011 at 4:31 PM, Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
See the plugin.xml in org.eclipse.ptp.launch for how to do it. You provide your own id.
Greg On Aug 1, 2011, at 6:42 PM, Wyatt Spear wrote: Switching over to the extension-point based tab layout is turning out to be not-totally-straightforward. The 'Common' tab doesn't have a TAB_ID so you can't explicitly position tabs after it and I get random tab positioning when the position isn't explicit (or even multiple tabs are set to follow the same tab). The tab ordering changes between instances of the launch manager window, which seems especially bizarre...
=Wyatt On Mon, Aug 1, 2011 at 8:56 AM, Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
Wyatt,
I'd also suggest using the org.eclipse.debug.ui.launchConfigurationTabs extension point for defining the tabs rather than hard coding tabs in the ParallelToolLaunchConfigurationTabGroup class. Plugins could then add their own tabs using this extension point, rather than needing to have a separate org.eclipse.ptp.etfw.configurationTabs extension point.
Greg
On Aug 1, 2011, at 11:43 AM, Greg Watson wrote:
Hi Wyatt,
For 1, all that needs to happen is change the type field of the launchConfigurationTabGroup to "org.eclipse.ptp.launch.parallelLaunch". You should probably also remove the old launch configuration type otherwise it will show up in the launch dialog.
If you'd like to make the changes, that's fine with me. Or I can make them and you could test the non-ptp launch issue. Let me know whatever works best.
Cheers,
Greg On Aug 1, 2011, at 10:27 AM, Wyatt Spear wrote: I like all of these. I can implement 2 and 3 pretty quickly. For 1 I'll have to do a little digging to remind myself of which string to change and which to use to switch the etfw configuration type. Also 1 may require some changes to documentation and I need to make sure we retain support for non-ptp launches.
=Wyatt On Mon, Aug 1, 2011 at 7:14 AM, Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
Wyatt & other ETFw users,
1. The profile configuration uses it's own launch configuration type. If the launch configuration type was the same as the Parallel Application launch configuration type, then run/debug launch configurations created using the Parallel Application launch configuration could be used for a profile launch. In some situations, this would reduce the amount of configuration required for a development work flow. I propose that the profile configuration use the same configuration type.
2. The profile launch configuration has the Application tab before the Resources tab. However, for remote launches in particular, the resource manager must be selected before the application executable. Otherwise there is no way to know on which remote host the executable is located. I propose reversing these two tabs.
3. The profile launch configuration has a Debugger tab which is not required, but, annoyingly, still needs to be completed by the user. I propose removing this tab.
Please let me know ASAP if you have any objections, or are ok with these changes.
Thanks,
Greg
_______________________________________________
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
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
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
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
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
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
|
