Samantha Chan
2008-12-08 19:36:48 UTC
Hi all,
Ted Williams and I have been working together to come up with a Memory
View development plan for Eclipse 3.5.
The main development theme is to enhance the Memory View framework to
allow debug implementers to have more control over the Memory View
workflow.
Targeted for M5:
===============
Bug 214956 Go To Address Bar
Bug 257837 Memory View Import/Export
Bug 257842 Expression Evaluation API
Targeted for M6:
=============
Bug 257838 Allow debug model to control action visibility - need to
schedule design meeting
Bug 257841 Refresh action & API invalidate content
Bug 257845 RenderingViewPane needs to be API
Bug ??? More fine-grained control for debug change events
We plan to finish majority of the development work by M6.
You can find details of the plan here:
http://wiki.eclipse.org/DSDP/DD/MemoryView#3.5_Work_Items
Please let us know if you have any feedback about this plan.
Thanks...
Samantha
Ted Williams and I have been working together to come up with a Memory
View development plan for Eclipse 3.5.
The main development theme is to enhance the Memory View framework to
allow debug implementers to have more control over the Memory View
workflow.
Targeted for M5:
===============
Bug 214956 Go To Address Bar
Bug 257837 Memory View Import/Export
Bug 257842 Expression Evaluation API
Targeted for M6:
=============
Bug 257838 Allow debug model to control action visibility - need to
schedule design meeting
Bug 257841 Refresh action & API invalidate content
Bug 257845 RenderingViewPane needs to be API
Bug ??? More fine-grained control for debug change events
We plan to finish majority of the development work by M6.
You can find details of the plan here:
http://wiki.eclipse.org/DSDP/DD/MemoryView#3.5_Work_Items
Please let us know if you have any feedback about this plan.
Thanks...
Samantha