Hi:
On 12/1/10 14:11 , "Jimmy Johnson" <[email protected]> wrote:
> Basically our operators are used to being able to X display many
> discrete UIs onto their desktop ...
> That said there are definitely benefits to the CSS integrated tools
> support ...
Right, there are benefits to both.
> ... I was hoping ... something along the lines of
> "boy_displaymanager test.opi"
Yes, we'd like to have something like that, too.
Here at the SNS we have mostly EDM screens, and there's no need to replace
them in the foreseeable future.
Still, it would be great to be able to open new CSS OPIs from the existing
EDM screens, via a command-line tool as you describe.
Java code tends to have a certain startup time.
Starting CSS can be slow, while opening another display within the running
instance is then no problem.
Plus I would still include at least probe, PV tree, Data Browser
PV-fields-viewer with SNS Database connection, SNS logbook support, settings
for SNS network in that tool.
So I don't think a boy-only product is the solution.
Better would be something that signals the already running instance of CSS
to open another screen.
-Kay
- References:
- RE: How to use BOY/OPI to produce standalone simple displays Jimmy Johnson
- Navigate by Date:
- Prev:
RE: How to use BOY/OPI to produce standalone simple displays Jimmy Johnson
- Next:
Re: CSS/Trend and small numbers Maren Purves
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: How to use BOY/OPI to produce standalone simple displays Jimmy Johnson
- Next:
Build EPICS Base3.14.9 on Windows 张玉亮
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|