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: DM recommedation. |
From: | "Siddons, David via Tech-talk" <[email protected]> |
To: | "[email protected]" <[email protected]> |
Date: | Thu, 25 Oct 2018 17:11:32 +0000 |
Hi David, For my own personal use I use epicsQt (https://qtepics.github.io/). This is very easy to use, adding Epics functionality to QtDesigner to build screens, similar to MEDM (I was a MEDM user before :) ). Like Medm, it offers code-free development of interfaces, and has a good range of widgets. The NSLS-II official stuff is CSS-based. Pete.
On 10/25/2018 12:19 PM, Kline, David wrote:
Hello Lewis, Thanks for responding and the information. I'll have a closer look at the links you provided. Currently I'm using MEDM for monitoring register and market data, but was looking for something currently supported and modern, preferably based on GTK+ for internal reasons. I would have preferred to use caQtDM because a number of .adl files are already converted. I've used and developed quite a few number of MEDM screens while at and outside of APS [EBRICK, laser and timing controls, etc...] and agree with conclusions made in : https://epics.anl.gov/tech-talk/2018/msg00502.php "1. MEDM : It works! This old gem works (almost) perfectly. It has a very easy to use interface, but of course, is rather limited." Thanks again, best, /david-----Original Message----- From: J. Lewis Muir <[email protected]> Sent: Thursday, October 25, 2018 10:43 AM To: Kline, David <[email protected]> Cc: Gabriel de Souza Fedel <[email protected]>; [email protected] Subject: Re: DM recommedation. On 10/25, Kline, David wrote:What I meant to ask is for a recommendation of a tool similar to either MEDM or caQtDM for screen development and operations on Linux systems which have GTK+ and is actively supported. Typically Qt is not part of the distribution but could be if no alternative exists, if it was I would be using caQtDM.Hi, David. You're probably going to get lots of different recommendations as was the case in https://epics.anl.gov/tech-talk/2018/msg00502.php One thing to keep in mind is whether or not the EPICS display manager supports old formats, in particular, that of MEDM (.adl), or whether or not old formats can be automatically converted into the format of the EPICS display manager you choose. This is not just for backward compatibility; it's also very useful for developers that are providing display manager screens with their modules and don't want to have to create and maintain N sets of screens for N display managers! I currently use MEDM https://epics.anl.gov/extensions/medm/ It's lightweight, it runs on Windows, macOS, and Linux (and probably other UNIX-like OSs), lots of EPICS modules include screens for it, and the screens can be automatically converted to CSS BOY (.opi) which Display Builder supports. One interesting project is Display Builder https://github.com/kasemir/org.csstudio.display.builder running on Phoebus https://github.com/shroffk/phoebus I haven't tried it, but if I were going to switch away from MEDM, it's probably the direction I'd be leaning. Lewis------------------------------------------------------------------------------ This message is intended only for the personal and confidential use of the recipients named above. If the reader of this email is not the intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited. If you have received this email in error, please notify the sender immediately by return email and permanently delete the copy you received. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. Wolverine is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity that may be attached to or contained in this communication. Wolverine accepts no liability for any content contained in the email, or any errors or omissions arising as a result of e-mail transmission. Any opinions contained in this email constitute the sender's best judgment at this time and are subject to change without notice. |