Advice for developing in python with Microsoft Office?
John J. Lee
jjl at pobox.com
Thu Jun 26 15:18:48 CEST 2003
"Steve Holden" <sholden at holdenweb.com> writes:
> "John J. Lee" <jjl at pobox.com> wrote in message
> news:871xxhvimo.fsf at pobox.com...
> > claird at lairds.com (Cameron Laird) writes:
> > > it's hard to falsify the proposition that some of the
> > > documentation has been managed in order to maximize
> > > frustration.
> > of documentation are bad, so much as the fact that the various bits
> > often don't seem to know of each others' existence. Perhaps that's
> Indeed, one of my own pet peeves about Microsoft documentation is the way
> help systems will restate the blindingly obvious without providing any
> actual help. Suppose there's a "Varm Fnoogle" menu item in my application. I
Yeah, that's the end-user help (whoever the end-user happens to be).
The stuff on MSDN (which has a different purpose, of course) *is*
informative, if you can find it.
> Cameron, with an unusual lack of cynicism, appears to me to be quite wrong
> about the reason for the state of Microsoft documentation. They write it
> that way to maximize training and publishing opportunities.
More information about the Python-list