I don't know that I would have a queue of textfields. I would probably have just one textfield sized to the dimensions of the chat window and just update that with a generated HTML text string each time an update is needed. The source data might be stored in a queue/list/array. But before you even get to that, you need to think about what kind of data you are storing, and how it will be used.
I assume that you'll be storing what someone chats, and possibly other notifications as well. The type of message will most likely determine the color of the text. right ?
There are multiple ways you might approach this. One might be a simple array that stores strings. Each string would be an html encoded version of the text, with the appropriate formatting for color/font/bold.
But even with that approach, you might have to consider what other requirements your chat widget might have. For instance... What if it needs to filter messages ? Like you might have the ability to only see a certain kind of notification/message based on a criteria that might or might not even be "custom" based on user preferences.
You can see how that design aspect might completely change the data and the way you handle the data, to facilitate only displaying the ones desired. Because now you need to be able to make logical decisions and it might not be enough to just store a string, but you might also need to store other data defining the purpose of the string (chat message, notfication, npc message etc)
I say all this, because as you will learn, sometimes just deciding to do something by perceived steps without evaluating the full scope of your design goal... can lead to alot of extra work in redesigning to facilitate new functionality you introduce.
In terms of learning, I'd not focus on just FIFO. I'd suggest that you explore arrays/list to start and then move to different methodology in organizing them etc.
You can google "Arrays AS3 Tutorial" and maybe "FIFO AS3 Tutorial" to search for resources.
As a note, I think that these forums are of great use for specific issues, but am not a fan of threads where you have a goal of creating a widget and go through the step by step development and all it entails in a single thread. So I'd suggest that you post topics that are not so broad, and focus on the specific issue at hand. ie -- FIFO. That way someone looking for information on FIFO in these forums is likely to find a useful discussion on that topic with any answers someone might give on that topic (links to tutorials ect) and not the development of a chat dialog widget.
In my opinion, the topic of this thread has been resolved as it has given information on how to create a textfield with color formatting, a general suggestion as to using a queue for storing the data, and a note about the importance of design in what approach you might choose with a widget like this.
Hope that doesn't come across as rude!
Good Luck my friend.
