[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-ui-dev] Voting: View Activation and Opening
|
My vote is +1 because I agree with the general direction. However, I have a
few comments...
- A view opened programmatically will open as a fast or detached/floating
window. It seems there will be a preference to choose which one. We need to
be careful here because some platforms (like linux) do not support
detached/floating windows. How will we indicate this to the user? If we
specify the platforms it works on, this can get out of date as new
platforms are supported by SWT. Maybe we do not give them a preference at
all - it is always fast view.
- I agree with the guideline that most time the view should only come to
the front when the user explicitly ask for it. We need to include in this,
not only when the user clicks on the view's tab or selects from the Show
View menu, but also cases like choosing "Inspect" in the editor during
debug will need to cause the Inspect view to show (otherwise it will seem
like nothing happen). Or showing the Debug view when a breakpoint is hit
(otherwise the user will not clue in that the program is suspended because
of a breakpoint).
Simon :-)
David_Springgay@xxxxxxx
Sent by: To: platform-ui-dev@xxxxxxxxxxx
platform-ui-dev-admin@e cc:
clipse.org Subject: [platform-ui-dev] Voting: View Activation
and Opening
12/11/2001 03: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
