Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Allow `-clean` command line option with `-app` and `-resource` options

Aperta
  • Qualcosa non va?
#3,828 6 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
java
Ambito
desktop

Direzione di ricerca

Start by reading Phoebus's command-line handling for -clean, -app, and -resource, then trace how startup and requests are handled when Phoebus is already open. The issue does not name specific files or tests, so locate the relevant entry points and existing coverage first. Done means a clean launch opens the requested app or resource without restoring prior state, while an already-running instance ignores -clean and opens the request normally.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

We have a use case where we would want to launch a BOB screen in its own window from the terminal, e.g.

phoebus.sh -resource "file:/path/to/file/example.bob@target=window"

The only problem with this is that by default this will bring up the persisted Phoebus state, which might contain other open windows or screen editor tabs etc. At that point, the only way to ensure only the 'example.bob' screen appears is to make sure you close all the other windows/tabs before shutting phoebus down (not ideal!) or you first run with -clean:

phoebus.sh -clean
phoebus.sh -resource "file:/path/to/file/example.bob@target=window"

I feel like it would be much cleaner to be able to run something like:

phoebus.sh -clean -resource "file:/path/to/file/example.bob@target=window"

which is basically saying I want a clean start (no persisted state) and to open the following resource.

However the current design of Phoebus is such that -clean overrides any other option (e.g -resource xx, -app xx). Does anyone know the original reasoning behind this and whether we could change this behavior to something like that described above?

The desired behavior would be as such:

  • If Phoebus isn't open then clean (i.e. do not load previous state) and open the resource/app.
  • If Phoebus is already open, then the -clean is automatically ignored and the resource/app will just be opened as normal (and everything already open remains).

I am happy to put in a PR to make this change but wanted to get some feedback first to make sure I haven't missed anything about the behavior?

Lingua principale
Java
Stelle
130
Fork
132
Merge medio
3g 1h
PR unite (30g)
24

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ControlSystemStudio/phoebus

Tutte le issue di ControlSystemStudio/phoebus

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.