Extension naming about vscode-peripheral-inspector HOT 6 CLOSED

Great, I'll rename this to peripheral-inspector

from vscode-peripheral-inspector.

Hi @thegecko,

My personal opinion is the project has a potential to expand its capabilities to other system definition formats. The fundemental goal of the project could be considered as "define a UI extension for embedded system developers that they can explore the peripherals information".

If we consider the goal in that way, SVD will be one of the formats supported by the extension and, semantically, we can think about renaming the extension to something like "peripheral-explorer" or "peripheral-inspector" or something which may have more general meaning.

from vscode-peripheral-inspector.

Hi @thegecko , I agree with @asimgunes . With a more generic name, this extension could become the home for other technologies and views to support inspection of peripherals in embedded systems. Making a start with SVD.

In terms of exact naming, we should probably look for something that is consistent with other extensions in eclipse-cdt-cloud. Considering that we have a "Memory Inspector" extension already, I'd suggest to go with "Peripheral Inspector".

from vscode-peripheral-inspector.

See #12

from vscode-peripheral-inspector.

#12 Has been merged, now awaiting repo name change at eclipse-cdt-cloud/.eclipsefdn#9

from vscode-peripheral-inspector.

All renaming complete and initial version published

from vscode-peripheral-inspector.