EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
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  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 
<== Date ==> <== Thread ==>
Subject: Re:Re: .opi from CSS to Phoebus
From: Hasbroucq Dorian via Tech-talk <[email protected]>
To: "[email protected]" <[email protected]>
Cc: Patard Charles-Henri <[email protected]>
Date: Fri, 14 Jun 2019 14:25:06 +0000

Hi all , 

First of all thank you for your answers.

>Hi Dorian,
>
>I was asking similar thing the other day. Here is what I compiled so far in the github ticket for ADCore:
>
>https://github.com/areaDetector/ADCore/issues/411
>
>Instructions are not limited to areaDetector .opi. I still have not found the time to do this, but would like to .. soon.
>
>Kay and Oksana were very helpful in informing me on how to do it, so the credit is not mine.
>
>Thank you,
>//hinko

Alright, I'll try this. Thank you for the tip.


>Hi:

>> I am new to CS-Studio and Phoebus. Currently, I evaluate the cost of evolving to Phoebus.
>Good question. How much have you so far paid directly to develop CS-Studio?
>Or are you measuring the cost in the form of non-monetary contributions in the form of source code , documentation, platform tests?

By cost,  I meant the time needed to migrate from CS-Studio to Phoebus. I hope to contribute to Phoebus by some documentation, suggesting improvements, solutions to issue I'll face, etc.

I was added to the SPIRAL2 project (GANIL, FRANCE) a few weeks ago. This equipment has an existing CSS environment. Now, we are faced with the question: do we continue to maintain the existing or do we implement a new solution from the existing one? On the one hand, I have to evaluate the cost of each solution, explain why and how I'll choose one, because this is my graduation project. On the other hand, because we already have a configured CSS environment, I need to plan the migration to organize myself.

>> I tried to import CS-Studio project in Phoebus, it contains a dozen .opis of our own. Some difference shows up in the IHM as sizes, scripts, ... 
>>I assume it is due  to the gap between AWT/String and JavaFXT. There is two unsolved questions : 
>>- Can I convert .opi file into .bob file ? Am I obliged to ?
>>- Is there an easy way to convert old .opi (working with AWT&Swing) into new .opi/.bob (working with JavaFX) ? Do I need to rewrite all existing .opi ?
>CS-Studio has so far been based on Eclipse, i.e. SWT & JFace.
>After about 10 years of developing it based on Eclipse, the developers noticed that it might be a good idea to look for alternatives.
>For details, see presentations at recent EPICS meetings.
>The new, ongoing development no longer depends on Eclipse, and uses JavaFX.
>Its Display Builder opens existing *.opi files.
>There are small differences in the exact look of widgets, because internally pretty much everything  is different.
>Still, most displays should just work.
>What doesn't work out of the box: XYPlot and scripts.
>The *.opi  XYPlot has many operating modes. What it does exactly often depends on the type of PV, i.e. from simply looking at the display file you can't predict what will happen.
>The Display Builder has separate plot widgets for the different behaviors, and that's not always auto-updated.
>For scripts, every introduction to the CS-Studio display tools have stated that scripts are an advanced feature for special cases.
>They allow you to do pretty much anything, but they touch internals of the software that can change, and now they did.
>We do our best to translate Rules, but with scripts pretty much anything beyond calls to PVUtil and widget.setPropertyValue will need to be updated.
>So displays that include XYPlots and scripts need to be opened in the editor, adjusted, and then saved (which will save them as a *.bob file).

>You are of course free to continue using the Eclipse-based CS-Studio for the time being, in fact several CS-Studio developers are devoted to trying to keep it relevant by porting it to the current release of Java, and for as long as we have spare resources, we will continue to provide bug fixes.

>Best Regards,
>Kay

Thank you for those enlightments. It's clearer.

I have few more questions  :
Does  Archive Engine and Scan server are  still working the same way ?
Is the integration of homemade plugins is still the same despite the specificity of each plugin ?
Can Phoebus launch Java/MAtlab/... apps from the File Manager ?
Finally do you have advices regarding the migration ?

Best regards
Dorian

Préservons notre environnement, n’imprimez ce mail que si nécessaire.
Preserve our environment, print this email only if necessary.

Replies:
Re: Re:Re: .opi from CSS to Phoebus Hinko Kocevar via Tech-talk
Navigate by Date:
Prev: Re: Asyn 4-35 IOC upgrade misbehavior Lucas Russo via Tech-talk
Next: [AsynDriver] getAddress and callbacks Joao Afonso via Tech-talk
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: .opi from CSS to Phoebus Kasemir, Kay via Tech-talk
Next: Re: Re:Re: .opi from CSS to Phoebus Hinko Kocevar via Tech-talk
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 
ANJ, 28 Jun 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·