[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-debug-dev] Launch Configuration working sets
|
Darin,
I have no problem with using working sets/"customize"/perspective filtering
approach as long as
this could be done programmatically.
I really think that in some enterprise-level products we get too many
launch configuration types
that are irrelevant to many customers. I also hate to see deep trees like
that, but I think that some
of our customers need to get a 'customized' solution 'out of the box' or
else they get quite confused :-)
Thanks,
Vadim
|---------+------------------------------------>
| | "Darin Wright" |
| | <Darin_Wright@xxxxxxx> |
| | Sent by: |
| | platform-debug-dev-admin@|
| | eclipse.org |
| | |
| | |
| | 10/02/2002 04:51 PM |
| | Please respond to |
| | platform-debug-dev |
| | |
|---------+------------------------------------>
>-----------------------------------------------------------------------------------------------------------|
| |
| To: platform-debug-dev@xxxxxxxxxxx |
| cc: |
| Subject: Re: [platform-debug-dev] Launch Configuration working sets |
| |
| |
>-----------------------------------------------------------------------------------------------------------|
Personally, I think that groups just add another level of complexity that
is not needed - the tree just gets deeper. Using the working
sets/"customize"/perspective filtering approach, the tree remains at two
levels, and there is no additional extension point infrastructure required.
Darin
Jared Burns
<jared-eclipse@xxxxxxxxx> To:
Sent by: platform-debug-dev@xxxxxxxxxxx
platform-debug-dev-admin@ec cc:
lipse.org Subject: Re:
[platform-debug-dev] Launch Configuration
working sets
10/02/2002 03:31 PM
Please respond to
platform-debug-dev
Depends on what the groupings represent. You can either group the config
types by vendor or by functionality. If the groups represent vendors, you
just use names that are vendor specific ("JDT Java", "WSAD JSP", etc.). If
the groups are functional, the problem is harder... but you could just
allow
people to specify their functional grouping and then merge any groups that
overlap.
- Jared
On Wednesday 02 October 2002 03:13 pm, you wrote:
> I think launch config groups would solve this problem, and perhaps a few
> others. The problem is how to administer these groups. For example,
> suppose I write a plugin that knows how to launch files written in some
> new language XYZ. Since mine is the first XYZ plugin, I declare an XYZ
> launch config group in XML. Later, somebody else writes another plugin
> that does a different kind of launching for XYZ resources. They can
> declare that their launch config type belongs to my group, but this
> requires that anyone using their plugin must also have mine installed. I
> don't think this is tenable long-term. The problem is how to declare
> 'well-known' groups that others can use without creating large plugin
> dependency chains.
>
> Joe
>
>
>
>
>
>
> berestet@xxxxxxxxxx
> Sent by: platform-debug-dev-admin@xxxxxxxxxxx
> 10/02/2002 03:03 PM
> Please respond to platform-debug-dev
>
>
> To: platform-debug-dev@xxxxxxxxxxx
> cc:
> Subject: Re: [platform-debug-dev] Launch Configuration
> working sets
>
> I have downloaded the latest ECLIPSE driver and have looked at the
working
> sets for the launch configurations.
> I think they will allow users to reduce the amount of launch
configuration
> that see at the same time, however...
> they have to do work in order to accomplish this.
>
> I still think that given the number of launch configurations that will
> appear in the launch configuration dialog in
> some of the products, it will make things easier for the end uses if
> launch
> configuration types where grouped
> into the launch configuration type trees.
> Alternatively, I wonder if there is a programmatic way to create a
working
> set? This way 'undesired' launch
> configuration types could be filtered out, but I'd still prefer the
launch
> configuration type groups...
>
> Any thoughts?
> Vadim Berestetsky
> Distributed Debugger Development
>
> |---------+------------------------------------>
> |
> | | "Joe Szurszewski" |
> | | <Joe_Szurszewski@xxxxxxx>|
> | | Sent by: |
> | | platform-debug-dev-admin@|
> | | eclipse.org |
> | |
> | |
> | | 08/23/2002 10:33 AM |
> | | Please respond to |
> | | platform-debug-dev |
> |
> |---------+------------------------------------>
> |
> >
--------------------------------------------------------------------------
> >---------------------------------|
> >
> | To: platform-debug-dev@xxxxxxxxxxx |
> | cc: |
> | Subject: Re: [platform-debug-dev] Launch Configuration working
>
> sets |
>
> >
--------------------------------------------------------------------------
> >---------------------------------|
>
> No, the work I did was strictly to add working set support. I'm
> interested
> in any feedback from working set users regarding the extent to which the
> feature you mentioned is still needed, given that you can add entire
> config
> types to a working set.
>
> Joe
>
>
>
>
> berestet@xxxxxxxxxx
> Sent by: To:
> platform-debug-dev-admin@ec platform-debug-dev@xxxxxxxxxxx
> lipse.org cc:
> Subject: Re:
> [platform-debug-dev] Launch Configuration
> 08/22/2002 06:01 PM working sets
> Please respond to
> platform-debug-dev
>
>
>
>
>
> Hi Joe,
>
> I haven't got a chance to try this out quite yet. But I am wondering if
> this will contain support
> for grouping launch configuration types into launch configuration types
> trees?
>
> Thanks,
> Vadim Berestetsky
> Distributed Debugger Development
> Phone (905) 413-4403; T/L 969-4403
> Internet: berestet@xxxxxxxxxx
>
> |---------+------------------------------------>
> |
> | | "Joe Szurszewski" |
> | | <Joe_Szurszewski@xxxxxxx>|
> | | Sent by: |
> | | platform-debug-dev-admin@|
> | | eclipse.org |
> | |
> | |
> | | 08/22/2002 12:18 PM |
> | | Please respond to |
> | | platform-debug-dev |
> |
> |---------+------------------------------------>
>
>
---------------------------------------------------------------------------
>---------------------------|
>
> | To: platform-debug-dev@xxxxxxxxxxx
> |
> | cc:
> |
> | Subject: [platform-debug-dev] Launch Configuration working sets
>
>
---------------------------------------------------------------------------
>---------------------------|
>
>
>
>
>
> Support for using working sets consisting of launch configurations &
> launch
> configuration types has been released to the HEAD stream and should be in
> the next integration build. You can access this via the context menu on
> the tree in the launch configuration dialog. Working sets may consist of
> individual configs and/or entire config types. In the latter case, any
> future configs of the selected type essentially become members of the
> working set. The working set selected in the launch config dialog is
> persisted across dialog & workbench invocations. Please file any bugs
> against platform-debug.
>
> Joe
>
>
> _______________________________________________
> 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
_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-debug-dev
