[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-debug-dev] Launch Configuration Templates
|
Darin,
I expect this will be a very useful feature for our customers. Here's
some feedback:
1. The transformation of a launch configuration to a template due to
a drag-n-drop concerns me. Coming out of a drag is always a bit error
prone, and a misplaced drop is ok if you're just moving stuff around,
but if the mistake ends up transforming something else, then it makes
the mistake more serious. I recommend either prompting the user prior
to the transformation or altogether dropping this capability.
2. I think a "New template" action in the context menu of the viewer
would be helpful. Context menus are the first place I look to see
what sort of operations I can carry out on an object. When enacted on
a launch config type, it would create a new empty template. When
carried out on a launch config, it would create a template from that config.
3. I really like the ability to update child configurations by
updating the template. I think that will come in really handy for
users with lots of configurations (I know our customers wish they had
that today).
4. I'm concerned that the "Remove" action will be confused with
deleting a template. Perhaps "De-templatize"? (Not crazy about that,
either, but can't think of anything better at the moment).
5. I'm unclear on the action of associating a configuration with an
existing template. It's not a lasting association, right? In other
words, after cross-applying the settings to the target template,
there is no association between the two, or is there?
6. Use of a checkbox for mutual exclusive enablement seems a little
unorthodox to me. Radio buttons are the defacto widget for that sort
of thing. I looked through a lot of Eclipse GUI searching for an
example of what you've proposed but didn't find any. If there is
precedent, then I'm not so concerned. If there is no precedent, I'm
slightly concerned, though in actuality it seems intuitive enough to me.
7. Will a decoration be applied to template icons in the viewer to
visually differentiate a template from a regular configuration?
8. There are discrepancies between the interface changes that you
committed the other day and the wiki. E.g., see
ILaunchConfigurationType. Should we be reviewing the API in the wiki
or the changes committed so far? (Not sure if you've abandoned some
of the ideas on the wiki)
9. I don't know if it's implied, but it seems to me that the GUI for
launch configurations should be enhanced to be lax in their
validation. A template should not be subject to the same level of
validation as a regular config. For example, a user currently has to
specify an executable in a CDT launch configuration, or an error is
exposed. A template would want to be able to leave that field blank.
John
At 03:01 PM 10/14/2009, Darin Wright wrote:
I've updated the debug wiki with a design document for launch
configuration templates:
http://wiki.eclipse.org/Debug/Plan/3.6/Launch_Templates
An initial implementation of the core infrastructure is also available on
the associated bug (and will be released to HEAD shortly).
https://bugs.eclipse.org/bugs/show_bug.cgi?id=41353
Please review and provide any feedback. We intend to complete the user
interface for launch templates during M4.
Thanks,
Darin
_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-debug-dev
