I like the idea of using symlinks:
/some/path/main.bob
/some/path/motor/motor_overview.bob
/some/path/motor/motor_detail.bob
/some/path/lakeshore/ls_overview.bob
/some/path/lakeshore/ls_detail.bob
..
where motor is a symlink to ......../support_modules/..../motor/opi,
lakeshore
is a symlink to ......../support_modules/..../lakeshore/opi
That way the display files are inside the support modules together with *.db, *.dbd and can be kept in git/cvs/... that way, while at the same time you have a display file tree where main.bob can open motor/motor_overview.bob with short relative links, and
motor_overview.bob can trivially reach
motor_detail.bob in the same folder.
It gets more complicated when you feel you need to keep several versions, so you end up with
/some/path/motor_v1/motor_overview.bob
/some/path/motor_v2/motor_overview.bob
...
/some/path/motor_v99/motor_overview.bob
Still, same ideas remain, just a larger display file tree with more symlinks to versioned copies of the support modules.
-Kay
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Cobb, Tom (DLSLtd,RAL,LSCI) via Tech-talk <tech-talk at aps.anl.gov>
Sent: Tuesday, March 28, 2023 6:02 AM
To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: [EXTERNAL] Links between bob files in different support modules
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
|