WowAce

Hard to determine if the difficulty filter _needs_ to be moved to it's own dropbox... For me it's much more obvious that there is a filter I can use (instead of "blind right clicking" on the header column). Don't know if there is enough space to move most (all) filters to their own dropbox) but I'd prefer such a solution.

Regards, Highend

I noticed the not being able to craft occasionally. I partly solved this by doing a /reload or /rl and was able to select a item to craft.

I have the same problem as Oukami — the create button is dimmed. The queue button was there, I think. I did have some filtering enabled, if I remember correctly. I'll go back and check that when I get a chance.

For some reason with the newest version (r40) I can't select items to craft. I had to revert back to r39 to get that function back. I would try to select an item listed by clicking on it, but nothing would happen. Is it just me having this issue, or are others as well?

I like the "group by" dropdown functionality. Do you think it would make more sense to move the "filter by difficulty" out of the recipe name header and put it in a drop down field (above or under the group by filter)?

The inventory list is broken, too. If I craft anything (e.g. epic gems) they never show up in that list.

Regards and keep up the good work, Highend

Excellent! :-)

Found another problem. put something in the queue, and then get the mats for it, the button that says "stop" (at least, I think that's what it says, the left one in the queue window) should, I think, change to "process", but it doesn't. No error message though. Maybe that's just not implemented yet?

Yeah, I'm getting the same error. Tried to chase it down to a conflict with another addon, but it seems to be random. It seems to corrupt the saved variables, and once that happens the only fix seems to be to dump the file and start fresh - until the next time. :-(

I really like the look of the addon, though! :-)

With r39:

Message: Interface\AddOns\GnomeWorks\Inventory.lua:203: attempt to index local 'playerData' (a nil value)
Time: Thu Jul  1 09:09:45 2010
Count: 632
Stack: [C]: ?
Interface\AddOns\GnomeWorks\Inventory.lua:203: in function `GetInventoryCount'
Interface\AddOns\GnomeWorks\Inventory.lua:121: in function `InventoryRecipeIterations'
Interface\AddOns\GnomeWorks\MainWindow.lua:961: in function `func'
Interface\AddOns\GnomeWorks\ScrollFrame.lua:375: in function <Interface\AddOns\GnomeWorks\ScrollFrame.lua:354>
Interface\AddOns\GnomeWorks\ScrollFrame.lua:370: in function `UpdateData'
Interface\AddOns\GnomeWorks\ScrollFrame.lua:386: in function `RefreshRows'
Interface\AddOns\GnomeWorks\ScrollFrame.lua:849: in function `Refresh'
Interface\AddOns\GnomeWorks\plugins\lsw.lua:380: in function `RefreshWindow'
...ace\AddOns\LilSparkysWorkshop\lilsparkysworkshop.lua:1226: in function `triggerFunction'
...ace\AddOns\LilSparkysWorkshop\lilsparkysworkshop.lua:2182: in function <...ace\AddOns\LilSparkysWorkshop\lilsparkysworkshop.lua:2174>

