Post by Moongaze on Aug 15, 2008 13:19:15 GMT -5
Hey everyone! Here's a status update on some LunarSphere stuff. As I've said a few weeks ago, I am currently working on another project for a company and have put LunarSphere on a very slow schedule until the end of August. I have created another template and I want to get one more in before I release the next version. LunarSphere just needs the remaining templates to be made, two or three small features, and localization ... then it is finished for public release. I WANT to get this done ASAP, but it will take a little bit of time.
Now, anyone who is using WotLK right now for the Beta ... LS doesn't work. I know this and am actually really really NOT looking forward to updating my code to make it work for WotLK. I don't understand why Blizzard insists on changing a huge set of the API with every expansion, but whatever. LunarSphere suffers from two fatal flaws that prevents it from working on WotLK:
1) Blizzard removed the legacy support for the "this" variable. So, I have to add some extra arguments to a lot of functions that would typically use it and start using "self" instead. I could probably use "this" still, but I would rather make sure that the code is more in line to how it should look.
2) Secure Buttons ... TOTALLY CHANGED! *cry x10* So, to make the buttons work for WotLK, I have some studying to do and a lot of trial and error since Blizzard hasn't really finished this part yet. This is the big one, and will take some time. My plan is to get a public release of LunarSphere out before WotLK and then work on WotLK support. Once WotLK goes live, I hope to have that version ready and will release it so it will work. As well the BC expansion, the API code changes will go into effect as a downloaded patch ... so even if you don't buy WotLK, a LOT of addons will break that day, and I won't LS to not be one of them.
So, that's about it for the update
Now, anyone who is using WotLK right now for the Beta ... LS doesn't work. I know this and am actually really really NOT looking forward to updating my code to make it work for WotLK. I don't understand why Blizzard insists on changing a huge set of the API with every expansion, but whatever. LunarSphere suffers from two fatal flaws that prevents it from working on WotLK:
1) Blizzard removed the legacy support for the "this" variable. So, I have to add some extra arguments to a lot of functions that would typically use it and start using "self" instead. I could probably use "this" still, but I would rather make sure that the code is more in line to how it should look.
2) Secure Buttons ... TOTALLY CHANGED! *cry x10* So, to make the buttons work for WotLK, I have some studying to do and a lot of trial and error since Blizzard hasn't really finished this part yet. This is the big one, and will take some time. My plan is to get a public release of LunarSphere out before WotLK and then work on WotLK support. Once WotLK goes live, I hope to have that version ready and will release it so it will work. As well the BC expansion, the API code changes will go into effect as a downloaded patch ... so even if you don't buy WotLK, a LOT of addons will break that day, and I won't LS to not be one of them.
So, that's about it for the update