Re: [platform-debug-dev] launch configuration filtering

[Jared Burns <jared-eclipse@xxxxxxxxx>]

I like the idea of being able to see only the launch configurations that 
apply to your current mental context. I'm just not certain that the proposed 
interface will be ideal. If you want to launch a "testing" launch config, it 
seems reasonable to select your "Tests" project and you'd only see launch 
configs from that project. 

However, it seems that you'd want a way to change contexts with the dialog 
already open. I don't have a suggestion for implementing this (seems like it 
would be messy), but it might be worth mentioning.

I would suggest, though, that if you are going to filter the contents of the 
tree in the launch config dialog, you might also want to filter the configs 
that show up in the list of "favorites" in the various launching menus.

- Jared

On Thursday 08 August 2002 03:21 am, you wrote:
> hi,
>
> i had an idea for a small improvement to the launch configurations dialog.
>
> the problem: i typically have three or four projects i'm working on at any
> one time, each with its own set of launch configurations. when i have to
> change course and run things in another project, i find myself having to
> hunt down the desired configuration in the list of ~15-20 existing
> configurations.
>
> ideally, i'd be able to toggle the launch configurations display between
> displaying those that are associated with the currently selected project in
> the workspace, and displaying everything.
>
> this isn't as easy as i thought it would be, since the project attribute is
> currently provided by JDT. however, i don't see why this attribute can't be
> made more general, then the launch configuration treeview's content
> provider can do the filtering. and if launch configuration types don't have
> the concept of an associated project, well, thats fine, it won't have that
> attribute and hence filtering will not apply to it.
>
> pseudocode for the filtering in the content provider:
>
>     if filteringByProject
>
>         if configProject is null
>             # if we're filtering, we typically want to ignore
> configurations # with no associated project
>             continue
>
>         if selectedResourceProject not null
>             # we also only want to filter if we can determine the selected
> project,
>             # if we can't we display everything
>             if not selectedResourceProject equals configProject
>                 continue
>
>
> where selectedResourceProject is an IProject obtained from
> LaunchConfigurationDialog.getResourceContext(),
> if any, and configProject is an IProject obtained by looking up a project
> from its name (if any) using ILaunchConfiguration.getAttribute().
>
> the feature request i opened for this feature is at:
>
> http://bugs.eclipse.org/bugs/show_bug.cgi?id=22195
>
> anyone like or dislike this suggestion?
>
> regards,
> leon.
>
>
> _______________________________________________
> platform-debug-dev mailing list
> platform-debug-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-debug-dev