EVE Technology Lab

yeah i see. i will test it later.

Not really if that's the only error message you get but make sure you updated the DB with the install/ script. You can take a look at the cached XML in cache/char/charCharacterSheetxxx.xml and see if you notice anything that doesn't seem the same as you find at http://wiki.eve-id.net/APIv2_Char_CharacterSheet_XML that might give a clue as well.

No and should really only need to update the utilRegistered tables the other's get updated from the API itself and manual changes there could cause problems it's better to just delete info and clear utilCachedUntil so it can pull everything again.

A copy of the CharacterSheet schema and the XML would be useful I would suggest E-Mailing link to me using one listed in my GibHub account and set them to expire in say a day. Other option is of course to just E-Mail them to me while your at it

Alright thought it was time for an update on things. I just did a large 209 commit merge into 1.1.x from the WIP branch with only one minor conflict I'm even more impressed with Git after that then I have been.

So I'll do a quick overview of what's working.

• Account section 3 of 3.
• Api section 1 of 1. New to Yapeal.
• Map section 4 of 4.
• Eve section 3.5 of 13. Faction War stuff not done yet could maybe be done but no way to test. CharacterInfo is WIP and new to Yapeal. Many of the APis in this section aren't something that Yapeal is made to do but at some point may include just to allow users to have a single interface to everything in the Eve APis.
• Char section 12 of 31 APIs. Things like AccountBalance, CharacterSheet, MarketOrders, Wallets are done. Some others like Industrial jobs could be but it just has a lot of columns to do you know Major missing here is AssetList.
• Corp Section 2 of 27. Most of the ones that are same as char section can be done just need some time.
• Server 0 of 1. Can be done just haven't got to it.

For the details on what is and isn't done take a look in the lib/Database/ directory for the GitHub 1.1.x branch.

So anyone that developing a new application it's strongly suggested that you develop against the new code vs the old 1.0.x versions as they are end of live and being depreciated as soon as I feel the new code is complete enough. Existing application can of course continue to use the old version but as it's not going to be receiving any updates and CCP seems to be continuing to make changes to the existing APIs and adding new ones you'll find that things will stop working or you can't add the newer stuff because data isn't available from Yapeal.

So I'm going to just add some somewhat random thoughts here I think would be of interest. First off the new code is faster. Yapeal has always been fast in that the code outside of network and database stuff took less than a quarter of a second to run here locally even on my older laptop. Now though with the move from ADOdb (May it die lonely and forgotten) to PDO the database access is much faster. I'm sure most of that has to do with go from most of the code being badly written PHP in ADOdb to using C code in PDO but also I have done a few things in Yapeal itself to take better advantage of things like transactions and prepare statements which can lead to quicker access.

Yapeal now does a much better job of reusing it's network connection as well which seems to have had a nice speed boost as well. Before Yapeal would re-use the network connection for say all the characters/corprations in one API call but didn't reuse it between different API calls in most cases which cause a lot of slow down. Now Yapeal truly uses just one connection for all the API calls when it is ran. The new network in Guzzle which it now uses IMHO is better too.

I haven't done any real benchmarking but to give you some idea using the same computer with all the current APIs active but need to do network refresh because their caches has expired Yapeal runs in ~20 seconds with my test keys vs the current master taking a little over a minute. Master of course has some additional APIs but just the feel with the new code on a couple of APIs seems much faster than the same thing with the older code.

Anyway think this post is long enough for now so please take a look at the new code and kick it's tires so to say a little and let me know what you think.

Okay been thinking about the above end of life on PHP 5.3 and thought I'd ask for some input from current users of Yapeal and other people interested in using it. You may have to do a little research with your hosting site for the answer.

If the next version of Yapeal required at least PHP 5.4 would anybody have problems with their site?

Main reason I'm asking is I would prefer with the current re-write to go ahead and make it for PHP 5.4 as there are some features that Yapeal can take advantage of if it's not going to cause to many problems for people. First thing that this would do is allow Yapeal to use PHP traits which because of both the design of Yapeal and the Eve APIs could be very useful.

Anyway would like to hear everyone's thoughts on this.

Just a quick update for everyone. PHP5.4 will be required for the next version of Yapeal as some of the new language structures just make a huge difference on the amount of duplicate code needed. I've spent last week and a half or so on re-factoring a lot of stuff and now many of the class can have only a single method and maybe a single property vs 3-4 methods and several properties. The main thing that PHP 5.4 give is Traits which allows for a more horizontal sharing of code which better fits the APIs vs a parent-child inheritance PHP normally allows.

I'm going to try to get at least a good solid beta/RC version out before the new update to Eve comes out since it'll be making a lot of changes to industrial job and research stuff you'll need to be updating in your applications as well for those of you working with those things.

Anyway as always thank you for using Yapeal, Dragonaire

IndustryJobs ad History are out in WIP for testing but need to do some other updates to have corp ones ready as well. I'll be starting some short run jobs to have new test data but looks like they still have some issues at CCP that may cause a few issues too.
https://forums.eveonline.com/default.aspx?g=posts&t=360020

I'm personally still downloading updated and should be able to try things out in an hour or less I hope.

Edit: Looks like it works fine be looking at updating stuff for corp to work as well. Have to add Facilities API still for it still.

Keep up the awesome work!

Hi Dragonaire!

First of all: Thank you for your awesome work, Yapeal is really great!

However, I am trying to intergate it into an existing PHP project and I have no experience with composer at all. You install.md is empty and points me towards composer. I installed it and I ran "composer install" in the folder I extracted yapeal to (without my existing project for now) but I get 34 "problems" from composer.

So is composer even the best way to integrate yapeal into an existing project or what else should I try?
If you point me into the right direction or just say "follow an old version#s install instruction as far as it matches" I will do so ;)

Any help is much appreciated!