Re: Windows/Macro Language Info?

..    On  30.03.05
wrote  docdwarf@panix.com
on  /COMP/LANG/COBOL
in  d2eaim$r9b$1@panix5.panix.com
about  [OT] Windows/Macro Language Info?


d> ... and I was wondering if anyone could tell me what language this is
d> supposed to be emulating - looks kinda sorta familiar, almost - and
d> where I might be able to find a reference-manual for it.

I would say: this is the Autohotkey-Macro-Language.

I would use a real script language, like REXX (IBM's Object REXX
for Win has just been released as Freeware: http://www.oorexx.org) or
Windows Scripting  in either JScript or VBScript flavors. Others may
prefer Perl.



Yours,
Lüko Willms                                     http://www.willms-edv.de
/--------- L.WILLMS@jpberlin.de -- Alle Rechte vorbehalten --

Wir wohnen in Göttingen in Scheiterhaufen, die mit Türen und Fenstern verseh
en sind. -G.C.Lichtenberg

In article <9Tpp1rGuflB@jpberlin-l.willms.jpberlin.de>,
Lueko Willms <l.willms@jpberlin.de> wrote:
>.    On  30.03.05
>  wrote  docdwarf@panix.com
>     on  /COMP/LANG/COBOL
>     in  d2eaim$r9b$1@panix5.panix.com
>  about  [OT] Windows/Macro Language Info?
>
>
>d> ... and I was wondering if anyone could tell me what language this is
>d> supposed to be emulating - looks kinda sorta familiar, almost - and
>d> where I might be able to find a reference-manual for it.
>
>   I would say: this is the Autohotkey-Macro-Language.

I was afraid of that, aye... but thanks anyhow.

DD

<docdwarf@panix.com> wrote in message news:d2erlm$ec3$1@panix5.panix.com...
> In article <9Tpp1rGuflB@jpberlin-l.willms.jpberlin.de>,
> Lueko Willms <l.willms@jpberlin.de> wrote: 
>
> I was afraid of that, aye... but thanks anyhow.
>
> DD
>
Doc, I would be very wary about releasing a procedure that relies on window
co-ordinates and keystrokes.

The equivalent to JCL on a mainframe can be achieved by Windows Host
Scripting on a Windows box.

It costs nothing, is already installed with your Operating System, and
utilises a "proper" language that is very easy to pick up.

I have found it to be extremely useful for application installs where I want
things configured, files created, other files accessed conditions tested and
so on.

For incremental backups you could easily run the programs you do now, under
control of a windows script; you can even automatically schedule it using
the Windows scheduler so your non-diligent user doesn't have to do ANYTHING.
(He would get a message box telling him to load an appropriately labelled CD
in the drive and optionally informing him that backups were about to be run
and was that OK, or would he like to defer it..or whatever you design into
the process. (You have complete controlover the process and can make it do
whatever you want to with whatever mix of manual/automatic you decide is
appropriate. Your backup procedures could be activated by clicking an icon
on the desktop, for example.)

From Windows Host Scripting you can run any program you want to, pass
whatever parameters it requires, access the file system and check whether
files exist, create, update, and delete them, as well as checking what
happened and interfacing to the user via message boxes (you can also get
input if you want to).

It really has all the facilities we used to enjoy with DOS procedures, and
then some. JCL is primitive by comparison.

I turned to it in desperation for a JCL equivalent, about 3 years ago and
have never looked back.

If you decide to try this route and need any help, mail me privately.

Keystroke macros are really NOT the answer here...

Pete.

PS check out: http://www.winguides.com/scripting/

In article <3b4ubnF6g5n3rU1@individual.net>,
Pete Dashwood <dashwood@enternet.co.nz> wrote:
>
><docdwarf@panix.com> wrote in message news:d2erlm$ec3$1@panix5.panix.com...
 
>Doc, I would be very wary about releasing a procedure that relies on window
>co-ordinates and keystrokes.

Well, I've learned how to remove half of that... judicious use of
keystrokes removes the need to rely on window location, there's no need to
right-click to get the Add Files to Zip option after selecting all files
when an alt-F brings it up.

[snip]

>For incremental backups you could easily run the programs you do now, under
>control of a windows script; you can even automatically schedule it using
>the Windows scheduler so your non-diligent user doesn't have to do ANYTHING.[/color
]

*That* is an advantage which merits research.

[snip]

>If you decide to try this route and need any help, mail me privately.

Greatly appreciated, old boy... but be careful what you offer!

kkDD