Introduction of Calling Quick Screens as Functions
Glenn
Glenn" <glenn@baxterit.com.au
Tue, 25 May 2004 19:47:54 +1000
This is a multi-part message in MIME format.
------=_NextPart_000_002A_01C44291.2BFBA620
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
It is great that Quick gives a "for each" or "while retrieving" =
construct enabling managed control, beyond Qtp.
As the "top level" or more "in your face tool" within Powerhouse, these =
features are often overlooked. Although, running a screen driver for =
greater control, in batch/thin client/background mode, to some, could =
appear a little strange!!
The ghost screen is/can be a little like a batch process, you never see =
it, hopefully only when it goes wrong, but providing the control I speak =
of above.
Go PH
----- Original Message -----=20
From: Jon Hawks=20
To: chuck.reinke ; Darren Reely ; powerh-l@lists.sowder.com=20
Sent: Tuesday, May 25, 2004 3:35 PM
Subject: Re: Introduction of Calling Quick Screens as Functions
Try this, and for the hard-core's, please excuse the simplicity. I =
copied it from one of our regular jobs we run in batch using quick.
quick auto=3Dqk-batch-1 term=3Dvt220 (if you're on an Open/VMS your =
site might need this)
Screen qk-batch-1
file customer designer
file invoices designer
file payments designer=20
Procedure Internal Special-payments
begin
some great stuff here
gets=20
lets
puts
end
Procedure internal regular-payments
begin
some other great stuff here
get an invoice
get the payment
lets reconcile
puts
end
procedure cust-run
begin
while retrieving customer sequential=20
begin
if cust-type =3D "regular joe"
do internal regular-payments
if cust-type =3D "special"
do internal special-payments
end
procedure initial
begin
do internal cust-run
return
end
build
"chuck.reinke" <chuck.reinke@sbcglobal.net> wrote:
I believe the practice arose many years ago on ancient HP systems =
where
programmers often ran out of stack space. A GHOST screen, as a =
sub-process,
was a technique for gaining additional system resources. Eventually =
some
programming logic supported the technique as well as the idea of =
shared
subroutines.
Chuck
----- Original Message -----=20
From: "Darren Reely"=20
To:=20
Sent: Monday, May 24, 2004 6:10 PM
Subject: Introduction of Calling Quick Screens as Functions
> We were wondering today when the concept was introduced allowing =
coders
> to call quick screens as hidden functions. The code I'm =
maintaining
> seems to have been created as early as April 1992.
>
> While we're on the subject. What is the best way to set up the =
screen
> statement? A! pparently the GHOST option is not _required_ when =
calling
> the screen.
>
> Thanks for the interest.
>
> Darren
>
>
> =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D
> Mailing list: powerh-l@lists.sowder.com
> Subscribe: "subscribe" in message body to
powerh-l-request@lists.sowder.com
> Unsubscribe: "unsubscribe " in message body to
powerh-l-request@lists.sowder.com
> http://lists.sowder.com/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you must be a =
subscriber.
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D
Mailing list: powerh-l@lists.sowder.com
Subscribe: "subscribe" in message body to =
powerh-l-request@lists.sowder.com
Unsubscribe: "unsubscribe " in message body to =
powerh-l-request@lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a =
subscriber.
------=_NextPart_000_002A_01C44291.2BFBA620
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>It is great that Quick gives a "for =
each" or "while=20
retrieving" construct enabling managed control, beyond Qtp.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>As the "top level" or more "in your =
face tool"=20
within Powerhouse, these features are often overlooked. Although, =
running a=20
screen driver for greater control, in batch/thin =
client/background mode, to=20
some, could appear a little strange!!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The ghost screen is/can be a =
little like=20
a batch process, you never see it, hopefully only when it goes wrong, =
but=20
providing the control I speak of above.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Go PH</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3Dhawksj@yahoo.com href=3D"mailto:hawksj@yahoo.com">Jon =
Hawks</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dchuck.reinke@sbcglobal.net=20
href=3D"mailto:chuck.reinke@sbcglobal.net">chuck.reinke</A> ; <A=20
title=3Ddarren.reely@latticesemi.com=20
href=3D"mailto:darren.reely@latticesemi.com">Darren Reely</A> ; <A=20
title=3Dpowerh-l@lists.sowder.com=20
=
href=3D"mailto:powerh-l@lists.sowder.com">powerh-l@lists.sowder.com</A> =
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, May 25, 2004 =
3:35 PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: Introduction of =
Calling=20
Quick Screens as Functions</DIV>
<DIV><BR></DIV>
<DIV>Try this, and for the hard-core's, please excuse the simplicity. =
I copied=20
it from one of our regular jobs we run in batch using quick.</DIV>
<DIV> </DIV>
<DIV>quick auto=3Dqk-batch-1 term=3Dvt220 (if you're on an =
Open/VMS your=20
site might need this)</DIV>
<DIV> </DIV>
<DIV>Screen qk-batch-1</DIV>
<DIV>file customer designer</DIV>
<DIV>file invoices designer</DIV>
<DIV>file payments designer </DIV>
<DIV> </DIV>
<DIV>Procedure Internal Special-payments</DIV>
<DIV> begin</DIV>
<DIV> some great stuff here</DIV>
<DIV> gets </DIV>
<DIV> lets</DIV>
<DIV> puts</DIV>
<DIV> end</DIV>
<DIV>Procedure internal regular-payments</DIV>
<DIV> begin</DIV>
<DIV> some other great stuff here</DIV>
<DIV> get an invoice</DIV>
<DIV> get the payment</DIV>
<DIV> lets reconcile</DIV>
<DIV> puts</DIV>
<DIV> end</DIV>
<DIV>procedure cust-run</DIV>
<DIV> begin</DIV>
<DIV> while retrieving customer sequential </DIV>
<DIV> begin</DIV>
<DIV> if cust-type =3D "regular =
joe"</DIV>
<DIV> do internal=20
regular-payments</DIV>
<DIV> if cust-type =3D =
"special"</DIV>
<DIV> do internal=20
special-payments</DIV>
<DIV> end</DIV>
<DIV>procedure initial</DIV>
<DIV> begin</DIV>
<DIV> do internal cust-run</DIV>
<DIV> return</DIV>
<DIV> end</DIV>
<DIV>build<BR><BR><B><I>"chuck.reinke"=20
<chuck.reinke@sbcglobal.net></I></B> wrote:</DIV>
<BLOCKQUOTE class=3Dreplbq=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px =
solid">I=20
believe the practice arose many years ago on ancient HP systems=20
where<BR>programmers often ran out of stack space. A GHOST screen, =
as a=20
sub-process,<BR>was a technique for gaining additional system =
resources.=20
Eventually some<BR>programming logic supported the technique as well =
as the=20
idea of shared<BR>subroutines.<BR><BR>Chuck<BR><BR>----- Original =
Message=20
----- <BR>From: "Darren Reely" <DARREN.REELY@LATTICESEMI.COM><BR>To: =
<POWERH-L@LISTS.SOWDER.COM><BR>Sent: Monday, May 24, 2004 6:10=20
PM<BR>Subject: Introduction of Calling Quick Screens as=20
Functions<BR><BR><BR>> We were wondering today when the concept =
was=20
introduced allowing coders<BR>> to call quick screens as hidden=20
functions. The code I'm maintaining<BR>> seems to have been =
created as=20
early as April 1992.<BR>><BR>> While we're on the subject. =
What is the=20
best way to set up the screen<BR>> statement? A! pparently the =
GHOST=20
option is not _required_ when calling<BR>> the =
screen.<BR>><BR>>=20
Thanks for the interest.<BR>><BR>> =
Darren<BR>><BR>><BR>> =3D =3D=20
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D =3D =3D =3D =3D =3D =3D<BR>> Mailing list:=20
powerh-l@lists.sowder.com<BR>> Subscribe: "subscribe" in message =
body=20
to<BR>powerh-l-request@lists.sowder.com<BR>> Unsubscribe: =
"unsubscribe=20
<PASSWORD>" in message body =
to<BR>powerh-l-request@lists.sowder.com<BR>>=20
http://lists.sowder.com/mailman/listinfo/powerh-l<BR>> This list =
is=20
closed, thus to post to the list you must be a =
subscriber.<BR><BR><BR>=3D =3D =3D=20
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D =3D =3D =3D =3D =3D<BR>Mailing list:=20
powerh-l@lists.sowder.com<BR>Subscribe: "subscribe" in message body =
to=20
powerh-l-request@lists.sowder.com<BR>Unsubscribe: "unsubscribe =
<PASSWORD>"=20
in message body to=20
=
powerh-l-request@lists.sowder.com<BR>http://lists.sowder.com/mailman/list=
info/powerh-l<BR>This=20
list is closed, thus to post to the list you must be a=20
subscriber.</BLOCKQUOTE><BR><BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_002A_01C44291.2BFBA620--