Carl,
I think the only solution is administrative, not technical. It involves instruction to the users and guidelines for EDM and script developers. One small technical thing to do is (figure out how to get and then) pass the "read-only-ness" into the scripts with a required (for script developers) parameter; or perhaps set an EDM-related environment variable which the scripts are required to honor.
For "dangerous" things, we sometimes put text on the EDM screen warning the user of possible side-effects.
Ron Chestnut
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Carl Schumann
Sent: Thursday, April 22, 2010 10:50 AM
To: [email protected]
Subject: EDM's -ro option and running arbitrary scripts w/ in our case caputs
Hi,
Our EDM display authors frequently use EDM's shell widget to run
scripts, including scripts that do 'caput's. Such buttons/scripts
appear to be able to do settings even when EDM is started with its -ro
option. While I can understand why this is so from a difficulty of
implementation perspective it does seem to mislead the user. Are my
facts correct? If yes, what does one do or think about it?
Thanks,
Carl Schumann
- References:
- EDM's -ro option and running arbitrary scripts w/ in our case caputs Carl Schumann
- Navigate by Date:
- Prev:
EDM's -ro option and running arbitrary scripts w/ in our case caputs Carl Schumann
- Next:
Re: Striptool crashes for Fedora 11 64 bit version... Janet Anderson
- 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
- Navigate by Thread:
- Prev:
EDM's -ro option and running arbitrary scripts w/ in our case caputs Carl Schumann
- Next:
Re: EDM's -ro option and running arbitrary scripts w/ in our case caputs John William Sinclair
- 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
|