Summarizing my experience, I would have to say: Dr. Weltner was right.
Anglophones should avoid the product (as it is, for now).
If you do download and install the product, here is what you get. A "so-so"
editor for script, with primitive syntax-highlighting (I expected a RichEdit
control, but found CodeMax, an edit control oriented towards code). Dr.
Weltner also takes a run through your registry, and appears to be tapping
into all the (scriptable?) typelibs he can find. So when the editor comes
up, you get some "hinting". Rather than "tooltip-type" hinting (positioned
near the cursor), Dr. Weltner's "hinting" appears in a little window at the
bottom of your screen. Also, in spite of Dr. Weltner's extensive search of
the registry for typelib info, he seems to have missed (or ignored?) _MY_
scriptable objects (wshLWF et al). Ouch! What an insult!!! Also, Dr.
Weltner is storing all the typelib info that he gathers somewhere, but I
couldn't figure out where. I do hope it's not in my registry.
The syntax colorization colors are "fixed". Dr. Weltner takes the "Henry
Ford approach", you can get any colors you want, so long as they are black
on white (with green highlighting). Call me a member of the "WordPerfect
Generation", but I prefer white text on a dark background. Black on white
seems too "glarey" for me. Since CodeMax is fully customizable as far as
colors, I suppose I could arrange to sent it some messages to get the
colorization I want, but a built-in option for color selection in a code
editor is almost standard these days.
And, while my few words of German are generally sufficient to order a good
meal (mit ein Mass, bitte) in the Ratskeller, my German was not enough to
get me through Dr. Weltner's documentation. One suggestion: there are only
a few menu items, why not include a button for every one on the toolbar?
The toolbar does have buttons for New/Open/Save, but why not all? The point
here is that the toolbar buttons (with their "universally understood"
bitmaps) would have made it easier for non-Deutschophones, to understand the
menu selections. For example, why not buttons for cut/copy/paste, rather
than have you use menu selections (Ausschneiden/Kopieren/Einfügen), and
further, these menu items don't even include the standard speed-keys? OTOH,
there is a somewhat amusing mixture of Deutsch/Englisch. The speed-key for
"Beenden" (Quit) is Ctrl-Q, instead of Ctrl-B.
My final concern is the "installation package". The installer will
"install" a number of system dll's and vb6 runtime controls (ocx's) along
with the "Scripting Spy" utility. However, I am not sure whether there is
any checking as to whether your current controls are newer or older than
what Dr. Weltner is installing. It would have been more reassuring if Dr.
Weltner had used an installer that asks you whether you want a newer/older
version of some dll/ocx that you already have installed on your pc.
For those who don't care to spend $100 for PrimalScript, in my opinion your
best bet for a "hinting" editor for vbs is (good ole reliable) vb5cce,
Microsoft's "Gift to Scripters". Just don't bother to type-cast your
variables (vb will default to "variant", or use "DefVar A-Z" if you prefer),
and away you go...
cheers, jw
"Tobias Weltner" <tobwe...@hotmail.com> wrote in message
news:OgjSqqDRBHA.1904@tkmsftngp05...