|
Thanks everyone for the suggestions. I like Kay's idea of a directory of softlinks, but I also like the idea of replicating a search path at the IOC
level. Using Kay's example I think I will have a go with the following:
IOC1/motor_overview.bob -> /path/to/motor/v1/motorApp/opi/bob/motor_overview.bob
IOC1/motor_detail.bob -> /path/to/motor/v1/motorApp/opi/bob/motor_detail.bob
IOC1/ls_overview.bob ->
/path/to/lakeshore/v1/lakeshoreApp/opi/bob/ls_overview.bob
IOC1/ls_detail.bob -> /path/to/lakeshore/v1/lakeshoreApp/opi/bob/ls_detail.bob
IOC1/ioc1_overview.bob
IOC2/motor_overview.bob -> /path/to/motor/v2/motorApp/opi/bob/motor_overview.bob
IOC2/motor_detail.bob -> /path/to/motor/v2/motorApp/opi/bob/motor_detail.bob
IOC2/ioc2_overview.bob
bl_overview.bob
This means that if motor_detail.bob wanted to link to ls_detail.bob, it would have an action button that opened
ls_detail.bob. It would then pick up the version of lakeshore that was defined for that IOC. If
iocx_overview.bob wanted to open motor_detail.bob it would have an action button to
motor_detail.bob and if bl_overview.bob wanted to open
ioc1_overview.bob it would have an action button to IOC1/ioc1_overview.bob.
Thanks,
Tom
From: Paul Sichta <psichta at pppl.gov>
Sent: 28 March 2023 18:02
To: Cobb, Tom (DLSLtd,RAL,LSCI) <tom.cobb at diamond.ac.uk>
Cc: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Re: [External] Re: Links between bob files in different support modules
Tom
I was thinking: in your environment before calling the phoebus startup command from your shell
I use a script to startup our phoebus so I could put such things there as well,
export BSUPPORT=../../../BSupport/BSupportApp/op/bob
of course this only works if your running bob file is at the right spot relative to the targeted bob file .
-ps
-ps
Hi Paul,
Interesting, I hadn't thought of using macros. So, I guess these macros would be how to get to the bob files of a particular module from a common root. So from a bob file in the root, you could refer to
$(ASUPPORT)/A_details.bob. However, I still can't work out how you could make a relative link from a screen in ASupport to a screen in BSupport...
Thanks,
Tom
Tom
To simplify the syntax in the bob files You could use a macro based on a (relative) path definition from your phoebus environment.
Regards
-ps
Hi all,
We are looking at how to structure bob files within our support modules, especially how to link between support modules. For example, imagine we have a bob file
ASupport/ASupportApp/op/bob/A_details.bob and we want to link to
BSupport/BSupportApp/op/bob/B_details.bob. As phoebus doesn't support a search path (for
good reasons) we would need to supply an absolute or relative path to B_details.bob in
A_details.bob. My instinct is to use relative paths, so the directory tree can be served over http at runtime, but this means a link to
../../../BSupport/BSupportApp/op/bob/B_details.bob in A_details.bob which mandates that the two support modules be checked out next to each other.
Has anyone else had to link between bob files in two different support modules? If so, how have you done it?
Thanks,
Tom
--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify
us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify
us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
|
