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.
Difference between revisions of "Debug/Phone 3-Dec-2009"
< Debug
m (New page: == Call Info == {|border=1 cellspacing=0 cellpadding=4 | Meeting Title: | '''Conference Call on Device Debugging''' |- | Date & Time: | '''Thursday 3 Dec 2009 at 8:00am PDT / 10:00 am CD...) |
m (→Agenda and Minutes) |
||
| Line 24: | Line 24: | ||
* Status | * Status | ||
* (Alain Lee) Bug 145635 - Pin-to-context | * (Alain Lee) Bug 145635 - Pin-to-context | ||
| + | ** Pawel: I think we have three options to proceed here: | ||
| + | **# Bury the idea and just declare that pin and clone for Debug views is just misguided. | ||
| + | **# Try to resurrect the pin and clone bug in platform. This is a labor intensive and risky option. Adding a breadcrumb is one option which would address some of the concerns raised in the bug. However, using a breadcrumb would introduce its own complications in that it would need to allow debug context providers from other views besides the Debug view. Otherwise it would not be a general solution. | ||
| + | **# Go for an alternative. The compare mode (http://wiki.eclipse.org/DSDP/DD/MultiContext#Proposal:_Compare_mode_in_Variables_views) is my favorite: much more elegant and than the whole pin and clone business, and it accomplish the main use case pin+clone: to compare data from different contexts. This would actually require only a small change in platform, while most of the work would be up to the debug model (i.e. DSF). | ||
== Action == | == Action == | ||
Revision as of 19:48, 2 December 2009
Call Info
| Meeting Title: | Conference Call on Device Debugging |
| Date & Time: | Thursday 3 Dec 2009 at 8:00am PDT / 10:00 am CDT / 11:00am EDT |
| USA/Canada tool free dial-in: | (866) 869-3090 |
| International dial-ins: | Austria 01 92 87 547, Germany 06 92 22 21 61 10, Sweden 08 56 61 94 27, France 01 70 73 27 20, UK 02 08 11 81 026 or 08 44 57 90 592 |
| Passcode: | 5107492128# |
Attendees
Agenda and Minutes
- Status
- (Alain Lee) Bug 145635 - Pin-to-context
- Pawel: I think we have three options to proceed here:
- Bury the idea and just declare that pin and clone for Debug views is just misguided.
- Try to resurrect the pin and clone bug in platform. This is a labor intensive and risky option. Adding a breadcrumb is one option which would address some of the concerns raised in the bug. However, using a breadcrumb would introduce its own complications in that it would need to allow debug context providers from other views besides the Debug view. Otherwise it would not be a general solution.
- Go for an alternative. The compare mode (http://wiki.eclipse.org/DSDP/DD/MultiContext#Proposal:_Compare_mode_in_Variables_views) is my favorite: much more elegant and than the whole pin and clone business, and it accomplish the main use case pin+clone: to compare data from different contexts. This would actually require only a small change in platform, while most of the work would be up to the debug model (i.e. DSF).
- Pawel: I think we have three options to proceed here: