Iirc it is planned to load and update an template image by URL. Like, you "Import" an image by entering a GH-raw link for example. And every now and then (on page refresh, on manual trigger, ..?) the specified url gets fetched and a potential updated template is loaded.
I now bring you another idea that builds off of this: Specifying a Git(Hub?) repo by URL.
Thats the base idea. How it works should be self explanatory. You "Import" by URL again, this time however, it a Git repo URL. If theres a new commit, it means the images could be pulled again.
Well, idk if it is even possible to somehow build some sort of lightweight git client on tamper monky...
And, well, for the UI... I simply thought of:
Yes, yet another idea: Folders and subfolders to organize templates in the manager's overview.
So, you can create a folder ("group") and navigate into it to only show its child templates (and its subgroups).
You can dis-/enable an entire group by clicking on the groups 👁-icon (just like templates).
When importing a git repo, it is displayed pretty much identical to a group. When you navigate into it, you get all its templates. The only differences are:
- you can't create/import new templates in this group.
- instead you have a COG button in its place (or somewhere) to edit the URL, remove the repo, and a fetch-for-updates-manually button.
Iirc it is planned to load and update an template image by URL. Like, you "Import" an image by entering a GH-raw link for example. And every now and then (on page refresh, on manual trigger, ..?) the specified url gets fetched and a potential updated template is loaded.
I now bring you another idea that builds off of this: Specifying a Git(Hub?) repo by URL.
Thats the base idea. How it works should be self explanatory. You "Import" by URL again, this time however, it a Git repo URL. If theres a new commit, it means the images could be pulled again.
Well, idk if it is even possible to somehow build some sort of lightweight git client on tamper monky...
And, well, for the UI... I
simplythought of:Yes, yet another idea: Folders and subfolders to organize templates in the manager's overview.
So, you can create a folder ("group") and navigate into it to only show its child templates (and its subgroups).
You can dis-/enable an entire group by clicking on the groups 👁-icon (just like templates).
When importing a git repo, it is displayed pretty much identical to a group. When you navigate into it, you get all its templates. The only differences are: