Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
TM Future Planning
Revision as of 06:02, 5 July 2006 by Mober.at+eclipse.gmail.com (Talk | contribs)
Collect input for the planning process for RSE 2.0 next year. These are just ideas for now, detailed planning will follow in autum. Bugzilla entries should be used for tracking requests as soon as the feature description is sufficiently clear and there is some group supporting a feature.
RSE 2.0 will be released with Eclipse 3.3 - presumably end of June 2007. An Eclipse 3.3 draft plan is not yet available.
Themes and Priorities
- Adopt Platform Changes - RSE should adopt Eclipse Platform concepts wherever possible. For instance:
- Use Common Navigator for the Remote Systems View
- Support Content Assist for Remote Search / Regular Expression field
- Clarify Usage / Adoption of EFS
- Use existing Platform Extension Points for popup menus, property pages etc.
- Integrate Content Types / RSE File Types
- Collaborate with Platform/Team to re-use jsch "officially"
- Add a Terminal View with Terminal Emulation (in addition to the current Commands view)
- Add outstanding features from RSE 7.0
- User Actions
- Compile Commands
- Import/Export
- Support Shell Pattern Matching on the client
- Support pattern matching, compiler error navigation and code completion in ssh shells and any other contributed shell
- Add Autodetect as defined by the Autodetect group bug 140320, bug 142493
- Add Multicore capabilities to the RSE Tree
- Support target groups as defined by the Connection Groups initiative
- Define a standard for remote system properties as defined by the Spirit group - bug 146090
- Integrate improved Launching as defined by the Launching group