Strawman Proposal

Filesystem Layer

IBM/McQ - Szymon wants to be able to deal with System/i or System/z file systems: could have 2 aliases for the same directory, but depending on the path going there, one could be case sensitive, the other not

Add symbolic link awareness

Making the file system layer more powerful, writing providers becomes more difficult. Might want to have superclasses with default implementations for some commonly needed functionality

ChrisR: Want to deal with files that live outside the Resource tree -- may want to express stateful things (such as caching) to such files as well

Some Metadata (Markers) should live on the filesystem layer

On what items are editors opened on: IResources or Files? Likely Files...

Martin: What is the borderline between Resources and Files? Pushing down a lot of functionality into the file system.

File system always is an accurate view of the world, not backed by an in-memory tree.

Resource deltas at project level only. For direct manipulations on the file system, invent some additional notification mechanism (between project and FS) - perhaps similar to RefreshMonitor. Deltas need to know the state before the change happened.