J
John McGhie [MVP - Word and Word Macintosh]
Hi Phillip:
Well, yes, it was left out on purpose. But the "purpose" was Adobe's.
Microsoft announced five years ago that VBA was to be killed off. On BOTH
platforms.
They did this after much internal pain and soul-searching. The reason is
that, BY DESIGN, VBA cannot be properly secured. On Any platform. So it
had to go. It was a great idea (which is why it instantly became so
popular). But AppleScript did it better.
AppleScript you CAN secure. So Microsoft went with AppleScript on the Mac,
and replaced VBA with .NET on the PC. (Dot-NET enables you to choose a wide
variety of source coding languages, including COBOL and, I suspect X-Code or
AppleScript will be offered by someone real soon now ...)
Had Adobe chosen to re-code their add-in in C-sharp, it would run on both
platforms and Save to PDF would have the same functions on Mac as it does on
Windows.
The PDFMaker.dot is not a large piece of code. And it's badly designed. It
creates all manner of problems on the PC (where it works), as well as on the
Mac (where it doesn't).
Cheers
--
Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.
John McGhie <[email protected]>
Microsoft MVP, Word and Word for Macintosh. Consultant Technical Writer
Sydney, Australia +61 (0) 4 1209 1410
platforms for example the PDFMaker added by adobe that allows you to
create PDF's. In the PC version all web-links, and mailto: and such are
appropriately color coated, and are live when PDFMaker is used to create
a PDF. In the Mac version you can still create a PDF but all of the
links are de-colored, and You have to add them. Adobe says That certain
hooks in the PC version to allow this are not in the mac version, on
purpose.
Things like that stuff within the PC version that are deliberately
left. As Mac users we feel like "Second Class" citizens.
Well, yes, it was left out on purpose. But the "purpose" was Adobe's.
Microsoft announced five years ago that VBA was to be killed off. On BOTH
platforms.
They did this after much internal pain and soul-searching. The reason is
that, BY DESIGN, VBA cannot be properly secured. On Any platform. So it
had to go. It was a great idea (which is why it instantly became so
popular). But AppleScript did it better.
AppleScript you CAN secure. So Microsoft went with AppleScript on the Mac,
and replaced VBA with .NET on the PC. (Dot-NET enables you to choose a wide
variety of source coding languages, including COBOL and, I suspect X-Code or
AppleScript will be offered by someone real soon now ...)
Had Adobe chosen to re-code their add-in in C-sharp, it would run on both
platforms and Save to PDF would have the same functions on Mac as it does on
Windows.
The PDFMaker.dot is not a large piece of code. And it's badly designed. It
creates all manner of problems on the PC (where it works), as well as on the
Mac (where it doesn't).
Cheers
--
Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.
John McGhie <[email protected]>
Microsoft MVP, Word and Word for Macintosh. Consultant Technical Writer
Sydney, Australia +61 (0) 4 1209 1410