Re: [platform-debug-dev] Breakpoint property pages

["Darin Wright" <Darin_Wright@xxxxxxxxxx>]

Jared,

I don't understand how we make this "generic" debug platform support. Looking at the property page extension point, one or more pages is contributed for an "object class". Each contributor will have to define their own property page extensions, and the "Properties" action should appear for free, once the extensions are defined. Am I missing something?

Darin

Jared Burns <jaredburns@xxxxxxx> Sent by: platform-debug-dev-admin@xxxxxxxxxxx 07/21/2003 04:29 PM Please respond to platform-debug-dev

To:        platform-debug-dev@xxxxxxxxxxx         cc:                 Subject:        [platform-debug-dev] Breakpoint property pages

Bug 10900 - Improve breakpoint properties dialog
https://bugs.eclipse.org/bugs/show_bug.cgi?id=10900

For this bug, I'm adding support for property pages to configure 
IJavaBreakpoints. I can either add an action that will only appear on Java 
breakpoints (like our current story) or I can add generic support to open the 
property dialog on all breakpoints.

I'd like to do the former, because it would provide a common editing story for 
all breakpoint extenders. However, it would require breakpoint contributors 
to migrate their current (custom) configuration stories to the property page 
framework. Personally, I'm liking the property page framework a lot better 
than the custom dialog we shipped in 2.1.

First, is this considered an API change? Technically, I don't think it is. If 
a breakpoint contributor didn't migrate to the property page framework, their 
custom story would still work - there would just be a "Properties" action on 
their breakpoints that would open a useless dialog.

Second, do we want to do this?

Thanks,
- Jared
_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-debug-dev