Ace3

  • 7 pages found
NameAuthorLast updated byUpdated on
NameAuthorLast updated byUpdated on
API / Dec 08, 2013
AceComm-3.0 Kaelten Kaelten Sep 13, 2013
AceConfig-3.0 Kaelten Kaelten Sep 13, 2013
AceConfigRegistry-3.0 Kaelten Nevcairiel Dec 08, 2013
AceDB-3.0 Kaelten Kaelten Sep 13, 2013
AceEvent-3.0 Kaelten Kaelten Sep 13, 2013
AceGUI-3.0 Kaelten Kaelten Sep 13, 2013
AceLocale-3.0 Kaelten Kaelten Sep 13, 2013
AceTimer-3.0 Kaelten Kaelten Sep 13, 2013
AceAddon-3.0 Kaelten Kaelten Apr 04, 2009
AceBucket-3.0 Kaelten Kaelten Apr 05, 2009
AceConfigCmd-3.0 Kaelten Kaelten Apr 05, 2009
AceConfigDialog-3.0 Kaelten Kaelten Apr 04, 2009
AceConsole-3.0 Kaelten Kaelten Oct 05, 2009
AceDBOptions-3.0 Kaelten Kaelten Apr 03, 2009
AceHook-3.0 Kaelten Kaelten Apr 04, 2009
AceSerializer-3.0 Kaelten Kaelten Apr 04, 2009
AceTab-3.0 Kaelten Kaelten Apr 04, 2009
AceConfig-3.0 Options Tables Nevcairiel mikk Oct 22, 2011
The AceOptions table format is a standardized way of representing the commands available to control an addon. An example table, very minimalistic: myOptionsTable = { type = "group", args = { enable = { name = "Enable", desc = "Enables / disables the addon", type = "toggle", set = function(info,val) MyAddon.enabled = val end, get = function(info) return MyAddon.enabled end }, moreoptions={ name = "More Options", type = "group", args={ -- more options go here } } } The Basics Every option table...
AceDB-3.0 Tutorial Nevcairiel Nevcairiel Apr 05, 2009
AceDB-3.0 is a library to manage the SavedVariables of an addon. It offers profile management, smart defaults and child-databases for modules. Getting Started First, we need to make sure that we have the table we want to use to store our DB in defined in the addons .toc, like this. ## SavedVariables: AceDBExampleDB Now we can register our table with AceDB-3.0 and start writing our addon. Note: You have to register the table after the ADDON_LOADED event (e.g. in OnInitialize) or the table will...
AceGUI-3.0 Tutorial Nevcairiel Nevcairiel Apr 06, 2009
AceGUI-3.0 is a library designed to simplify UI creation. This tutorial will focus on the basics in creating a very simple UI, explaining how the different Layouts work, and showing most of the widgets in action. In all examples and code snippets in this tutorial, we'll assume that you have a local AceGUI variable containing the reference to an AceGUI-3.0 instance, as returned by LibStub. A Container Frame Every UI starts with a container. You can use your own container frames to place the...
AceGUI-3.0 Widgets Nevcairiel mikk Jun 20, 2011
Base Widget APIs This is a list of all commonly used and public APIs all widgets (and containers) share. There are additional APIs that are reserved for internal use by the Layout functions or the Widgets themself, and are not documented here. widget:SetCallback(name, func) Set the callback function of a specific callback. Only one function can be assigned to every callback. Usage local frame = AceGUI:Create("Frame") frame:SetCallback("OnClose", function(widget) AceGUI:Release(widget) end)...
Getting Started Aiiane mikk Oct 27, 2010
Keep in mind when reading through this that Ace3 is designed to be modular: not all addons may need to use every portion of it. Feel free to pick and choose those which suit the purposes of your addon, and skip over sections relating to bits you don't need. Basic Addon File Setup Start by creating a folder for the addon in <WoW Directory>\Interface\Addons. The name can be whatever you want as long as it's unique, so pick something descriptive of what you're writing. Within that directory,...
Main wowaceSVN Arrowmaster May 21, 2013
AddOn development framework A basic introduction to usage can be found here: http://www.wowace.com/addons/ace3/pages/getting-started/ Documentation can be found here: http://www.wowace.com/addons/ace3/pages/ For historic purposes, the "old" documentation is still around on the old wiki, some articles may not be converted yet, and only exist on the old wiki: http://old.wowace.com/wiki/Ace3
  • 7 pages found