[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-ui-dev] Voting: View Activation and Opening
|
I think the behavior you have describe is ideal. And I think your
suggestion, that the preference be turned off by default, will be enshrined
within the UI guidelines we are developing.
Dave
Darin_Wright@xxxxxxx
Sent by: To: platform-ui-dev@xxxxxxxxxxx
platform-ui-dev-admin@e cc:
clipse.org Subject: Re: [platform-ui-dev] Voting:
View Activation and Opening
12/12/01 10:11 AM
Please respond to
platform-ui-dev
Currently, the debugger opens/activates views in the following situations:
(1) When output is written to the console and the "Show console when there
is program output" preference is turned on. In this case, I believe the
debugger is following the convention that a view should "only be activated
if they have explicitly asked to see the view" - since the preference is
turned on. One thing the debugger could do to be less intrusive, is to have
the preference turned off by default.
(2) When the user "inspects" an expression, an inspector is activated.
Again, I believe the debugger is following the same convention here, as the
user has explicitly asked to inspect an expression.
In both cases, the result can be a little ugly, as there may not be a
placeholder for the view that is opened. However, if the view is opened as
a "fast view", this would be less of an issue.
If we are in agreement that the debugger is not breaking the rules, then my
vote is +1.
Darin
David_Springgay@xxxxxxx
Sent by: To:
platform-ui-dev-admin@eclips platform-ui-dev@xxxxxxxxxxx
e.org cc:
Subject: [platform-ui-dev]
Voting: View Activation and Opening
12/11/2001 02:28 PM
Please respond to
platform-ui-dev
View Activation and Opening
The Loss of Context Proposal has been split up so we can move forward on
individual issues. This section concerns the State View Activatoin and
Opening issues (Problem #7). We would like to vote on the direction of
this proposal. If agreement can be reached, we will progress with the
implementation and address PR's as they come up.
In Eclipse, many complaints have been made about intrusive behavior in the
platform. For instance, if the console view appears with a normal status
message, users don't want to see it. The feel it should only appear if
there is an important message to be seen. Many users also complain when a
view is opened, causing a layout change in the perspective.
To resolve these problems, we will:
# define guidelines for the appropriate use of view activation. In
general, a view should only be activated if the user explicitly asks to
see the view. If an error occurs, and it requires user attention, a modal
dialog should be used to communicate that error to the user.
# if a view is opened programmatically, we will open it as fast view or
floating view until user places it in page. In the current prototype
the user can choose either one, or the existing behavior. We will make one
of them (fast or floating) the default, rather than the existing
behavior.
For the time being, we have no plans to implement a "flash view" feature.
Voting:
+1 = You are in favour of this proposal & agree with further
exploration to determine API/contribution
changes.
0 = Abstain
-1 = You are opposed to this proposal. When voting -1 you must also
provide a detailed explanation of your
reasons.
Voting ends 1 week from date proposal is submitted to the mailing list.
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-ui-dev