Locals: self = <table> {
 RecipeGroupPruneList = <function> defined @Interface\AddOns\GnomeWorks\RecipeGroups.lua:595
 ToggleTradeSkillOptionDropDown = <function> defined @Interface\AddOns\GnomeWorks\RecipeGroups.lua:849
 CancelTimer = <function> defined @Interface\AddOns\Ace3\AceTimer-3.0\AceTimer-3.0.lua:311
 RecipeGroupAddSubGroup = <function> defined @Interface\AddOns\GnomeWorks\RecipeGroups.lua:196
 InventoryScan = <function> defined @Interface\AddOns\GnomeWorks\Inventory.lua:224
 SetInventoryCount = <function> defined @Interface\AddOns\GnomeWorks\Inventory.lua:146
 TRADE_SKILL_UPDATE = <function> defined @Interface\AddOns\GnomeWorks\MainWindow.lua:1111
 RecipeGroupConstructDBString = <function> defined @Interface\AddOns\GnomeWorks\RecipeGroups.lua:562
 GetTradeIcon = <function> defined @Interface\AddOns\GnomeWorks\GetTradeSkill.lua:155
 QueueWindow = GnomeWorksQueueFrame {
 }
 GetInventoryCount = <function> defined @Interface\AddOns\GnomeWorks\Inventory.lua:161
 RegisterMessageDispatch = <function> defined @Interface\AddOns\GnomeWorks\GnomeWorks.lua:74
 ScheduleTimer = <function> defined @Interface\AddOns\Ace3\AceTimer-3.0\AceTimer-3.0.lua:276
 ShowReagents = <function> defined @Interface\AddOns\GnomeWorks\Details.lua:327
 AddToQueue = <function> defined @Interface\AddOns\GnomeWorks\Queue.lua:911
 RegisterMessage = <function> defined @Interface\AddOns\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:118
 UnregisterMessage = <function> defined @Interface\AddOns\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:181
 data = <table> {
 }
 RecipeGroupSort = <function> defined @Interface\AddOns\GnomeWorks\RecipeGroups.lua:413
 SetFilterText = <function> defined @Interface\AddOns\GnomeWorks\MainWindow.lua:1125
 PopSelection = <function> defined @Interface\AddOns\GnomeWorks\SkillList.lua:399
 ExpandAllHeaders = <function> defined @Interface\AddOns\GnomeWorks\ScrollFrame.lua:580
 RecipeGroupOpRename = <function> defined @Interface\AddOns\GnomeWorks\RecipeGroups.lua:1007
 GetTradeSkillIcon = <function> defined @Interface\AddOns\GnomeWorks\GetTradeSkill.lua:196
 ConstructPseudoTrades = <function> defined @Interface\AddOns\GnomeWorks\GetTradeSkill.lua:55
 IsTradeSkillLinked = <function> defined @Interface\AddOns\GnomeWorks\GetTradeSkill.lua:196
 OnLoad = <function> defined @Interface\AddOns\GnomeWorks\GnomeWorks.lua:257
 DoTradeSkillUpdate = <function> defined @Interface\AddOns\GnomeWorks\MainWindow.lua:1043
 ParseSkillList = <function> defined @Interface\AddOns\GnomeWorks\SkillList.lua:213
 PLAYER_GUILD_UPDATE = <function> defined @Interface\AddOns\GnomeWorks\GnomeWorks.lua:248
 RecipeGroupNew = <function> defined @Interface\AddOns\GnomeWorks\RecipeGroups.lua:68
 RecipeGroupOpNew = <function> defined @Interface\AddOns\GnomeWorks\RecipeGroups.lua:926
 GetSkillColor = <function> defined @Interface\AddOns\GnomeWorks\SkillList.lua:772
 CreateQueueWindow = <function> defined @Interface\AddOns\GnomeWorks\Queue.lua:1341
 Recip

Hey lilsparky,

Thank you again for offering so much insight into what you're doing. You've definitely gone above and beyond what I'd normally expect from a developer. I also appreciate you mentioning the Auctioneer people are on top of this. I'll probably just wait for them to release a patch and keep using skillet in the mean time.

The idea of a built-in mod to figure out what's profitable, then intelligently craft & post it sounds really intriguing. I've also wondered why glypher only handles glyphs. My conclusion is that the glyph market's dynamics are somewhat unique and amenable to automation for short-term profits.

Anyway, raw trade goods, intermediate trade goods, potions/elixirs/scrolls, vanity items, combat gear, etc all have slightly different market dynamics. Because of this I do like Auctioneer's notion of having several different pricing mechanics. I do think that for a plugin to make this easier, you want the crafting and the posting somewhat tied together—hooking into both Auctioneer and GW. You'd also need some kind of market feedback (BeanCounter) to determine how many of each item you can reasonably sell before market conditions change. There's also questions about finding optimal stack sizes, or posting with multiple stack sizes, but that may be reaching a bit too far into the AI sky.

So thanks for the suggestion, I'm going to do a little more looking into this. Is there any emerging documentation for how to write a gw addon? I've only just started using it and skimming some of the code. If I were going to look at doing this, it's necessary to have a way to calculate the cheapest route to craft something. Just searching the graph one level deep is often a very poor reflection of the optimal crafting costs. Do you have some functionality like this in development? If not I may take a stab at it and hopefully you can make use of it. It seems like a pretty orthogonal component with many uses.

I'll try to get in touch with the Auctioneer people a little too so as to not duplicate effort if something cool is going on. No promises, but I kinda feeling like writing some code for WoW, and trade skills and auctions are the areas that interest me most.

Thanks again,
Sarah

PS: I have to say that part of me doesn't want this stuff to get too easy. I make fair gold being one of the few people on my server who really knows the tools and techniques to use to efficiently and statistically work the auctions market. (Not that you need a Ph.D in economics, just frequent market scans and some knowledge of basic statistics.) But a healthy market is ultimately good for everyone, and I've profited a lot from the work of others, so it's probably a good thing. :-)

Lilsparky—thank you for your thoughtful reply.

Here's what's needed to make Glypher continue to work. To make the basic functionality work, you only really need the ability to add n of an arbitrary item, just like the user clicked Queue.

However, it also has an (optional) feature to auto-clear the queue if it's not empty, so that you're not crafting twice as many as you need or continue to craft after market conditions have changed. The queue glyphs mechanism basically assumes that the current character's queue is empty, and the option ensures that this is so.

My ideal would be to have something like this. I don't know the blizz apis that well, and there might be an additional set if you plan to allow different queues for the same player… but I can't imagine a scenario where there wasn't a main or default queue.

Anyway, this is just a proposal for what I'd probably do. Many of these are simple convenience methods, but I can't easily imagine a scenario where you wouldn't want all these methods, or one where any of them would have to change (except possibly adding addition methods for multiple queues). I had something like just the first of these I could kludge things, but a clear queue would be nice.

# Add count of the output of a recipe to the given
# character's queue
addItem(characterId, recipeId, count);

# Add count of the output of a recipe to the current
# character's queue
addItem(recipeId, count);

# Clear the given character's queue
clearQueue(characterId);

# Clear the current character's queue
clearQueue();

# Check the size of the given character's queue
queueSize(characterId);

# Check the size of the current character's queue
queueSize();

# Check whether the given character's queue is empty
isQueueEmpty(characterId);

# Check whether the current character's queue is empty
isQueueEmpty();

This does bring up one tricky issue that I forgot to mention last time: multiple-output crafting. Examples here are tailoring or alchemy specialization. When I tailor, I always get two when I make primal mooncloth or moonshroud. But all of the TS replacements I've tried will queue it up in dependencies as though I always get one. Trickier is alchemy, where I sometimes get more than I asked for. At the very least, I'd like to see the dependency resolution mechanism account for my Mooncloth Tailoring. (Yes, this is going away in Cataclysm, but it's not here yet and it's pretty annoying for now.)

This mechanism might argue for queue management functions for both "go until I've crafted n" and "execute n times." I'd say for shopping lists, you might want to always use only estimates that are 100% probable. So I'd say you'd count mooncloth tailoring toward shopping lists, and ignore elixir mastery. But, for example, if I wanted 10 elixirs a prerequisite for something, ideally it would stop when I had 10 if my elixir bonus proc'd.

My dream example here:

1. Say that to level up I decide the most profitable thing is to make 5 Toughened Leather Gloves, each of which requires 2 Elixir of Defense.
2. I queue this and get the leather, but I don't have the necessary Elixirs of Defense. I choose (or GW chooses by default) to craft these.
3. I hop over to my alchemist and open GW, which already has those queued up.
   • This might work best in a separate dependency queue with its own Process button, that my normal Clear doesn't empty. The fact that my alt wants something shouldn't prevent me from doing my own stuff. My alt's needs are often low priority, but I don't necessarily want to empty their queues either. Something like a drop-down with my name and the names of all my GW-using alts might work here.
4. I press queue and it starts crafting Elixir of Defense until I have 10, regardless of how many times the recipe needs to be executed.
5. I mail them back and craft my gloves.

All make sense? This is a dream scenario, but I thought it might be useful to you to see the kind of stuff I would envision in my ideal TSW. If nothing else, dream scenarios can help you design APIs and mould your code flexibly for functionality that you might add later. (Just so long as you avoid the infamous second-system syndrome.)

Again, if I can give any help with any of this, let me know. Otherwise good luck. I hope I don't seem pushy: I'm only trying to be helpful.

Thanks for listening,
Sarah

lilsparky,

Great work so far! I'm really liking what I see.

I'm with sarah on the API. The only reason that I haven't switched over to using Gnomeworks full time is that I didn't want to hook my jewelcrafting/inscription addon into a "private" function.

I'd vote for a simple API function that adds a given number of an item to the current queue to get us started with the understanding that it is completely possible that it might change in the future if the need arises.

My addon is a modification of kevqueue that I put into a frame and modified to fit my needs so I can change as I need to when you need to change the API.

Keep up the good work!