FERGUSON@TMASL.EXXON.COM (06/16/89)
At my old Bucknell job, we got the new GMR 2D with all of the text/attribute
block changes, and I considered using the INTERLUDE routines for
transition. They were contained in a directory called /sys/gmr2d I think,
but I had trouble using them, they didn't seem to work quite right.
Could've been my fault. Anyway, after a bit of practice (and headaches),
I found that setting up the environment file was the hard part, and
then you could just do global substitutions from calls like
gm_$font_family to gm_$font_family_index. I think even the arguments
to these calls were the same.
I don't particularly like the environment files, especially it's near
impossible to create your own in FORTRAN. The domain_examples programs
used pre-created environment files, and there was no good example of how
to make your own, especially not in fortran. Most of the graphics
programs created in Bucknell's Engineering College were done in FORTRAN
with GMR, and I managed to sneak out of completing that transition
before leaving my job.
I'll take this opportunity to blow off yet some more steam about the
GMR fiasco. Apollo giveth, and Apollo taketh away.
Scott: "Hello, Apollo? This is Scott Ferguson. There's a lot of problems
I'm having with GMR 2D. Can you help me?"
Apollo: "Well, most of your problems are fixed in the wonderful new
GMR 2d V2.0! You should install it."
Scott: "I'm on a maintenance contract, how come I didn't automatically
receive it?"
Apollo: "I don't know, call your sales office. Bye."
Scott: "Hello, sales office? Where's my GMR2D update?"
Sales office: "Do you have GMR 2D on maintenance?"
Scott: "I have Aegis/Domain/IX on maintenance, and GMR 2D is bundled."
Sales office: "No it isn't."
Scott: "Yes it is."
Sales office: "No it isn't." etc, etc, etc.
I don't even use GMR in my new job, but I'm still mad about it.
Scott Ferguson
ferguson@erevax.bitnet
Exxon Research & Engineering