Logical Resource Support in Eclipse 3.1

item is under development

item is finished

[>3.1] item is deferred

Last Updated: October 13, 2004

This document will track the platform work in Eclipse 3.1 that is related to better support for Logical Resources (37723) in Eclipse. The problem is wide reaching and requires work from every component in Eclipse. If you want to understand progress, start by reading the Problem Statement then you can review the list of related work items

• Mapping of logical resources to physical files
  
  This item involves providing a new interface to describe a mapping: IModelElement (Jean-Michel)
  
  • Bug 32582 logical to physical mapping problem , 1 model element = 2 Files problem
    Bug 3979 [CVS Decorator] show version info works incorrectly for sub packages (1GFDIEB)
  Also, several bugs/enhancements need to be fixed to enable this support:
  
  • Bug 53217 [RCP] [Contributions] Should use new adapter manager API for obtaining objectClass when adaptable=true
  • Bug 32436 Using adapters to filter UI selections without loading plugins
  • Bug 59963 Expression language support for object contributions
    
  • Bug 76599 [Adapters] add support for transitive adapters to IAdapterManager

• Logical models can participant in file refactoring operations (Dirk + Jean-Michel)
  
  Resource modification could be delegated to the logical model. This would allow for logical models to participate in all resource modifications. The participation would be enabled using the refactoring participant APIs and new support from PlatformUI for dynamic retargetable actions.
  
  Here is a rough outline of the work that is required:
  
  • ltk.core.refactoring should be split to remove IResource dependency from core compoment.
  • ltk.ui.refactoring needs to remove dependency on jdt.core and jdt.ui
  • CVS team to evaluate converting actions into operations so that plug-ins can participate.
  • Enable dynamic re-targetable actions in platform ui based on a criteria (e.g. nature)
  • Allow logical models to provide standard refactoring operations for resources that it owns.

• Logical model aware rendering (used by refactoring preview, sync view, search) (Dirk+Jean-Michel)
  
  Start by investigating static rendering first (showing the model without supporting updates when the logical model changes). This is good for the refactoring preview and search. Can possible use WorkbenchAdapter mechanism. No support for model specific actions in the context menu
  
  Dynamic rendering with action contributions is much more complicated, post 3.1?
  

• Generalizing the resource navigator (Billy Biggs)
  
  Plug-ins copy the resource navigator/packages explorer to build their own logical model navigators.
  what pieces of these navigators are generally useful re-usable components?
  See platform ui page for more details on this work item.