| Home >> All >> org >> eclipse >> ltk >> internal |
Package Samples:
• org.eclipse.ltk.internal.ui.refactoring.util
• org.eclipse.ltk.internal.ui.refactoring
• org.eclipse.ltk.internal.core.refactoring
Classes:
• Assert: Assert is useful for for embedding runtime sanity checks in code. The predicate methods all test a condition and throw some type of unchecked exception if the condition does not hold. Assertion failure exceptions, like most runtime exceptions, are thrown when something is misbehaving. Assertion failures are invariably unspecified behavior; consequently, clients should never rely on these being thrown (and certainly should not being catching them specifically).
• Assert: Assert is useful for for embedding runtime sanity checks in code. The predicate methods all test a condition and throw some type of unchecked exception if the condition does not hold. Assertion failure exceptions, like most runtime exceptions, are thrown when something is misbehaving. Assertion failures are invariably unspecified behavior; consequently, clients should never rely on these being thrown (and certainly should not being catching them specifically).
• ExceptionHandler: The default exception handler shows an error dialog when one of its handle methods is called. If the passed exception is a CoreException an error dialog pops up showing the exception's status information. For a InvocationTargetException a normal message dialog pops up showing the exception's message. Additionally the exception is written to the platform log.
• AssertionFailedException: AssertionFailedException is a runtime exception thrown by some of the methods in Assert . This class is not declared public to prevent some misuses; programs that catch or otherwise depend on assertion failures are susceptible to unexpected breakage when assertions in the code are added or removed.
• AssertionFailedException: AssertionFailedException is a runtime exception thrown by some of the methods in Assert . This class is not declared public to prevent some misuses; programs that catch or otherwise depend on assertion failures are susceptible to unexpected breakage when assertions in the code are added or removed.
• WorkbenchRunnableAdapter: An IRunnableWithProgress that adapts and IWorkspaceRunnable so that is can be executed inside IRunnableContext . OperationCanceledException thrown by the adapted runnable are caught and re-thrown as a InterruptedException .
• ChangeElementContentProvider: A default content provider to present a hierarchy of IChange objects in a tree viewer. TODO should remove dependency to JDT/Core (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=61312)
• ViewerPane: A ViewerPane is a convenience class which installs a CLabel and a Toolbar in a ViewForm .
• PreviewWizardPage: Presents the changes made by the refactoring. Consists of a tree of changes and a compare viewer that shows the differences.
• ChangeElement: Instances of ChangeElement are used to present IChange object as nodes in a tree.
• PseudoJavaChangeElement: TODO should remove dependency to JDT/Core (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=61312)
• Strings: Helper class to provide String manipulation functions not available in standard JDK.
• ErrorWizardPage: Presents the list of failed preconditions to the user
• ListenerList: Local copy of org.eclipse.jface.ListenerList
• FinishResult: Enumeration representing the finish result
• UndoManager: Default implementation of IUndoManager.
• RefactoringWizardDialog: A dialog to host refactoring wizards.
• TextChanges: Helper class for text file changes.
• UndoDocumentChange
• BufferValidationState
• DirtyBufferValidationState
• SavedBufferValidationState
| Home | Contact Us | Privacy Policy | Terms of Service |