[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [platform-ui-dev] Working set framework
|
I've just updated bug 11044. You can use the IWorkingSet for anything that
is a set of IAdaptables. As per the proposal persistence will be done via
the IPersistableElement interface. You will get it for free as long as
your working set items implement the IPersistableElement interface.
Knut
Jared Burns <jared-eclipse@xxxxxxxxx>
Sent by: platform-ui-dev-admin@xxxxxxxxxxx
03/20/02 08:41 AM
Please respond to platform-ui-dev
To: platform-ui-dev@xxxxxxxxxxx
cc:
Subject: [platform-ui-dev] Working set framework
The latest comments in the "Working Sets framework" bug
(http://bugs.eclipse.org/bugs/show_bug.cgi?id=11044), indicate that each
IWorkbenchPage will have an active working set associated with it. This is
handy for views that want to use working sets as a filter. But will
working
sets be available for use by clients who want to use them for other
purposes?
I'm currently working on an "Editor View"
(http://bugs.eclipse.org/bugs/show_bug.cgi?id=10941) and I'd like to add the
notion of working sets such that users can open defined sets of editors.
This
could be handy when you have a few common editor contexts that you switch
between often. For example, I might like to define a working set of
editors
that I need when I'm working on a problem with breakpoints. It would
include
the classes in the breakpoints hierarchy, the debug event handler, and the
debug target.
Coming back to the question at hand, I'm just wondering if the base
working
set functionality (persistence, creation/management UI, etc.) will be
generic
enough for reuse or if it will be tightly coupled to this notion of one
active working set per page.
Thanks,
- Jared
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-ui-dev