I have a module in Prat which enhances the chat bubbles in several ways.
I was considering making it into its own addon for those people who do not use Prat.
The features of the non-Prat version would be:
1) Change the Font of the bubbles to match the font of the chatframe, and size the font however you like
2) Change the outline of the chat bubbles to match the type of chat
3) Enable display of raid icons
4) Enable dynamic compression of the chat bubbles so they only display 1 line of text (unless you mouse over them)
Here are some screenshots from the Prat version, in a standalone the name "sylvaann" would not be colored most likely:
Wow... slick code. I was going to offer some advice on how to do it but clearly from your code you're way on top of the game.
stuff I'd already typed...
If I did it I'd use CHAT_MSG_SAY and CHAT_MSG_YELL and keep all text it captures for 30 seconds (for example) with two variables... message and sender (args 1 and 2) and if the first argument matched your fontstring variable then I'd just tweak
fontstring = sender..": "..fontstring
Wow... slick code. I was going to offer some advice on how to do it but clearly from your code you're way on top of the game.
stuff I'd already typed...
If I did it I'd use CHAT_MSG_SAY and CHAT_MSG_YELL and keep all text it captures for 30 seconds (for example) with two variables... message and sender (args 1 and 2) and if the first argument matched your fontstring variable then I'd just tweak
fontstring = sender..": "..fontstring
Its a reasonable next step for certain, but the user could have that chat type disabled on all thier chatframes - in that case you'd still see a bubble, but nothing would print on any chatframe to reference.
Also, there is the issue where the chatbubble is displayed before the chatframe message (it may be possible), and 2 people saying the same thing.
Those are all edge cases obviously.
I could probably do more than I am currently, or perhaps improve my implementation somewhat. Next time I have some free time I'll look into it some more.
you know what... that's the difference between a seasoned programmer and a hobbyist like me... I just thought about how to achieve it.
You came up with "what could go wrong, what could be changed to prevent a match happening, and what are the outlier cases."
Pre-emptive stikes >> debugging lazy code.
:)
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I was considering making it into its own addon for those people who do not use Prat.
The features of the non-Prat version would be:
1) Change the Font of the bubbles to match the font of the chatframe, and size the font however you like
2) Change the outline of the chat bubbles to match the type of chat
3) Enable display of raid icons
4) Enable dynamic compression of the chat bubbles so they only display 1 line of text (unless you mouse over them)
Here are some screenshots from the Prat version, in a standalone the name "sylvaann" would not be colored most likely:
Ok...working on it.
EDIT: .... done
http://www.wowace.com/addons/bubblicious/
Is it possible to add the name in front of the text, like :
Sylvaann : Hello my name is sylvaann.
...
I was going to say yes, but I'll just say maybe. It would take a bit of work to track who said what recently.
stuff I'd already typed...
If I did it I'd use CHAT_MSG_SAY and CHAT_MSG_YELL and keep all text it captures for 30 seconds (for example) with two variables... message and sender (args 1 and 2) and if the first argument matched your fontstring variable then I'd just tweak
fontstring = sender..": "..fontstring
Its a reasonable next step for certain, but the user could have that chat type disabled on all thier chatframes - in that case you'd still see a bubble, but nothing would print on any chatframe to reference.
Also, there is the issue where the chatbubble is displayed before the chatframe message (it may be possible), and 2 people saying the same thing.
Those are all edge cases obviously.
I could probably do more than I am currently, or perhaps improve my implementation somewhat. Next time I have some free time I'll look into it some more.
You came up with "what could go wrong, what could be changed to prevent a match happening, and what are the outlier cases."
Pre-emptive stikes >> debugging lazy code.
:)