Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Phoebus display option in CS-Studio #2694

Open
rjwills28 opened this issue Jun 15, 2021 · 4 comments
Open

Phoebus display option in CS-Studio #2694

rjwills28 opened this issue Jun 15, 2021 · 4 comments

Comments

@rjwills28
Copy link
Contributor

There is an option in CS-Studio to launch the Phoebus application from the top toolbar > CS-Studio > Display > Phoebus. This only works if the phoebus_home and phoebus_version have been set in applications/phoebus/phoebus-plugins/org.csstudio.phoebus.integration/preferences.ini. Otherwise exceptions are thrown in the log and nothing happens.
phoebus

Do you think there should be a preference to define whether or not the Phoebus launch is shown in the CS-Studio > Display menu in the case that Phoebus has not been installed?

@shroffk
Copy link
Member

shroffk commented Jul 6, 2021

Not including the Phoebus integration plugin/feature in your product would achieve the same result.
I don't like preferences to disable a feature which is included without intention to use...

@kasemir
Copy link
Contributor

kasemir commented Jul 6, 2021

Yes, simply not including what you don't need is most straight forward.
You can update your site-specific product build to only include what you need in the first place.
After the fact, I also find it practical to simply delete the corresponding *.jar file from the product.

@willrogers
Copy link
Contributor

After looking into this, I find that opibuilder depends on org.csstudio.phoebus.integration. So anyone who includes opibuilder gets the Phoebus menu entry, or so it seems. We have not changed the preference use_phoebus=false.

@shroffk
Copy link
Member

shroffk commented Sep 23, 2021

I will look into this.
The dependency might have happened with the "open in Phoebus" action

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants