Ok... So the last commit had some networking code in the release notes, but I have a feeling most of that will be lost. I have never truly felt comfortable with the solution I had, in terms of elegance and scalability, and network effeciency etc.

I asked myself, how can I get it right? Well, I decided I needed to look at as much of other people's network code as I can get. Unfortunately I've not found a great deal, but I did find Almindor's (the guy who wrote lnet, which I use for networking) Lentilwars code. This has some elegant solutions to some problems I wasn't sure how to get through. The other piece of code is called DataPacker - written by Theo Lustenberger, which will be able to compress the data I send (zip), and make it easy for me to incrementally "decipher" the messages that was sent.

So generally I have hope to get the networking fully going, but for now it's still far off. I'm trying to get at least 30m of programming in a day. Obviously some days it'll be more, and others will be less. But 30m of DA focus a day... (even if it's more research).

Unfortunately, revision 102 is not the big network release I'd hoped it would be. I'll talk more about networking after the revision 102 parts. (seperate post)

I fixed a bug that was reported on the Bugs part of the wiki (thanks for whoever added that), Also, while testing my next export for excel stats, I found that loading a deck didn't display in the titlebar, and also requested you to save, even though you didn't change anything. So those are fixed too.

I was playing around with Magic Set Editor, and found their statistics to be pretty cool. So I suggested that they maybe fork that part of the project to create more of their nice statistics. I was told no go. For me... the thing about stats is that it's not so easy to program graphs etc. and I already know an application which is pretty good at it... Excel. So I've created an excel spreadsheet which can handle the stats. And added a function in DA to export the stats to a little text file.

So now, via Excel, you can have Mana Curve + Type graphs, or Color + Type (the two I have in by default)... but it's Excel Pivots... just use the data available. You can analyse however you want. I added a column called "mana source" which looks for "add" and "to your mana pool" to check for mana sources. This might be crude, and could sometimes be wrong, but it's a start. Obviously this will not work so 100% if you're using a non-english database. --- Which is kind of a hole...

Revision 102:

C : Lots of "template" code
C : Split the NetSend and NetReceive codes
Fix : Delete from SB button now deletes from SB and does not add to SB (rev 100 fixed the code).
Fix : On deckopen, the filename is now displayed in the deckeditor.
Fix : Loading a file (in deckeditor) no longer makes it dirty. (doesn't prompt for save if you exit without changes)
F : Export tab delimited data to Excel for deck stats (note, it drops it to the folder where the .exe is installed)
F : Added DeckStats.xls to the installs to help with stats (I made it not use macros, for security)

Newer Posts Older Posts Home

Blogger Template by Blogcrowds.