Thanks for the feedback so far, it's been really useful.
There are indeed a lot of exceptions when it comes to skinning frames. I have a bunch of API functions to handle the most common widget templates, but often I need to manually code the rest myself. I do rely on settings for colours and borders, mind you, so other addons would just have to pass on those.
Part of the problem is reloading the entire theme if a new skin is found after Aurora already applied its own theme. It's doable, but very resource-intensive. I suppose I could ask the user to reload the UI the first time a new skin is registered and copied to the cvars, though, so the next time, Aurora can load it right away.
|