[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [platform-vcm-dev] Team Operations from top level menus
|
Your point is valid and its great to get feedback on the requirements.
We would prefer to have a Team pulldown because there is a Team context
menu, thus making the UI consistent for all. Another issues is if we grow
the common Team facilities in the future, its important that we have a
place to hang these off of (a Team pulldown).
However, the multiple provider case, although agreed to be rare, does mess
up the problem. This is the part we are trying to sort out. Note its not
even required that you are using the other providers (unlikely), this
happens if you simply have the plugins (more likely), since the actions are
global and not filtered by project nature.
The choices at present are:
1. One team menu, everyone just contributes their actions to it. If we have
more than one provider then these items will get mixed in with each other.
2. Every provider has their own top level menu (we are not a fan of this,
as explained).
3. There is a submenu in the Team pulldown for each provider. This isn't
very nice for the single provider case.
Not really happy with any of these choices.
Kevin
"Zulli, Joseph"
<Joseph.Zulli@xxxxxx> To: platform-vcm-dev@xxxxxxxxxxx
Sent by: cc:
platform-vcm-dev-admin@ Subject: RE: [platform-vcm-dev] Team Operations from top
eclipse.org level menus
05/01/2002 01:53 PM
Please respond to
platform-vcm-dev
I am designing a Team 2.0 provider and personally, I would rather there not
be a Team menu on the top menubar. I see no need for it and I feel that as
many UI elements as possible should be left to the repository providers to
implement so that they can have maximum flexability. For instance, what if
I don't want to put anything on the top menu, or I do, but don't want to
call it Team? Having multiple repository adapters installed is an issue,
but how many users are really going to ever have more than one or two?
Anyway, just my 2 cents.
Joe
-----Original Message-----
From: James_Moody@xxxxxxx [mailto:James_Moody@xxxxxxx]
Sent: Wednesday, May 01, 2002 7:44 AM
To: platform-vcm-dev@xxxxxxxxxxx
Subject: Re: [platform-vcm-dev] Team Operations from top level menus
We would like to put some variant of this functionality in for M6. See bug
9855 in bugzilla. We just haven't decided what shape it will take.
james
|---------+---------------------------------->
| | Bryan Stephenson |
| | <Bryan.Stephenson@meran|
| | t.com> |
| | Sent by: |
| | platform-vcm-dev-admin@|
| | eclipse.org |
| | |
| | |
| | 05/01/02 09:51 AM |
| | Please respond to |
| | platform-vcm-dev |
| | |
|---------+---------------------------------->
>
------------------------------------------------------------------------------------------------------------|
|
|
| To: platform-vcm-dev@xxxxxxxxxxx
|
| cc:
|
| Subject: [platform-vcm-dev] Team Operations from top level menus
|
>
------------------------------------------------------------------------------------------------------------|
Are there any concrete proposals for adding a top level menu for Team
operations. There were a number of
postings discussing this but there seems to be no conclusion. Obviously
Team providers can add their own menus
to the top level, however, the ability to have multiple providers active in
a workspace means that the top level menus may
expand arbitrarily. There was discussion of a "Team" top level menu where
providers could attach their menus.
In general, these menus implement non-project specific operations such as
launching the providers client program, getting
a project from the provider (functionality already in provider - no need
for repository browser as in CVS).
Taking the example of a well known C++ IDE, there is a Source Control menu
in the "Project" group. Would this be a more appropriate place to add
"Team" menus. If so where are the menu definitions for this menu so we
can find an appropriate separator to attach to.
Bryan Stephenson mailto:Bryan.Stephenson@xxxxxxxxxx
_______________________________________________
platform-vcm-dev mailing list
platform-vcm-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev
_______________________________________________
platform-vcm-dev mailing list
platform-vcm-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev
