Community
Participate
Working Groups
Eclipse 3.5 org.eclipse.ltk.core.refactoring.Change should support "mandatory" semantics, meaning that a mandatory change cannot be disabled by the user. Rationale: Change is the smallest unit of modification in the refactoring framework. Often it is also used to present the structure of the refactoring to the user on the preview page. In our case, we would like to show the structure of the changes, but the entire change tree (or a certain subset of the change nodes) are mandatory, i.e. may not be disabled by the user. It would of course be possible to prevent the user from continuing the refactoring once the mandatory changes are disabled. However, it would be much nicer to not show those changes as optional. Since the preview page of RefactoringWizard is hard-wired, it is not possible to just replace that page. Selectively leaving out the checkboxes for tree elements may be hard using CheckboxTreeViewer. Alternatively, the entire change tree could be marked as mandatory and a normal TreeViewer used?
Bug 259092 and bug 203943 request API to disable (i.e. "lock") individual check boxes. We should first see whether we can go that way. If we can't, we can add a global option to remove the checkboxes from the tree. > It would of course be possible to prevent the user from continuing the > refactoring once the mandatory changes are disabled. Rather than disabling the refactoring, you could also just enable the mandatory changes silently. I think you could already write a subclass of CompositeChange, mark it as synthetic in the constructor, and extend isValid(..) to enable all necessary changes again.
