Provide an elegant way to install plug-ins from Microsoft Store
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 24.7k
- Forks
- 1.3k
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 1
Description
1.A plug-in panel (store) is directly provided in the main program, and the plug-in is directly put on the shelves by the ql-win developer. Users can also freely download/install plug-ins from third parties.
- Advantages:
-
As part of the main program, it is directly audited by Microsoft Store;
-
at the same time, it is open.
2.The method officially recommended by the application store: on the shelves as an add-on.
- Advantages:
- officially recommended.
- Disadvantages:
- It must be submitted using the same account as the main application, which means that the main maintainer needs to maintain a plug-in update system, which has a lot of work;
- plug-in developers need to go through the double review of ql-win and Microsoft Store, especially the store review requires wisdom and courage, which makes ql-win and plug-in developers very labored.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue proposes two Microsoft Store plug-in distribution models but names no files, tests, or entry points. Start by clarifying which model and acceptance criteria the maintainers want; done would be an agreed implementation scope for plug-in installation and updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100