Provide an elegant way to install plug-ins from Microsoft Store
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
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.
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.
- Dominant language
- C#
- Stars
- 25.8k
- Forks
- 1.4k
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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.
More from QL-Win/QuickLook
-
遇到超大文件会卡住Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 4 days
-
[MarkdownViewer] Mermaid classDiagram with <<annotation>> fails with "Syntax error in text"Possibly taken @suhyun-nam claimed this 13 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
QL-Win/QuickLook#2028 · 3 comments ·
Maintainers usually reply within 4 days
-
[Bug] If the first character entered into the search box is a space, the preview window will close.Possibly taken @MORTEM3845 claimed this 27 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 4 days
-
[Crash] Fatal CLR error (80131506) previewing any SVG when WebView2 controller creation fails — initialization failure is silently ignoredPossibly taken @Henglie claimed this 14 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
QL-Win/QuickLook#2057 · 1 comment ·
Maintainers usually reply within 4 days
All issues in QL-Win/QuickLook
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Bug IronPython Python 3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pyrevitlabs/pyRevit#4184 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
yusei36/KeePassPasskey#66 · 2 comments ·
Maintainers usually reply within 1 day
-
🐛 bug 🕒 low effort good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
guibranco/Sankhya-SDK-dotnet#654 ·
Maintainers usually reply within 1 day
-
巫女のセリフに声を付けるOpenassets claude-proposal
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Fialuxe/MouthOfGod_System#358 ·
Maintainers usually reply within 1 day