Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#3,828 6 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
java
Área
desktop

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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?

Lenguaje dominante
Java
Estrellas
130
Forks
132
Merge medio
2 d 11 h
PR fusionados (30 d)
19

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ControlSystemStudio/phoebus

Todos los issues de ControlSystemStudio/phoebus

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.