Refactoring with interfaces about blazor.svgeditor

[KristofferStrube]

Hey @ABIOLI-COM awesome that you found the project useful once again. 😁

I've been thinking of releasing the project as a NuGet package and making all features configurable and togglable which I think is what you have tried to achieve by copying the SVG, Path, Shape, etc. classes.
This is a list of the things I would like to be configurable on the SVG component so that people don't need to modify (or copy) it. If you have any other things that you would like to be configurable or be able to toggle off then please note so. 😀

• Disable/enable context menu
• Disable/enable zoom
• Disable/enable panning
• Disable/enable deselecting elements
• Disable/enable selecting elements
• Disable/enable window marking of multiple shaped
• Disable anchors and lines (basically meaning disabling shape edits)
• Add/remove/reorder/replace all individual menu items.
• Add/remove shape handlers
• Add/remove animation handlers
• Change primary and secondary colors for anchors, striped lines, scalar boxes, and the background.

All of the above would then be configurable but with the defaults that are the current ones. What do you think of this and are there any settings that you would be missing for your use case?

I'm updating the above checklist as I add support for configuring each part.

[KristofferStrube]

@ABIOLI-COM I have released the project to NuGet now with features that should make it more configurable so that you don't have to do source code copying. Here is a link to the NuGet package: https://www.nuget.org/packages/KristofferStrube.Blazor.SVGEditor

You can check out two examples of how to use this here:
https://kristofferstrube.github.io/Blazor.SVGEditor/Minimal/
https://kristofferstrube.github.io/Blazor.SVGEditor/CustomElements/

If you would like to test using it in one of your projects then I would be very happy to get any feedback you might have.