Originally Posted by Vladinator
Hehe, I'll try clear up any confusion or misunderstanding to my earlier post. :P
What I meant is, since there are signs of lua code running (pet battles) that isn't exported as an addon, meaning we can't see the sources, meaning it makes things just more complicated and busywork to figure out how that particular addons works, what events it uses, API, e.g.
One may say that's a good thing to "bake" all addons into the binary and get rid of all the Blizzard_* addons, but on the other hand if that happens, how can we explore the sources of their LOD addons and learn from them? I think it's an important aspect of both learning how to code for the game, and getting an idea how things work around here.
It's early to say though, they might make the baked addons exportable too, it may be that they just haven't made the export feature export this new type of lua code, so it's no biggie if they fix this for retail release.
I only dislike the idea having the sources completely unavailable and having us guess on API changes and how their addons work. I didn't mean to sound like "they are doing it right now", just saying if they are... 
Just a side note, I personally don't see how baking all the Blizzard_* addons would make it any better. Please DO enlighten me though on what you thought! |
Could you give an example of this? There has always been lua code running out of the Blizzard_* addons, namely in the FrameXML (and on the login screen, GlueXML etc) - but I take it that's not what you mean.
Personally though I simply don't like the mess of all the Blizzard_* folders in my addons, just makes it longer to scroll through and there's nothing you can do with them anyway. Better to just export it all when you need it.
@ Strife[CUK]; Tried this, still crashes from the GetRegions() function and slash commands.