[FEATURE REQUEST] Global progress bar for multi-package downloads and updates
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 30/100
Direzione di ricerca
L’issue non identifica file, test o punti di ingresso, quindi per prima cosa individua in UniGetUI i flussi delle operazioni di installazione, aggiornamento e download in batch. Definisci il comportamento dell’avanzamento globale per i pacchetti concorrenti, le dimensioni non disponibili, i tentativi ripetuti, gli errori, le cancellazioni e i pacchetti ignorati; il completamento significa che viene mostrato un riepilogo finale del batch, mentre l’avanzamento individuale rimane disponibile.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Please confirm these before moving forward.
- I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
- This proposal is a completely new feature. If you want to suggest an improvement or an enhancement, please use this template.
Describe the new feature
Global progress bar for multi-package downloads and updates
Problem
When installing or updating multiple packages at once, UniGetUI currently does not provide a clear global overview of the overall download progress.
Users can see the progress of individual package operations, but it is difficult to understand:
- how much data has already been downloaded in total;
- how much data remains;
- the overall progress of the entire operation;
- the current average download speed;
- the estimated time remaining (ETA).
This is especially noticeable when multiple package managers are involved or when several packages are processed concurrently.
Proposed solution
Add a global progress bar for batch operations such as:
- installing multiple packages;
- updating multiple packages;
- downloading package installers or archives;
- other operations involving multiple downloads.
Before starting the operation, UniGetUI should collect and parse the expected download size of all available package candidates whenever this information is provided by the package manager.
The global progress indicator could display:
- total downloaded size;
- total expected size;
- remaining size;
- overall percentage;
- current or average download speed;
- estimated time remaining (ETA);
- number of completed, active, and pending packages.
For example:
Downloading 1.24 GB of 3.80 GB — 32.6%
Average speed: 18.5 MB/s · Remaining: 2.56 GB · ETA: 2 min 18 sec
4 of 12 packages completed
Expected behavior
- When a batch operation starts, UniGetUI determines the total expected download size from all package candidates where possible.
- The global progress bar combines the progress of all active and pending downloads.
- Progress should remain accurate when multiple downloads are running simultaneously.
- The downloaded amount should be updated in real time.
- The average download speed should be calculated for the entire batch operation.
- The ETA should be based on the remaining amount and the current average speed.
- Packages for which the download size is unavailable should not break the global progress display.
- If the total size cannot be calculated reliably, UniGetUI should still show an indeterminate progress state together with the number of completed and active operations.
- The progress should account for retries, failed downloads, cancellations, and skipped packages.
- Once the operation finishes, the progress area should show a final summary, including the total downloaded size and duration.
Possible UI layout
A global progress section could be displayed above or alongside the list of individual package operations. Individual package progress should remain available for users who want more detailed information.
Describe how this new feature could help users
A global progress indicator would make batch operations more predictable and transparent, especially for large updates or installations. It would allow users to estimate how long the operation will take without having to monitor each package individually.
- Lingua principale
- C#
- Stelle
- 26.4k
- Fork
- 939
- Merge medio
- 21h 37m
- PR unite (30g)
- 70
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di Devolutions/UniGetUI
-
bug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
Devolutions/UniGetUI#5029 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
Devolutions/UniGetUI#4918 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
Devolutions/UniGetUI#4768 ·
I maintainer di solito rispondono entro 1 giorno
-
[BUG] Opening "Experimental settings and developer options" Always Causes "Restart UnigetUI to Apply Changes" to ShowForse già presa @r4venrudy l’ha presa 1 giorno fa. Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 55/100
Devolutions/UniGetUI#5507 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 30/100
Devolutions/UniGetUI#5505 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di Devolutions/UniGetUI
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
I maintainer di solito rispondono entro 1 giorno
-
area:re1 bounty help wanted needs-game
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
StackExchange/StackExchange.Redis#3274 ·
I maintainer di solito rispondono entro 1 giorno
-
affected/v17 affected/v18 area/frontend type/bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
umbraco/Umbraco-CMS#24186 ·
I maintainer di solito rispondono entro 2 giorni