Bella’s Eve Tools

Maltari and I have been poking at assets on and off for the last couple of weeks.  Minor changes and fixes mostly, but we’re also starting to play with some wallet and transactions information alongside the assets.  Maltari is playing with some sweet javascript chart generation code as well as just shoring up issues here and there.  If you use the nightly build, you’ll be seeing some random stuff show up and go away and possibly have a few things change in the database structure (most shouldn’t affect the core assets viewing).

We’re starting to track our bugs and feature desires a little bit on the trac homepage as well.

Note to self: I also really need to centralize my two copies of the assets code on nonninja so that people aren’t going to 2 different places.  We need to have a stable release copy as well that is guaranteed to work without weird stuff.

End randomness.

So, I’ve hacked in preliminary corp asset support (thanks to the fellow who loaned me the full API key of a corp director).  The initial UI simply requires checking the ‘Load Corp Assets’ checkbox when you enter your API key and choose the character that is a corp director.  This will load the corp assets instead of the personal assets in the same manner as loading personal assets.

The application simply handles a corp like it handles a player - the assets are stored in the same way and the corporation will have its own charid_hash that is accessible if you know the API key or someone has given you the URL.  The only difference in the database is the new field is_corp in the asset_update table.

I have not yet implemented the addition of conquerable stations to the database.  Hopefully I’ll be able to get around to this soon.

Medians are roughly implemented in the assets viewer and there are no more direct calls to eve-central.  Instead, the code retrieves the static median exports from my price system and loads them into a table.  This is not automated or scheduled in any way at this point, it’ll require manually running process_median_xml.php whenever you want fresh medians or scheduling that script to run daily/weekly/whatever.  It also allows to retrieve medians for all of the regions or any single region and lets the user choose the region to get prices from - generally The Forge will have the most data and the least chance of really wacky prices since volume is so much greater in Jita and surrounding areas.

You can check this stuff out at the live beta site.  The code that powers this should be available in the nightly when it generates at approximately midnight CST (-0600 GMT).  There are probably still some rough edges in this code.

It also requires a few changes/additions to the database, so check out import_extra.sql for any new tables that you might not have if you install this newer version.

Medians have been updated today.  Cron was indeed not running on nonninja.  Tables are repaired and any attempts to do mass deletions from the highly indexed raw price table have been abandoned.  I’ve got some code brewing that should let me do that without, y’know, taking down my host.

I’m also planning on doing some assets work this week - primarily getting my median price feeds integrated into the application as well as removing the last vestiges of direct calls to eve-central which have been a thorn in the side of the app, especially for folks installing the code on their own machines.

I’ll just put this here in case anyone is willing - I am looking for full API key access to someone with director roles in a corp with a few assets to test out “official” integration of corp assets into the codebase.   It’s a lot to ask so I doubt anyone will be forthcoming, just wanted to throw it out there.  Making a corp with an alt is still on my lists of things to do, just haven’t gotten there yet (mainly because I’m lazy and not playing a ton of EVE atm).

The current nightly build of the PHP Assets Viewer is not very stable.  In particular, the character picker is not working correctly.  I’ve not yet had a chance to look into and fix this issue - until it’s resolved, you should use the older stable version.