Community
Participate
Working Groups
ILocalWorkingSetManager marked as under construction
Nick, JDT/UI makes use of the ILocalWorkingSetManager interface. In addition to removing the under construction clause we should make a reference to IWorkbench#createLocalWorkingSet which is the factory method to create a working set. Additional API problems I found: IWorkingSetManager#dispose: is under construction as well. The method is in use and we should keep it. IWorkingSetManager#createWorkingSetNewWizard: can be removed. The method got introduced in 3.1 and is now deprecatred.
Dirk, what is the main distinction between an ILocalWorkingSetManager and an IWorkingSetManager again? The current Javadoc doesn't really spell this out clearly. When should I use one vs. the other? If you could provide a patch to the Javadoc clarifying its role, that would be great.
I've fixed up the issues in comment 0 and comment 1.
Also removed the "under construction" comment from IWorkbench.createLocalWorkingSetManager(). Scanned for other "experimental" or "under construction" comments in this area, and found none.
Nick, here an updated version of the comment. Creating a patch requires checking out ui.workbench.... /** * A local working set manager can be used to manage a set of * working sets independent from the working sets managed by * the workspace wide working set manager. A local working set * manager can be saved and restored using the methods <code>saveState</code> * and <code>restoreState</code>. A new local working set manager can be created * using {@link org.eclipse.ui.IWorkbench#createLocalWorkingSetManager()}. * <p> * This interface is not intended to be implemented or extended by clients. * </p> * * @see org.eclipse.ui.IWorkbench#createLocalWorkingSetManager() * @since 3.1 */
Created attachment 19404 [details] Patch for Javadoc changes Thanks Dirk. I made some slight tweaks to the wording. Patch applied.
Fixed.
Verified in 3.1 RC2.