This project is abandoned and its default file will likely not work with the most recent version of World of Warcraft. Whether this project is out of date or its author has marked it as abandoned, this project is no longer maintained.
GnomeWorks TradeSkill Frame -
a complete replacement for the blizzard trade skill frame.
I really have no idea what people are complaining about. On any toon I've logged in on it's taken like 30 seconds TOPS.
This is NOT a bad thing, especially if it gives Gnomeworks more accurate information to work with. Lets not criticize lilsparky for trying to make things better.
I guess I must have been lucky, my scanning didn't take forever to complete and only took about 1 - 2 minutes to finish. Although I do admit I find it somewhat of an annoyance scanning for ones I don't have but oh well. I also want to say thank you for working on this again.
I would like to thank Sarah for her post. I totally agree.
I just logged in and GW is scanning my recipes. I want to do a transmute, but I can't because GW is scanning and there's no obvious way to stop it. And it's taking a long time. I've been logged on for 25 minutes and it's not even halfway done.
To summarize Sarah's post, this is a bad thing, and it needs to go. There's got to be a better and less annoying way to do what you need to do.
Update: After first posting this, I turned off GW so I could do my transmute and raid without dealing with the scan. I restarted it after raid. It started with Alchemy, which I assumed it was scanning because it was one of my professions. Then, when it finished Alchemy over 2 hours later, it started on Blacksmithing (which is not one of my professions)! At this rate, it would take almost a day!
Just now, I tried clicking on my Alchemy icon and noticed that it caused the scan complete one recipe for each click. I was able to get through Blacksmithing in a few seconds by repeatedly clicking on the Alchemy icon. So I'm guessing that this is the expected speed and that the glacial rate scanning is the result of a bug.
honestly, i'm not sure how much data libpt is providing to gw these days. it may go bye-bye soon.
what is it saying about the skill #'s for fire prism? i'm actually scanning the client for skill levels instead of relying on wowhead or whatever other source. wowhead is actually not terribly accurate and since it's not too hard to get actual concrete numbers from the actual game client, i prefer to use that method.
however, i did recently change the skill level code so it's possible something got broke.
I'm not sure where the information for "orange/yellow/green/gray" skill level comes from but r146 has at least one incorrect change... I believe Jewelcrafting Fire Prism should be orange until 525.
sarah, i understand what you're saying, but keep in mind this is something that should only ever scan when there's a new patch or when you first install gw. in the future i'll include data for the current build (at the time of commit) to avoid the scan if there's no newer data.
First, why does GW need to know about recipes that I don't have? I know you have the All Recipes lists available, is the is the only use case? (Seems a bit thin as a justification.)
If you need to have this information around for other reasons, couldn't you mine it once and include it as a library? If a user tried to go to the All Recipes area with an outdated version of the data, you could offer to scan for an updated version.
Alternately, if this feature is only useful if you view the All Recipes lists, just generate it as needed when the user selects an all-recipe list—preferably only for the recipe type they chose. (If I only really do inscription, enchanting and cooking seriously, I don't need all the leatherworking and blacksmithing recipes loaded all the time.)
If you plan to keep this, please at least delay this scan until the user first opens GnomeWorks. At the very least let us move or hide the thermometer.
I don't mind you trying things out, but I hope you will reconsider the way you implement this. I expanded on my rationale a little bit below, but I didn't want to derail my comment with a big rant. I have strong feelings about this implementation, but not the feature itself.
I think I've mentioned before, but add-ons that insist on popping windows on startup are one of my serious pet peeves. It violates a basic UI principle going back to the early days of Apple's UI work: never pop a modal dialog box unless there is no way to proceed without immediate user attention. Put another way, never assume that your widget is as important to the user as it is to you, the developer.
I have yet to come across a situation where an add-on legitimately needed to pop a window at startup. I have, however, several times come across a situation where add-ons will plaster some big display right across the intro cinematic if you make a character without enough initialization in your account settings.
Most WoW users have a dozen or more add-ons. I personally have about 70. Most of them have a very specific function, like managing free space my bags, opening mage portals, switching between specs, telling how long a flight will take, etc. Their job is to do one task when I want and don't take up CPU, memory or visual space otherwise.
When you have lots of add-ons, all the little not-so-often indulgences developers allow themselves turns into a constant barrage of annoyances. This is something that Microsoft has struggled with, as they historically gave developers more weight than designers. Witness all the pop-ups in the notification area or Vista's UAC system. Those were all things the developer thought were important and wouldn't happen often. Taken together, they became a constant stream of annoyances.
it should only scan once and then not scan again until it detects that the game client has been patched. the scan should not take more than a couple minutes at most.
new version is up. addressed some of the latest issues mentioned.
lemme know if anything explodes. i decided to add a live data scanner to the mix. right now, it's hardly used, but i'm thinking i might have it pre-scan all trade skill data (once each time a new patch has been introduced) rather than have it accumulate over time.
the benefit of pre-scanning all the data is that the db would be way more complete. the drawback is that it would inflate the db for people who don't bother with looking around the full recipe lists... still debating this...
@cashew49721: If you google this behavior, you will find that the auto-bag opening is something that Blizzard added in the last patch, and is in no way related to Gnomeworks. If you have no bags open when you go to a vendor, auction, bank, etc, WOW will auto-open your bags. If you have 1 or more bags already open, it won't do anything.
cashew: gw shouldn't be opening your bags at all. please make sure something else isn't doing this.
krellmax: there will be an update soon, i hope. i've addressed the search responsiveness and a few of the other bugs, but part of the fix has added some code that needs some more work. i want to sort out the mail lag as well before committing.
Really like GW, one question... is there any way to turn off/toggle the bags? I would like to open GW or any profession without all my bags opening at once and covering half my screen. I can't find a way to turn this off or do I not have a choice?
It looks like all the issues I've had have been reported. I opened one requesting optimizations though. The mod is great and I'm now very dependent on it's features but it's painful to use because of how poor it performs. When are we going to have a new release?
I really have no idea what people are complaining about. On any toon I've logged in on it's taken like 30 seconds TOPS.
This is NOT a bad thing, especially if it gives Gnomeworks more accurate information to work with. Lets not criticize lilsparky for trying to make things better.
I guess I must have been lucky, my scanning didn't take forever to complete and only took about 1 - 2 minutes to finish. Although I do admit I find it somewhat of an annoyance scanning for ones I don't have but oh well. I also want to say thank you for working on this again.
I would like to thank Sarah for her post. I totally agree.
I just logged in and GW is scanning my recipes. I want to do a transmute, but I can't because GW is scanning and there's no obvious way to stop it. And it's taking a long time. I've been logged on for 25 minutes and it's not even halfway done.
To summarize Sarah's post, this is a bad thing, and it needs to go. There's got to be a better and less annoying way to do what you need to do.
Update: After first posting this, I turned off GW so I could do my transmute and raid without dealing with the scan. I restarted it after raid. It started with Alchemy, which I assumed it was scanning because it was one of my professions. Then, when it finished Alchemy over 2 hours later, it started on Blacksmithing (which is not one of my professions)! At this rate, it would take almost a day!
Just now, I tried clicking on my Alchemy icon and noticed that it caused the scan complete one recipe for each click. I was able to get through Blacksmithing in a few seconds by repeatedly clicking on the Alchemy icon. So I'm guessing that this is the expected speed and that the glacial rate scanning is the result of a bug.
Okay, going back to lots of clicking...
The .toc is not correct with the most recent version, it is still showing as version 40000 and it should be 40100.
honestly, i'm not sure how much data libpt is providing to gw these days. it may go bye-bye soon.
what is it saying about the skill #'s for fire prism? i'm actually scanning the client for skill levels instead of relying on wowhead or whatever other source. wowhead is actually not terribly accurate and since it's not too hard to get actual concrete numbers from the actual game client, i prefer to use that method.
however, i did recently change the skill level code so it's possible something got broke.
When I compare r144 with r146 I see changes to LibPeriodicTable-3.1-*.toc but no updated *.lua files. Is this kosher?
I'm not sure where the information for "orange/yellow/green/gray" skill level comes from but r146 has at least one incorrect change... I believe Jewelcrafting Fire Prism should be orange until 525.
I also believe that r144 had it right.
sarah, i understand what you're saying, but keep in mind this is something that should only ever scan when there's a new patch or when you first install gw. in the future i'll include data for the current build (at the time of commit) to avoid the scan if there's no newer data.
So I have a few thoughts on the new scanning.
First, why does GW need to know about recipes that I don't have? I know you have the All Recipes lists available, is the is the only use case? (Seems a bit thin as a justification.)
If you need to have this information around for other reasons, couldn't you mine it once and include it as a library? If a user tried to go to the All Recipes area with an outdated version of the data, you could offer to scan for an updated version.
Alternately, if this feature is only useful if you view the All Recipes lists, just generate it as needed when the user selects an all-recipe list—preferably only for the recipe type they chose. (If I only really do inscription, enchanting and cooking seriously, I don't need all the leatherworking and blacksmithing recipes loaded all the time.)
If you plan to keep this, please at least delay this scan until the user first opens GnomeWorks. At the very least let us move or hide the thermometer.
I don't mind you trying things out, but I hope you will reconsider the way you implement this. I expanded on my rationale a little bit below, but I didn't want to derail my comment with a big rant. I have strong feelings about this implementation, but not the feature itself.
I think I've mentioned before, but add-ons that insist on popping windows on startup are one of my serious pet peeves. It violates a basic UI principle going back to the early days of Apple's UI work: never pop a modal dialog box unless there is no way to proceed without immediate user attention. Put another way, never assume that your widget is as important to the user as it is to you, the developer.
I have yet to come across a situation where an add-on legitimately needed to pop a window at startup. I have, however, several times come across a situation where add-ons will plaster some big display right across the intro cinematic if you make a character without enough initialization in your account settings.
Most WoW users have a dozen or more add-ons. I personally have about 70. Most of them have a very specific function, like managing free space my bags, opening mage portals, switching between specs, telling how long a flight will take, etc. Their job is to do one task when I want and don't take up CPU, memory or visual space otherwise.
When you have lots of add-ons, all the little not-so-often indulgences developers allow themselves turns into a constant barrage of annoyances. This is something that Microsoft has struggled with, as they historically gave developers more weight than designers. Witness all the pop-ups in the notification area or Vista's UAC system. Those were all things the developer thought were important and wouldn't happen often. Taken together, they became a constant stream of annoyances.
it should only scan once and then not scan again until it detects that the game client has been patched. the scan should not take more than a couple minutes at most.
Hi I have installed the new version. I must clicking on the buttons to scan why
new version is up. addressed some of the latest issues mentioned.
lemme know if anything explodes. i decided to add a live data scanner to the mix. right now, it's hardly used, but i'm thinking i might have it pre-scan all trade skill data (once each time a new patch has been introduced) rather than have it accumulate over time.
the benefit of pre-scanning all the data is that the db would be way more complete. the drawback is that it would inflate the db for people who don't bother with looking around the full recipe lists... still debating this...
@cashew49721: If you google this behavior, you will find that the auto-bag opening is something that Blizzard added in the last patch, and is in no way related to Gnomeworks. If you have no bags open when you go to a vendor, auction, bank, etc, WOW will auto-open your bags. If you have 1 or more bags already open, it won't do anything.
lilspark, anything I can do to help you test? I can apply a patch file to my local repo and help you test. Let me know. PM me for my e-mail address.
cashew: gw shouldn't be opening your bags at all. please make sure something else isn't doing this.
krellmax: there will be an update soon, i hope. i've addressed the search responsiveness and a few of the other bugs, but part of the fix has added some code that needs some more work. i want to sort out the mail lag as well before committing.
Really like GW, one question... is there any way to turn off/toggle the bags? I would like to open GW or any profession without all my bags opening at once and covering half my screen. I can't find a way to turn this off or do I not have a choice?
Thanks
@spiralofhope
It looks like all the issues I've had have been reported. I opened one requesting optimizations though. The mod is great and I'm now very dependent on it's features but it's painful to use because of how poor it performs. When are we going to have a new release?
@lilsparky
This is really nice to here. Hopefully it won't be too long before an update is put out. :)
fwiw, i'm still here. just busy. tho i'm becoming less busy and i've actually been doing some work on gw again...
Guys, feature requests and bug reports need to be created as tickets.