Date
1 - 3 of 3
A quick pre-emptive note regarding Add-On Compatibility #addonrelease
|
In going through my own personal email about this, I can see it coming again unless something has changed, and I doubt that it has.
Please, everyone, remember that if an add-on is shown as compatible with a given year's dot one release, which is supposed to be the one that breaks forward compatibility unless an update is made, that it will remain compatible with the dot two and forward releases. So if you have an add-on that is noted as compatible with NVDA 2023.1, it will remain compatible with all 2023.X releases (unless some really weird, one-time exception to the rule of the first "year number" release breaking compatibility is itself broken, and I don't expect that). Often the compatibility notices do not get updated after the dot one release for a given year has been deemed compatible. But if it has been, then presume compatibility will remain for all the subsequent NVDA dot releases that still have the same year number associated with them. -- Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit It is much easier to be critical than to be correct. ~ Benjamin Disraeli, 1804-1881 |
|
|
|
Brian's Mail list account
What about those which have no current maintainer but work with just the manifest tweak?
toggle quoted message
Show quoted text
The 3D sound comes to mind, a very handy add on which seems to have within it some notes that parts of its use of Python code as it stands will be deprecated? I would suspect all bets are off, but just wondered how much one could deduce from the code actually working. 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: "Brian Vogel" <britechguy@...> To: <nvda@nvda.groups.io> Sent: Monday, March 20, 2023 7:21 PM Subject: [nvda] A quick pre-emptive note regarding Add-On Compatibility #addonrelease In going through my own personal email about this, I can see it coming again unless something has changed, and I doubt that it has. Please, everyone, remember that if an add-on is shown as compatible with a given year's dot one release, which is supposed to be the one that breaks forward compatibility unless an update is made, that it will remain compatible with the dot two and forward releases. So if you have an add-on that is noted as compatible with NVDA 2023.1, it will remain compatible with all 2023.X releases (unless some really weird, one-time exception to the rule of the first "year number" release breaking compatibility is itself broken, and I don't expect that). Often the compatibility notices do not get updated after the dot one release for a given year has been deemed compatible. But if it has been, then presume compatibility will remain for all the subsequent NVDA dot releases that still have the same year number associated with them. -- Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit *It is much easier to be critical than to be correct.* ~ Benjamin Disraeli, 1804-1881 |
|
|
|
Brian,
Your question, while a good one, is not germane to the topic I introduced and why I introduced it. Any unmaintained add-on is, and always will be, a complete crap shoot as far as whether it just takes a manifest tweak and it will chug merrily along or whether it's hopelessly broken unless rewritten at some point. The latter point will, always, eventually be reached. It's a matter of exactly when, not if, when dealing with old, unmaintained code. You get passive forward compatibility for as long as you're lucky enough to get it. Otherwise, someone has to step up and take over maintenance of the code. Since the vast majority of NVDA add-ons are "home brew" items, and many developers never even think about a transition plan for when they want to walk away from something (which is entirely their right, I might add), this will be a perpetual problem. -- Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit It is much easier to be critical than to be correct. ~ Benjamin Disraeli, 1804-1881 |
|
|