Template improvements

[mast-eu]

Created new issue from what @Cussa wrote in gitextensions/gitextensions#6624 (comment).

• Most of the plugins will have some UI. So, it makes sense to have the template with some UI already.
  • In my case, I cloned the Plugin Manager, and I'm using that as a reference to create mine.
• Most of the plugins will have some Settings. So, it makes sense to have the template with some Settings examples.
  • Again, I'm using the Plugin Manager as a model. However, as it has only one type of setting, It would be handy to have some examples.
• It would be good to include some Script to rename the points to the plugin name.
  • When you use the template from GitHub, it generates the repo, but you have to go everywhere to rename files and folders to your plugin name. I'm thinking about some simple script that could do that easily.

[RussKie]

Once migrated to .NET Core, we can entertain an idea of a dotnet global tool, that would create a new template project. E.g. `dotnet new geplugin -n MyPlugin`

…

On Mon, Nov 11, 2019, 10:12 AM Martin Steinisch ***@***.***> wrote: Created new issue from what @Cussa <https://github.com/Cussa> wrote in gitextensions/gitextensions#6624 (comment) <gitextensions/gitextensions#6624 (comment)> . - Most of the plugins will have some UI. So, it makes sense to have the template with some UI already. - In my case, I cloned the Plugin Manager, and I'm using that as a reference to create mine. - Most of the plugins will have some Settings. So, it makes sense to have the template with some Settings examples. - Again, I'm using the Plugin Manager as a model. However, as it has only one type of setting, It would be handy to have some examples. - It would be good to include some Script to rename the points to the plugin name. - When you use the template from GitHub, it generates the repo, but you have to go everywhere to rename files and folders to your plugin name. I'm thinking about some simple script that could do that easily. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#11?email_source=notifications&email_token=ABBTEXRQXIFGEHMSEVTAKG3QTCINZA5CNFSM4JLOZAYKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HYI27YA>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABBTEXRRQ5TVUJQNI5VU6WDQTCINZANCNFSM4JLOZAYA> .