New (or revived) add-on: Office Desk


 

Hi all,

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:

https://github.com/josephsl/officedesk

 

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):

https://github.com/josephsl/officeDesk/releases/download/dev/officeDesk-20220917-dev.nvda-addon

 

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.

Cheers,

Joseph


Brian's Mail list account
 

I was thinking about the attributes issue the other day, and did wonder if there was any mileage in designing bespoke little sounds of for these changes being on or off during editing a file. My concern would be to find sounds that are short, not too annoying but different enough to be understood.
As an originally sighted person, I do appreciate that one could end up with a string of parameters just to describe one word in a sentence, for example.
Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@...>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Saturday, September 17, 2022 1:44 AM
Subject: [nvda-addons] New (or revived) add-on: Office Desk


Hi all,

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:

https://github.com/josephsl/officedesk



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):

https://github.com/josephsl/officeDesk/releases/download/dev/officeDesk-2022
0917-dev.nvda-addon



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.

Cheers,

Joseph


Rowen Cary
 

Thanks, it's so exciting.


 

Hi,
Not really as it requires traversing the line to figure out each attribute,
which could lead to performance hits.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>
On Behalf Of Brian's Mail list account via groups.io
Sent: Saturday, September 17, 2022 1:17 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] New (or revived) add-on: Office Desk

I was thinking about the attributes issue the other day, and did wonder if
there was any mileage in designing bespoke little sounds of for these
changes being on or off during editing a file. My concern would be to find
sounds that are short, not too annoying but different enough to be
understood.
As an originally sighted person, I do appreciate that one could end up with
a string of parameters just to describe one word in a sentence, for example.
Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@...>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Saturday, September 17, 2022 1:44 AM
Subject: [nvda-addons] New (or revived) add-on: Office Desk


Hi all,

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:

https://github.com/josephsl/officedesk



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):

https://github.com/josephsl/officeDesk/releases/download/dev/officeDesk-2022
0917-dev.nvda-addon



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.

Cheers,

Joseph


 

Hi all,

An issue on NVDA GitHub repo came up that might be resolved with Office Desk: announcing envelope field names in Word 365. I have a working solution but it will lead to conflict with Word Access add-on by Paul as my solution modifies Word app module. There is a slightly hacky solution I'm thinking of that will not modify Word app module directly but can lead to unpredictable results as I need to replace parts of NVDA's support for Word via UIA through a global plugin approach.

This is one of those cases where I think combining add-ons would be better in the long term. I will post my solution as part of September 18th dev build of Office Desk which will be the first beta level build of the add-on (this build will also move formatting announcement fix to Word app module).

Cheers,

JOseph


 

Hi all,

September 18th dev build posted:

https://github.com/josephsl/officeDesk/releases/download/dev/officeDesk-20220918-dev.nvda-addon

 

Changelog:

  • In backstage view, NVDA will announce search suggestion count, as well as letting you use up or down arrows to move between suggestions (NVDA Core issue 13772).
  • In Word, NVDA will announce labels for places such as envelopes dialog (NVDA Core issue 14156).

 

And yes, Word app module was added based on latest code from NVDA Core. I’m working on refactoring it to reduce its size.

Cheers,

Joseph

 

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Joseph Lee via groups.io
Sent: Saturday, September 17, 2022 11:07 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] New (or revived) add-on: Office Desk

 

Hi all,

An issue on NVDA GitHub repo came up that might be resolved with Office Desk: announcing envelope field names in Word 365. I have a working solution but it will lead to conflict with Word Access add-on by Paul as my solution modifies Word app module. There is a slightly hacky solution I'm thinking of that will not modify Word app module directly but can lead to unpredictable results as I need to replace parts of NVDA's support for Word via UIA through a global plugin approach.

This is one of those cases where I think combining add-ons would be better in the long term. I will post my solution as part of September 18th dev build of Office Desk which will be the first beta level build of the add-on (this build will also move formatting announcement fix to Word app module).

Cheers,

JOseph


Rowen Cary
 

Hi,

Just hope that paul will consider joining the project