For example, AtlasLoot might be cleaner if there was one combobox/dropdown for zone and one for boss, much like continent/zone in the default map. Hell toss in some auto-complete majicks with a combobox and it'd be really nice.
I tried a lot of different ways to avoid DewDrop, but in every case I got user backlash. People are used to the interface, because it draws heavily on how Atlas works. I originally had 3 dropdowns (zone, instance and boss) but again, the extra click was one too many for most people.
There just does not seem to be anything that can do everything Dewdrop does as elegantly. As well as the main selection menus for the interface, I use it in lots of little ways all across the interface. I agree with the fact that it used to be overused horribly in some mods (menus in menus in menus!), but for someone like me with a legacy interface, there is a huge amount of user inertia to overcome. I get emails of complaint just for reskinning part of the UI!
I will probably revisit all this again next time I have the time (and motivation) to do a partial rewrite of the code base.
Atlasloot should be just hardcoding the itemids, then showing a tooltip when you ask for it, thus caching the item. If it's showing textures than it may be pre-caching missing items on load or a timer or such.
To close the unanswered question left in the thread, AtlasLoot is at the core a giant list of itemIDs associated with loot tables. GetItemIcon is used to the textures, other information like tooltips is grabbed if possible with GetItemInfo, if that doesn't work placeholder explanatory text is displayed.
Kicking 4 errors on load, and a 5th on opening AtlasLoot. Latest alpha from wowace (r161); just wanted to make sure this was known.
Note that my alpha builds are never guaranteed to work, that is why they are alphas. I frequently commit half-done stuff in case one of the other guys has time to finish it before I do.
EDIT: Or do you mean alpha BabbleBoss not working with release AtlasLoot? Not sure why that would happen.
As far as I can see, updating a translation via the web form does not trigger the packager for an alpha build, so for a library like Babble, the latest translations are not always available to other mods.
All the errors (for English anyway) were squashed a couple of versions ago, if you are still having problems, try deleting all the old files before upgrading to be sure the old files get overwritten.
Did anyone end up committing these to the SVN? It doesn't look like it from the BabbleBoss commit log.
ifilgud, I would highly recommend you get yourself a free SVN account login. That way you commit these changes yourself and immediately help out a large number of addons.
LibBabble is not tied to Ace in any more, it is a great general purpose localisation tool.
All I could find is the old Babble-2.2 documentation, but the principle hasa not changed.
Say for example, you needed to use BabbleBoss. Just load it with you addon in the toc file (this assumes you stuck the libraries in a folder called 'Libs'):
0
0
Ditto here.
0
0
Status
Can't connect to service, please try again later.
At least you can commit changes and do SVN updates again now, even if you can't push a release.
0
I tried a lot of different ways to avoid DewDrop, but in every case I got user backlash. People are used to the interface, because it draws heavily on how Atlas works. I originally had 3 dropdowns (zone, instance and boss) but again, the extra click was one too many for most people.
There just does not seem to be anything that can do everything Dewdrop does as elegantly. As well as the main selection menus for the interface, I use it in lots of little ways all across the interface. I agree with the fact that it used to be overused horribly in some mods (menus in menus in menus!), but for someone like me with a legacy interface, there is a huge amount of user inertia to overcome. I get emails of complaint just for reskinning part of the UI!
I will probably revisit all this again next time I have the time (and motivation) to do a partial rewrite of the code base.
0
To close the unanswered question left in the thread, AtlasLoot is at the core a giant list of itemIDs associated with loot tables. GetItemIcon is used to the textures, other information like tooltips is grabbed if possible with GetItemInfo, if that doesn't work placeholder explanatory text is displayed.
0
I think the standalone addon list will wind up HUGE since adding a launcher is so trivial.
0
Note that my alpha builds are never guaranteed to work, that is why they are alphas. I frequently commit half-done stuff in case one of the other guys has time to finish it before I do.
EDIT: Or do you mean alpha BabbleBoss not working with release AtlasLoot? Not sure why that would happen.
0
0
0
Have a great festive season guys, and look forward to a bigger and better '09.
-Daviesh (posting from work, hope none of you guys have to work too)
0
0
ifilgud, I would highly recommend you get yourself a free SVN account login. That way you commit these changes yourself and immediately help out a large number of addons.
0
All I could find is the old Babble-2.2 documentation, but the principle hasa not changed.
Say for example, you needed to use BabbleBoss. Just load it with you addon in the toc file (this assumes you stuck the libraries in a folder called 'Libs'):
[FONT=Courier New]Libs\LibStub\LibStub.lua
Libs\LibBabble-Boss-3.0\lib.xml[/FONT]
Then at the top of any file you need it for, just add:
[FONT=Courier New]local BabbleBoss = LibStub("LibBabble-Boss-3.0"):GetLookupTable();[/FONT]
Then if you want [FONT=Courier New]"Meathook"[/FONT] somewhere, you replace it with [FONT=Courier New]BabbleBoss["Meathook"][/FONT].
The same technique goes for BabbleFaction, BabbleZone, etc.
There are other ways to load in Babble, some more elegant than this, but this is the simplest way to get it to 'just work'.
0