Migrate the Memory Inspector from Theia to its extension under cdt-cloud umbrella

[jonahgraham]

The Memory Inspector is a very powerful UI delivering the best Memory View in the market today. However today it is tied to Theia and cannot be used in VSCode as an extension.

There have been preliminary discussions at the Embedded SIG about moving the memory inspector to its own extension that can be consumed by VSCode or Theia.

Interested parties in this work include ARM, Ericsson and Renesas. Specifically @colin-grant-work, @thegecko, @jonahgraham have shown interest in contributing to this work.

This issue is the umbrella to track making it its own extension. Once there is a git repo for the extension it is expected that this issue will be moved to that repo.

[colin-grant-work]

Thanks @jonahgraham. This work is our agenda for the mid-term, hoping to wrap up - at least for internal use - by June of next year. We'd be very interested to gather feedback on the current iteration and requirements for the next, VSCode-API version so we can plan work and distribute it, as appropriate.

[thegecko]

Thanks for opening this issue @jonahgraham

Arm are keen to accelerate this work where possible, but as it is already on the roadmap with Ericsson, perhaps its better led from there?

@colin-grant-work is there anything we can plan short-term to help? Perhaps setting up an initial repository and extension if you are happy to port in the open?

CC @federicobozzini @jreineckearm @arekzaluski

[colin-grant-work]

@thegecko,

is there anything we can plan short-term to help?

Mainly we'd like to be sure that we have others' use cases in mind at the outset, so if there are areas where you're unhappy with the existing implementation or where you've made enhancements for your use cases, we'd like to hear about them. Perhaps makes most sense to either set up the repo and then post those, or if there are things you'd like to discuss on greater detail or demo, we could set up a meeting or set aside a little bit more time in a SIG meeting?

Perhaps setting up an initial repository and extension if you are happy to port in the open?

This sounds good if you'd like to move ahead with it - I think we'll start this work in December or January, and we're happy to do the work in the open, I believe.

[jonahgraham]

Looping @markgoodchild in so he can comment / be aware of direction here.

[thegecko]

FYI, initial port of memory inspector for VSCode can be found here:

https://github.com/eclipse-cdt-cloud/vscode-memory-inspector

[colin-grant-work]

@thegecko, awesome, thank you. I think we at Ericsson will start taking this work up in January - would it make sense to set aside some time at a Cloud SIG meeting in January for a bit of discussion about it?

[thegecko]

@thegecko, awesome, thank you. I think we at Ericsson will start taking this work up in January - would it make sense to set aside some time at a Cloud SIG meeting in January for a bit of discussion about it?

Sure, we could work out responsibilities & approach