Re: Open .opi file from command line with CSS Display Builder?

["Kasemir, Kay" <kasemirk@ornl.gov>]

> Thanks for this explanation.  So it can only open a .opi file from the
> command line if it's already open in CSS?  That's not very useful to me.
Misunderstanding.
The file doesn't have to be open, but it needs to be accessible in the workspace.
You can assert that a file is in the workspace via the -share_link option.

For example, on our beamlines the files are basically in a directory /path/to/the/displays.
So we start CSS with

   css -share_link  /path/to/the/displays=/displays

So a file  /path/to/the/displays/sub/a/b/c.opi is visible in the workspace as /displays/sub/a/b/c.opi  and you can thus use

   css -share_link  /path/to/the/displays=/displays  --launcher.openFile /displays/sub/a/b/c.opi 

That "workspace" concept is an Eclipse idea that doesn't really help us much.
On the contrary, we spend time emailing about how to work around it.
So for the Phoebus project we remove the workspace, the files that we use are just the files in the filesystem

> Thanks for all of this!  And (the question I'm sure you get all the
> time) when will Phoebus be ready for production use? :-)  It seems like
> a very positive update project; I really look forward to it!  Thanks for
> your effort on it!

At recent EPICS meetings we said: End of this year.
You can get an update on that in 2 weeks at the APS EPICS meeting.

-Kay