Does Ace3 not have AceLibrary? If I try to disable Ace2, the only error I have kicked is a missing AceLibrary. Is this something I'll need to keep Ace2 installed for, or can I just copy the folder over somewhere else...?
It's also worth mentioning that you may not have any addons that directly require Ace2, but you may have an addon (AtlasLoot is one example) that uses a library that does require Ace2 (DewdropLib in the case of AtlasLoot).
Post the error, or read it yourself and notice which addon is actually triggering the error; that one still requires at least some parts of Ace2.
It is the AtlasLoot needing Dewdrop that's needing AceLibrary. Which sucks, because Broker_SocialState needs Dewdrop as well, and the BugSack LDB needs AceLibrary :/. So much for moving away completely from Ace2...
Who would I need to bug about making DewdropLib play nice >.> ? And BugSack as well I guess...
You'd essentially need to write a new library from scratch, as the "powers that be" here on WoWAce have already stated quite firmly that they will not host any LibStub port of DewdropLib; discussion on that topic can be found in the thread gramg linked.
I think it's mostly a reaction to the horrible overuse they got with DewDrop is all. I have a total of like 4 dropdowns in all my addon's configs. They certainly have their place, but they shouldn't be used for all-out config systems, which is what people want it for. Making a simple little dropdown with blizzy's template is not hard at all.
I'd tend to argue that the "horrible overuse" of Dewdrop sprang from the fact that there was no real GUI alternative. It was either command-line, Dewdrop, or write your own GUI.
The addons the OP mentioned don't use Dewdrop for configuration, but rather for nested dropdown menus for quick access to stuff.
AtlasLoot uses Dewdrop to give you a dropdown menu where the main level selects an instance and the second level selects a boss from that instance. Doable without Dewdrop? Sure, but I certainly wouldn't want to deal with it.
BugSack uses Dewdrop to give you a quick right-click menu from its LDB feed, with options to select which bug(s) you want to view, send them to other BugSack users, etc. Is it even possible to put sliders and edit boxes in Blizzard dropdown menus?
Nowadays, AceGUI makes it super easy to give users real GUI configurations, so I don't see much likelihood of a LibStubbed Dewdrop making a hostile takeover in the configuration arena. :p
I won't argue that it's overuse was due to the lack of GUI libs. But now that there *is* a proper GUI config library, is a DewDrop replacement really needed, or do the people wanting one need to re-asses their needs?
Simple 1-level menus are usually not an issue, but when people start digging into multi-level menus that's usually when they need to reconsider their GUI design. For example, AtlasLoot might be cleaner if there was one combobox/dropdown for zone and one for boss, much like continent/zone in the default map. Hell toss in some auto-complete majicks with a combobox and it'd be really nice. BugSack sounds like it's only using a single-level, but the sending to other users would probably be cleaner in a popup dialog. Use the menu to pick a bug, it opens a frame with the full bug details and widgets to perform actions with the bug, like sending to other users.
Like I said, dropdowns certainly have their place, but they are not an end-all solution to GUIs.