i microsoft.public.mac.office.word skrev John McGhie
Sun, 18 May 2008 08:33:36 +0930 (-), i en artikel med
ID <C4559A60.15117%john@[EMAIL PROTECTED]
>
og titlen "Re: VBA to return in the next version of Office Mac !?",
følgende:
: Hi Mitrokhin:
:
Hi there
: On 16/05/08 5:38 PM, in article
: 160520081008452444%Mitrokhin@[EMAIL PROTECTED]
"Mitrokhin"
: <Mitrokhin@[EMAIL PROTECTED]
> wrote:
:
: > Perhaps this is old hat to some but I havn't seen it mentioned in
here.
:
: The decision was made about two months ago. Some of us have been under
a
: non-disclosure agreement that has prevented us talking about it until
the
: Microsoft announcement appeared.
:
Yes I gathered as much after reading the link provided earlier in this
thread ... can't say that I regret the rewriting (which it still in
progress) now though, because for one thing Word 2008 is so much
nicer to work in than the earlier version, so I would have had to make
the transition - rewriting and all - at some point anyway.
Btw I'm not a professional by a long shot. My "programming" (consisting
mostly of gathering bits and pieces here and there and adding a little
of my own code) is only for my personal non-business use.
: > I wonder if it's worthwhile to rewrite VBA macros in Applescript,
: > (which btw I have been doing for the last couple of days :().
:
: Yes, I think so.
:
: VBA is very good for automation "within" an Application. It begins to
have
: problems across applications, and cannot automate non-Microsoft
Applications
: at all.
:
: AppleScript's strength is that it can automate ANYTHING on a Macintosh.
: Because the AppleScript compiler/runtime runs outside the application,
it is
: extremely good at coordinating the efforts of multiple applications.
:
: AppleScript begins to struggle WITHIN an Application, depending on how
: richly-implemented the AppleScript Dictionary is.
:
: Because the AppleScript dictionaries in Microsoft Office are simply a
: re-expression of the VBA Object Model, and because Microsoft Office's
core
: applications were designed from the get-go to be automated, AppleScript
: provides the ability to automate almost every dot and comma in a
Microsoft
: Office application.
:
Indeed, Applescript seems to be very well integrated. I've also found
that in most cases the rewriting wasn't as hard as I expected (guees it
helped having the MacTech guide close at hand too :), but alas there're
a couple of macros I just can't convert (more due to my own lack of
skills than anything else)
: So now, solution vendors get the ability to choose between two
automation
: technologies. AppleScript will be the winner when the task involves
: automating non-Microsoft applications. VBA will be the winner when the
task
: benefits from having common code with the PC version.
:
: > [first Wordbasic then VBA then Applescript then perhaps VBA 2 then ?
: > sigh]
:
: The one we REALLY want is "dot-Net". Dot-Net is very difficult to do on
the
: Mac, although there are efforts to get it working beginning to appear.
: Microsoft's original plans for dot-Net included making it available on
: platforms other than Win-Tel.
:
: On a personal note, I am "hoping" (and that's all it is, a "hope") that
"VBA
: 2" will take us closer to .Net. By the way, I am also hoping that what
we
: get will be "VBA 7" (the PC Office 2007 version). What we have in
Office
: 2004 is two levels behind that, and the differences are becoming
annoying.
:
My view on this is colored by the fact stated above. I'm not a
professional in contrast to yourself - and I have no idea what a
dot-netification of Mac Office would entail precisely, a part from the
almost guarenteed (?) nescessity of another rewriting of macros on
my part , since as I've hinted at I have a couple of usefull macros
that I just can't convert to AS, which means that they would have to
be converted to the new VBA variety, so I would be perfectly happy
with the old VBA version. *Still* a re-adding of VBA (be that a
completely new version or not) is of course a good thing and can't
help making Mac Office even better than it is today. Also this "VBA to
VBA 2" conversion is a couple of years off too.
May I ask what features of "VBA 7" you miss. Ie. I've found that one
feature that's often lamented is the lack of good Userform sup****t
but I've found that WordBasic.BeginDialog/EndDialog constructs
works really well and looks great in Word 2004 (you can even use
the old Word 6 dialog tool if you have access to a wintel computer).
: Hope this helps
: --
:
: Don't wait for your answer, click here: http://www.word.mvps.org/
:
: Please reply in the group. Please do NOT email me unless I ask you to.
:
: John McGhie, Microsoft MVP, Word and Word:Mac
: Nhulunbuy, NT, Australia. mailto:john@[EMAIL PROTECTED]
Hilsen
Ken
|
