→Start Coding!: yank "custom ui editor"
mNo edit summary |
(→Start Coding!: yank "custom ui editor") |
||
| Line 59: | Line 59: | ||
== Start Coding! == | == Start Coding! == | ||
Start with the tutorials | Start with the tutorials extracted by the [http://us.blizzard.com/support/article.xml?locale=en_US&articleId=21466 Interface AddOn Kit]. The [[HOWTOs]] here has a ton of great examples to help you learn. Don't be shy to dig through someone else's addon for help, just be sure not steal code and give credit where credit is due. | ||
== Slash Commands == | == Slash Commands == | ||
A slash command is one way for the user to interact with your addon. These will be the easiest way for a beginner to let the user supply command and change options. | A slash command is one way for the user to interact with your addon. These will be the easiest way for a beginner to let the user supply command and change options. | ||
| Line 68: | Line 69: | ||
== SavedVariables == | == SavedVariables == | ||
The [[ | The [[Saving variables between game sessions]] article covers the key points. For folks new to Addons but not other programming languages, just bear in mind that: | ||
* The SavedVariables is only read from on UI loading, not real time, and only saved to on UI unloading. This will generally be from a user logging in or logging out. | * The SavedVariables is only read from on UI loading, not real time, and only saved to on UI unloading. This will generally be from a user logging in or logging out. | ||
* Basically, WoW makes a SavedVariables file for you named after your addon. You only get to specify in your TOC *which* variables get saved into that file. | * Basically, WoW makes a SavedVariables file for you named after your addon. You only get to specify in your TOC *which* variables get saved into that file. | ||