Remote Systems
v6.4.1

com.ibm.etools.systems.editor.internal
Class SystemAutosaveController

java.lang.Object
  extended bycom.ibm.etools.systems.editor.internal.SystemAutosaveController

public class SystemAutosaveController
extends Object

Singleton class for managing autosaves. Possible future enhancment: cancel (do we want to enable cancel on autosave?)


Field Summary
static String copyright
           
 
Method Summary
 void addEditor(SystemTextEditor editor)
          Add a new editor to autosave list.
 void deleteBackup(SystemTextEditor editor)
          Helper method for deleteing autoave backups
 File getBackupFile(IFile file)
          Helper method for building autosave pathname for an IFile
static SystemAutosaveController getInstance()
          Returns the singleton isntance.
 boolean isAutosaveStale(IFile file)
          Test if the autosave backup is from a previous version of the file
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

copyright

public static final String copyright
See Also:
Constant Field Values
Method Detail

getInstance

public static SystemAutosaveController getInstance()
Returns the singleton isntance.


addEditor

public void addEditor(SystemTextEditor editor)
Add a new editor to autosave list. If this is the first editor added to the list then the autosave daemon thread is started.


getBackupFile

public File getBackupFile(IFile file)
Helper method for building autosave pathname for an IFile


deleteBackup

public void deleteBackup(SystemTextEditor editor)
Helper method for deleteing autoave backups


isAutosaveStale

public boolean isAutosaveStale(IFile file)
Test if the autosave backup is from a previous version of the file


Remote Systems
v6.4.1

Copyright © 2005 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.