国际社区的 Joseph发起了一项针对办公软件的改进方案，命名为 Office Desk 目前该项目已发布第一个稳定版插件。
在这个项目当中 Joseph 多数时候会担任协调者的身份，主要的开发工作会留给社区贡献者，预计每季度发布一个稳定版，插件内的相关功能成熟后会逐步合并到 NVDA 本身。
笔者相信以 Joseph 对代码的严格要求程度，相关功能往 NVDA 本身合并不会存在太大的困难， Windows App Essentials 的功能被逐步合并也可以很好的证明这一点。
Office Desk 22.10 (initial release) is now (officially) available:
The release was queued for distribution on community add-ons website. Changelog is same as development releases: general fix to recognize search fields in backstage view, formatting announcement and envelopes dialog label reading fixes in Word 365.
IMPORTANT: if you are using Windows App Essentials and using Word 365, please install Office Desk as upcoming Windows App Essentials release (this weekend at the earliest) will remove format command announcement fix in Word 365.
A few months ago I announced Office Desk, an add-on similar in scope to Windows App Essentials except covering Microsoft Office applications – providing support for controls found in Office apps. Back then I didn’t know whether or not I should proceed in publishing it, but I think the time is right to revive the add-on. The add-on source code can be found at:
The first development build is also available, featuring Word 365 formatting announcement workaround where NVDA will not announce formatting changes such as bold and italic on/off multiple times (after installing the add-on):
The add-on source code contents resemble Windows App Essentials: a global plugin and several app modules. The app modules represent Office apps such as Excel, PowerPoint, Publisher, OneNote, and Access to be filled as development progresses. The global plugin will house handlers for controls found across Office applications. I did not include Outlook and Word app modules since we have add-ons addressing these applications. The end goal of Office Desk is quite similar to Windows App Essentials: provide support, enhancements, and bug fixes for NVDA users using Microsoft 365 (Office) applications, and if possible, bring parts of the add-on to NVDA Core via pull requests.
A couple differences from Windows App Essentials:
• Release cadence: perhaps once a quarter (three months) as I need to devote more time to things other than add-on development and would like to serve as release manager for the add-on, with development snapshots from time to time.
• Development approach: I would like this add-on to be developed via a team of developers working on different aspects of Microsoft 365 applications. I envision my role as more toward a coordinator and release manager than the primary developer (even though the add-on is hosted under my GitHub username, I welcome contributions in the form of issues and pull requests). In other words, I would like to take my hands off coding as much as possible so others can learn and shine (besides, I need to devote more time to other things).
• Word and Outlook Extended add-ons: these will not become part of Office Desk unless authors of these add-ons say it would be best to let Office Desk incorporate work from their add-ons.
Besides trying out a team-based development approach and to bring needed functionality to Office users, the ultimate reason for reviving Office Desk is to lessen the burden on Windows App Essentials add-on – currently Windows App Essentials also covers some parts of Microsoft 365, which is vast and require their own issues to be resolved. I’m also bringing something some people have talked about for some time: separation of concerns and labor between add-ons (let one add-on cover a single area or a concern, or one justifiable, related group of concerns).
I hope to work on one major addition to Office Desk before asking the community to register the add-on on community add-ons website. Thanks.