AtlasLootReverse 

Yay, First !

This addon is nice, especially since the Daviesh and the crew seemingly cba to make this functionality of their own volition.

However : Why does it have to suck up so much memory?.. And apparently it forces atlasloot to load all it's modules in the scanning process (something I doubt you can avoid) but even then it takes up more memory than atlasloot itself (without the modules).

Sorry, but for this amount of memory, I think I'd be better off with Mendeleev.

While I can see the lure of scanning Atlasloot's database and building a structure of your own, I could suggest that you maybe build in a "scan" function that makes a compact database, so when I log back in, it doesn't have to get all the data from Atlasloot, but instead load it from a much smaller database of it's own.

If it becomes out of date (if it perhaps can detect the version of atlasloot installed and bug me to rescan if that version is newer than the one I used to build my current database?) I could get a prompt to ask me to rescan atlasloot or I could choose to do so myself.

But using almost 2 megs of memory and forcing atlasloot to load all the modules EVERY time is a bit rich, I think.

Just my thoughts

Agree, altho i've w8ed for this to be released, im happy with the function from Altoholic of this, since it gives me both alt info and drop info.

EDIT: Suggestion to add this to the original AtlasLoot page as Patch, since you can't use this unless you have it

I think you've found an old version of Mendeleev.

On http://www.wowace.com/projects/mendeleev/ you can DL the latest version, and it definatly has all the WotLK look.

It only takes up 7-800kb and also includes all types of crafting info (if you mouseover Adder's Tongue, you can see a list of alchemy things it's used in and so on).

I'm not really sure how they do that.

And sorry about the initial blurb.. I should've checked a few times more after logging in on how much memory it uses and so on.

I could suggest maybe building a instance and or mob list, assigning numbers to them and then associating the item id with only 2 numbers instead of 2 whole strings per item?

So instead of displaying the itemID's associated strings, it would display the strings associated with the itemID's instance and boss number.

I'm no .lua expert or a hardcore programmer, but it would seem to make it a lot more efficient and make the DB consume less m/kb's

While I think you could've compressed the data further by using the method I suggested, the current change will do nicely as my goal was to get a tooltip addition that gave me the boss who drops it and take up less space than Mendeleev.

I guess playing the devil's advocate for a bit can bring a bit of change for the good

Thanks for your quick replies and very decent work on minimizing the memory impact.

hey pceric,

welcome to the altas-plugin-family^^ maybe you'd like to join us at:

http://atlasmod.com/phpBB3/
and
http://www.daviesh.net/atlasloot_enh...pBB3/index.php

As far as I know, Mendeleev uses the Periodic Table library, so as long as stuff gets added to that, it should stay 'updated'.

This sort of mod is good, it is something I always wanted to see as a separate module as I didn't want to contaminate the main AtlasLoot code with tooltip hooking (more things to check on patch day). It wasn't just that I couldn't be bothered, you would not believe the time that goes into the mod (Not just me, there are usually at least 3 or 4 other people working on things).

The memory use is kind of inevitable in constructing the reverse lookup table, but I would invite you to look at the wishlist/search code in AtlasLoot, where we do reverse lookups on the fly rather than having a second copy in memory. It may turn out to be too laggy for tooltips, but worth a look.

thank you for such a wonderful addon.

"Drops from Priest - Shadow (Tier 7/8 sets)"
Uhhahahahahaha!!!!!
Either way, can we please have embed mode configurable?
Yes, I can hack the hook by hands, but i'd like to see more natural approach.

ns\AtlasLootReverse\libs\LibExtraTip\LibExtraTip.lua:252: Usage: GameTooltip:SetUnit("unit"[, hideStatus]):
...ns\AtlasLootReverse\libs\LibExtraTip\LibExtraTip.lua:252: in function <...ns\AtlasLootReverse\libs\LibExtraTip\LibExtraTip.lua:246>:
<in C code>: ?
<in C code>: in function `SetUnit'
Interface\FrameXML\UnitFrame.lua:146: in function `UnitFrame_UpdateTooltip':
Interface\FrameXML\UnitFrame.lua:133: in function `UnitFrame_OnEnter':
Grid-1.30100.2009041601\GridFrame.lua:228: in function `OnEnter'
GridCaster-0.091\GridCastbar.lua:781: in function `OnEnter'
Grid-1.30100.2009041601\GridFrame.lua:103: in function <Interface\AddOns\Grid\GridFrame.lua:103>

---