[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [platform-ui-dev] Working sets on a workbench window
|
I think the question is for what purpose you are using working sets. I see
the following use cases:
- only have those elements at my finger tips I am actively working on. A
use case is selecting a working set in the package explorer.
- further filter down a "result" of an action. An example is building a
type hierarchy. I normally want to see the whole hierarchy first and then
apply a working set to it to filter away
unwanted types. This filter is most of the time a different one than the
one I use in the package explorer. The same is somehow true for search.
However for performance
reason you provide the working set as an input to the search instead of
filtering the result afterwards.
Dirk
"Ed Burnette"
<Ed.Burnette@sas.
com> To
Sent by: "Eclipse Platform UI component
platform-ui-dev-b developers list."
ounces@xxxxxxxxxx <platform-ui-dev@xxxxxxxxxxx>
g cc
Subject
29/09/2005 05:54 RE: [platform-ui-dev] Working sets
PM on a workbench window
Please respond to
"Eclipse Platform
UI component
developers list."
<platform-ui-dev@
eclipse.org>
Pardon the question, but if there's a global working set then why would one
realistically need or want to pick a working set in each view?
From: platform-ui-dev-bounces@xxxxxxxxxxx
[mailto:platform-ui-dev-bounces@xxxxxxxxxxx] On Behalf Of Martin
Aeschlimann
Sent: Thursday, September 29, 2005 9:04 AM
To: Eclipse Platform UI component developers list.
Subject: Re: [platform-ui-dev] Working sets on a workbench window
As I see it, Dirk's proposal has the advantage that it means no changes at
all for viewers that already support working sets. Opening the normal
working set selection dialog, a view can select the 'global working set',
which is just a redirection. The working set selection dialog is all
controlled by platform, so views don't need to know about the special
characteristics of the global working set. The advantage is also that a
view could choose not to take the global working set but a different one.
It can be discussed if that feature really will be used, but it seem to be
a compromise so that also friends of the old behavior are not broken.
Martin
Michael Van Meekeren
<Michael_Van_Meekeren@xxxxxxxxxx>
Sent by:
platform-ui-dev-bounces@xxxxxxxxxxx To
"Eclipse Platform UI
component developers list."
09/28/2005 02:54 PM <platform-ui-dev@xxxxxxxxxx
g>
cc
Please respond to
"Eclipse Platform UI component Subject
developers list." Re: [platform-ui-dev]
<platform-ui-dev@xxxxxxxxxxx> Working sets on a workbench
window
For M3 we propose the following. Working sets are selected per Window.
While the suggestion of a global working set (global being understood as
one per window) would make the listening scenario a little simpler for
views, it would still be necessary for views to look at the global working
set to filter out working set types that are not meaningful for a
particular view. So since views need to do this anyway, it does not seem
like a big benefit and is not worth doing. Also we need to consider what
type this global working set is, how to make it read only etc...
The goal is to allow views to remove as much of the working set related
menu/toolbar items that have in favour of putting it in one place, if this
does not support that goal then we are keen to make sure it does.
/michael
Dirk Baeumer
<dirk_baeumer@xxxxxx.
com>
Sent by: To
platform-ui-dev-bounc "Eclipse Platform UI component
es@xxxxxxxxxxx developers list."
<platform-ui-dev@xxxxxxxxxxx>
cc
09/09/2005 01:17 PM "Eclipse Platform UI component
developers list."
<platform-ui-dev@xxxxxxxxxxx>,
Please respond to platform-ui-dev-bounces@xxxxxxxxxxx
"Eclipse Platform UI Subject
component developers Re: [platform-ui-dev] Working sets on
list." a workbench window
Cool ! I am missing that feature as well. That's why I started hacking on
a
comparable
feature in July. Here is what I did. May be it is of any help:
- added a special working set (global working set) which is simply a
reference to
an existing working set
- views (e.g. package explorer) selected the global working set for
filtering
- changing the global working set to reference another working set updated
all views referencing this working set since the global working set
changed.
The nice thing was that this didn't require any additional code on the
view
part
side.
Dirk
Kimberly Horne
<kim@xxxxxxxxxxxx
m> To
Sent by: "Eclipse Platform UI component
platform-ui-dev-b developers list."
ounces@xxxxxxxxxx <platform-ui-dev@xxxxxxxxxxx>
g cc
Subject
09/09/2005 04:39 Re: [platform-ui-dev] Working sets
PM on a workbench window
Please respond to
"Eclipse Platform
UI component
developers list."
<platform-ui-dev@
eclipse.org>
Yes. For instance, the package explorer currently has a menu item to
select the visible working sets (when you're in the working set
mode). With this new API, you could simply show all working sets
that are of the java type and listen for changes so that you can
update your tree appropriately.
On 9-Sep-05, at 10:27 AM, Dirk Baeumer wrote:
> Kimberly
>
> can you explain the purpose of the new API to me. Is the idea that
> view
> parts listen to these
> changes and update there current working set accordingly.
>
> Dirk
>
>
>
>
> Nick Edgar
> <Nick_Edgar@xxxxx
>
> m.com> To
> Sent by: "Eclipse Platform UI component
> platform-ui-dev-b developers list."
> ounces@xxxxxxxxxx <platform-ui-dev@xxxxxxxxxxx>
>
> g cc
>
>
> Subject
> 09/09/2005 04:03 Re: [platform-ui-dev]
> Working sets
> PM on a workbench window
>
>
> Please respond to
> "Eclipse Platform
> UI component
> developers list."
> <platform-ui-dev@
> eclipse.org>
>
>
>
>
>
>
> Is there any kind of notification (e.g. property change event) when
> it's
> changed?
> How would a view tracking this know to update?
>
> Nick
>
>
>
>
> Kimberly Horne <kim@xxxxxxxxxxxxx>
> Sent by: platform-ui-dev-bounces@xxxxxxxxxxx
> 09/09/2005 08:20 AM
> Please respond to
> "Eclipse Platform UI component developers list."
>
>
> To
> "Eclipse Platform UI component developers list."
> <platform-ui-dev@xxxxxxxxxxx>
> cc
>
> Subject
> [platform-ui-dev] Working sets on a workbench window
>
>
>
>
>
>
> Next weeks integration build will introduce the following new API on
> IWorkbenchPage:
>
> IWorkingSet[] getWorkingSets();
> void setWorkingSets(IWorkingSet[])
>
> The intention of these methods is to allow you to specify what
> working sets should be visible across all components within a given
> workbench window. Currently this API is not being used by any
> downstream component but we're making it public (and visible) now to
> gauge interest.
>
> By visible I am referring to a new action that's been added to the
> Resource Navigation action set.
>
> You will see in your toolbar and in your Window menu a pulldown
> action called Working Sets. The children of this action represent
> all working sets registered with the system IWorkingSetManager and
> are either checked or unchecked. If they're checked, they're
> contained in the array returned by IWorkbenchPage.getWorkingSets().
>
> The notable problems with the implementation as it currently sits are
> as follows:
> The "Edit..." action currently opens the "Select Working Set"
> dialog despite there being no selection required. We will replace
> this with a more particular editing dialog at some later point.
> The dropdown won't scale when the user has a large number of
> working sets.
> The action needs a toolbar icon.
> The action probably doesn't belong in the Resource Navigation
> action set.
> Please don't log these bugs. We've already done so :)
>
>
>
> _______________________________________________
> platform-ui-dev mailing list
> platform-ui-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/platform-ui-dev
>
>
> _______________________________________________
> platform-ui-dev mailing list
> platform-ui-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/platform-ui-dev
>
>
> _______________________________________________
> platform-ui-dev mailing list
> platform-ui-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/platform-ui-dev
>
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev
