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

CDT/Obsolete/BreakpointsWorkingGroup

< CDT‎ | Obsolete
Revision as of 19:06, 9 November 2011 by Pawel.piech.windriver.com (Talk | contribs) (Breakpoint Properties Dialog)

Introduction

Purpose of this group is to discuss Wind River's contribution to improve breakpoints features and usability in CDT.

Links

TODO

Design Notes

Breakpoint Properties Dialog

The breakpoint properties dialog design directly affects three of the plan bugs:

  • bug 360291 - Allow user to edit line breakpoint file in properties dialog
  • bug 360295 - Customize property dialog for editing breakpoints
  • bug 360588 - Allow user to edit all its properties prior to creating the breakpoint

The data flow in the breakpoint properties dialog is illustrated in the following diagram. Below it is a comparison diagram from the Wind River product.

CDT Breakpoint Properties Dialog - Overview
Wind River Breakpoint Properties Dialog - Overview

The following changes should be made to CDT dialog design:

  1. Introduce a central preference store -
    • The preference store in the properties dialog will be initialized using the raw attributes extracted from the breakpoint marker.
    • Likewise, upon okPressed() the attributes from the preference store will write out to the breakpoint.
  2. The property pages need to be updated to read/write attributes to the preference store instead of directly to the breakpoint. Pages that support this new paradigm should use a new marker interface.
    • ...in progress...
CDT Breakpoint Properties Dialog - Pages class hierarchy
Wind River Breakpoint Properties Dialog - Pages class hierarchy

Back to the top