[Feature Request] Meta-issue: Standardize OSD and notification formatting for file operations
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
This meta-issue is needed to capture the big picture across related trackers and make it easier to coordinate, discuss, and work on a unified solution. Specifically, it connects:
- https://github.com/libretro/RetroArch/issues/19252
- https://github.com/libretro/RetroArch/issues/16222
- https://github.com/libretro/RetroArch/issues/19246
- https://github.com/libretro/RetroArch/issues/19254
The examples provided in this issue give a clearer, more holistic overview of how these different settings interact and complement each other in practice.
Proposal
Standardize all file operation messages to follow this consistent base structure:
[Status Icon] [Operation] [Full directory path] [Filename] [Directory Title]
- Core Components:
[Status Icon],[Operation], and[Filename]are always displayed. - Optional Modifiers:
[Full directory path](#19246) is toggled viaDisplay full directory paths in file operations.[Directory Title](#16222) is toggled viaShow directory labels for file operations.
Configuration Options & Examples
*Applies to actions such as Online Updater → Core Downloader → [Selected Core]*
- Default (Minimal):
- ✅ Extracting
"core.zip"
- ✅ Extracting
- Default (Minimal) if it fails:
- ❌ Extracting
"core.zip"
- ❌ Extracting
- If
Show directory labels for file operationsis enabled:- ✅ Extracting
"core.zip"in Core directory
- ✅ Extracting
- If
Display full directory paths in file operationsis enabled:- ✅ Extracting
"/home/gamer/Downloads/RetroArch-Linux-x86_64/RetroArch-Linux-x86_64.AppImage.home/.config/retroarch/cores/core.zip"
- ✅ Extracting
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 reviewing the linked issues #19252, #16222, #19246, and #19254 to understand the related settings and existing proposals. Then trace the file-operation messages used by Online Updater → Core Downloader and verify that the status icon, operation, filename, optional full path, and optional directory title follow one consistent format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100