Workspace3.7

Workspace 3.7 Development Plan draft. Some items listed below can end up in the official 3.7 component plan. Some items that can't be applied to 3.x can end up in e4.

If you are not a member of the Platform Workspace Team and you want to add your work to the plan, please follow the steps below.

1. Update an appropriate section with your request/idea/issue. If no section matches your issue, add a new section.
2. Find a bug in the bugzilla describing the issue and link it next to your entry.
3. Place your contact details (name, bugzilla id, email) next to your item.

Remember

1. Add an item to the draft plan, only if you think you can work on it.
2. Adding an item to the official plan is a strong commitment!
3. The Platform Workspace team reserves the right to decide what is published on the official dev plan page.

To give you an idea what is the official dev plan, see the official 3.6 component plan.

Resources

Content Type detection should support MIME type and charset retrieved from file store

See bug 305481 for proposal and implementation.

Linked Resources and Virtual folders

• The PathVariableSelectionDialog should support building argumented path variables (such as ENVIRONMENT) bug 305005
• The Workspace Path Variable Manager should support variables/macros bug 312760
• IResource methods that causes the .project file to be written need to scale with large projects bug 271912

Compare Framework

• [Edit] Use separate editors for comparisons bug 278005
• [Edit] Investigate ways of improving how Compare Editor works in multi-threading environment bug 304693
• Regressions introduced by SaveablesCompareEditorInput bug 275153

Team

• [Apply Patch] Compare current workspace against a patch bug 198149 <- use case (Dani P2)
• Import PSF from URL bug 162608

Mapping between Repository Providers and Linked/Virtual Folders

Currently in Eclipse, repository providers are mapped to a project. This works well in many cases but is problematic if a project contains links to resources that are coming from other repositories (e.g. Git vs. CVS).

The proposal is to provide a capability to register a repository provider (programmatically and/or via UI) for a linked resource. All team-/repository-related functionality (Team menu, File Modification Validator, Move Delete Hook, Scheduling Rules Factory) should be delegated to the registered provider/hooks.

The request has been formulated as part of initial 4.0 requirement list. See [1]. The bug 313096 should be used to discuss the details.

Contact: Eduard Bartsch, SAP AG

CVS

• Exception when trying to commit a lot of projects bug 299538
• Full support for links and virtual folder in CVS bug 41929