In any event, I really am very busy. I got a grown-up people's job recently, and it has slowly but surely been sucking the lifeblood out of me. In any event, I have an idea for Parrot 2.0 in my mind's eye, but I lack hours in the day and energy at the end of it to continue some days.
I appreciate your support. While Parrot is non-functional, feel free to peruse any of my competitor's options (SCT, MSBT, Blizzard's FCT) as long as you promise to take a look at Parrot 2.0 when it's done.
Because DogTag-2.0 doesn't work right on 2.4 and I don't want to support multiple systems at one time. I didn't have adequate time to work on LDT-3.0 before WoW 2.4 came out, I plan to get things like the ingame documentation working properly as soon as possible.
Also: I don't have faith in people to "learn and test out", since that didn't happen at all it seems when I had it up and running for PTR testers.
I am really not fond of Blizzard's option dialog in 2.4, it's not resizeable, it lacks features that RockConfig has, I just don't see it as necessary to support right now.
Imho, this could be better done as a standard like how ClickCastFrames is done rather than another library. An extra library for such a specific and small task seems like overkill.
Hey all, I've been working on LibDogTag-3.0 quite a bit recently. It's not to a point that's usable yet by addons, due to the lack of unit-oriented tags, but it's getting there.
All in all, the syntax is pretty set on now, but it could still be changed or added to at a later point in time.
Adirelle, in making DogTags simpler, I don't think RPN is the best idea. People aren't used to prefix or postfix notation for operations, infix, although harder to parse for computers, makes more sense for people.
0
http://wowace.com/wiki/LibDogTag-3.0
0
Granted, I do like this (http://www.youtube.com/watch?v=WGoi1MSGu64), so *shrug*.
In any event, I really am very busy. I got a grown-up people's job recently, and it has slowly but surely been sucking the lifeblood out of me. In any event, I have an idea for Parrot 2.0 in my mind's eye, but I lack hours in the day and energy at the end of it to continue some days.
I appreciate your support. While Parrot is non-functional, feel free to peruse any of my competitor's options (SCT, MSBT, Blizzard's FCT) as long as you promise to take a look at Parrot 2.0 when it's done.
0
0
Also: I don't have faith in people to "learn and test out", since that didn't happen at all it seems when I had it up and running for PTR testers.
0
text:TruncEllipsis => text:Truncate
And the help isn't coded yet. I'm hoping to do that tonight.
0
0
0
0
[ [IsPlayer ? IsFriend] ? Name:ClassColor ! Name:HostileColor]
=>
[IsPlayer & IsFriend ? Name:ClassColor ! Name:HostileColor] or
[if IsPlayer and IsFriend then Name:ClassColor else Name:HostileColor]
------
[ [Guild == Text([Guild#player])] ? Guild:Angle:Purple ! Guild:Angle:HostileColor ]
=>
[Guild = Guild(unit="player") ? Guild:Angle:Purple ! Guild:Angle:HostileColor] or
[if Guild = Guild(unit="player") then Guild:Angle:Purple else Guild:Angle:HostileColor]
------
[ [ Target | InCombat | [CurHP ~= Text([MaxHP])] ] ? CurHP:Append( / ) ][MaxHP]
=>
[(Target | InCombat | CurHP ~= MaxHP ? CurHP " / ") MaxHP] or
[(if Target or InCombat or CurHP ~= MaxHP then CurHP " / ") MaxHP]
------
[ [HasAura(Arcane Intellect) | HasAura(Arcane Brilliance)] ? Text(AI)]
=>
[HasAura("Arcane Intellect", "Arcane Brilliance") ? "AI"] or
[if HasAura("Arcane Intellect", "Arcane Brilliance") then "AI"]
(I plan on allowing HasAura to support any amount of arguments)
------
Note: the names of the tags may change, this is mostly a way to show how tags will look.
0
All in all, the syntax is pretty set on now, but it could still be changed or added to at a later point in time.
I think you'll all like what's been done.
0
0
Also, I recommend backing up and clearing your PitBull and CowTip saved variables, see if that helps.
0
0
For one, I added the ability to show alpha on all bars.
For two, I already claimed Ellipsis, so hands off.
0