hi gang,
I have recently been attempting to familiarize myself
with AutoIt.
http://www.autoitscript.com/autoit3/
AutoIt is appealing from a scripting perspective in that
it is a scripting language that has evolved into a
programming language (with api calls and "forms capability")
-- and continues to evolve as we speak (with a new release
comming out every week!).
The autoit gang has adopted the SciTE (Scintilla Text
Editor) as a "development platform". The initial
attraction was that SciTE allows for syntax-coloring,
plus it is extremely customizable. And so, the autoit
gang has been busy customizing. They have "hinting"
(for language, but not typelibs), they have "expando"
(type in "ifthen", and it will give you a template
of a filled-in if statement), they have "tidy", they
have auto debug and tracing capabilities, an "immediate"
window (they call it a "console" window), and on-and-on.
Oh yes, I forgot to mention the form designer. Very
Impressive, plus this all comes at no cost to
the consumer.
This has given me a serious case of SciTE envy.
SciTE does support a number of languages (about 30,
gasp!) including vb and vbScript (no wsf). However,
the vb/vbs support may be fairly characterized as
primitive compared with the autoit support. I would
guess that less than half the vbs keywords are defined.
Alex K. Angelopoulos(sp?) apparently got interested in
SciTE at one point, and did post an updated vbs keyword
file (ca. Nov 2002) which is more complete, but still
not totally complete.
So (finally) here's the question. Has anybody out
there in the vbs world taken it upon him/herself to
customize and/or enhance SciTE for vbs, along the
lines of the autoit enhancements? I am intrigued
by the possibilities of SciTE for use with vbs, but
don't want to waste time in "reinventing-the-wheel".
Yes, yes, I know what you're thinking -- I should just
go and raid my piggy-bank, and spend the $100 for a
copy of PrimalScript. But hey, what's the fun in that?
tiafah, jw