I'm giving a small intro into my new CSS app to other CSS users this Friday. All of them are still using BOY/Opi with mostly Jython scripting.
As my knowledge on Java is not great, I need to some advise on the following (if you have time):
The 'Builder' can convert most OPI files but the underlying scripts must be changed to the new 'Display' java classes.
As much as possible and coding time allows, it reads existing displays, at least to the extend that I absolutely need this for operation of SNS beam lines where we have existing *.opi files.
What doesn't convert:
Scripts: They were always reserved for special cases, to do things that were impossible with EDM, MEDM, ...
If you have to ask how to do a script, you probably shouldn't use them.
If you still wanted to use them, you can now rewrite them.
Is there indication that other CSS users are also moving to the Builder ?
You'd have to ask them.
ESS has been contributing to the display builder, they intend to use it.
FRIB is interested.
Those that have many *.opi files will certainly need some time to update, that's OK.
But starting a new project with BOY now, and continuing to add code to BOY at this time is a very bad idea:
The BOY code entangles model, runtime and display. It's 99% on the UI thread and tightly depends on SWT, which in turn is dead.
Any way to add a genuine debugger in the newer CSS ? (or is this already possible?)
Not sure what you mean.
You can attach jvisualvm to the running instance to monitor CPU, memory, ..
You can start CSS from within Eclipse in debug mode and then single-step through everything.