Message Command Interface

[nlewis05]

Main Topics:
Deciding on the path forward for the in progress MessageCommand-Interface branch and MessageCommand-Interface issue

Discuss potential implementation of messaging algorithm between the 3 extension components ( DFDL Runtime, Data Editor Extension, Data Editor UI).

MessageCommand-Interface Path
During this discussion, displayed the current status of defining the messaging structure between the Data Editor Extension and its Svelte UI. It was brought up that a standardize messaging structure should be implemented after developing the implementation of replacing the hexView with the data editor.

It was brought up the idea of utilizing protobuf ( protobuf-ts ) because of its ability to define message structures across multiple languages & system domains.

Current Determination
Research if the usage of protobuf will be the best solution and then determine the status us pushing the branch for review.

Extension Component Messaging Strategy
The main topic of this discussion was pointing out the rudimentary current listen-all & switch event listeners being attached the the current debug session.

Creating topic specific event emitters for usage within the entire DFDL extension, rather than simply listening to all debug events.

Current Determination
Develop a simple implementation of a DFDL extension event emitter to determine if this development route is achievable.