Advisory for NVDA add-on developers: new and changed modues, compilatoin requiremenets for 2017.3 and later

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Advisory for NVDA add-on developers: new and changed modues, compilatoin requiremenets for 2017.3 and later

Joseph Lee

Hi NVDA Core and add-on devleopers,

 

For those on the NVDA users and add-ons lists should have seen an advisory regarind Windows 10 OCR and NVDA 2017.3. The below advisory serves as a developer version of that one:

 

Due to introduction of Windows 10 OCR powered partially by Universal Windows Platform (UWP), the following modules will come standard with NVDA 2017.3 and later:

 

  • Json (Javascript Object Notation): if your add-on uses this module, you don’t need to include this library in your add-on as an external package. If you need to support users using old NVDA releases, please continue to bundle json as an external package.
  • contentRecog: a new facility that is used to plug in various OCR packages, including UWP API version, and perhaps in the future, Tesseract, the framework used in current OCR add-on.

 

Also, if you plan to run NVDA from source, from 2017.3, you cannot build NVDA with Visual Studio 2015 Express nor with Community with UWP support packages not installed. In other words, you need to use Visual Studio Community with Windows SDK+XP support and tools and SDK’s for Universal Windows Platform installed.

 

Thank you.

Cheers,

Joseph


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel