Microsoft Word 2008
#15
Posted 16 January 2008 - 03:11 PM
I don't use VB, but I can see why it's a problem. Hopefully they'll increase automation in the future. For now, I think they just want to get the product out the door. iWork is showing potential, but it's not quite there yet. Numbers needs more work.
#16
Posted 16 January 2008 - 04:20 PM
Separate issue regarding font families: I agree that the long lists scrolling is annoying. Thankfully, I usually know what font I want, so I just type the name in the font pull down menu area rather than scrolling down the list. I get my font faster that way. :)
#17
Posted 16 January 2008 - 05:15 PM
#18
Posted 16 January 2008 - 06:16 PM
#19
Posted 16 January 2008 - 06:18 PM
#20
Posted 16 January 2008 - 07:50 PM
Remember, folks, Word is for recreational desktop publishing, not professional publishing. Better yet, Word should be for . . . words.
#21
Posted 16 January 2008 - 08:34 PM
I have written VBA Excel code to do everything from coding simple task-specific functions to writing complex programs that analyze/summarize huge data sets. If you are not in those market segments then it is understandable that you would rarely come across VBA-encoded documents, especially in Word. In all my coding experience I have only ever written VBA code on the backend of a Word document to create an electronic form for a course survey.
As to AppleScript, I have only ever written—or more correctly recorded and (slightly) modified—one AppleScript in Mac OS 9 to overcome an issue with frequent Canvas 7 preference file corruption. The script would delete the Canvas preference file when the computer was started up and replace it with a backup copy that I knew was not corrupted. With Automator, I created a workflow to do batch renaming. Otherwise, I too have rarely used and therefore have had not compelling reason to learn AppleScript. Except for personal projects, my work must be cross-platform.
Due to Microsoft’s position in the productivity suite market learning VBA was became a de facto skill for a core group of Office users. Unfortunately, AppleScript has never gained that type of traction nor has it, to the best of my knowledge, ever migrated onto Windows in any form. At this point a cross-platform scripting solution is needed and neither Apple nor Microsoft offer it. Office:mac 2004 supported REALbasic coding, but that functionality was not brought to the Windows market making the feature about as useful as adding AppleScript/Automator support. If Microsoft is incapable of keeping scripting parity between the Mac and Wintel PCs, perhaps they should forfeit the task to a company such as REAL Software.
#22
Posted 16 January 2008 - 08:51 PM
That stated, people definitely should not be using a word processor as a pre-press layout program. Word is fine for documents that will be making their way to the user’s printer and not a service bureau.
#23
Posted 17 January 2008 - 04:42 AM
I can honestly say, Microsoft did a very nice job on updating Word. It is organized much nicer, and as the article says, Microsoft made some nice design decisions. There are no more tool bars getting lost, and it is much easier to find functions. Microsoft also upped Apple one on including Page Layout features and templates. It is also more appealing to look at.
Do not get me wrong, I think the listed price stinks. However, Word is far more functional then Pages for people who use a word processor frequently for more then just plain writing. More over, compatibility with other versions of Word is much nicer then what Pages and other competing products are able to offer. Of course this is Microsoft's fault for not opening up the formats, but I can't tell my boss that.
I also do not think you can lay the blame entirely with Microsoft for killing Visual Basic. When Apple decided to go Intel, both Adobe and Microsoft were both halfway into their development cycles for their next versions of Mac products. They both had to stop what they were doing and switch over to new developer tools in order to make Universal applications. Apple's free developer tools are nice, but they were hardly as feature complete as competing products. So, both Adobe and Microsoft had to spend a significant amount of time working with Apple to update its tools to include features and capabilities they were accustomed to in their other development environments. the developers also had to master the new tools, which can be a real pain when you are accustomed to working a certain way.
Microsoft essentially had to rework every line of Office code to make it Universal. If it would have included Visual Basic scripting, we would be waiting probably another year or two for that capability. If rumors are true, Microsoft may be killing Visual Basic in the Windows version of Office in an upcoming release. If so, that even makes more sense as a reason to not incorporate it this time around in the Mac version. As a user, I think that stinks. From a company standpoint, I can certainly understand the reasoning.
#24
Posted 17 January 2008 - 05:14 AM
#25
Posted 17 January 2008 - 05:49 AM
#26
Posted 17 January 2008 - 06:21 AM
My only wish is that Bookends would directly support Pages 08.
This is the first version of Office I've misses since I bought 98. I won't miss it.
#27
Posted 17 January 2008 - 06:29 AM
Aside from the big shift from the text-based UI to the graphical UI in the mid-90's (which was a non-event on the Mac), Word just hasn't changed that much. What other computer product hasn't changed in 12 years, let alone 24? (Answer: Quicken. But that's beside the point.) Browsers barely existed 12 years ago. Digital cameras were a joke. Movie editing on your home PC? Nearly impossible.
I think the travesty of Word is total lack of innovation. The fact that MS cleaned up their interface and rewrote their code is supposed to justify four years of effort and a multi-hundred dollar upgrade? How about truly new features, workflows, IDEAS in word processing? Isn't that where the "R&D" investment should have gone?
This seems to be a real downside of MS's dominant (monopoly?) position in the Office marketplace: they have no reason to innovate, and competitors have no ability to introduce new ideas. http://I think the s...s with Quicken.
I've been searching for a while for a viable Word alternative. Nisus Writer and Mellel are very nice, but don't work for me because of their spotty Endnote support. Other folks, however, may really like them.
OpenOffice is a nice thought, but cloning MS Office seems like exactly the wrong way to create good software. Pages seems kind of hokey.
I really, truly wish that MS or someone would create a NEW word processor, one rethought from the ground up and without 24 years of detritus built in.
#28
Posted 17 January 2008 - 06:33 AM



Sign In
Register
Help


MultiQuote