1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-04-21 21:52:10 +02:00
cdt/NewAndNoteworthy
Jonah Graham ae9f145856
Always show CDT Debug Preference Pages (#974)
The CDT Debug Activites was originally added when we had two
distinct debuggers in CDT, the DSF one and the CDI one. To
eliminate confusion the preferences for the respective
debug infrastructures were only displayed if users actually
ran such a debug session.

Now with just one debug infrastructure, we should always display
the preference pages. It also removes some confusion that some
preference pages weren't visible until after you started the
debug session. So for example, users couldn't turn on or off
a bunch of default settings until after creating and launching
a debug session.

I have left the enableActivity call in GdbLaunchDelegate in
case any extenders were hiding some of their UI behind that key.

The only exception in the above is the View Performance preference
page which was misplaced in the top level Run/Debug preference
tree, even though it is CDT specific. That preference page has
been re-parented to C/C++ -> Debug

Fixes https://github.com/eclipse-cdt/cdt/issues/972
2025-01-06 12:46:55 -05:00
..
images Add GNU archiver other objects option to N&N 2024-11-03 08:40:53 +00:00
OlderReleases Migrate New and Noteworthy from Wiki to GitHub 2022-10-02 20:46:56 -04:00
CDT-10.0.md Update wiki.eclipse links to their new locations 2022-11-09 10:56:55 -05:00
CDT-10.1.md Update wiki.eclipse links to their new locations 2022-11-09 10:56:55 -05:00
CDT-10.2.md Move https://wiki.eclipse.org/CDT/StandaloneDebugger to GitHub 2022-11-09 10:56:55 -05:00
CDT-10.3.md Migrate New and Noteworthy from Wiki to GitHub 2022-10-02 20:46:56 -04:00
CDT-10.4.md Migrate New and Noteworthy from Wiki to GitHub 2022-10-02 20:46:56 -04:00
CDT-10.5.md Migrate New and Noteworthy from Wiki to GitHub 2022-10-02 20:46:56 -04:00
CDT-10.6.md Update wiki.eclipse links to their new locations 2022-11-09 10:56:55 -05:00
CDT-10.7.md Migrate New and Noteworthy from Wiki to GitHub 2022-10-02 20:46:56 -04:00
CDT-11.0.md Add lack Dwarf5 support to release notes 2022-12-07 19:54:49 -05:00
CDT-11.1.md CDT 11.1.1 Release Notes updates 2023-03-20 09:27:32 -04:00
CDT-11.2.md Add Cross GCC toolchain uses GNU Elf Parser to N&N 2023-04-24 15:25:02 +01:00
CDT-11.3.md Add CDT LSP information to CDT's READMEs and N&N (#566) 2023-09-20 06:38:22 -04:00
CDT-11.4.md Convert \b to 0x7f to properly handle backspace in the terminal (#619) 2023-11-14 17:53:17 -05:00
CDT-11.5.md Bug579242: allow user to override CMake Settings (#683) 2024-02-07 13:52:58 -05:00
CDT-11.6.md Updates for CDT 11.6.1 (#858) 2024-07-02 21:11:07 -04:00
CDT-12.0.md Always show CDT Debug Preference Pages (#974) 2025-01-06 12:46:55 -05:00
CHANGELOG-API.md Remove DiscoveredPathContainerPage (#701) 2024-02-08 15:06:12 -05:00
README.md Bump version to CDT 12.0.0 (#911) 2024-10-08 12:52:15 -04:00

CDT Release Notes and New & Noteworthy

What's new and noteworthy in:

CDT LSP

The CDT LSP (LSP based C/C++ Editor) provides its own changelog highlighting its release notes and new and noteworthy entries.

Older Versions

Older Versions

Older Versions

Older versions of CDT's New & Noteworthy page have not been converted from Wikitext to GitHub markdown, instead these older pages have simply been saved from the browser to preseve them. This may lead to some minor rendering issues that hopefully do not detract too much from the overall information provided.

API Changes

The Eclipse CDT project announces and tracks breaking API changes in CHANGELOG-API.

How to write a New & Noteworthy entry

How to write a New & Noteworthy entry

Use the model of any of the previous New & Noteworthy entry pages as a starting point. CDT 10.3/2021-06 is a fairly extensive entry and is a useful page to copy examples from.

Using Images

Upload images to the images/ subfolder and prefix the file with the version number, e.g. CDT-10.5-. The images should be embedded using the <img> tag with (gernally) a width of 50% like this:

<p align="center"><img src="images/CDT-10.0-CTAD.jpg" width="50%"></p>

Referecing Code

Especially when writing New & Noteworthy entries about API it is useful to link to the file. This should be done using a relative path, such as:

The [SerialPort](../native/org.eclipse.cdt.native.serial/src/org/eclipse/cdt/serial/SerialPort.java) supports arbitrary baud rates.

which renders like this:

The SerialPort supports arbitrary baud rates.

API Changes and Improvements

Improvements and changes to API should be announced in the New and Noteworthy for the release so they get visibility. Linking directly to the code or Javadoc for the new API is encouraged.

API Breakages and Removals

Anything that breaks or removes API should be listed in the CHANGELOG-API. If the API change is very significant (such as a new version of Java) listing it in the New and Noteworthy for the release is also advisable.