I actually picked this up the other day as something to do while on business travel. Didn't realize there were any further developments since the original post and hadn't seen anyone else's effort til I was ready to post.
Took a quickish but very dirty attempt in python.
run it in the directory with all your XML tooltip files, and you'll get an output.csv file that has each unique field as a column header.
Several sacrifices were made for simplicity, but if I was still maintaining my hunterlist, I'd be able to easily use the output in conjuction with my spreadsheet's sort/filter tools.
rename to .py extension
edit: as far as I can tell, this depends on having something similar to the individual .xml file per tooltip that disquette originally provided
Last edited by Lurchington : 08/08/07 at 11:46 PM.
I've actually written a smart parser that will dynamically setup all pulls (you don't have to worry about number of circumstances). I'll have it finished this weekend, all that's left to do in it, is write the data to database / external file. I'm using PERL for the entire project, but I'm more than willing to share any code / ideas.
What I would also like is to be able to extract the text of the Socket Bonus into a column, is there a way of achieving this?
e.g. For the line "<span class="esock">Socket Bonus: +3 Spell Crit Rating</span><br />"
I would like "+3 Spell Crit Rating" written into a column.
Also knowing whether it is a green, blue, purple would be useful by reference to <span class="bluename"> or <span class="purplename"> and so on.
I tried to do the same thing, but unsuccessfully.
Then I looked into the source code and the line is basically skipped and only used to get the name of the item.
I would try to change the code, but unfortunately I don't have anything to compile for .NET. I assume it's only possible with VisualBasic or alike and there are no free tools to compile?
As part of the framework for a character profiler, I wrote a program to pull data from the Armory and parse it, then write it out to a custom XML format. I ran a full crawl the other day, so I should have an items.xml and sets.xml file covering most items.
I realize XML isn't the easiest thing to work with compared to a flat text file, but it's possible to write a translator to whatever flat format you want; I might include this in the data-handling tool whenever I get around to it. If anyone is interested in the two xml files let me know and I'll put them up somewhere.