Examples of IWorkspace

com.sas.iom.SAS.IWorkspace
com.subgraph.vega.api.model.IWorkspace
org.apache.flex.compiler.workspaces.IWorkspace
Implementations maintain a collection of ICompilerProject's in the workspace and state that it is shared across multiple ICompilerProject's.
This interface extends {@link IFileSpecificationGetter} so that compilationunits that do not wish to virtualize access to the file system can just use a workspace as their {@link IFileSpecificationGetter}.
org.eclipse.core.resources.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 sub-directory, the workspace metadata area, contains internal information about the workspace and its resources. This metadata area should be accessed only by the Platform or via Platform API calls.

Workspaces add value over using the file system directly in that they allow for comprehensive change tracking (through IResourceDelta s), various forms of resource metadata (e.g., markers and properties) as well as support for managing application/tool state (e.g., saving and restoring).

The workspace as a whole is thread safe and allows one writer concurrent with multiple readers. It also supports mechanisms for saving and snapshooting the current resource state.

The workspace is provided by the Resources plug-in and is automatically created when that plug-in is activated. The default workspace data area (i.e., where its resources are stored) overlap exactly with the platform's data area. That is, by default, the workspace's projects are found directly in the platform's data area. Individual project locations can be specified explicitly.

The workspace resource namespace is always case-sensitive and case-preserving. Thus the workspace allows multiple sibling resources to exist with names that differ only in case. The workspace also imposes no restrictions on valid characters in resource names, the length of resource names, or the size of resources on disk. In situations where one or more resources are stored in a file system that is not case-sensitive, or that imposes restrictions on resource names, any failure to store or retrieve those resources will be propagated back to the caller of workspace API.

This interface is not intended to be implemented by clients.

Workspaces implement the IAdaptable interface; extensions are managed by the platform's adapter manager.

Examples of org.eclipse.core.resources.IWorkspace

    public void stop(final BundleContext context) throws Exception {
        stopping = true;
        try {
            ErlideEventTracer.getInstance().dispose();


            final IWorkspace workspace = ResourcesPlugin.getWorkspace();
            workspace.removeSaveParticipant(getBundle().getSymbolicName());


            if (core != null) {
                core.stop();
            }
        } finally {

View Full Code Here

Examples of org.eclipse.core.resources.IWorkspace

    @Override
    public void start(final BundleContext context) throws Exception {
        super.start(context);
        ErlLogger.debug("Core starting");


        final IWorkspace workspace = ResourcesPlugin.getWorkspace();
        final IWorkspaceRoot workspaceRoot = workspace.getRoot();
        ErlideEventTracer.getInstance().traceSession(
                workspaceRoot.getLocation().toPortableString());


        final IExtensionRegistry extensionRegistry = Platform.getExtensionRegistry();
        final String logDir = workspaceRoot.getLocation().toPortableString();

View Full Code Here

Examples of org.eclipse.core.resources.IWorkspace

  }
  
  public void create(final URI location, final IProgressMonitor monitor) {
    try {
      IHandle _parent = this.getParent();
      final IWorkspace workspace = ((ErlModel) _parent).getWorkspace();
      workspace.run(
        new IWorkspaceRunnable() {
          public void run(final IProgressMonitor monitor0) {
            try {
              IProgressMonitor _elvis = null;
              if (monitor0 != null) {
                _elvis = monitor0;
              } else {
                NullProgressMonitor _nullProgressMonitor = new NullProgressMonitor();
                _elvis = _nullProgressMonitor;
              }
              final IProgressMonitor monitor = _elvis;
              try {
                monitor.beginTask("", 4);
                final IProjectDescription description = workspace.newProjectDescription(ErlProject.this.name);
                description.setLocationURI(location);
                SubProgressMonitor _subProgressMonitor = new SubProgressMonitor(monitor, 1);
                ErlProject.this.workspaceProject.create(description, _subProgressMonitor);
                SubProgressMonitor _subProgressMonitor_1 = new SubProgressMonitor(monitor, 1);
                ErlProject.this.workspaceProject.open(_subProgressMonitor_1);

View Full Code Here

Examples of org.eclipse.core.resources.IWorkspace

import org.eclipse.core.runtime.IPath;


@SuppressWarnings("all")
public class PathResolver {
  public Collection<IPath> resolvePaths(final Collection<IPath> paths) {
    IWorkspace _workspace = ResourcesPlugin.getWorkspace();
    final IPathVariableManager pathVariableManager = _workspace.getPathVariableManager();
    int _size = paths.size();
    final List<IPath> result = Lists.<IPath>newArrayListWithCapacity(_size);
    for (final IPath path : paths) {
      {
        URI _uRI = URIUtil.toURI(path);

View Full Code Here

0 1 2 3 4 5

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.