Write a GUI for configuration
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 766
- Forks
- 51
- Avg merge
- 16d 14h
- Merged PRs (30d)
- 1
Description
GUI
Description
This requires careful planning: an interface that allows people to do everything the engine is capable of would result in something even harder to use without careful design.
The GUI needs to support:
- Multiple originating servers
- Blacklisting of files per patch
- Font settings
- A simple-to-use, verbose and clear wizard
A way to suggestDependenciesbase_tsa, yet also allow for configurations that don't use it- Enable and disable self-updating
- more... ?
Prerequisites
- Settle on a GUI framework (decided on wxWidgets)
Implementation
Patches are visualized as horizontal blocks and colored according to their downloading status. These blocks contain little icons symbolizing the various types of data included in a patch:
- Version information
- Binary hacks and breakpoints (may share one icon, maybe?)
- Fonts
- Text translations
- Images
Maybe we could also indicate progress in some way?
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
No files, entry points, or tests are named. Start by reviewing the engine capabilities and the settled wxWidgets choice, then turn the listed requirements into a scoped GUI design. Done would require an agreed interface covering the listed configuration, wizard, update, patch visualization, and status-indicator needs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100