TAO

Release 6.0
This is to update the toc file for the new build number of Wow and to fix a problem with getting the role of a party member. Before that API call was returning a boolean, now it returns a string (TANK, DAMAGER, HEALER). This means that for NON-enUs clients, if that API call returns a different string it still won't fix it. I thought I had kept up-to-date on what was coming out for the API in 4.0.1, but I guess I missed that.

As for raids, the old fashion main tank and main assist still worked, but there is a new thing, namely, if you right click in the new raid frames you can set a role of tank. TAO does not make use of that role, it still uses the main tank and main assist set in the old raid window.
-------------------------
Release 5.0
I created 5.0 because I was jumping into BGs more frequently and finding that I was just spending a lot of time typing out /taotarget. Since TAO won’t access your “local” raid/party, I made it check to see if you were in a battlefield, which means arena too, and if so, redirect /tao to /taotarget instead of /taotank. This basically allows you to do a /taotarget in a battlefield with the /tao command. NOTE: It will only work if going to the default macro, either factory version or your variable override.

Since I was creating 5.0, I removed getglobal and setglobal which are in the process of being deprecated. They have been replaced by _G accesses.

ASIDE:
If you haven’t already heard, there has been some debate over BattleNet api calls and obtaining player real name lists. If you’re a little worried you might want to check your addons for any of the battlenet api functions. They pretty much start with BN.

release 4.0

WARNING WARNING WARNING WARNING WARNING     BEGIN     WARNING WARNING WARNING WARNING WARNING

Saved variables have changed.
taomacroprefix and taomacrosuffix are no longer used, and therefore no longer persist. They will be lost, and you should get their values before
installing the new version so you can set them in the new metaphor. Worst case be able to recreate their functionality in the new metaphor.

WARNING WARNING WARNING WARNING WARNING       END     WARNING WARNING WARNING WARNING WARNING

I updated the default macro icon to 378 which is the Swiss Army Knife. If you were using the taomacroicon override I suggested in the comments you can remove that and go with the default.

This version is more geared towards generic tricks of the trade macros which require multiple substitutions of the player's name, for whispering them, or indicating in message they are the target. This is done by using a new variable taomacrobody which follows the same \ escape sequence translations but also uses the character # as a place holder for the substitution spot for the player's name. Each time a # is found it is replaced by the player's name when the macro is updated/created. This also means the method for determining the target used by /taoshow internals has changed. It now uses a meta command #taotarget to determine this. This is inserted as the second line of your macro (takes up space but I couldn't think of any other way). There is also a variable taomacrotooltip for setting what bubble help you want to appear when you mouse over the hotbutton. This has the side effect of allowing other locales to specify the correct skill if it was language dependent. Hopefully character limit restrictions will not be hit with this new format as it requires more characters. To help, I went to the new @ format for targets. The macro now looks like this:
#showtooltip Tricks of the Trade
#taotarget <SomePlayersNameHere>
/cast [@<SomePlayersNameHere>,help] Tricks of the Trade

But this macro is created from three parts:
tooltip part (controlable by you with taomacrotooltip, default supplied, will be the first line of your macro)
target part (not controlable by you, always the second line and always, #taotarget PlayersName)
body part (controlable by you with taomacrobody, default supplied, can be multiple lines but # is a token which will be replaced by PlayersName)

I have tested this, and believe this is solid enough to be called a release.
------------------
release 3.0

This release is to take advantage of the new "add on local" table variable for storing the api abstraction layer object and the localization library object. The main guts of TAO have not changed, except to obtain the new references. In doing this version I changed the "reference names" of the three libraries, so if you've written some extra functionality of your own that obtains references to the libraries make sure you update that (especially augmenting/overriding the localization lua file).

This version SHOULD NOT IMPACT your saved settings. They should be available and function as if nothing has changed.
------------------
release 2.2

Forgot to add the two new functions tao_MacroPrefix and tao_MacroSuffix into the documentation of release 2.1

release 2.2 is purely a documentation update.
------------------
release 2.1

This is a release to fix a bug with the get macro player name logic (tao_GetTricksMacroPlayerName).

It did not take into account the variables taomacroprefix and taomacrosuffix, it strictly used the default values.
What this means is, everything works fine EXCEPT for /taoshow and the tooltip line which shows the target's name
IF you are using customized settings for the macro prefix or macro suffix or both.

This release fixes that issue.

NOTE: This is a logic error only. TAO would still allow you to set a target and Tricks of the Trade them normally, it
just wouldn't let you see who the target was so you may not have run into this bug and found things working fine.
-------------------------
release 2.0

There are new commands. The documentation has been updated to explain them all, and has a table of contents so you can quickly see what's in
it.
Some of the new commands are:
/taolang to change the locales used by the localization routines. Probably not very necessary.
/taovar to set variables, which is the way you customize the add on now. These can be changed on the fly and the last value is saved.
/taotarget to set the macro to the current target, so long as they are in your party/raid.
/taoname to set it to a typed in name.
to name a few (if not all)

I sort of redid a lot of it as the number of routines growing meant there was a number of replicated lines of code. It sits at 50K on my machine which seems rather large. When it initially loads up it spikes for a bit. I saw 119K or 149K or something, then drops back to 50K where it seems to remain. I'd like it to be lighter in the future. I think my initial non-distributed version was very small possibly under 20K (pre-localization, persistence etc...)

client language may force customization of the macro tooltip and body through the /taovar command, and if desired, the messages used in the locale file.