Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support multiple plugin repositories #48

Closed
mitosagi opened this issue Aug 15, 2021 · 3 comments · Fixed by #56
Closed

Support multiple plugin repositories #48

mitosagi opened this issue Aug 15, 2021 · 3 comments · Fixed by #56
Assignees
@mitosagi
Labels
Feedback: enhancement New feature or request Type: new feature Suggesting new features

Comments

@mitosagi
Copy link
Collaborator

Is your feature request related to a problem? Please describe.

Currently, APM can install packages that are defined in the default repository. However, this is not so for the unregistered packages, which are the vast majority.

Describe the solution you'd like

Make it possible to add your own plugin list like package.json in npm.

AviUtl Plugin Manager issue

As shown in the figure, make the third party plugins_list.xml available. It would be even better if it could handle file paths in addition to URLs.

Describe alternatives you've considered

None in particular.

Additional context

If this becomes possible, plugin authors can distribute plugins in plugins_list.xml format, or publish prerequisite plugin configurations in plugins_list.xml format.
@mitosagi mitosagi added the Feedback: enhancement New feature or request label Aug 15, 2021
@hal-shu-sato hal-shu-sato added the Type: new feature Suggesting new features label Aug 17, 2021
@hal-shu-sato
Copy link
Member

Thank you for your issue!
I have thought about it before but I have one problem.

It is a conflict of plugins. When another data repository editor adds the same data with a different ID, APM will show the plugin twice because it is difficult to identify it by anything other than its ID.
So I think we need an ID assignment or acquisition system.

What do you think about this?
If you have any ideas, please let me know.

@mitosagi
Copy link
Collaborator Author

I don't think it's that bad to show two of the same thing.

Displaying plugins with the same plugin>files as a group will prevent a cluttered look. And restricting the installation to only one plugin per group should prevent the files from actually conflicting.

@hal-shu-sato
Copy link
Member

I see.
That's a good idea.
Let's try it.

mitosagi referenced this issue in mitosagi/apm Aug 21, 2021
@mitosagi
feat(plugin.js&script.js): avoid plugin or script id conflicts
cb7ebc5 
BREAKING CHANGE: This commit changes the data structure for 'installedVersion.plugin' and
'installedVersion.script'.

fix #48
@mitosagi mitosagi mentioned this issue Aug 21, 2021
Merged
8 tasks
mitosagi referenced this issue in mitosagi/apm Aug 24, 2021
@mitosagi
feat(plugin.js&script.js): avoid plugin or script id conflicts
9e95363 
BREAKING CHANGE: This commit changes the data structure for 'installedVersion.plugin' and
'installedVersion.script'.

fix #48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mitosagi mitosagi

Labels
Feedback: enhancement New feature or request Type: new feature Suggesting new features
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: support multiple repositories mitosagi/apm
2 participants
@hal-shu-sato @mitosagi