LizardByte / LizardByte/roadmap
Sunshine: refactor the application launch system
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- Avg merge
- 25m
- Merged PRs (30d)
- 5
Description
### Is there an existing issue for this item?
- [x] I have searched the existing issues
### Repositories
LizardByte/Sunshine
### Languages/Skills/Technologies
C++, Vue, CSS, HTML, JavaScript
### Description
The Application system for launching is becoming very difficult to understand (prep/detatched/normal commands, configuration flags and such).
Idea from @TheElixZammuto
> A flowchart-like editor (think zapier/n8n) to define the order of commands for an app. Some other features can be templates and import/export directly from Steam, Playnite and Lutris
### Estimated Effort
effort:Extra-Large
### Priority
priority:Medium
### Target Milestone
6+ months
### Dependencies
_No response_
Contributor 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.
Research direction
Start by mapping the application launch system, including prep, detached, and normal commands, configuration flags, and their current relationships. Define what the proposed flowchart-like editor and Steam, Playnite, and Lutris import/export should cover, then confirm that the launch flow and integrations are represented consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, css, html, javascript
- Domain
- desktop, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100