These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
 

Yapeal PHP API library (version 1.0.5)

First post
Author
Tiberius Zol
Moira.
Villore Accords
#501 - 2014-06-17 12:54:15 UTC
yeah i see. i will test it later.

Mr. Tibbers on twitter: @Mr_Tibbers

Mr. Tibbers Blog: www.eve-versum.de

Tiberius Zol
Moira.
Villore Accords
#502 - 2014-06-19 19:05:08 UTC
hey.
seem to be one problem to go:

2014-06-19 17:00:42.121
WARN: Insert/upsert failed for yapeal_charCharacterSheet
File: /eve/yapeal/class/YapealQueryBuilder.php(425)

any idea?

Mr. Tibbers on twitter: @Mr_Tibbers

Mr. Tibbers Blog: www.eve-versum.de

Dragonaire
Here there be Dragons
#503 - 2014-06-19 23:13:42 UTC
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.

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.

Tiberius Zol
Moira.
Villore Accords
#504 - 2014-06-20 08:15:02 UTC  |  Edited by: Tiberius Zol
Didn't found anything. But, as a sidenote I have changed all the keyID and vCode for my chars manually in the MySQL Tables (yapeal_accountAccountStatus,yapeal_accountAPIKeyInfo,yapeal_accountKeyBridge,yapeal_utilRegisteredKey).
Is there some other thing to change, that i didn't see? Some stuff for the insert?

Mr. Tibbers on twitter: @Mr_Tibbers

Mr. Tibbers Blog: www.eve-versum.de

Dragonaire
Here there be Dragons
#505 - 2014-06-21 05:32:34 UTC
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.

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.

Tiberius Zol
Moira.
Villore Accords
#506 - 2014-06-21 08:11:13 UTC  |  Edited by: Tiberius Zol
I have truncated
- yapeal_accountAPIKeyInfo
- yapeal_accountAccountStatus
- yapeal_accountCharacters
- yapeal_accountKeyBridge
- yapeal_charAccountBalance
- yapeal_charAttributeEnhancers
- yapeal_charAttributes
- yapeal_charCharacterSheet
- yapeal_charContactList
- yapeal_charCorporationRoles
- yapeal_charCorporationRolesAtBase
- yapeal_charCorporationRolesAtHQ
- yapeal_charCorporationRolesAtOther
- yapeal_charCorporationTitles
- yapeal_charSkillInTraining
- yapeal_charSkillQueue
- yapeal_charSkills
- yapeal_utilCachedUntil
But still getting the same Error:
2014-06-21 07:40:24.586
WARN: Insert/upsert failed for yapeal_charCharacterSheet
File: /eve/yapeal/class/YapealQueryBuilder.php(425)

I can copy specific db schemes and an actual xml in a pastebin if it helps. Just give me a short info, what you need.

Mr. Tibbers on twitter: @Mr_Tibbers

Mr. Tibbers Blog: www.eve-versum.de

Dragonaire
Here there be Dragons
#507 - 2014-06-21 15:19:50 UTC
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 Blink

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.

Tiberius Zol
Moira.
Villore Accords
#508 - 2014-06-21 17:29:54 UTC
i send some files to your yahoo mail. :-)

Mr. Tibbers on twitter: @Mr_Tibbers

Mr. Tibbers Blog: www.eve-versum.de

Dragonaire
Here there be Dragons
#509 - 2014-06-26 17:57:38 UTC
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 Big smile 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 Blink 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.

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.

Dragonaire
Here there be Dragons
#510 - 2014-06-27 17:33:06 UTC
Just something I got reminded of today and decided to make post about that everyone should probably take a look at. PHP 5.3 end of life

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.

Dragonaire
Here there be Dragons
#511 - 2014-06-27 20:59:39 UTC
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.

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.

Tiberius Zol
Moira.
Villore Accords
#512 - 2014-06-30 13:12:20 UTC
Used 5.2 until now. But changed to 5.4 now. :) so no problem with it.

Mr. Tibbers on twitter: @Mr_Tibbers

Mr. Tibbers Blog: www.eve-versum.de

Dragonaire
Here there be Dragons
#513 - 2014-07-10 15:37:57 UTC
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

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.

Tiberius Zol
Moira.
Villore Accords
#514 - 2014-07-22 07:30:51 UTC
Guys... how is the update for the Crius API changes going? :-)

Mr. Tibbers on twitter: @Mr_Tibbers

Mr. Tibbers Blog: www.eve-versum.de

Dragonaire
Here there be Dragons
#515 - 2014-07-22 16:33:27 UTC  |  Edited by: 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.

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.

KnifeOrSpoon
Contraposition Industries Inc
#516 - 2014-07-23 09:04:54 UTC
Delicious! Thanks mate, my own implementation is a little dodgy for a hack of your work. I'd much prefer to have your own implementation instead of my rusty nail in the baseball bat.
CCP FoxFour
C C P
C C P Alliance
#517 - 2014-07-23 10:19:21 UTC
Keep up the awesome work!

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.

Dragonaire
Here there be Dragons
#518 - 2014-07-24 01:21:04 UTC
Lots of updates pushed today to 1.1.x-WIP branch including adding the corp versions of Industry stuff for people to try out. All the char versions seem to be working fine so I expect corp ones to be good as well. Fixed one typo (actually bad C/P) in createCorpTables.sql so make sure you update DB.

Just wanted to say something about a as yet to be documented feature of the bin\yc Database:Initialize command. The last thing it looks for is a bin/sql/CreateCustomTables.sql file. This can be used to automatically insert all your registered keys to save having to manually do so. I actually use this myself for that during testing. You can use it for other things as well as any SQL is generally allowed but I wouldn't try something like re-importing all of your tables data etc with it.

Please bug report anything that you find that's wrong and as always thank you for using Yapeal.

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.

Legedric Striker
DRUCKWELLE Evolution
#519 - 2014-07-24 11:16:39 UTC
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!

EVE-Skillplan.net - Plan your pilot skill training online on PC, Mac, tablet or smartphone!

Tiberius Zol
Moira.
Villore Accords
#520 - 2014-07-24 11:25:42 UTC
I would also like to see an alternative to composer, cause my web-provider does not allow to install it.

Mr. Tibbers on twitter: @Mr_Tibbers

Mr. Tibbers Blog: www.eve-versum.de