Unfortunately most of the tutorials on Wowpedia.org (and Wowwiki.com) are written using outdated techniques, with a huge amount of lengthy and unnecessary XML, and lots of global variables.
I don't have time to write up a tutorial right now, but you might also take a look at the code for the parts of the
default UI that use a "fake" scroll frame (usually with the FauxScrollFrameTemplate template), such as the friends frame, the ignore frame, and the guild roster frame.
Some code I posted in
another thread over on WowAce might also be useful, as it already (a) creates a frame for displaying rows of data, and (b) has functions for sorting data, without a lot of other code.
You could also look at the code for simpler damage meter addons (eg. not Recount or Skada), as those also display sorted rows of data in a scrollable list.
On a final note, in response to this:
Originally Posted by rx12network
P.s. i have some more questions.. maybe anyone have a bit time to can tell me something what i want to know in a chatsession.. [...] (please send me a pm))
|
Asking people to answer your questions by PM defeats the purpose of having a community forum. The whole point of this forum is that when you ask a question,
anyone can answer it. If one person doesn't know the answer, someone else probably does, and if someone posts wrong information, others can correct it.
You also don't have to wait on one person's free time (for example, if they are sleeping when you send your PM, you have to wait until they wake up and check their PMs to get an answer); since anyone can read the forum and reply, you will usually get an answer faster.
Finally, when the question and answer are only in PMs, they only benefit
you, and anyone who has the same (or a similar) question in the future has to spend time asking the question again, and others have to spend time answering it again. If the question and answer are on the forums, they benefit everyone. Someone else with the same question can get the answer immediately, and nobody has to spend any time writing the same answer again.