1 / 6

Enhancements in Memory View December 21, 2005

Enhancements in Memory View December 21, 2005. Enhancements. Support for multiple address space environment Saving of model-specific data and settings Communication to Debug Model on background thread Support for flexible hierarchy and update policy. Address Space. Challenges:

francesca-hoffman
Download Presentation

Enhancements in Memory View December 21, 2005

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enhancements in Memory ViewDecember 21, 2005

  2. Enhancements • Support for multiple address space environment • Saving of model-specific data and settings • Communication to Debug Model on background thread • Support for flexible hierarchy and update policy

  3. Address Space • Challenges: • Cannot customize rendering labels to show address space id • Add Memory Dialog cannot be customized to allow user enter address space information • Passing of address space information from UI to the model • No way to show debug hierarchy with address spaces • Customize rendering labels by ILabelDecorator • Retargettable “Add Memory Block” action from Memory View • Retargettable “Add Memory Rendering” action • Flexible hierarchy in tree view pane (use Async Tree Viewer) • Question: Do we need the Add Memory Rendering action to be retargettable too?

  4. Persistence of Model Specific Data • Persistence of row and column size based on model / target type. • Persistence of memory blocks and renderings • Platform does not persist these data, clients are responsible to persist them. • Persist data using IPersistableDebugElement interface • This interface will remain internal for 3.2.

  5. IPersistableDebugElement

  6. Flexible Hierarchy and Update Policy • Use AsynchronousTableViewer in table rendering • Communicate with model on background thread • Allow clients to control when the rendering should be updated using update policy • Plans for this item: • Create new internal asynchronous table rendering for 3.2 • Deprecate existing table rendering when the new table rendering becomes public in the future • All base renderings will be migrated to use the new asynchronous table rendering.

More Related