[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cdt-dev] multi launch
|
Pruitt, John wrote:
This has been seen before.
1. In the case I have seen, the name was originally Multi-Launch but it
was changed to Launch Control or something like that in order to avoid
collisions with products named MULTI.
The latest name is "Launch Group"
2. This doesn't seem CDT specific.
Yes but I can only commit it to CDT. We can later maybe move it to platform but we have to start somewhere.
3. Other bells and whistles include pre-launch and post-launch actions
or scripts to run. Console output becomes more important here.
This can be implemented using same launch configuration.
4. How are errors handled? Is there any kind of "unwinding" or "error
recovery"?
Errors now processed as if user would launch all of them by quickly clicking on launch configuration,
i.e. independently (but sequentially).
4. Presumably a multi-launch can be included in a multi-launch?
Right now it won't allow it because it can be create infinite loop.
John
------------------------------------------------------------------------
*From:* cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
*On Behalf Of *Schaefer, Doug
*Sent:* Tuesday, March 31, 2009 12:59 PM
*To:* CDT General developers list.
*Subject:* RE: [cdt-dev] multi launch
Welcome, Christian ;)
I'm also wondering if this is something we'd like to contribute to the
Debug Platform, at least down the road. Would we design it differently
if we had more control over the launch UI?
Doug.
------------------------------------------------------------------------
*From:* cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] *On Behalf Of *Christian W. Damus
*Sent:* Tuesday, March 31, 2009 1:51 PM
*To:* CDT General developers list.
*Subject:* Re: [cdt-dev] multi launch
Hi, Elena,
I don't have objections, but questions :-)
What happens when a launch config that is referenced by the
multi-launch is deleted? Is the multi-launch config then broken,
such that the user must repair it (by removing the reference to the
missing launch, or perhaps replacing it with another) before it can
be launched again? This would seem intuitive to me. Also, is there
any kind of delete-participant or the like for launch
configurations, by which you could pro-actively warn the user of the
dependency from a multi-launch on a config that is being deleted?
How about validation of the sharing of these configs? It might be a
good idea to warn when a multi-launch that includes private launch
configs is shared in the workspace.
Will a multi-launch track the processes that it creates so that they
can be aggregated in a console, terminated as a group, etc?
Regarding a name for the launch config type, I think "Multi-Launch"
is appropriate. It doesn't imply semantics of pipeline or any other
specific multi-process scenario, and names like "Launch Family"
would connote a commonality of characteristics that also doesn't
apply. Perhaps "Launch Group" would be a less jargon-ish alternative.
Cheers,
Christian
On Tue, 2009-03-31 at 12:39 -0400, Elena Laskavaia wrote:
I was going to commit another launch configuration, which is "Multi Launch".
It has only one tab - user select "Add" to add another launch configuration (can be anything, including external)
and picks a mode of launch for it (run, debug, profiler, whatever or default). Default mean it would be launched in the mode in which multi-launch configuration
is launched. Any objections/suggestions? Also I am not sure how to call it.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx <mailto:cdt-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/cdt-dev
------------------------------------------------------------------------
Christian W. Damus
Software Developer, IDE Team
QNX Software Systems <http://www.qnx.com/>
------------------------------------------------------------------------
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev