Welcome to Xalp!

So I've wanted to write my own (off-line!) Everquest necro DPS parser for some time.
It's polished to a point where it's not overwhelmingly embarassing, but it still needs a bunch of work.

Really I'm just trying to catch some subtle things that most parsers gloss over, like the anguish BP click and Chaotic Power procs, and how they affect dps. Also I added in the ability to export out each view into comma seperated files for fun excel analysis, and a html version of the graph using basic tables.

Given some time I'll stick in the crit information and add a method to save some parses into a database for faster parsing and for comparisons.

So like I said, it's very beta, download it and feel free to report any fun bugs to Maelin.Xislaben, crashing etc may be more easily to identify with the actual log file, so if you want you can zip it and email it to me here at dzert.com.

What all does it install?
References:
Microsoft DAO 3.6 Object Library - dao360.dll (communicating with the db)
Microsoft Data Formatting Object Library 6.0 (SP4) - MSSTDFMT.dll (I forget what I used this for!)
Microsoft Jet and Replication Objects 2.6 Library - msjro.dll (compacting the db)

Controls:
Microsoft Chart Control 6.0 (SP4) (OLEDB) - MSCHRT20.ocx (making pretty graphs)
Microsoft Common Dialog Control 6.0 (SP3) - COMDLG32.dll (file system object to grab log files)
Microsoft Windows Common Controls 5.0 (SP2) - COMCTL32.ocx (listviews etc)
Microsoft Windows Common Controls 6.0 (SP6) - MSCOMCTL.ocx (better listviews etc)

Application:
Xalp.exe - Main app
XalpDB.mdb - MsAccess Database
12 gif images - 4 pixel gif files for use with the graph export

UPDATE - 09/16/2007:
Well just as an update, I've been looking into ways to parse an entire raid and spit out all of a log file for a single fight only (and do it quickly), and I've been experimenting with various controls to make things more functional, treeviews, msflexgrid, etc.

This software stores lots of information in memory, so it becomes something of a memory hog, and I'm looking to cut down on that as well. Maybe I should selectively calculate things like Yalp instead of calculate everything up front. At least storing data in a database instead of memory lets me keep a relatively low memory footprint at the cost of speed. I did find some batch update functionality with ADO but I'm not seeing much of a speed improvement.