openframeworks / openframeworks/projectGenerator
vscode template, show only the addons listed in addons.make
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 90
- Forks
- 79
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 5
Description
It would be GREAT to have listed on VSCode project only the addons.make selected addons.
I've manually did that by editing the file {PROJECT}.code-workspace and listing each individual addon folder in this format
{ "path": "${workspaceRoot}/../../../../addons/ofxMicroUI" },
{ "path": "${workspaceRoot}/../../../../addons/ofxMicroUIFFT" },
{ "path": "${workspaceRoot}/../../../../addons/ofxTools" },
{ "path": "${workspaceRoot}/../../../../addons/ofxSvg" },
It is best if you have to read addon code or if you are developing an addon.
Thank you
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
Start by tracing the project generator's VS Code workspace generation and how addons.make is read. Compare the generated {PROJECT}.code-workspace with the listed addon paths. Done means the workspace includes only the addons selected in addons.make, while retaining the VS Code project setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100