| Home >> All >> org >> eclipse >> core |
Package Samples:
• org.eclipse.core.resources.ant
• org.eclipse.core.resources.team
• org.eclipse.core.resources.refresh
• org.eclipse.core.resources
• org.eclipse.core.internal.watson
• org.eclipse.core.internal.utils
• org.eclipse.core.internal.resources
• org.eclipse.core.internal.indexing
• org.eclipse.core.internal.events
• org.eclipse.core.internal.dtree
• org.eclipse.core.internal.localstore
• org.eclipse.core.internal.properties
• org.eclipse.core.internal.refresh
• org.eclipse.core.runtime.preferences
• org.eclipse.core.runtime.jobs
• org.eclipse.core.runtime.content
• org.eclipse.core.runtime
• org.eclipse.core.internal.runtime
• org.eclipse.core.internal.registry
• org.eclipse.core.internal.preferences
Classes:
• Plugin: The abstract superclass of all plug-in runtime class implementations. A plug-in subclasses this class and overrides the appropriate life cycle methods in order to react to the life cycle requests automatically issued by the platform. For compatibility reasons, the methods called for those life cycle events vary, please see the "Constructors and life cycle methods" section below. Conceptually, the plug-in runtime class represents the entire plug-in rather than an implementation of any one particular extension the plug-in declares. A plug-in is not required to explicitly specify a plug-in runtime ...
• IResourceChangeEvent: Resource change events describe changes to resources. There are currently five different types of resource change events: After-the-fact batch reports of arbitrary creations, deletions and modifications to one or more resources expressed as a hierarchical resource delta. Event type is PRE_BUILD , and getDelta returns the hierarchical delta. The resource delta is rooted at the workspace root. These events are broadcast to interested parties immediately before the first build of any kind in a workspace modifying operation. If autobuilding is not enabled, these events still occur at times when autobuild ...
• Preferences: A table of preference settings, mapping named properties to values. Property names are non-empty strings; property values can be either booleans, non-null strings, or values of one of the primitive number types. The table consists of two, sparse, layers: the lower layer holds default values for properties, and the upper layer holds explicitly set values for properties. Normal retrieval looks for an explicitly set value for the given property in the upper layer; if there is nothing for that property in the upper layer, it next looks for a default value for the given property in the lower layer; ...
• IMarker: Markers are a general mechanism for associating notes and metadata with resources. Markers themselves are handles in the same way as IResources are handles. Instances of IMarker do not hold the attributes themselves but rather uniquely refer to the attribute container. As such, their state may change underneath the handle with no warning to the holder of the handle. The Resources plug-in provides a general framework for defining and manipulating markers and provides several standard marker types. Each marker has: a type string, specifying its type (e.g. "org.eclipse.core.resources.taskmarker" ), ...
• IResource: The workspace analog of file system files and directories. There are exactly four types of resource: files, folders, projects and the workspace root. File resources are similar to files in that they hold data directly. Folder resources are analogous to directories in that they hold other resources but cannot directly hold data. Project resources group files and folders into reusable clusters. The workspace root is the top level resource under which all others reside. Features of resources: IResource objects are handles to state maintained by a workspace. That is, resource objects do not actually ...
• EvaluationResult: An evaluation result represents the result of an expression evaluation. There are exact three instances of evaluation result. They are: FALSE , TRUE and NOT_LOADED . NOT_LOADED represents the fact that an expression couldn't be evaluated since a plug-in providing certain test expressions isn't loaded yet. In addition the class implements the three operation and , or and not . The operation are defined as follows: The and operation: AND FALSE TRUE NOT_LOADED FALSE FALSE FALSE FALSE TRUE FALSE TRUE NOT_LOADED NOT_LOADED FALSE NOT_LOADED NOT_LOADED The or operation: OR FALSE TRUE NOT_LOADED FALSE ...
• DeadlockDetector: Stores all the relationships between locks (rules are also considered locks), and the threads that own them. All the relationships are stored in a 2D integer array. The rows in the array are threads, while the columns are locks. Two corresponding arrayLists store the actual threads and locks. The index of a thread in the first arrayList is the index of the row in the graph. The index of a lock in the second arrayList is the index of the column in the graph. An entry greater than 0 in the graph is the number of times a thread in the entry's row acquired the lock in the entry's column. An entry of ...
• IAdapterManager: An adapter manager maintains a registry of adapter factories. Clients directly invoke methods on an adapter manager to register and unregister adapters. All adaptable objects (that is, objects that implement the IAdaptable interface) funnel IAdaptable.getAdapter invocations to their adapter manager's IAdapterManger.getAdapter method. The adapter manager then forwards this request unmodified to the IAdapterFactory.getAdapter method on one of the registered adapter factories. Adapter factories can be registered programatically using the registerAdapters method. Alternatively, they can be registered ...
• IWorkspace: Workspaces are the basis for Eclipse Platform resource management. There is only one workspace per running platform. All resources exist in the context of this workspace. A workspace corresponds closely to discreet areas in the local file system. Each project in a workspace maps onto a specific area of the file system. The folders and files within a project map directly onto the corresponding directories and files in the file system. One subdirectory, the workspace metadata area, contains internal information about the workspace and its resources. This metadata area should be accessed only by the ...
• ILock: A lock is used to control access to an exclusive resource. Locks are reentrant. That is, they can be acquired multiple times by the same thread without releasing. Locks are only released when the number of successful acquires equals the number of successful releases. Locks are capable of detecting and recovering from programming errors that cause circular waiting deadlocks. When a deadlock between two or more ILock instances is detected, detailed debugging information is printed to the log file. The locks will then automatically recover from the deadlock by employing a release and wait strategy. ...
• IProgressMonitor: The IProgressMonitor interface is implemented by objects that monitor the progress of an activity; the methods in this interface are invoked by code that performs the activity. All activity is broken down into a linear sequence of tasks against which progress is reported. When a task begins, a beginTask(String, int) notification is reported, followed by any number and mixture of progress reports ( worked() ) and subtask notifications ( subTask(String) ). When the task is eventually completed, a done() notification is reported. After the done() notification, the progress monitor cannot be reused; ...
• IResourceRuleFactory: A resource rule factory returns scheduling rules for API methods that modify the workspace. These rules can be used when creating jobs or other operations that perform a series of modifications on the workspace. This allows clients to implement two phase commit semantics, where all necessary rules are obtained prior to executing a long running operation. Note that simple use of the workspace APIs does not require use of scheduling rules. All workspace API methods that modify the workspace will automatically obtain any scheduling rules needed to perform the modification. However, if you are aggregating ...
• PluginVersionIdentifier: Version identifier for a plug-in. In its string representation, it consists of up to 4 tokens separated by a decimal point. The first 3 tokens are positive integer numbers, the last token is an uninterpreted string (no whitespace characters allowed). For example, the following are valid version identifiers (as strings): 0.0.0 1.0.127564 3.7.2.build-127J 1.9 (interpreted as 1.9.0 ) 3 (interpreted as 3.0.0 ) The version identifier can be decomposed into a major, minor, service level component and qualifier components. A difference in the major component is interpreted as an incompatible version change. ...
• PropertyTester: Abstract superclass of all property testers. Implementation classes of the extension point org.eclipse.core.expresssions.propertyTesters must extend PropertyTester . A property tester implements the property tests enumerated in the property tester extension point. For the following property test extension <propertyTester namespace="org.eclipse.jdt.core" id="org.eclipse.jdt.core.IPackageFragmentTester" properties="isDefaultPackage" type="org.eclipse.jdt.core.IPackageFragment" class="org.eclipse.demo.MyPackageFragmentTester"> </propertyTester> the corresponding implemenation class looks ...
• Job: Jobs are units of runnable work that can be scheduled to be run with the job manager. Once a job has completed, it can be scheduled to run again (jobs are reusable). Jobs have a state that indicates what they are currently doing. When constructed, jobs start with a state value of NONE . When a job is scheduled to be run, it moves into the WAITING state. When a job starts running, it moves into the RUNNING state. When execution finishes (either normally or through cancelation), the state changes back to NONE . A job can also be in the SLEEPING state. This happens if a user calls Job.sleep() on a ...
• AliasManager: An alias is a resource that occupies the same file system location as another resource in the workspace. When a resource is modified in a way that affects the file on disk, all aliases need to be updated. This class is used to maintain data structures for quickly computing the set of aliases for a given resource, and for efficiently updating all aliases when a resource changes on disk. The approach for computing aliases is optimized for alias-free workspaces and alias-free projects. That is, if the workspace contains no aliases, then updating should be very quick. If a resource is changed in a ...
• IFileState: A previous state of a file stored in the workspace's local history. Certain methods for updating, deleting, or moving a file cause the "before" contents of the file to be copied to an internal area of the workspace called the local history area thus providing a limited history of earlier states of a file. Moving or copying a file will cause a copy of its local history to appear at the new location as well as at the original location. Subsequent changes to either file will only affect the local history of the file changed. Deleting a file and creating another one at the same path does not affect ...
• DeltaDataTree: Externally, a DeltaDataTree appears to have the same content as a standard data tree. Internally, the delta tree may be complete, or it may just indicate the changes between itself and its parent. Nodes that exist in the parent but do not exist in the delta, are represented as instances of DeletedNode . Nodes that are identical in the parent and the delta, but have differences in their subtrees, are represented as instances of NoDataDeltaNode in the delta tree. Nodes that differ between parent and delta are instances of DataDeltaNode . However, the DataDeltaNode only contains the children whose ...
• IValueVariable: A variable with a value that can be set and retrieved. The context in which a value variable is referenced does not effect the value of the variable. A value variable can be contributed by an extension or created programmatically. A contributor may optionally specify an initial value for a variable, or provide a delegate that will initialie the variable with a value. Example of a value variable contribution with an initial value, the specified variable is created with the initial value "/usr/local/foo". <extension point="org.eclipse.core.variables.valueVariables"> <variable name="FOO_HOME" ...
• WorkspaceJob: A job that makes an atomic modification to the workspace. Clients must implement the abstract method runInWorkspace instead of the usual Job.run method. After running a method that modifies resources in the workspace, registered listeners receive after-the-fact notification of what just transpired, in the form of a resource change event. This method allows clients to call a number of methods that modify resources and only have resource change event notifications reported at the end of the entire batch. A WorkspaceJob is the asynchronous equivalent of IWorkspaceRunnable Note that the workspace is ...
• BinarySignatureDescriber: A content describer for binary formats that present some simple signature at a known, fixed offset. This executable extension supports three parameters: "signature", "offset" and "required", the first one being mandatory. If the ":-" method is used, then the value is treated as the "signature". The "signature" parameter is a sequence of hex codes, one for each byte in the signature. For example, "CA FE BA BE" would be a signature for Java class files. The "offset" parameter is an integer indicating the offset where the signature's first byte is found. The "required" parameter is a boolean (default ...
• ISynchronizationContext: A file buffer manager (see IFileBufferManager uses a ISynchronizationContext in order to execute commands encapsulated as java.lang.Runnable . The synchronization context executes the Runnables according to a specific synchronization/execution policy. This could be that the given Runnable is executed in a specific thread or environment or adhere to specific timing constraints. The concrete characteristics of the policy is to be specified by the context implementer. This interface can be implemented by clients. Clients use IFileBufferManager.setSynchronizationContext(ISynchronizationContext) 55 ...
• ElementTreeDelta: Describes the differences between two element trees. Specifically, an ElementTreeDelta describes the changes that have been made to the tree returned by getParent() to obtain the tree returned by getElementTree(). ElementTreeDeltas are meant to be treated as light-weight query structures with a relatively short lifespan. Deltas cannot be serialized. ElementTreeDeltas support pluggable logic for delta calculation. By implementing the IElementComparator interface, the client can specify the kind of change (addition, removal, etc) to any given element based on the element's data. There are two ways ...
• ElementTreeIterator: A class for performing operations on each element in an element tree. For example, this can be used to print the contents of a tree. When creating an ElementTree iterator, an element tree and root path must be supplied. When the iterate() method is called, a visitor object must be provided. The visitor is called once for each node of the tree. For each node, the visitor is passed the entire tree, the object in the tree at that node, and a callback for requesting the full path of that node. Example: // printing a crude representation of the posterchild IElementContentVisitor visitor= new IElementContentVisitor() ...
• IJobManager: The job manager provides facilities for scheduling, querying, and maintaining jobs and locks. In particular, the job manager provides the following services: Maintains a queue of jobs that are waiting to be run. Items can be added to the queue using the schedule method. Allows manipulation of groups of jobs called job families. Job families can be canceled, put to sleep, or woken up atomically. There is also a mechanism for querying the set of known jobs in a given family. Allows listeners to find out about progress on running jobs, and to find out when jobs have changed states. Provides a factory ...
| Home | Contact Us | Privacy Policy | Terms of Service |