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: Links between bob files in different support modules |
From: | Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> |
To: | "Cobb, Tom (DLSLtd,RAL,LSCI)" <tom.cobb at diamond.ac.uk>, "Kasemir, Kay" <kasemirk at ornl.gov>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Tue, 28 Mar 2023 16:33:45 +0000 |
Hi Tom,
And the standard screens in both ADCore and AD support modules have links to the asynRecord screen from asyn, and some other synApps screens like yySeq_full. Mark From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of
Cobb, Tom (DLSLtd,RAL,LSCI) via Tech-talk Hi Kay, Just to check I have this right, if you had a button in motor_detail.bob that opened ls_overview.bob, then it would point to
In case it is helpful, my use-case at the moment is something like areaDetector, where the detector support modules may want to link to bob files from the ADCore support
module. Thanks, Tom From: Kasemir, Kay <kasemirk at ornl.gov> 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> 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
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. -- 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. |