I am the author of Locknotes, and my users want a GUI to filter spells and announcements.

I have no idea how to do this, I only know how to make a frame. I have no idea how to make a drop down menu or any of that stuff.

So I had an idea to make a separate LUA file for each spell and put them all in the .toc file.

This would take up alot of the space in the Load addons screen, but its better then nothing.

My question is, will it have an effect on howmuch memory Locknotes uses? What about any other effects I'm not aware of?

I'd check the resources at wowace.com  You might be able to find some low UI memory code for acheiving what you want.  I believe the waterfall system is what handles drop downs for ACE mods if I'm not mistaken.

You might also want to look into whatever code it is that detects classes and have your mod NOT load the spells of other classes.   For example-you log in to your hunter, you're not going to care about backlash or shadow trance.  Another option would be to create a LUA file that users can edit or rem out spells they don't want tracked.  The issue I see there is if a user wants to not track spells on toon A but continue to track them on toon B.

  Quote:

Originally Posted by Vampyrate

I believe the waterfall system is what handles drop downs for ACE mods if I'm not mistaken.

What would be the easiest way to let users choose what spells they want? I dont care how they do it, I just want to deliver what they want in an efficient and clean way.

Well, you could have them pick the class at lvl one of the waterfall and then the spells of that class at level 2.  Look at an addon called RABuffs.  When you are setting up buffs to query or track, first you pick the class and then you pick the spell.  Example-I'm a raid leader and want to check for people missing AI.  I go into the setup of RABuffs, pick add a new query, pick mages and voila-there's AI. 

Just a quick FYI: Waterfall and DewDropLib are both depreciated, yet still functional. The reason I say depreciated is because they are no longer being maintained, as they are for Ace2, and neither have been fully fixed for patch 3.x of WoW. According to the braintrust over at WowAce, Ace2 is bloatware, and as such was replaced by the much more streamlined Ace3 or Rock libs. There are no Ace3 or Rock equivalants to DDL or WF; however, this may be of some help. Xinhuan (Omen3, Postal, others) wrote a rather in-depth how-to for using Blizzard's UIDropDownMenu, found here.

Follow-up. The wowwiki has a tutorial on using Blizzard's Interface Options gui. It is a bit sparse, but gets the point across. You don't need to write your own GUI if the heavy lifting is done for you, right? Anyway, here is the link.

http://www.wowwiki.com/Using_the_Interface_Options_Addons_panel

Thanks Myrro.  I'm not an addon writer so my knowledge of code is limited.  I was happy to even know waterfall :D

Vampy, you are a BigWigs user, I presume? *chuckles* BW is about the only major addon left still using Waterfall for its menu config. Still has a unique, rather attractive look, that has never been duplicated.

You might not be an addon coder, but more and more, I see former Ace2 addons either fully changing over to Ace3, or hybrid Ace2/3 because of these older libraries. I am not a fan of writing hybrid code. Ace 2 is still being maintained, even if several of the AceAddon-2.x loaded libs aren't. I suggest sticking to one or the other, if you use Ace. If Nov3mber is not using Ace2 or Ace3, and sticking to just Blizzard APIs, then so much the better.

Yeah, I'm still trying to learn the basic Blizzard ui API. I'll try to read up on that stuff.