Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "CDT/Archive/planning/4.0"

< CDT‎ | Archive‎ | planning
m (changed formatting)
m (Jonah.kichwacoders.com moved page CDT/planning/4.0 to CDT/Archive/planning/4.0)
 
(17 intermediate revisions by 9 users not shown)
Line 1: Line 1:
=== Indexing ===
 
  
* Support headless creation of indexes (PDOM), and import of these prebuilt indexes into user workspaces.
+
{{warning|Note: The contents of this page refer to planning documents of past Eclipse CDT releases. See [[CDT/planning]] for current information. }}
  
 +
[[Category:CDT:Archive]]
 +
 +
=== Indexing ===
 +
 +
* Support headless creation of indexes (PDOM), and import of these prebuilt indexes into user workspaces. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=074433 bug 74433].
 +
** Enable pdom index files to be relocatable (contain relative or symbolic paths)
 +
* Refactor the parser to allow it to be deployed as a standalone JAR file if so desired. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=151846 bug 151846]
 +
* Refactor the indexer to allow it to be deployed as a standalone JAR file if so desired. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158975 bug 158975]
 +
* Refactor the indexer to remove hard dependencies on having an Eclipse project. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=151847 bug 151847]
 +
* Allow customizability of which parser to run on particular projects/files/resources. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=151850 bug 151850]
  
 
=== UI ===
 
=== UI ===
Line 19: Line 28:
  
 
==== New Views ====
 
==== New Views ====
* '''Include Browser''': Visualize the include relations among files in a tree. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=142149 Bug 142149]
+
* '''Include Browser''': Visualize the include relations among files in a tree as proposed in [https://bugs.eclipse.org/bugs/show_bug.cgi?id=142149 bug 142149]
* '''Call Hierarchy''': Explore call-graphs by means of a tree. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=48212 Bug 48212]
+
* '''Call Hierarchy''': Explore call-graphs by means of a tree as proposed in [https://bugs.eclipse.org/bugs/show_bug.cgi?id=48212 bug 48212].
* Reintroduce '''Type Hierarchy''': Present inheritance relations and members of types. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=108879 Bug 108879] <br>The implementation will consider the following bugs: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=48213 bug 48213], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=70246 bug 70246], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=71943 bug 71943], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=87815 bug 87815], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=94197 bug 94197], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=99833 bug 99833], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=99835 bug 99835], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=100655 bug 100655], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=108879 bug 108879] and optionally also [https://bugs.eclipse.org/bugs/show_bug.cgi?id=73904 bug 73904].
+
* Reintroduce '''Type Hierarchy''': Present inheritance relations and members of types. This is proposed in [https://bugs.eclipse.org/bugs/show_bug.cgi?id=142189 bug 142189]. <br>The implementation will also consider [https://bugs.eclipse.org/bugs/show_bug.cgi?id=48213 bug 48213], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=70246 bug 70246], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=71943 bug 71943], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=87815 bug 87815], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=94197 bug 94197], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=99833 bug 99833], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=99835 bug 99835], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=100655 bug 100655], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=108879 bug 108879] and optionally also [https://bugs.eclipse.org/bugs/show_bug.cgi?id=73904 bug 73904].
 +
 
 +
 
 +
=== New Project Model ===
 +
The main goal of the New Project Model is to increase the CDT usability, tool-integrator support and multi language support.
 +
 
 +
See the [https://bugs.eclipse.org/bugs/attachment.cgi?id=46637 New Project Model Design] attached to [https://bugs.eclipse.org/bugs/show_bug.cgi?id=115935 bug 115935] for more detail.
 +
 
 +
=== Debugger ===
 +
 
 +
==== CDI ====
 +
How to make the CDI model flexible and extensible [[Proposals]]. See also [https://bugs.eclipse.org/bugs/show_bug.cgi?id=162080 bug 162080].
 +
 
 +
==== Further improvements to GDB GUI ====
 +
TBD...

Latest revision as of 13:57, 22 January 2020

Warning2.png
Note: The contents of this page refer to planning documents of past Eclipse CDT releases. See CDT/planning for current information.

Indexing

  • Support headless creation of indexes (PDOM), and import of these prebuilt indexes into user workspaces. bug 74433.
    • Enable pdom index files to be relocatable (contain relative or symbolic paths)
  • Refactor the parser to allow it to be deployed as a standalone JAR file if so desired. bug 151846
  • Refactor the indexer to allow it to be deployed as a standalone JAR file if so desired. bug 158975
  • Refactor the indexer to remove hard dependencies on having an Eclipse project. bug 151847
  • Allow customizability of which parser to run on particular projects/files/resources. bug 151850

UI

C/C++ Editor

  • Support indent width independent of tab width. Allow to specify indent width independent of tab width to support mixed-mode indentation as already requested by bug 53994 and bug 92036.
  • Default formatter. Implement a (simple) default formatter/indenter. bug 95274
  • Text Drag and Drop. Implement Text Drag and Drop for the editor. bug 78677
    Note: This may become obsolete if Eclipse platform implements it in 3.3. See also bug 11624.
  • View non-printable characters. Provide a command and toolbar button to enable visualization of non-printable characters in the editor (CR, LF, TAB, SPACE). bug 140333
    Note: This may become obsolete if Eclipse platform implements it in 3.3. See also bug 22712.
  • Auto-save. Implement an option to regularly save dirty editor buffers to the Eclipse local history as a backup mechanism. bug 140334
    See also Eclipse platform bug 34076.
  • Semantic highlighting. Colorize definitions and declarations of various C/C++ elements: function, variable, type, enum, etc. bug 140335
  • Inactive code highlighting. Highlight lines of code which are inactive (ie. which are excluded by conditional preprocessor directives) in the current scanner configuration. bug 81511

CView

  • Common Navigator extensions. Adopt the new Common Navigator (CN) framework and create CDT specific extensions to plug the content and functionality of the C/C++ Projects view (aka CView) into any Common Navigator view. The extensions will be initially contributed to the new general purpose "Project Explorer", which serves as a playground for early adopters of the technology (like JDT). This should also help to stabilize and improve the CN framework by providing feedback and bug reports. bug 140337

New Views


New Project Model

The main goal of the New Project Model is to increase the CDT usability, tool-integrator support and multi language support.

See the New Project Model Design attached to bug 115935 for more detail.

Debugger

CDI

How to make the CDI model flexible and extensible Proposals. See also bug 162080.

Further improvements to GDB GUI

TBD...

Back to the top