Not that i really care but what would EOL for Ace2 look like? removal of the repo, or some sort of lock that gives people errors trying to use it via .pkgmeta, or simply no more updates/fixes if things break?
Killing would mean officially announcing its death, what people do with its corpse is not our business then!
But like Torhal said, just don't worry about it anymore. If it breaks, it breaks. The project page gets a note that its EOL and not going to be fixed.
Well, in a way it will, since Dewdrop requires AceLibrary, so every addon still using Dewdrop is also pulling down Ace2 (the full package for nolib users), and most such addons are still running on the Ace2 framework as well.
I thought the idea was to have it demise when Cata launches (because people update addons then anyway) and give it this grace-period that needs that become uncovered can be covered by ace2-free replacements.
Dewdrop is of course on of the more frequent reasons why addons are still ace2, that otherwise could easily be ace3.
I've spoken with ckknight about the issue, and he said to keep the repository open:
if someone wants to make it work without Ace2, go for it or have it so that something better comes out so people use it instead of Dewdrop. preventing something being fixed feels like bad governance
Yes, Dewdrop will pull all of Ace2 down for someone running disembedded. If Ace2 is broken, however, Dewdrop will most likely be shunned and authors will either go away from it or actually do something about its Ace2-dependence.
That's what I thought, too, but now we have people committing Cataclysm fixes to Dewdrop, so who knows...
(i didnt do it but) it needed to be fixed, i'd already fixed by local lib - and realistically its was just more this/self references that should have been done when that change happened, cata just forced it.
<snip>
how hard would it be to move dewdrop to ace3?
To do it right - to keep the options table functionality - would be a tedious undertaking. I'm sure there are other factors, such as the desire for a replacement rather than a port.
There have also been other projects started from-scratch which were intended to replace Dewdrop but never saw the light of day.
People commiting fixes for Dewdrop but not complaining about big Ace2 breakage probably means it didnt just break, eh?
Anyhow, like people said before, it was previously tried to port Dewdrop to Ace3, and we kinda aggreed that a simple port would result in way too ugly code to be really a lib we would want on WoWAce.
If someone insists on writing a new Dropdown library for Ace3 options table, roughly based on Dewdrop if you must, but with clean code and good documentation, well, go for it.
Alternatively, one could also rip out the Ace2 options tables out of Dewdrop and only offer its manual dropdown building system in a seperate lib, i for one used that back in the day occasionally -- not that i'm missing it now.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Forum Moderator-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThat, I would hope. Actively breaking it would be pointlessly antagonistic.
-
View User Profile
-
View Posts
-
Send Message
Project AuthorWhy are we fixing Ace2 libraries if Ace2 is being left to rot? ???
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIts open source, and It was a simple fix. EDIT: And I was using it in a library tester addon.
-
View User Profile
-
View Posts
-
Send Message
Forum Moderator-
View User Profile
-
View Posts
-
Send Message
Curse PremiumDo we close other people's open repo's here?
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumOk then.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumYou have to open it again.
-
View User Profile
-
View Posts
-
Send Message
Project Author-
View User Profile
-
View Posts
-
Send Message
Curse PremiumDewdrop is of course on of the more frequent reasons why addons are still ace2, that otherwise could easily be ace3.
-
View User Profile
-
View Posts
-
Send Message
Project AuthorYes, Dewdrop will pull all of Ace2 down for someone running disembedded. If Ace2 is broken, however, Dewdrop will most likely be shunned and authors will either go away from it or actually do something about its Ace2-dependence.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium(i didnt do it but) it needed to be fixed, i'd already fixed by local lib - and realistically its was just more this/self references that should have been done when that change happened, cata just forced it.
how hard would it be to move dewdrop to ace3?
-
View User Profile
-
View Posts
-
Send Message
Project AuthorTo do it right - to keep the options table functionality - would be a tedious undertaking. I'm sure there are other factors, such as the desire for a replacement rather than a port.
There have also been other projects started from-scratch which were intended to replace Dewdrop but never saw the light of day.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorAnyhow, like people said before, it was previously tried to port Dewdrop to Ace3, and we kinda aggreed that a simple port would result in way too ugly code to be really a lib we would want on WoWAce.
If someone insists on writing a new Dropdown library for Ace3 options table, roughly based on Dewdrop if you must, but with clean code and good documentation, well, go for it.
Alternatively, one could also rip out the Ace2 options tables out of Dewdrop and only offer its manual dropdown building system in a seperate lib, i for one used that back in the day occasionally -- not that i'm missing it now.