Posts Tagged “documentation”

Currently, the list of underline types in the Office JS documentation is incomplete when compared with the list offered by IntelliSense (as seen in Script Lab). Read the rest of this entry »

Comments No Comments »

Until the release of Office 2013 and all the new information and hype about the “Apps for Office” developer interfaces, there was a useful page on MSDN that collected links to all relevant information concerning developing for the Ribbon and Backstage (http://msdn.microsoft.com/en-us/office/aa905530.aspx), also known as the “Office Fluent UI”.

For a number of months you could still find the link, but it was redirected to a page about the new technology, containing no information whatsoever about the Ribbon. Recently, the old page doesn’t show up any more in internet searches, so only those of us with old “Favorites” or bookmarks to the link collection get to enjoy this frustration. But this is no help at all to the developer unfamiliar with what documentation is available nor any idea where to search for it.

In my work as forum moderator I constantly need to refer to, and refer people to, Ribbon documentation. So I’ve collected all the useful links from that page and posted them in the General Office Developer forum here.

I’ve tried to remove any links that are no longer active, but I may have missed some. So if anyone comes across a problem in that listing, please leave a comment here, or in the forum.

(And I also apologize for the lousy formatting of the post. The forum software doesn’t “like” it and refuses to use the correct spacing and bold formatting )

Comments No Comments »

I think many of us are still trying to come to terms with the fact that the only Help for Office 2013 is on-line. The official information can be found here:
http://technet.microsoft.com/en-us/library/cc178954.aspx
in the section AWS (Assistance and Worldwide Services).

The official line is that this is “better” all around. Help can now be searched on-line and translated. Of course, the fact that this was already the case for almost ten years isn’t mentioned…

Truth be told, the real reason is resources (financial). If Help has to be delivered with the product, then it has to be written before the product is released. This means lots of man-hours just prior to release, then down-time until the next product release. So, to a certain degree, the decision is understandable.

The other side of the coin, however, is that there’s no deadline that forces the documentation to actually be done and finished.

The result at the time of this writing, some months after the official release of Office 2013, is that the object model language reference (Help) hasn’t been reviewed for relevance to Office 2013, and new functionality isn’t fully incorporated. So you can spend literally hours trying to find information in the new, less friendly MSDN interface with the result that
you can’t find what you were looking for because it’s simply not there.

The “final straw” for me was a question about the Word object model in the Word for Developers forum the other day. So I’ve set up a new “page” on this blog to document un-documented behavior and information concerning Office. Everyone is welcome to contribute!

Comments No Comments »