[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-debug-dev] Adding an Initial Debug Context
|
At this point (i.e. late in the 3.0 game), we don't want to get into the
business of a welcome page. I'd rather see the initial set of views in the
debug perspective be restricted to a minimal set: Debug View, Breakpoints
View, Editor pane & outline, Console.
Darin
Jeff Turnham/Toronto/IBM@IBMCA
Sent by: platform-debug-dev-admin@xxxxxxxxxxx
03/09/2004 12:57 PM
Please respond to
platform-debug-dev
To
platform-debug-dev@xxxxxxxxxxx
cc
Subject
Re: [platform-debug-dev] Adding an Initial Debug Context
Yep good point about the Welcome Pages in the mutli-vendor case. I think
in the case of 2 or maybe 3 vendors, separate Welcome Pages each getting
displayed wouldn't be too cumbersome (but that's definitely debatable).
However, since there is no way to know how many debug contributors could
be in a given solution then the centralized Welcome Page with extension
points sounds like a really good idea.
In an attempt to address the issue of the order of information in the
Welcome Page implying a relative importance of the debug
contributions...perhaps the Welcome page could be divided up in to
sections which each get contributed to by Debug Providers, so that one
debug provider's info isn't completely listed ahead of another? Something
like:
----------------------------------------------------------------------
Welcome to the Debug Perspective
Overview
Debug Contribution_1's Overview brief description and link
JDT Debug's Overview brief description and link
Debug Contribution_2's Overview brief description and link
Samples/Tutorials
Debug Contribution_1's Samples link
JDT Debug's Samples link (if any)
Debug Contribution_2's Samples link
Actions
Debug Contribution_1's Actions (debug a compiled app)
JDT Debug's Actions (debug a java app, goto the help, etc)
Debug Contribution_2's Actions (debug a script of some kind)
----------------------------------------------------------------------
I'm not advocating those specific sections, just the structure.
Also I was giving the "initial context" thing a bit more thought. I
think that the functionality could be attained with the given extension
points. The only change would be that the core Eclipse plugins define
and activate a context (something like org.eclipse.debug.initial) that has
no views bound to it (or maybe just the Breakpoint view if at least one
view has to be bound). Then debug providers can just come along and bind
the views they want to show to it. In the multi-provider case there may
be more views showing up than any one vendor wants, but that would happen
anyway.
Thanks...
---------------------------------------------------------------------
Jeff Turnham
---------------------------------------------------------------------
Peter Nicholls/Toronto/IBM@IBMCA
Sent by: platform-debug-dev-admin@xxxxxxxxxxx
03/09/2004 12:54 PM
Please respond to
platform-debug-dev
To
platform-debug-dev@xxxxxxxxxxx
cc
Subject
Re: [platform-debug-dev] Adding an Initial Debug Context
How does the Welcome page concept work when there are several vendors
contributing Welcome pages and the debug perspective is "empty". Whose
Welcome page gets displayed? I think this is one of the fundamental
problems with trying to handle the empty perspective nicely.
The only solution I can come up with is a standard debug welcome page in
the eclipse debug core that had extension points where debug providers
could register a link to their "welcome page" or something similar. This
way all contirbutors would be displayed via a single wlecome page and the
user can select a provider for more information.
Pete Nicholls
Mary Kroening <mary@xxxxxxxx>
Sent by: platform-debug-dev-admin@xxxxxxxxxxx
03/09/2004 11:31 AM
Please respond to platform-debug-dev
To: platform-debug-dev@xxxxxxxxxxx
cc:
Subject: Re: [platform-debug-dev] Adding an Initial Debug
Context
This would be great. Another simplification is to hide (not dim) some of
the debug command buttons and menu options.
Mary Kroening
Amzi! inc.
At 10:45 AM 3/9/2004 -0500, you wrote:
Hi,
We would like to override the initial view choices for an "empty" Debug
Perspective.
Rather than showing views that the user cannot typically do anything with
yet (such as Variables), we would like to just show the breakpoints view,
and display an editor or View that acts as a Welcome Page describing our
debug function and providing buttons/links for the user to get started.
One solution to this is for you to provide a way for Debug Providers to
provide an initial context (in the absence of a target/launch). So for
example, we could setup a context where we would not include the views we
want to hide, and would include the Welcome Page view. In the absence of
one of these "initial" contexts, then you could default to what you are
showing today.
I'm not sure yet whether these "initial" Contexts should be always active
or just active when there is no other DebugModelContextBinded context
active...I'd have to experiment a bit with the Usability of having the
Welcome page stick around vs vanish/re-appear.
The implementation of this for providers, could just be via another
extension point, as in:
(<initalDebugContext> is the only new tag):
<extension
point="org.eclipse.ui.contexts">
<context
name="Welcome to IBM Debug"
description="Welcome to IBM Debug"
id="com.ibm.debug.welcome">
</context>
</extension>
<extension
point="org.eclipse.debug.ui.debugModelContextBindings">
<intialDebugContext
contextId="com.ibm.debug.welcome">
</initialDebugContext>
</extension>
<extension
point="org.eclipse.debug.ui.contextViewBindings">
<contextViewBinding
viewId="org.eclipse.debug.ui.BreakpointView"
contextId="com.ibm.debug.welcome">
</contextViewBinding>
<contextViewBinding
viewId="com.ibm.debug.welcome.WelcomeView"
contextId="com.ibm.debug.welcome">
</contextViewBinding>
</extension>
Thoughts?
Thanks...
---------------------------------------------------------------------
Jeff Turnham
---------------------------------------------------------------------
----------------------------------------------------
Amzi! inc.
5861 Greentree Road
Lebanon, OH 45036 U.S.A.
web http://www.amzi.com
tel +1 513 425 8050
e-mail info@xxxxxxxx
fax +1 513 425 8025
----------------------------------------------------
