RE: [Hardhats-members] Xdialog, dialog, m2web
On Sun, 2005-03-06 at 09:43 -0600, John Leo Zimmer wrote:
[KSB2] <...snip...>
> > [KSB] Try something like:
> >
> > export DIALOG=${DIALOG:=`which Xdialog`} ; if [[ -z $DIALOG ]] ;
> > then export DIALOG=`which dialog` ; fi
> >
> > and in your script use $DIALOG as the program to use. Now that I
> > think about it, a construct like the following might be even better:
> >
> > if [[ -z $DISPLAY ]] ; then export DIALOG=`which dialog` ; else ...
> > ; fi
> >
>
> [jlz] OK, Thanks. That's what I needed. This works to test for both X and
> Xdialog.
>
> ##
> if [[ -z $DISPLAY ]] ; then dialog --infobox "X not running" 0 0 ;
> $vista_source/dvista ; exit 1
> fi
> export XDIALOG=`which Xdialog`
> if [[ -z $XDIALOG ]] ; then dialog --msgbox "Xdialog not installed" 0 0 ;
> $vista_source/dvista ; exit 1
> fi
> ##
Try this (just 3 lines; watch out for line breaks):
export DIALOG=`which Xdialog`
if [[ -z $DIALOG || -z $DISPLAY ]] ; then export DIALOG=`which dialog` ;
fi
$DIALOG --title "Dialog Chooser Demo" --infobox "Using $DIALOG" 0 0
Sometime, I should probably update the vista script to allow dialog.
But Xdialog has more visual appeal.
-- Bhaskar
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
RE: [Hardhats-members] Xdialog, dialog, m2web
From: "Bhaskar, KS" <[EMAIL PROTECTED]>
Subject: RE: [Hardhats-members] Xdialog, dialog, m2web
> John --
>
> Something is really screwed up with e-mail. I received your e-mail
> after the responses in the thread it initiated! Comments below.
>
[jlz] that may be partly my doing. I initially used my local ISP but I'm not
a member at that address so it required approval... which came through some
hours after I had repeated myself from this webmail address. . . but something
seems to be dropping some of your mail lately. Maybe you have a full mailbox
or some sort of storage problem?
> I'm aiming toward Boston and I'm attempting to fancy up Bhaskar's
> install/run script. My ultimate goal is to include the installation
> of m2web into the scripts:
>
> [KSB] Actually, you can integrate M2web without touching the
> /usr/local/OpenVistA/vista script. Assuming that you have the
> database installed in (for example)
> /mnt/hda4/myVistA/OpenVistA/g/mumps.dat, then just put the routines
> for M2Web in /mnt/hda4/myVistA/OpenVistA/r/. The object files will
> automatically get compiled into /mnt/hda4/myVistA/OpenVistA/o/.
>
[jlz] I'm thinking
> 1b.) ?? How do I add wa test for the <> of Xdialog itself??
>
> [KSB] Try something like:
>
> export DIALOG=${DIALOG:=`which Xdialog`} ; if [[ -z $DIALOG ]] ;
> then export DIALOG=`which dialog` ; fi
>
> and in your script use $DIALOG as the program to use. Now that I
> think about it, a construct like the following might be even better:
>
> if [[ -z $DISPLAY ]] ; then export DIALOG=`which dialog` ; else ...
> ; fi
>
[jlz] OK, Thanks. That's what I needed. This works to test for both X and
Xdialog.
##
if [[ -z $DISPLAY ]] ; then dialog --infobox "X not running" 0 0 ;
$vista_source/dvista ; exit 1
fi
export XDIALOG=`which Xdialog`
if [[ -z $XDIALOG ]] ; then dialog --msgbox "Xdialog not installed" 0 0 ;
$vista_source/dvista ; exit 1
fi
##
>
> [KSB] I don't know about the environment variables that M2Web uses,
> but I would hazard a guess that if you are using M2Web, then the
> /usr/local/OpenVistA/vista script is superfluous.
>
[jlz] OK, That clarifies my thinking... I hope. I was fearful of a conflict
between VistA running under a local user logged into FileMan and M2Web hitting
the same database from outside. But the environental variables that each
chooses to employ have no crosstalk with each other. They just need to work
within their respective environs as they hit the common VistA database.
Understanding... now for something that <>. One small step for mankind,
one giant leap etc.
> regards,
> jlz better grandfather than programmer.
>
> [KSB] Yes, but better physician than programmer, I'm sure!
[jlz] Of late I have been impressed with the need to get our programs right.
I think the VistA community appreciates that software development can also be
a matter of life-and-death importance.
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
RE: [Hardhats-members] Xdialog, dialog, m2web
Title: RE: [Hardhats-members] Xdialog, dialog, m2web
John --
Something is really screwed up with e-mail. I received your e-mail after the responses in the thread it initiated! Comments below.
-- Bhaskar
-Original Message-
From: [EMAIL PROTECTED] on behalf of johnleozimmer
Sent: Sat 3/5/2005 10:46 AM
To: hardhats-members@lists.sourceforge.net
Cc:
Subject: [Hardhats-members] Xdialog, dialog, m2web
I'm aiming toward Boston and I'm attempting to fancy up Bhaskar's
install/run script. My ultimate goal is to include the installation of
m2web into the scripts:
[KSB] Actually, you can integrate M2web without touching the /usr/local/OpenVistA/vista script. Assuming that you have the database installed in (for example) /mnt/hda4/myVistA/OpenVistA/g/mumps.dat, then just put the routines for M2Web in /mnt/hda4/myVistA/OpenVistA/r/. The object files will automatically get compiled into /mnt/hda4/myVistA/OpenVistA/o/.
1.) I've added a test to ...OpenVistA/vista to switch from Xdialog to
plain old dialog in the absence of Xwindows, like so:
###
if [[ -z $DISPLAY ]] ; then dialog --infobox "X not running" 0 0 ;
$vista_source/dvista ; exit 1
fi
###
1b.) ?? How do I add a test for the <> of Xdialog itself??
[KSB] Try something like:
export DIALOG=${DIALOG:=`which Xdialog`} ; if [[ -z $DIALOG ]] ; then export DIALOG=`which dialog` ; fi
and in your script use $DIALOG as the program to use. Now that I think about it, a construct like the following might be even better:
if [[ -z $DISPLAY ]] ; then export DIALOG=`which dialog` ; else ... ; fi
2.) Now I have a new script "...OpenVistA/dvista" that uses dialog
instead of Xdialog. I will post that here if anyone needs it before Boston.
3.) I've added a menu option to do a rundown to both scripts:
case $action in
"Run") ...snip
"Erase") ...snip
"Install (and run)") ...snip
;;
"Rundown") clear
`$gtm_dist/mupip rundown -r "*"`
Xdialog --infobox "rundown finished" 0 0 6000 ; exit 1
;;
esac
3.) The addition of m2web's installation is giving me trouble, partly
because Jim Self uses environmental variables differently.
From m2web-vista-cgi:
#!/bin/bash
#invoke GT.M for M2Web CGI
export m2web="/usr/local/m2web"
export vista_home="/usr/local/vista/OpenVistA"
export gtm_sysid="vista.net"
export gtm_dist="/usr/local/gtm"
export gtm_log="$gtm_dist/log"
export gtmgbldir="$vista_home/g/mumps.gld"
export gtmroutines="$vista_home/o($m2web/w $vista_home/r) $gtm_dist"
Bhaskar's script uses $vista_source where Jim's has $vista_home.
And Bhaskar uses $vista_home for the location of the directory in which
Vista will run.
Guidance from Bhaskar and Jim would be appreciated.
[KSB] I don't know about the environment variables that M2Web uses, but I would hazard a guess that if you are using M2Web, then the /usr/local/OpenVistA/vista script is superfluous.
regards,
jlz better grandfather than programmer.
[KSB] Yes, but better physician than programmer, I'm sure!
Re: [Hardhats-members] Xdialog, dialog, m2web
Greg Kreis wrote: >Is the M2Web code namespaced in a VA recognized namespace? I think it >is essential to maintain the VistA coding practices in some areas in >order to avoid large conflicts in the future. No it is not. It is purposely written outside the VA coding conventions to ensure that there will be no conflict. The M2Web routines and variables are named in lowercase or mixed case. The ones associated with basic web features like HTTP, CGI, HTML all begin with "ht". --- Jim Self Systems Architect, Lead Developer VMTH Computer Services, UC Davis (http://www.vmth.ucdavis.edu/us/jaself) --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Xdialog, dialog, m2web
Greg;
Jim does have a namespace, but most of his routines
are not using the namespace. This plus, Jim has re-written a number of the
DI utilities so that they work with his code. There is little
conflict at this point because most of Jim's routines and globals use
lower-case, but most of the m2web globals are not fileman compatible, and
some parallel the OPTION and PROTOCOL files, but are different. He
has been developing in his own isolated environment and hasn't had to deal
with the VA standards. His namespace is a lower case, m2w. His
routines include ht* and some others.
Jim, have I described it correctly?
- Original Message -
From:
Greg Kreis
To: hardhats-members@lists.sourceforge.net
Sent: Saturday, March 05, 2005 12:43
PM
Subject: Re: [Hardhats-members] Xdialog,
dialog, m2web
When you say 'not to the namespacing conventions', what do you
mean specifically? I am glad to hear it has an official
namespace.Chris Richardson wrote:
Yes, m2web does have a VA namespace, but
the application is not written to the namespacing conventions.
That has been an issue we want to help rectify, but it will not be simple to
do.
-
Original Message -
From:
Greg Kreis
To:
hardhats-members@lists.sourceforge.net
Sent:
Saturday, March 05, 2005 11:07 AM
Subject:
Re: [Hardhats-members] Xdialog, dialog, m2web
Is the M2Web code namespaced in a VA recognized
namespace? I think it is essential to maintain the VistA coding
practices in some areas in order to avoid large conflicts in the
future.Kevin Toppenberg wrote:
Zimmer,
comments below
--- John Leo Zimmer <[EMAIL PROTECTED]> wrote:
I'm aiming toward Boston and I'm attempting to fancy
up Bhaskar's
install/run script. My ultimate goal is to include
the installation of m2web
into the scripts:
Do you mean that you will have the script
automatically install M2web on the system? Why not
simply install it, then create a master disk. This
would involve having Bhaskar burn a new Viva disk.
The same could apply for VPE. I think it should come
pre-installed.
1.) I've added a test to ...OpenVistA/vista to
switch from Xdialog to plain
old dialog in the absence of Xwindows, like so:
###
if [[ -z $DISPLAY ]] ; then dialog --infobox "X not
running" 0 0 ;
$vista_source/dvista ; exit 1
fi
###
1b.) ?? How do I add a test for the <> of
Xdialog itself??
Xdialog is a file that lives in /urs/bin. I think you
could do a "file-exists" type function. I don't know
what this is in Linux, but it should be standard.
2.) Now I have a new script "...OpenVistA/dvista"
that uses dialog instead
of Xdialog. I will post that here if anyone needs it
before Boston.
3.) I've added a menu option to do a rundown to both
scripts. This works
nicely and can be branched to on exit from GTM> so
the user can agree to
rundown routinely:
case $action in
"Run")...snip
"Erase") ...snip
"Install (and run)") ...snip
;;
"Rundown") clear
`$gtm_dist/mupip rundown -r "*"`
Xdialog --infobox "rundown finished" 0 0
6000 ; exit 1
;;
esac
I like this a lot.
I you were to try to make that script act like a
Windows install wizard, it might be nice to have it
create a text file that specifies the state of the
computer. This way it could recognize that GTM has
already been installed, and change the options
presented to the user. I.e. don't prompt for a
uninstall option unless it has been installed etc.
Also, do you know Xdialog well enough to include a
graphic on the dialog box at start up. It would make
it look much more professional.
3.) The addition of m2web's installation is giving
me trouble, partly
because Jim Self uses environmental variables
differently.
>From m2web-vista-cgi:
#!/bin/bash
#invoke GT.M for M2Web CGI
export m2web="/usr/local/m2web"
export vista_home="/usr/local/vista/OpenVistA"
export gtm_sysid="vista.net"
export gtm_dist="/usr/local/gtm"
export gtm_log="$gtm_dist/log"
export gtmgbldir="$vista_home/g/mumps.gld"
export gtmroutines="$vista_home/o($m2web/w
$vista_home/r) $gtm_dist"
Bhaskar's script uses $vista_source where Jim's has
$vista_home.
And Bhaskar uses $vista_home for the location of the
directory in which
Vista will run.
Not sure I can help you here. I think that the
$vista_home variable will only be referenced from the
install script. I don't think that GT.M needs it, and
Vis
Re: [Hardhats-members] Xdialog, dialog, m2web
John, It appears that I have not yet received your original message in this thread so I will respond to your questions about M2Web here. Actually, my use of the variable vista_home was borrowed from one of Bhaskar's scripts. He used vista_home to refer to the location that vista was (to be) installed in and vista_source as the location *from* which it would be installed. The M2Web script is only concerned with running GT.M, not installing it >--- John Leo Zimmer <[EMAIL PROTECTED]> wrote: >> 3.) The addition of m2web's installation is giving >> me trouble, partly >> because Jim Self uses environmental variables >> differently. >> From m2web-vista-cgi: >> >> #!/bin/bash >> #invoke GT.M for M2Web CGI >> export m2web="/usr/local/m2web" >> export vista_home="/usr/local/vista/OpenVistA" >> export gtm_sysid="vista.net" Change gtm_sysid to whatever name you want to give your server. >> export gtm_dist="/usr/local/gtm" >> export gtm_log="$gtm_dist/log" I think you can delete gtm_log. At the least put it somewhere else. Bhaskar has noted before that the log should not be located in $gtm_dist. >> export gtmgbldir="$vista_home/g/mumps.gld" >> export gtmroutines="$vista_home/o($m2web/w $vista_home/r) $gtm_dist" >> >> Bhaskar's script uses $vista_source where Jim's has >> $vista_home. >> And Bhaskar uses $vista_home for the location of the >> directory in which >> Vista will run. >Kevin > >P.S. >Can you post a URL where I can download the M2Web code >and install it? http://vista.vmth.ucdavis.edu/home/index/48.html --- Jim Self Systems Architect, Lead Developer VMTH Computer Services, UC Davis (http://www.vmth.ucdavis.edu/us/jaself) --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Xdialog, dialog, m2web
When you say 'not to the namespacing conventions', what do you mean
specifically? I am glad to hear it has an official namespace.
Chris Richardson wrote:
Yes, m2web does have a VA
namespace, but the application is not written to the namespacing
conventions. That has been an issue we want to help rectify, but it
will not be simple to do.
-
Original Message -
From:
Greg Kreis
To:
hardhats-members@lists.sourceforge.net
Sent:
Saturday, March 05, 2005 11:07 AM
Subject:
Re: [Hardhats-members] Xdialog, dialog, m2web
Is the M2Web code namespaced in a VA recognized namespace? I think it
is essential to maintain the VistA coding practices in some areas in
order to avoid large conflicts in the future.
Kevin Toppenberg wrote:
Zimmer,
comments below
--- John Leo Zimmer <[EMAIL PROTECTED]> wrote:
I'm aiming toward Boston and I'm attempting to fancy
up Bhaskar's
install/run script. My ultimate goal is to include
the installation of m2web
into the scripts:
Do you mean that you will have the script
automatically install M2web on the system? Why not
simply install it, then create a master disk. This
would involve having Bhaskar burn a new Viva disk.
The same could apply for VPE. I think it should come
pre-installed.
1.) I've added a test to ...OpenVistA/vista to
switch from Xdialog to plain
old dialog in the absence of Xwindows, like so:
###
if [[ -z $DISPLAY ]] ; then dialog --infobox "X not
running" 0 0 ;
$vista_source/dvista ; exit 1
fi
###
1b.) ?? How do I add a test for the <> of
Xdialog itself??
Xdialog is a file that lives in /urs/bin. I think you
could do a "file-exists" type function. I don't know
what this is in Linux, but it should be standard.
2.) Now I have a new script "...OpenVistA/dvista"
that uses dialog instead
of Xdialog. I will post that here if anyone needs it
before Boston.
3.) I've added a menu option to do a rundown to both
scripts. This works
nicely and can be branched to on exit from GTM> so
the user can agree to
rundown routinely:
case $action in
"Run")...snip
"Erase") ...snip
"Install (and run)") ...snip
;;
"Rundown") clear
`$gtm_dist/mupip rundown -r "*"`
Xdialog --infobox "rundown finished" 0 0
6000 ; exit 1
;;
esac
I like this a lot.
I you were to try to make that script act like a
Windows install wizard, it might be nice to have it
create a text file that specifies the state of the
computer. This way it could recognize that GTM has
already been installed, and change the options
presented to the user. I.e. don't prompt for a
uninstall option unless it has been installed etc.
Also, do you know Xdialog well enough to include a
graphic on the dialog box at start up. It would make
it look much more professional.
3.) The addition of m2web's installation is giving
me trouble, partly
because Jim Self uses environmental variables
differently.
>From m2web-vista-cgi:
#!/bin/bash
#invoke GT.M for M2Web CGI
export m2web="/usr/local/m2web"
export vista_home="/usr/local/vista/OpenVistA"
export gtm_sysid="vista.net"
export gtm_dist="/usr/local/gtm"
export gtm_log="$gtm_dist/log"
export gtmgbldir="$vista_home/g/mumps.gld"
export gtmroutines="$vista_home/o($m2web/w
$vista_home/r) $gtm_dist"
Bhaskar's script uses $vista_source where Jim's has
$vista_home.
And Bhaskar uses $vista_home for the location of the
directory in which
Vista will run.
Not sure I can help you here. I think that the
$vista_home variable will only be referenced from the
install script. I don't think that GT.M needs it, and
VistA don't need it. So you could search-and-replace
it in Bhaskar's install script. On the other hand,
M2Web may well reference the variable, so it might be
dicey changing that. So if I were doing this, I would
try to search in Bhaskar's script for all $vista_home
instances and rename them to $vista_home_1 or
something.
Glad you are working on this.
Kevin
P.S.
Can you post a URL where I can download the M2Web code
and install it?
Kevin
Guidance from Bhaskar and Jim would be appreciated.
regards,
jlz better grandfather than programmer.
Bhaskar, KS wrote:
[KSB] If you are still in the process of setting
up GT.M and the
environment (vs. configuring VistA itself), let me
Re: [Hardhats-members] Xdialog, dialog, m2web
Yes, m2web does have a VA namespace, but the application is not written to the namespacing conventions. That has been an issue we want to help rectify, but it will not be simple to do. - Original Message - From: Greg Kreis To: hardhats-members@lists.sourceforge.net Sent: Saturday, March 05, 2005 11:07 AM Subject: Re: [Hardhats-members] Xdialog, dialog, m2web Is the M2Web code namespaced in a VA recognized namespace? I think it is essential to maintain the VistA coding practices in some areas in order to avoid large conflicts in the future.Kevin Toppenberg wrote: Zimmer, comments below --- John Leo Zimmer <[EMAIL PROTECTED]> wrote: I'm aiming toward Boston and I'm attempting to fancy up Bhaskar's install/run script. My ultimate goal is to include the installation of m2web into the scripts: Do you mean that you will have the script automatically install M2web on the system? Why not simply install it, then create a master disk. This would involve having Bhaskar burn a new Viva disk. The same could apply for VPE. I think it should come pre-installed. 1.) I've added a test to ...OpenVistA/vista to switch from Xdialog to plain old dialog in the absence of Xwindows, like so: ### if [[ -z $DISPLAY ]] ; then dialog --infobox "X not running" 0 0 ; $vista_source/dvista ; exit 1 fi ### 1b.) ?? How do I add a test for the <> of Xdialog itself?? Xdialog is a file that lives in /urs/bin. I think you could do a "file-exists" type function. I don't know what this is in Linux, but it should be standard. 2.) Now I have a new script "...OpenVistA/dvista" that uses dialog instead of Xdialog. I will post that here if anyone needs it before Boston. 3.) I've added a menu option to do a rundown to both scripts. This works nicely and can be branched to on exit from GTM> so the user can agree to rundown routinely: case $action in "Run")...snip "Erase") ...snip "Install (and run)") ...snip ;; "Rundown") clear `$gtm_dist/mupip rundown -r "*"` Xdialog --infobox "rundown finished" 0 0 6000 ; exit 1 ;; esac I like this a lot. I you were to try to make that script act like a Windows install wizard, it might be nice to have it create a text file that specifies the state of the computer. This way it could recognize that GTM has already been installed, and change the options presented to the user. I.e. don't prompt for a uninstall option unless it has been installed etc. Also, do you know Xdialog well enough to include a graphic on the dialog box at start up. It would make it look much more professional. 3.) The addition of m2web's installation is giving me trouble, partly because Jim Self uses environmental variables differently. >From m2web-vista-cgi: #!/bin/bash #invoke GT.M for M2Web CGI export m2web="/usr/local/m2web" export vista_home="/usr/local/vista/OpenVistA" export gtm_sysid="vista.net" export gtm_dist="/usr/local/gtm" export gtm_log="$gtm_dist/log" export gtmgbldir="$vista_home/g/mumps.gld" export gtmroutines="$vista_home/o($m2web/w $vista_home/r) $gtm_dist" Bhaskar's script uses $vista_source where Jim's has $vista_home. And Bhaskar uses $vista_home for the location of the directory in which Vista will run. Not sure I can help you here. I think that the $vista_home variable will only be referenced from the install script. I don't think that GT.M needs it, and VistA don't need it. So you could search-and-replace it in Bhaskar's install script. On the other hand, M2Web may well reference the variable, so it might be dicey changing that. So if I were doing this, I would try to search in Bhaskar's script for all $vista_home instances and rename them to $vista_home_1 or something. Glad you are working on this. Kevin P.S. Can you post a URL where I can download the M2Web code and install it? Kevin Guidance from Bhaskar and Jim would be appreciated. regards, jlz better grandfather than programmer. Bhaskar, KS wrote: [KSB] If you are still in the process of setting up GT.M and the environment (vs. configuring VistA itself), let me suggest a much faster alternative. You will need Xdialog (http://xdialog.dyns.net) on your PC for this approach. Download an OpenVistA SemiVivA file (either OpenVistA SemiVivA 0.4 or OpenVistA SemiVivA FOIA Gold 20050212), say to /Distrib/OpenVistA. The following will install GT.M and OpenVistA (
Re: [Hardhats-members] Xdialog, dialog, m2web
I bet I know who we can ask where to put it. ;-) On Saturday 05 March 2005 02:07 pm, Greg Kreis wrote: > Is the M2Web code namespaced in a VA recognized namespace? I think it > is essential to maintain the VistA coding practices in some areas in > order to avoid large conflicts in the future. > > Kevin Toppenberg wrote: > >Zimmer, > > > >comments below > > > >--- John Leo Zimmer <[EMAIL PROTECTED]> wrote: > >>I'm aiming toward Boston and I'm attempting to fancy > >>up Bhaskar's > >>install/run script. My ultimate goal is to include > >>the installation of m2web > >>into the scripts: > > > >Do you mean that you will have the script > >automatically install M2web on the system? Why not > >simply install it, then create a master disk. This > >would involve having Bhaskar burn a new Viva disk. > >The same could apply for VPE. I think it should come > >pre-installed. > > > >>1.) I've added a test to ...OpenVistA/vista to > >>switch from Xdialog to plain > >>old dialog in the absence of Xwindows, like so: > >> > >>### > >>if [[ -z $DISPLAY ]] ; then dialog --infobox "X not > >>running" 0 0 ; > >>$vista_source/dvista ; exit 1 > >> fi > >>### > >> > >>1b.) ?? How do I add a test for the <> of > >>Xdialog itself?? > > > >Xdialog is a file that lives in /urs/bin. I think you > >could do a "file-exists" type function. I don't know > >what this is in Linux, but it should be standard. > > > >>2.) Now I have a new script "...OpenVistA/dvista" > >>that uses dialog instead > >>of Xdialog. I will post that here if anyone needs it > >>before Boston. > >> > >>3.) I've added a menu option to do a rundown to both > >>scripts. This works > >>nicely and can be branched to on exit from GTM> so > >>the user can agree to > >>rundown routinely: > >> > >>case $action in > >> > >> "Run")...snip > >> "Erase") ...snip > >> "Install (and run)") ...snip > >>;; > >> "Rundown") clear > >>`$gtm_dist/mupip rundown -r "*"` > >>Xdialog --infobox "rundown finished" 0 0 > >>6000 ; exit 1 > >>;; > >>esac > > > >I like this a lot. > > > >I you were to try to make that script act like a > >Windows install wizard, it might be nice to have it > >create a text file that specifies the state of the > >computer. This way it could recognize that GTM has > >already been installed, and change the options > >presented to the user. I.e. don't prompt for a > >uninstall option unless it has been installed etc. > > > >Also, do you know Xdialog well enough to include a > >graphic on the dialog box at start up. It would make > >it look much more professional. > > > >>3.) The addition of m2web's installation is giving > >>me trouble, partly > >>because Jim Self uses environmental variables > >>differently. > >>From m2web-vista-cgi: > >> > >>#!/bin/bash > >>#invoke GT.M for M2Web CGI > >>export m2web="/usr/local/m2web" > >>export vista_home="/usr/local/vista/OpenVistA" > >>export gtm_sysid="vista.net" > >>export gtm_dist="/usr/local/gtm" > >>export gtm_log="$gtm_dist/log" > >>export gtmgbldir="$vista_home/g/mumps.gld" > >>export gtmroutines="$vista_home/o($m2web/w > >>$vista_home/r) $gtm_dist" > >> > >>Bhaskar's script uses $vista_source where Jim's has > >>$vista_home. > >>And Bhaskar uses $vista_home for the location of the > >>directory in which > >>Vista will run. > > > >Not sure I can help you here. I think that the > >$vista_home variable will only be referenced from the > >install script. I don't think that GT.M needs it, and > >VistA don't need it. So you could search-and-replace > >it in Bhaskar's install script. On the other hand, > >M2Web may well reference the variable, so it might be > >dicey changing that. So if I were doing this, I would > >try to search in Bhaskar's script for all $vista_home > >instances and rename them to $vista_home_1 or > >something. > > > >Glad you are working on this. > > > >Kevin > > > >P.S. > >Can you post a URL where I can download the M2Web code > >and install it? > > > >Kevin > > > >>Guidance from Bhaskar and Jim would be appreciated. > >> > >> > >>regards, > >>jlz better grandfather than programmer. > >> > >>Bhaskar, KS wrote: > >>>[KSB] If you are still in the process of setting > >> > >>up GT.M and the > >> > >>>environment (vs. configuring VistA itself), let me > >> > >>suggest a much faster > >> > >>>alternative. You will need Xdialog > >> > >>(http://xdialog.dyns.net) on your PC > >> > >>>for this approach. > >>> > >>>Download an OpenVistA SemiVivA file (either > >> > >>OpenVistA SemiVivA 0.4 or > >> > >>>OpenVistA SemiVivA FOIA Gold 20050212), say to > >> > >>/Distrib/OpenVistA. The > >> > >>>following will install GT.M and OpenVistA (replace > >> > >>the filename in the > >> > >>>second line with appropriate name of downloaded > >> > >>file): > >> > >> > >> > >> > >> > >> > >> > >> > >>Healthcare, a human right. > > > >--- > > > >>SF email is sponsored by - The IT Produc
Re: [Hardhats-members] Xdialog, dialog, m2web
Is the M2Web code namespaced in a VA recognized namespace? I think it is essential to maintain the VistA coding practices in some areas in order to avoid large conflicts in the future. Kevin Toppenberg wrote: Zimmer, comments below --- John Leo Zimmer <[EMAIL PROTECTED]> wrote: I'm aiming toward Boston and I'm attempting to fancy up Bhaskar's install/run script. My ultimate goal is to include the installation of m2web into the scripts: Do you mean that you will have the script automatically install M2web on the system? Why not simply install it, then create a master disk. This would involve having Bhaskar burn a new Viva disk. The same could apply for VPE. I think it should come pre-installed. 1.) I've added a test to ...OpenVistA/vista to switch from Xdialog to plain old dialog in the absence of Xwindows, like so: ### if [[ -z $DISPLAY ]] ; then dialog --infobox "X not running" 0 0 ; $vista_source/dvista ; exit 1 fi ### 1b.) ?? How do I add a test for the <> of Xdialog itself?? Xdialog is a file that lives in /urs/bin. I think you could do a "file-exists" type function. I don't know what this is in Linux, but it should be standard. 2.) Now I have a new script "...OpenVistA/dvista" that uses dialog instead of Xdialog. I will post that here if anyone needs it before Boston. 3.) I've added a menu option to do a rundown to both scripts. This works nicely and can be branched to on exit from GTM> so the user can agree to rundown routinely: case $action in "Run")...snip "Erase") ...snip "Install (and run)") ...snip ;; "Rundown") clear `$gtm_dist/mupip rundown -r "*"` Xdialog --infobox "rundown finished" 0 0 6000 ; exit 1 ;; esac I like this a lot. I you were to try to make that script act like a Windows install wizard, it might be nice to have it create a text file that specifies the state of the computer. This way it could recognize that GTM has already been installed, and change the options presented to the user. I.e. don't prompt for a uninstall option unless it has been installed etc. Also, do you know Xdialog well enough to include a graphic on the dialog box at start up. It would make it look much more professional. 3.) The addition of m2web's installation is giving me trouble, partly because Jim Self uses environmental variables differently. >From m2web-vista-cgi: #!/bin/bash #invoke GT.M for M2Web CGI export m2web="/usr/local/m2web" export vista_home="/usr/local/vista/OpenVistA" export gtm_sysid="vista.net" export gtm_dist="/usr/local/gtm" export gtm_log="$gtm_dist/log" export gtmgbldir="$vista_home/g/mumps.gld" export gtmroutines="$vista_home/o($m2web/w $vista_home/r) $gtm_dist" Bhaskar's script uses $vista_source where Jim's has $vista_home. And Bhaskar uses $vista_home for the location of the directory in which Vista will run. Not sure I can help you here. I think that the $vista_home variable will only be referenced from the install script. I don't think that GT.M needs it, and VistA don't need it. So you could search-and-replace it in Bhaskar's install script. On the other hand, M2Web may well reference the variable, so it might be dicey changing that. So if I were doing this, I would try to search in Bhaskar's script for all $vista_home instances and rename them to $vista_home_1 or something. Glad you are working on this. Kevin P.S. Can you post a URL where I can download the M2Web code and install it? Kevin Guidance from Bhaskar and Jim would be appreciated. regards, jlz better grandfather than programmer. Bhaskar, KS wrote: [KSB] If you are still in the process of setting up GT.M and the environment (vs. configuring VistA itself), let me suggest a much faster alternative. You will need Xdialog (http://xdialog.dyns.net) on your PC for this approach. Download an OpenVistA SemiVivA file (either OpenVistA SemiVivA 0.4 or OpenVistA SemiVivA FOIA Gold 20050212), say to /Distrib/OpenVistA. The following will install GT.M and OpenVistA (replace the filename in the second line with appropriate name of downloaded file): Healthcare, a human right. --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op
Re: [Hardhats-members] Xdialog, dialog, m2web
> [jlz] > I am already spending too much time on Xdialog. > Pure, simple, old dialog is probably more > functional. > I think that Xdialog has all the functionality of dialog. I have made a M interface for Xdialog and dialog if you ever need it. Kevin __ Celebrate Yahoo!'s 10th Birthday! Yahoo! Netrospective: 100 Moments of the Web http://birthday.yahoo.com/netrospective/ --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Xdialog, dialog, m2web
s > > My ultimate goal is to include > > the installation of m2web > > into the scripts: > > Do you mean that you will have the script > automatically install M2web on the system? Why not > simply install it, then create a master disk. This > would involve having Bhaskar burn a new Viva disk. [jlz] That's my target. One Xdialog/dialog script to install and run the whole demo system... coLinux compatable as well. > The same could apply for VPE. I think it should come > pre-installed. [jlz] Agreed. But that can just be included in the OpenVistA tar > > > > 1.) I've added a test to ...OpenVistA/vista to > > switch from Xdialog to plain > > old dialog in the absence of Xwindows, like so: > > > > ### > > if [[ -z $DISPLAY ]] ; then dialog --infobox "X not > > running" 0 0 ; > > $vista_source/dvista ; exit 1 > >fi > > ### > > > > 1b.) ?? How do I add a test for the <> of > > Xdialog itself?? > > Xdialog is a file that lives in /urs/bin. I think you > could do a "file-exists" type function. I don't know > what this is in Linux, but it should be standard. > [jlz] I know the expertise is out there.. and searchable if I weren't so lazy... and on call all weekend. > > ;; > > "Rundown") clear > > `$gtm_dist/mupip rundown -r "*"` > > Xdialog --infobox "rundown finished" 0 0 > > 6000 ; exit 1 > > ;; > > esac > > Also, do you know Xdialog well enough to include a > graphic on the dialog box at start up. It would make > it look much more professional. > [jlz] I am already spending too much time on Xdialog. Pure, simple, old dialog is probably more functional. --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Xdialog, dialog, m2web
Hey Grandpa Z, have you talked with Chris or Jim or any of the folks at that grueling weekend of M2Web and VistA programming? You may be reinventing the wheel. Also, I added this to my .bashrc and I LOVE it, if I do say so myself! alias rundown="$gtm_dist/mupip rundown -r \"*\"" On Saturday 05 March 2005 12:15 pm, Kevin Toppenberg wrote: > Zimmer, > > comments below > > --- John Leo Zimmer <[EMAIL PROTECTED]> wrote: > > I'm aiming toward Boston and I'm attempting to fancy > > up Bhaskar's > > install/run script. My ultimate goal is to include > > the installation of m2web > > into the scripts: > > Do you mean that you will have the script > automatically install M2web on the system? Why not > simply install it, then create a master disk. This > would involve having Bhaskar burn a new Viva disk. > The same could apply for VPE. I think it should come > pre-installed. > > > 1.) I've added a test to ...OpenVistA/vista to > > switch from Xdialog to plain > > old dialog in the absence of Xwindows, like so: > > > > ### > > if [[ -z $DISPLAY ]] ; then dialog --infobox "X not > > running" 0 0 ; > > $vista_source/dvista ; exit 1 > >fi > > ### > > > > 1b.) ?? How do I add a test for the <> of > > Xdialog itself?? > > Xdialog is a file that lives in /urs/bin. I think you > could do a "file-exists" type function. I don't know > what this is in Linux, but it should be standard. > > > 2.) Now I have a new script "...OpenVistA/dvista" > > that uses dialog instead > > of Xdialog. I will post that here if anyone needs it > > before Boston. > > > > 3.) I've added a menu option to do a rundown to both > > scripts. This works > > nicely and can be branched to on exit from GTM> so > > the user can agree to > > rundown routinely: > > > > case $action in > > > > "Run")...snip > > "Erase") ...snip > > "Install (and run)") ...snip > > ;; > > "Rundown") clear > > `$gtm_dist/mupip rundown -r "*"` > > Xdialog --infobox "rundown finished" 0 0 > > 6000 ; exit 1 > > ;; > > esac > > I like this a lot. > > I you were to try to make that script act like a > Windows install wizard, it might be nice to have it > create a text file that specifies the state of the > computer. This way it could recognize that GTM has > already been installed, and change the options > presented to the user. I.e. don't prompt for a > uninstall option unless it has been installed etc. > > Also, do you know Xdialog well enough to include a > graphic on the dialog box at start up. It would make > it look much more professional. > > > 3.) The addition of m2web's installation is giving > > me trouble, partly > > because Jim Self uses environmental variables > > differently. > > From m2web-vista-cgi: > > > > #!/bin/bash > > #invoke GT.M for M2Web CGI > > export m2web="/usr/local/m2web" > > export vista_home="/usr/local/vista/OpenVistA" > > export gtm_sysid="vista.net" > > export gtm_dist="/usr/local/gtm" > > export gtm_log="$gtm_dist/log" > > export gtmgbldir="$vista_home/g/mumps.gld" > > export gtmroutines="$vista_home/o($m2web/w > > $vista_home/r) $gtm_dist" > > > > Bhaskar's script uses $vista_source where Jim's has > > $vista_home. > > And Bhaskar uses $vista_home for the location of the > > directory in which > > Vista will run. > > Not sure I can help you here. I think that the > $vista_home variable will only be referenced from the > install script. I don't think that GT.M needs it, and > VistA don't need it. So you could search-and-replace > it in Bhaskar's install script. On the other hand, > M2Web may well reference the variable, so it might be > dicey changing that. So if I were doing this, I would > try to search in Bhaskar's script for all $vista_home > instances and rename them to $vista_home_1 or > something. > > Glad you are working on this. > > Kevin > > P.S. > Can you post a URL where I can download the M2Web code > and install it? > > Kevin > > > Guidance from Bhaskar and Jim would be appreciated. > > > > > > regards, > > jlz better grandfather than programmer. > > > > Bhaskar, KS wrote: > > > [KSB] If you are still in the process of setting > > > > up GT.M and the > > > > > environment (vs. configuring VistA itself), let me > > > > suggest a much faster > > > > > alternative. You will need Xdialog > > > > (http://xdialog.dyns.net) on your PC > > > > > for this approach. > > > > > > Download an OpenVistA SemiVivA file (either > > > > OpenVistA SemiVivA 0.4 or > > > > > OpenVistA SemiVivA FOIA Gold 20050212), say to > > > > /Distrib/OpenVistA. The > > > > > following will install GT.M and OpenVistA (replace > > > > the filename in the > > > > > second line with appropriate name of downloaded > > > > file): > > > > > > > > > > Healthcare, a human right. > > --- > > > SF email is sponsored by - The IT Product Guide > > Read honest & candid reviews on hundreds of IT > > Products from real users. >
Re: [Hardhats-members] Xdialog, dialog, m2web
Zimmer, comments below --- John Leo Zimmer <[EMAIL PROTECTED]> wrote: > I'm aiming toward Boston and I'm attempting to fancy > up Bhaskar's > install/run script. My ultimate goal is to include > the installation of m2web > into the scripts: Do you mean that you will have the script automatically install M2web on the system? Why not simply install it, then create a master disk. This would involve having Bhaskar burn a new Viva disk. The same could apply for VPE. I think it should come pre-installed. > > 1.) I've added a test to ...OpenVistA/vista to > switch from Xdialog to plain > old dialog in the absence of Xwindows, like so: > > ### > if [[ -z $DISPLAY ]] ; then dialog --infobox "X not > running" 0 0 ; > $vista_source/dvista ; exit 1 >fi > ### > > 1b.) ?? How do I add a test for the <> of > Xdialog itself?? Xdialog is a file that lives in /urs/bin. I think you could do a "file-exists" type function. I don't know what this is in Linux, but it should be standard. > > 2.) Now I have a new script "...OpenVistA/dvista" > that uses dialog instead > of Xdialog. I will post that here if anyone needs it > before Boston. > > 3.) I've added a menu option to do a rundown to both > scripts. This works > nicely and can be branched to on exit from GTM> so > the user can agree to > rundown routinely: > > case $action in > > "Run")...snip > "Erase") ...snip > "Install (and run)") ...snip > ;; > "Rundown") clear > `$gtm_dist/mupip rundown -r "*"` > Xdialog --infobox "rundown finished" 0 0 > 6000 ; exit 1 > ;; > esac I like this a lot. I you were to try to make that script act like a Windows install wizard, it might be nice to have it create a text file that specifies the state of the computer. This way it could recognize that GTM has already been installed, and change the options presented to the user. I.e. don't prompt for a uninstall option unless it has been installed etc. Also, do you know Xdialog well enough to include a graphic on the dialog box at start up. It would make it look much more professional. > > 3.) The addition of m2web's installation is giving > me trouble, partly > because Jim Self uses environmental variables > differently. > From m2web-vista-cgi: > > #!/bin/bash > #invoke GT.M for M2Web CGI > export m2web="/usr/local/m2web" > export vista_home="/usr/local/vista/OpenVistA" > export gtm_sysid="vista.net" > export gtm_dist="/usr/local/gtm" > export gtm_log="$gtm_dist/log" > export gtmgbldir="$vista_home/g/mumps.gld" > export gtmroutines="$vista_home/o($m2web/w > $vista_home/r) $gtm_dist" > > Bhaskar's script uses $vista_source where Jim's has > $vista_home. > And Bhaskar uses $vista_home for the location of the > directory in which > Vista will run. Not sure I can help you here. I think that the $vista_home variable will only be referenced from the install script. I don't think that GT.M needs it, and VistA don't need it. So you could search-and-replace it in Bhaskar's install script. On the other hand, M2Web may well reference the variable, so it might be dicey changing that. So if I were doing this, I would try to search in Bhaskar's script for all $vista_home instances and rename them to $vista_home_1 or something. Glad you are working on this. Kevin P.S. Can you post a URL where I can download the M2Web code and install it? Kevin > > Guidance from Bhaskar and Jim would be appreciated. > > > regards, > jlz better grandfather than programmer. > > > > Bhaskar, KS wrote: > > > > > [KSB] If you are still in the process of setting > up GT.M and the > > environment (vs. configuring VistA itself), let me > suggest a much faster > > alternative. You will need Xdialog > (http://xdialog.dyns.net) on your PC > > for this approach. > > > > Download an OpenVistA SemiVivA file (either > OpenVistA SemiVivA 0.4 or > > OpenVistA SemiVivA FOIA Gold 20050212), say to > /Distrib/OpenVistA. The > > following will install GT.M and OpenVistA (replace > the filename in the > > second line with appropriate name of downloaded > file): > > > > > > Healthcare, a human right. > > > > --- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT > Products from real users. > Discover which products truly live up to the hype. > Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > ___ > Hardhats-members mailing list > Hardhats-members@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/hardhats-members > __ Celebrate Yahoo!'s 10th Birthday! Yahoo! Netrospective: 100 Moments of the Web http://birthda
