That's not what I ment .. I know it's easier with externals but they could go into a folder like
/OneBag/libs/AceAddon
/OneBag/libs/AceConsole
that would keep the addons main folder clean and would make clear which folders are external libs and make easier to recognice if there are folders for the addons like /OneBag/Sounds or /OneBag/Textures.
I'm not sure if I feel comfortable with all those ace2 folders directly in the Addon folder .. perhaps they should go into a subdirectory called libs :)
The same thing disturbs me a bit with bigwigs .. first you had a forlder for every instance ... now you have more folders about embedded libs then about stuff with the addon itself ;)
it should be no problem to write a bigwigs module that allows starting bars and warnings by sending a sync message, or an arbitary message to the ct_ra channel :) .. and fire it of by a macro or something like that ;)
If you don't trust your raidleader look for an other raid group.
You can't do it in lua because one has to be the real master looter and he always can just disable the addon anytime and I'm sure blizzard won't add something like that because it will only lead to more problems for their support staff ;)
IFrameManager and IFrameFactory are 2 libs also available at wowinterfaces.com.
The one is to create Frames in lua and the other is some kind of window manager so you can stick frames to other frames.
Besides Acegui (which I think is not so a good idea to use ?) I don't know any gui-libs using ace and I don't see any reason to ace every mod out there ,)
-- Record join / leaveing of the raid. Also record how long people were offline / out of the raid. (Say someone joins, goes offline for an hour for dinner, then comes back later. One of my biggest issues with CTRT right now is the lack of this. Not just first join / last leave.)
if you use the modified ct_raidtracker from curse-gaming (freddys) and export the dkp-string (xml) it contains every leave and every join ... it's just not shown in the ingame ui. You also get mob kill times and which member where in raid at the kill. It shows which mob dropt the item for the loot.
there are even ui's now for options like minimal item quality to log and a ui to ignore certain items (like coins in zg) and things like that.
the memory it use depends on how many raids you have stored, and if you log every grey item :) .. I think this version is already much faster then the original ct_raidtracker
0
That's not what I ment .. I know it's easier with externals but they could go into a folder like
/OneBag/libs/AceAddon
/OneBag/libs/AceConsole
that would keep the addons main folder clean and would make clear which folders are external libs and make easier to recognice if there are folders for the addons like /OneBag/Sounds or /OneBag/Textures.
0
The same thing disturbs me a bit with bigwigs .. first you had a forlder for every instance ... now you have more folders about embedded libs then about stuff with the addon itself ;)
0
Look for it at wowi ;)
0
tekkub .. perhaps edit your post and insert a link to that thread ;)
0
0
0
0
0
I added some addons from the wowsvn server as externals and it works great ;)
0
You can't do it in lua because one has to be the real master looter and he always can just disable the addon anytime and I'm sure blizzard won't add something like that because it will only lead to more problems for their support staff ;)
0
The one is to create Frames in lua and the other is some kind of window manager so you can stick frames to other frames.
Besides Acegui (which I think is not so a good idea to use ?) I don't know any gui-libs using ace and I don't see any reason to ace every mod out there ,)
0
if you use the modified ct_raidtracker from curse-gaming (freddys) and export the dkp-string (xml) it contains every leave and every join ... it's just not shown in the ingame ui. You also get mob kill times and which member where in raid at the kill. It shows which mob dropt the item for the loot.
there are even ui's now for options like minimal item quality to log and a ui to ignore certain items (like coins in zg) and things like that.
the memory it use depends on how many raids you have stored, and if you log every grey item :) .. I think this version is already much faster then the original ct_raidtracker