Jump to: navigation, search

Difference between revisions of "E4/Resources"

< E4
Line 15: Line 15:
 
*** Case sensitive patterns for content types
 
*** Case sensitive patterns for content types
 
*** UI for Project-specific content types
 
*** UI for Project-specific content types
 +
* Some ideas that came out of the modeling session
 +
** Need a model for the resource system
 +
** Need extensible so we can add project properties that get persisted with the project
 +
*** e.g. so we can get rid of maintaining our own .cdtproject file for the CDT
 +
** EMF? Are we ready for IResource to be an EMF object?
 +
*** How is this persisted?
 +
** Using DOM/CSS type thing, we can auto generate the project explorer
 +
** Support existing API as facade?
 +
** Does EFS become simpler? necessary? if model is extensible
 +
** Flexible support - Add/excludes recorded in model

Revision as of 13:24, 22 May 2008

Flexible Resource Model

  • From Architecture Council/Minutes May 15 2008#Workspace, Resources, Content_Types:
    • Project Nesting
      • Physically: Allow .project file below another .project file be separate full-blown projects -- break iterating over outer's children when finding a project
      • Logically: Have nested project inherit Preferences from outer project
    • Namespace Resolution (multiple projects with same name in a workspace)
    • Inclusion of Files from Anywhere on the file system
    • Full Native Support for Symbolic Links (avoiding problems with cyclic symlinks)
    • Add/remove project type/nature
    • Listeners and plug-in Loading
    • Getting rid of Project for RCP (see also e4/RCP Future) -- is the notion of "Project" a plumbing or User Artifact? Where should builders etc be hung off?
    • Content Types:
      • Pattern Matching for content types rather than just file extensions + stream evaluation
      • Case sensitive patterns for content types
      • UI for Project-specific content types
  • Some ideas that came out of the modeling session
    • Need a model for the resource system
    • Need extensible so we can add project properties that get persisted with the project
      • e.g. so we can get rid of maintaining our own .cdtproject file for the CDT
    • EMF? Are we ready for IResource to be an EMF object?
      • How is this persisted?
    • Using DOM/CSS type thing, we can auto generate the project explorer
    • Support existing API as facade?
    • Does EFS become simpler? necessary? if model is extensible
    • Flexible support - Add/excludes recorded in model