Because maybe the Library does not need to be updated?
Specifically I'm looking at LibAddonMenu
Specifically I'm looking at LibAddonMenu
In this case, the maintainer of the library is active. They just choose not to "update" it because there's nothing to update. The only "update" that LAM needs is for it to say, "yes, I still work with the latest Update 28 version of ESO, please stop asking". It's a placebo, since there aren't any actual changes/updates.
In such a case, some authors opt to "update" their addon just so that the addon manager doesn't complain about it being "oudated". And some other authors opt not to do these kinds of "placebo updates".
Just because an addon doesn't get an "update" every quarter to say, "yes, this addon still works" doesn't mean that it's not actually updated.
Not updating is sheer laziness.
Not updating is sheer laziness.
I do hope you realize that your words are more fitting of you than of addon developers. For example: A user who can't be bothered to check "Allow out of date add-ons" is lazy, and addon authors lament the "sorry state" of ungrateful users.
If an addon actually needs an update to keep working, then, yes, it should be updated. We're not talking about that. These are addons that don't need updates, because there is nothing to update. Now, if an addon author decides to bump the addon so that users won't have to check that checkbox, that's great. And if an addon author decides that non-code changes do not merit updates, that's their prerogative, and if you don't like it, you're free to fork the code and make your own. Have fun!
Not updating is sheer laziness.
I do hope you realize that your words are more fitting of you than of addon developers. For example: A user who can't be bothered to check "Allow out of date add-ons" is lazy, and addon authors lament the "sorry state" of ungrateful users.
If an addon actually needs an update to keep working, then, yes, it should be updated. We're not talking about that. These are addons that don't need updates, because there is nothing to update. Now, if an addon author decides to bump the addon so that users won't have to check that checkbox, that's great. And if an addon author decides that non-code changes do not merit updates, that's their prerogative, and if you don't like it, you're free to fork the code and make your own. Have fun!
How about sheer hybris? Read my words:
" By creating and hopefully maintaining an add-on one does have an implied duty to update it."
In no way would i denigrate the beautiful contributions that add-on creator accomplish. I rather question the unwillingness/inability to keep these tiny text-files up to date.
Because maybe the Library does not need to be updated?
With all due respect as I really like your posts why is such an important library not updated? I think that the creators/users of this library >>> Beam Me Up, Awesome Guild Store, Combat Metrics, Inventory Insight, Lore Books, Lost Treasure, Postmaster, Potion Maker, Sky Shards, Trait Buddy, Wit Worthy should have permissions to update this very important library.
As a technically proficient user I can update the API version manually but this is not really a convenient option, don't you agree?
MoonlightShadow wrote: »I took a look at the LibAddonMenu2. It was last updated in June, 2020. Which, really, is not that long ago since there have been no api changes that have required that it be updated. However, there are older addons which pre-packaged a form of LibAddonMenu2. These pre-packaged ones are severely out of date and throwing errors. The fault is not in the author of LibAddonMenu2, but with the author who is pre-packaging an outdated broken form of the library.
Not updating is sheer laziness.
I do hope you realize that your words are more fitting of you than of addon developers. For example: A user who can't be bothered to check "Allow out of date add-ons" is lazy, and addon authors lament the "sorry state" of ungrateful users.
If an addon actually needs an update to keep working, then, yes, it should be updated. We're not talking about that. These are addons that don't need updates, because there is nothing to update. Now, if an addon author decides to bump the addon so that users won't have to check that checkbox, that's great. And if an addon author decides that non-code changes do not merit updates, that's their prerogative, and if you don't like it, you're free to fork the code and make your own. Have fun!
How about sheer hybris? Read my words:
" By creating and hopefully maintaining an add-on one does have an implied duty to update it."
Thanks for the replies.
I've had a look at the text files for the libraries that are outdated and copied the latest API number into them. I will test today.
Hopefully I will now be able to use my inventory without having to disable out of date addons every time.
Specifically I'm looking at LibAddonMenu
In this case, the maintainer of the library is active. They just choose not to "update" it because there's nothing to update. The only "update" that LAM needs is for it to say, "yes, I still work with the latest Update 28 version of ESO, please stop asking". It's a placebo, since there aren't any actual changes/updates.
In such a case, some authors opt to "update" their addon just so that the addon manager doesn't complain about it being "oudated". And some other authors opt not to do these kinds of "placebo updates".
Just because an addon doesn't get an "update" every quarter to say, "yes, this addon still works" doesn't mean that it's not actually updated.
I'm sorry but I do not agree. By creating and hopefully maintaining an add-on one does have an implied duty to update it.
The mere fact of changing the API-value taking a few seconds in a text editor and the additional few seconds to send the update upstream is trivial.
Not updating is sheer laziness.
Specifically I'm looking at LibAddonMenu
In this case, the maintainer of the library is active. They just choose not to "update" it because there's nothing to update. The only "update" that LAM needs is for it to say, "yes, I still work with the latest Update 28 version of ESO, please stop asking". It's a placebo, since there aren't any actual changes/updates.
In such a case, some authors opt to "update" their addon just so that the addon manager doesn't complain about it being "oudated". And some other authors opt not to do these kinds of "placebo updates".
Just because an addon doesn't get an "update" every quarter to say, "yes, this addon still works" doesn't mean that it's not actually updated.
I'm sorry but I do not agree. By creating and hopefully maintaining an add-on one does have an implied duty to update it.
The mere fact of changing the API-value taking a few seconds in a text editor and the additional few seconds to send the update upstream is trivial.
Not updating is sheer laziness.
You’re welcome to do it yourself then.