Re: [platform-debug-dev] LCD need

[David Corbin <dcorbin@xxxxxxxx>]

On Thursday 27 November 2003 16:47, Darin Wright wrote:
> I don't believe that launch groups will solve this problem (correct me if
> I am wrong). A launch group identifies a group of launch configurations by
> "mode and categoty". For example, the "Debug" launch group contsists of
> all launch configurations that support the "debug" mode and belong to the
> default (application) category. The "External Tools" launch group consists
> of all launch configurations that support the "run" mode and belong to the
> "external tools" category.
>
> I beleive that David is looking for a way further filter what is displayed
> in the LCD within a launch group. Is that correct?
>

Yes it is.  I'm not done poking around, but it looks like the whole launch 
configuration thing is substantially (but not totally) one-sided.  It's very 
easy for plugins to provide launchConfigurationType, with a great deal of 
flexibility.  It's very hard for a plugin to consume 
launchConfigurations/Types, except in a narrow path.  As it stands now, most 
of the consumption is being down by the debug.ui plugin, and possibly one or 
two other eclipse-internal plugins (ant, external tools).

That having been said, I *may* have found to do what I need to do "well 
enough" using the LaunchConfigurationPropertiesDialog.  I'll know more by the 
time the weekends over, I expect.

> Darin
>
>
>
>
>
> Jared Burns <jaredburns@xxxxxxx>
> Sent by: platform-debug-dev-admin@xxxxxxxxxxx
> 11/26/2003 12:04 PM
> Please respond to platform-debug-dev
>
>
>         To:     platform-debug-dev@xxxxxxxxxxx
>         cc:
>         Subject:        Re: [platform-debug-dev] LCD need
>
>
>
> DebugPlugin.getDefault().getLaunchManager() will get you to the launch
> manager
> where you can access launch configs and config types.
>
> If you want the full LCD functionality, take a look at the
> DebugUITools.openLaunchConfigurationDialog* methods. If you want to open
> the
> config dialog on config types of your own creation, you can define a
> launch
> group and open the dialog on that to achieve victory. This is how external
>
> tools/Ant is able to open the LCD and only show Program and Ant launch
> config
> types.
>
> - Jared
>
> On Wednesday 26 November 2003 09:54 am, David Corbin wrote:
> > On Wednesday 26 November 2003 12:33, Jared Burns wrote:
> > > If you just want the user to be able to select (not configure) them,
>
> use
>
> > > an ElementListSelectionDialog or ElementTreeSelectionDialog depending
>
> on
>
> > > whether or not you want to show them as a flat list or you want to
> > > include the config types as top-level nodes.
> >
> > Select would be better than nothing.  However, I would like to allow the
> > user to create new configuration or modify an existing one.  Forcing the
> > user to go through the "regular" LCD page to add one, and then having to
> > select the configuration just added seems like a bad UI design.
> >
> > > Use the LaunchManager to get the collection of configs of a particular
> > > type.
> > >
> > > As I understand your problem, there's no need for new API here.
> >
> > Launch Manager is an internal class.  Doesn't that mean a new API is
> > required.
> >
> > David
> >
> > _______________________________________________
> > platform-debug-dev mailing list
> > platform-debug-dev@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/platform-debug-dev
>
> _______________________________________________
> platform-debug-dev mailing list
> platform-debug-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-debug-dev