All Packages from org.eclipse.jface.window.* to org.eclipse.jface.wizard.*

Home >> All >> org >> eclipse >> jface

Page 1 2

•

Package Samples:

• org.eclipse.jface.wizard
• org.eclipse.jface.window

Classes:

• IDocument: An IDocument represents text providing support for text manipulation positions partitions line information document change listeners document partition change listeners A document allows to set its content and to manipulate it. For manipulation a document provides the replace method which substitutes a given string for a specified text range in the document. On each document change, all registered document listeners are informed exactly once. Positions are stickers to the document's text that are updated when the document is changed. Positions are updated by IPositionUpdater s. Position updaters ...
• ITextViewer: A text viewer connects a text widget with an IDocument . The document is used as the widget's text model. It supports the following kinds of listeners: view port listeners to inform about changes of the viewer's view port text listeners to inform about changes of the document and the subsequent viewer change text input listeners to inform about changes of the viewer's input document. A text viewer supports a set of configuration options and plug-ins defining its behavior: undo manager double click behavior auto indentation text hover Installed plug-ins are not automatically activated. Plug-ins ...
• DelegatingDragAdapter: A DelegatingDragAdapter is a DragSourceListener that maintains and delegates to a set of TransferDragSourceListener s. Each TransferDragSourceListener can then be implemented as if it were the DragSource's only DragSourceListener. When a drag is started, a subset of all TransferDragSourceListeners is generated and stored in a list of active listeners. This subset is calculated by forwarding true . The DragSource 's set of supported Transfer types ({@link DragSource#setTransfer(Transfer[])}) is updated to reflect the Transfer types corresponding to the active listener subset. If and when {@link ...
• DelegatingDropAdapter: A DelegatingDropAdapter is a DropTargetListener that maintains and delegates to a set of TransferDropTargetListener s. Each TransferDropTargetListener can then be implemented as if it were the DropTarget's only DropTargetListener . On dragEnter , dragOperationChanged , dragOver and drop , a current listener is obtained from the set of all TransferDropTargetListeners . The current listener is the first listener to return true for TransferDropTargetListener.isEnabled(DropTargetEvent) 55 . The current listener is forwarded all DropTargetEvents until some other listener becomes the current listener, ...
• IContentFormatterExtension: Extension interface for IContentFormatter . Updates the content formatter to be able to pass IFormattingContext context objects to IFormattingStrategyExtension objects operating in context based mode. Clients using context based formatting call the method format(IDocument, IFormattingContext) with a properly initialized formatting context. The formatting context must be set up according to the desired formatting mode: For whole document formatting set the property FormattingContextProperties.CONTEXT_DOCUMENT 55 . This is equivalent to setting FormattingContextProperties.CONTEXT_REGION 55 with a ...
• Window: A JFace window is an object that has no visual representation (no widgets) until it is told to open. Creating a window involves the following steps: creating an instance of a concrete subclass of Window creating the window's shell and widget tree by calling create (optional) assigning the window to a window manager using WindowManager.add (optional) opening the window by calling open Opening the window will create its shell and widget tree if they have not already been created. When the window is closed, the shell and widget tree are disposed of and are no longer referenced, and the window is automatically ...
• ICompletionProposal: The interface of completion proposals generated by content assist processors. A completion proposal contains information used to present the proposed completion to the user, to insert the completion should the user select it, and to present context information for the chosen completion once it has been inserted. In order to provide backward compatibility for clients of ICompletionProposal , extension interfaces are used to provide a means of evolution. The following extension interfaces exist: ICompletionProposalExtension since version 2.0 introducing the following functions: handling of trigger ...
• IContentAssistant: An IContentAssistant provides support on interactive content completion. The content assistant is a org.eclipse.jface.text.ITextViewer add-on. Its purpose is to propose, display, and insert completions of the content of the text viewer's document at the viewer's cursor position. In addition to handle completions, a content assistant can also be requested to provide context information. Context information is shown in a tool tip like popup. As it is not always possible to determine the exact context at a given document offset, a content assistant displays the possible contexts and requests the user ...
• IVerticalRuler: This interface defines a visual component which may serve text viewers as an annotation presentation area. Implementers of this interface have to define the presentation modus. This can either depend on the connected viewer's view port or not. If the modus is view port dependent the ruler only shows those annotations that are attached to document regions that are visible in the view port. If independent, the presented annotations can also be attached to invisible document regions. This interfaces comprises three contracts: The vertical ruler retrieves the annotations it presents from an annotation ...
• IReconcileStep: A reconcile step is one of several steps of a reconcile strategy that consists of several steps. This relationship is not coded into an interface but should be used by clients who's reconcile strategy consists of several steps. If a reconcile step has an input model it will compute the correct model for the next step in the chain and set the next steps input model before reconcile gets called on that next step. After the last step has reconciled the reconcile result array gets returned to the previous step. Each step in the chain adapts the result to its input model and returns it to its previous ...
• IPreferenceStore: The IPreferenceStore interface represents a table mapping named preferences to values. If there is no value for a given name, then that preferences's default value is returned; and if there is no default value for that preference, then a default-default value is returned. The default-default values for the primitive types are as follows: boolean = false double = 0.0 float = 0.0f int = 0 long = 0 String = "" (the empty string) Thus a preference store maintains two values for each of a set of names: a current value and a default value. The typical usage is to establish the defaults for all known ...
• IPresentationReconciler: An IPresentationReconciler defines and maintains the representation of a text viewer's document in the presence of changes applied to the document. An IPresentationReconciler is a ITextViewer add-on. The presentation reconciler keeps track of changes applied to the text viewer. It sends each change to presentation damagers which are registered for the content types of the regions in which the change occurred. The presentation reconciler passes the computed damage to presentation repairer which construct text presentations. When applied to the presentation reconciler's text viewer, those text presentations ...
• IInformationControl: Interface of a control presenting information. The information is given in the form of an input object. It can be either the content itself or a description of the content. The specification of what is required from an input object is left to the implementers of this interface. The information control may not grab focus when made visible using setVisible(true) . In order to provide backward compatibility for clients of IInformationControl , extension interfaces are used as a means of evolution. The following extension interfaces exist: IInformationControlExtension since version 2.0 introducing ...
• AbstractReconciler: Abstract implementation of IReconciler . The reconciler listens to input document changes as well as changes of the input document of the text viewer it is installed on. Depending on its configuration it manages the received change notifications in a queue folding neighboring or overlapping changes together. The reconciler processes the dirty regions as a background activity after having waited for further changes for the configured duration of time. A reconciler is started using the install(ITextViewer) 55 method. As a first step initialProcess() 55 is executed in the background. Then, the reconciling ...
• ISourceViewer: In addition to the text viewer functionality a source viewer supports: visual annotations based on an annotation model visual range indication management of text viewer add-ons explicit configuration It is assumed that range indication and visual annotations are shown inside the same presentation area. There are no assumptions about whether this area is different from the viewer's text widget. As the visibility of visual annotations can dynamically be changed, it is assumed that the annotation presentation area can dynamically be hidden if it is different from the text widget. In order to provide ...
• IReconciler: An IReconciler defines and maintains a model of the content of the text viewer's document in the presence of changes applied to this document. An IReconciler is a org.eclipse.jface.text.ITextViewer add-on. Reconcilers are assumed to be asynchronous, i.e. they allow a certain temporal window of inconsistency between the document and the model of the content of this document. Reconcilers have a list of IReconcilingStrategy objects each of which is registered for a particular document content type. The reconciler uses the strategy objects to react on the changes applied to the text viewer's document. ...
• ITextViewerExtension2: Extension interface for ITextViewer . It provides text presentation invalidation enhancements text hover management enhancements a replacement for auto indent strategies support for custom painters It extends the means for text presentation invalidation by allowing a specific region of the presentation to get invalidated. It replaces ITextViewer.setTextHover(ITextHover, String) 55 with a new method that allows to specify state masks for a better control of the hover behavior. An IAutoEditStrategy is a generalization of the original IAutoIndentStrategy . Auto edit strategies can be arranged in a ...
• IDocumentPartitioner: A document partitioner divides a document into a set of disjoint text partitions. Each partition has a content type, an offset, and a length. The document partitioner is connected to one document and informed about all changes of this document before any of the document's document listeners. A document partitioner can thus incrementally update on the receipt of a document change event. In order to provided backward compatibility for clients of IDocumentPartitioner , extension interfaces are used to provide a means of evolution. The following extension interfaces exist: IDocumentPartitionerExtension ...
• IPainter: A painter is responsible for creating, managing, updating, and removing visual decorations on an ITextViewer 's text widget. Examples are the highlighting of the caret line, the print margin, or the highlighting of matching peer characters such as pairs of brackets. Clients may implement this interface. Painters should be registered with a PaintManager . The paint manager tracks several classes of events issued by an ITextViewer and reacts by appropriately invoking the registered painters. Painters are either active or inactive. Usually, painters are initially inactive and are activated by the ...
• ProjectionDocument: A ProjectionDocument represents a projection of its master document. The contents of a projection document is a sequence of fragments of the master document, i.e. the projection document can be thought as being constructed from the master document by not copying the whole master document but omitting several ranges of the master document. The projection document indirectly utilizes its master document as ITextStore by means of a ProjectionTextStore . The content of a projection document can be changed in two ways. Either by a text replace applied to the master document or the projection document. ...
• AbstractDocument: Abstract default implementation of IDocument and its extension interfaces IDocumentExtension , IDocumentExtension2 , IDocumentExtension3 , as well as IRepairableDocument . An AbstractDocument supports the following implementation plug-ins: a text store implementing ITextStore for storing and managing the document's content, a line tracker implementing ILineTracker to map character positions to line numbers and vice versa The document can dynamically change the text store when switching between sequential rewrite mode and normal mode. This class must be subclassed. Subclasses must configure which ...
• IReconcilingStrategy: A reconciling strategy is used by an reconciler to reconcile a model based on text of a particular content type. It provides methods for incremental as well as non-incremental reconciling. If a reconcile strategy consists of several steps between which model transformation is desired the each step should implement IReconcileStep . In order to provide backward compatibility for clients of IReconcilingStrategy , extension interfaces are used to provide a means of evolution. The following extension interfaces exist: IReconcilingStrategyExtension since version 2.0 introducing the following functions: ...
• IInformationPresenter: An information presenter shows information available at the text viewer's current document position. An IInformationPresenter is a org.eclipse.jface.text.ITextViewer add-on. An information presenters has a list of IInformationProvider objects each of which is registered for a particular document content type. The presenter uses the strategy objects to retrieve the information to present. In order to provide backward compatibility for clients of IInformationPresenter , extension interfaces are used to provide a means of evolution. The following extension interfaces exist: IInformationPresenterExtension ...
• ContentFormatter: Standard implementation of IContentFormatter . The formatter supports two operation modes: partition aware and partition unaware. In the partition aware mode, the formatter determines the partitioning of the document region to be formatted. For each partition it determines all document positions which are affected when text changes are applied to the partition. Those which overlap with the partition are remembered as character positions. These character positions are passed over to the formatting strategy registered for the partition's content type. The formatting strategy returns a string containing ...
• IContributionManager: A contribution manager organizes contributions to such UI components as menus, toolbars and status lines. A contribution manager keeps track of a list of contribution items. Each contribution item may has an optional identifier, which can be used to retrieve items from a manager, and for positioning items relative to each other. The list of contribution items can be subdivided into named groups using special contribution items that serve as group markers. The IContributionManager interface provides general protocol for adding, removing, and retrieving contribution items. It also provides convenience ...

Home | Contact Us | Privacy Policy | Terms of Service