EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  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  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: program for generating screens from database files?
From: Tim Mooney <[email protected]>
To: Rolf Keitel <[email protected]>
Cc: Susanna Jacobson <[email protected]>, tech_talk <[email protected]>
Date: Fri, 20 Oct 2006 12:40:46 -0500


Rolf Keitel wrote:

I agree with Tom Cobb that it is not generally useful to create screens directly from a .db file.

Me too. However, I'd guess the database developer has a pretty good idea which fields are intended for modification and display by the user, and which fields might usefully be archived, autosaved, etc.

What if vdct were to acquire a mechanism by which the database developer
could specify how specific fields are expected to be used?  Then
an automated display generator would have at least a prayer of getting
the right stuff on a display, in the right sort of widget.  I don't
think an autogenerated display will ever be the final thing to hand over
to a user, but it could take a lot of the grunt work out of the manual
display-development process.

Right now, vdct knows about the use to which a *record developer*
expected a field to be put (e.g., GUI_INPUT, etc.).  In my experience,
this has not been very useful, because the record developer's view
typically is too generic to make useful application-specific choices.

(BTW, we've been trying something sort of along these lines: most of the
databases in synApps are accompanied by an autosave-request file -- a
manually generated text file that lists the fields the database developer
thinks should be saved and restored on reboot.  In some cases, the database
developer is the only person with the information required to specify
which fields should be autosaved, because the developer knows how the
database's initialization strategy operates.  In practice, users/deployers
can override the database developer's choices, but they rarely do.)

--
Tim Mooney ([email protected]) (630)252-5417
Beamline Controls & Data Acquisition Group
Advanced Photon Source, Argonne National Lab.

References:
RE: program for generating screens from database files? Rolf Keitel

Navigate by Date:
Prev: RE: program for generating screens from database files? Rolf Keitel
Next: Re: program for generating screens from database files? Terry Carlino
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: program for generating screens from database files? Rolf Keitel
Next: Attaching VBA and ActiveX Controls Bill Nolan
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·