What exactly did he do that you told him not to do? Though our problems sound similar, I know our situations are not the same. In my case I made a new Git repository on a new addon, and in his he used an external Git repository from what I can only assume was some sort of WowAce-hosted repository.
Actually my bad, I thought starlon made this post. I was tired when I read it.
We warned you in IRC starlon, not to do what you were doing. I specifically said that you would likely break something (spoken from experience). What you did was voluntary.
And WTF did you make another thread about this for. It isn't like your posts about it lacked detail in the other places you posted them.
]
Just settle down and be patient - or go try and figure it out on your own. Did you delete all your tags for example? That was something we told you you would have to do.
The SYSTEM event for level up should not be passed to CF_MEH, in fact, CF_MEH, should not process it at all. It gets turned into an addmessage.and is printed by the system message event handelr
1) Put all your modules in your main addon folder.
2) Only reference the core modules from the main addon.
3) Create pseudo-addons which only have references to some of the modules in your *main* addon folder, but themselves contain no modules. This reference should be to a single xml file in your main addon which then references the modules for that optional addon.
Why?
Because if for some reason your main addon is updated without the other addons being updated you addon will *almost always* be up to date regardless.
Now. Optional modules.
The "Prat way" makes a trade-off that I think the users can live with. In prat there aren't 50 folders 1 for each module. Instead all the modules get loaded (fast) and then freed from memory if they aren't going to be used (fast).
This is an option that noone will mention to you - but it works *very* well. If you program it right, and don't do any work during the loading of the main chunk (which you shouldn't be doing anyways). Then the process is fast, and the garbage collector takes care of the rest.
Doing the above things are more complicated - but they have their updside.
EDIT: Not claiming to be "best-practice" on anything
I created a "mixin" type library to add autocomplete support to the WoW command line.
By autocomplete I mean completion of global identifiers and their fields.
So for example you could say:
chatframe1edi<tab> and it would complete the first proposal and subsequent tabs would cycle through the various completions.
then once you had say: "ChatFrame1EditBox"
you could type:
ChatFrame1EditBox.<tab> and see the available fields. or even ChatFrame1EditBox:<tab> and see the available functions with autocompletion available for both variants.
It still needs some work, but it is usable in its current form.
It uses a fix in the latest version of AceTab, so be sure you have that.
You can download Prat if you want to play around with this stuff, just grab the Prat-3.0_Debug folder from Prat-3.0/pullouts and put it in your addon directory along with Prat and the patched AceTab.
I wrote the source to be reusable so you can add it to any addon (with access to AceTab).
To reuse it, just copy the globalcomplete.lua into your addon. If you use the addon table supplied by blizzard then it will mix right in, and you just need to call self:EnableGlobalCompletions(...)
0
I was thinking of doing exactly this as well. Perhaps someone could make it into a lib of some kind.
0
Actually my bad, I thought starlon made this post. I was tired when I read it.
0
You need to wait until after PEW at least.
If you want to text the print while loading, Create a table, and print to it.
MYTABLE = {}
MYTABLE[#MYTABLE+1] = ""something I am going to want to read later"
Then when you are loaded into the game client:
/dump MYTABLE
0
And WTF did you make another thread about this for. It isn't like your posts about it lacked detail in the other places you posted them.
]
Just settle down and be patient - or go try and figure it out on your own. Did you delete all your tags for example? That was something we told you you would have to do.
0
The SYSTEM event for level up should not be passed to CF_MEH, in fact, CF_MEH, should not process it at all. It gets turned into an addmessage.and is printed by the system message event handelr
0
^ this
0
This is completely normal. The only way around it is less code.
0
1) Put all your modules in your main addon folder.
2) Only reference the core modules from the main addon.
3) Create pseudo-addons which only have references to some of the modules in your *main* addon folder, but themselves contain no modules. This reference should be to a single xml file in your main addon which then references the modules for that optional addon.
Why?
Because if for some reason your main addon is updated without the other addons being updated you addon will *almost always* be up to date regardless.
Now. Optional modules.
The "Prat way" makes a trade-off that I think the users can live with. In prat there aren't 50 folders 1 for each module. Instead all the modules get loaded (fast) and then freed from memory if they aren't going to be used (fast).
This is an option that noone will mention to you - but it works *very* well. If you program it right, and don't do any work during the loading of the main chunk (which you shouldn't be doing anyways). Then the process is fast, and the garbage collector takes care of the rest.
Doing the above things are more complicated - but they have their updside.
EDIT: Not claiming to be "best-practice" on anything
0
0
Just do what seems best to you.
0
I created a "mixin" type library to add autocomplete support to the WoW command line.
By autocomplete I mean completion of global identifiers and their fields.
So for example you could say:
chatframe1edi<tab> and it would complete the first proposal and subsequent tabs would cycle through the various completions.
then once you had say: "ChatFrame1EditBox"
you could type:
ChatFrame1EditBox.<tab> and see the available fields. or even ChatFrame1EditBox:<tab> and see the available functions with autocompletion available for both variants.
It still needs some work, but it is usable in its current form.
It uses a fix in the latest version of AceTab, so be sure you have that.
You can download Prat if you want to play around with this stuff, just grab the Prat-3.0_Debug folder from Prat-3.0/pullouts and put it in your addon directory along with Prat and the patched AceTab.
I wrote the source to be reusable so you can add it to any addon (with access to AceTab).
Source is here:
http://hg.wowace.com/wow/prat-3-0/mainline/file/tip/debug/globalcomplete.lua
Here's a screencast - keep in mind it is still sorta rough:
http://www.screencast.com/t/gRczrQJo3
To reuse it, just copy the globalcomplete.lua into your addon. If you use the addon table supplied by blizzard then it will mix right in, and you just need to call self:EnableGlobalCompletions(...)
0
0
There is now a setup video
0
0