1 / 7

Debugger Services Framework (DSF) View Model

Debugger Services Framework (DSF) View Model. Device Debugging Project Update by Pawel Piech Wind River Systems, Inc. Flexible Hierarchy: Delta Generation. View. Root. X. Y. Event: Change State. Z. Knows Full Path. Model Event Proxy. Generates Delta Root: NO_CHANGE

Download Presentation

Debugger Services Framework (DSF) View Model

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. Debugger Services Framework (DSF)View Model Device Debugging Project Update by Pawel Piech Wind River Systems, Inc.

  2. Flexible Hierarchy: Delta Generation View Root X Y Event: Change State Z Knows Full Path Model Event Proxy Generates Delta Root: NO_CHANGE X: NO_CHANGE Y: NO_CHANGE Z: STATE

  3. Flexible Hierarchy: Delta Generation (Notes) • Model Event Proxy for element "Z" needs to know the full path of Z in the view in order to generate the Delta. • Reusing the Model Event Proxy in views with different layouts is difficult because the view layout in hard-coded in its implementation.

  4. DSF "View Model" Structure View View Model Root Context Root Node Context X1 Node X Context X2 Context Y1 Node Y Context Z1 Context Y2 Node Z Context Z2 Context Z3

  5. DSF "View Model" Structure (Notes) • A view model is composed of a hierarchy of "Layout Nodes", where each node can have a number of "Child Nodes" • A layout node generates "Context" wrappers for elements which are used to populate the view. • Each node is self-contained so that it holds no references to other nodes in the model. • When handling updates and events, layout nodes use the TreePath of an element to extract data needed for the given evaluation. • Layout nodes can be arranged arbitrarily, however some nodes may require that certain elements be present in the TreePath when performing evaluations. • Layout of nodes for a given view can be changed at runtime.

  6. Content update for element "Y2" - Sequence

  7. Event Handling for Element Z3 - Sequence

More Related