EVE Search - Yapeal PHP API library (revision 1207 branches/keys/)

Check My IP Information

All Channels

EVE Technology Lab

Yapeal PHP API library (revision 1207 branches/keys/)

» Click here to find additional results for this topic using Google

Monitor this thread via RSS [?]

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 [17] 18 .. 18 :: one page

Author	Thread Statistics \| Show CCP posts - 1 post(s)
Dragonaire Here there be Dragons 54	Posted - 2014.05.27 06:13:00 - [481] - Quote Good to hear it Zynen. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information.
Dragonaire Here there be Dragons 54	Posted - 2014.05.31 20:10:00 - [482] - Quote So as most of you know have been working on updating Yapeal and part of that is a major re-factoring of all the code. I was kicking around some ideas with another developer and he made suggestion to have history of all the APIs. So as it is now the API data is either deleted and re-added on each API pull or the record is updated depending on some internal technical reasons but the end result is the same that basically there is only access to the most current version of the API data and no way to see how things might have changed. Now since Yapeal is being changed in a major way which will already have some backward compatibility changes I decided to ask if this was something you guys would find useful? Understand the simple way to do it on the design part is to add an auto-incremental column to all the tables and make a few changes to the keys and indexes. The problem becomes finding the most current record in your queries on a per API and ownerID basis for you. Some other ideas were kicked around but the all were more complex and had other problems that we might or might not be able to overcome. So to the questions: Would you like to see some kind of per API history feature added? Do you think it is worth adding know that probably all of your existing queries will need to be updated? So let me know what you think and we'll look at it some more based in the feedback I get. Also if anyone has some ideas on how to add the history but without the drawbacks of how I suggested it could be done please share it and if it works out to being a better way we'll be more than happy to try using it if everyone thinks it the way to go. As always thanks for using Yapeal. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information.
Somerset Mahm Cognitive Distortion 232	Posted - 2014.06.02 02:10:00 - [483] - Quote Which rows have useful history? Stuff like walletjournal is immutable, and I generally only care about the current state of a contract. SOMER Blink Microlotteries that finish in minutes! Running for over 2 years :)
Dragonaire Here there be Dragons 54	Posted - 2014.06.02 03:10:00 - [484] - Quote True for some APIs doesn't really matter one that we talked about is AssetList where you'd maybe be able to do audits on where stuff goes etc. MarketOrders might be interesting to as you could see how quickly something is selling or coming in which might be useful. Might be a couple others as well. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information.
Somerset Mahm Cognitive Distortion 232	Posted - 2014.06.02 20:49:00 - [485] - Quote Dragonaire wrote: True for some APIs doesn't really matter one that we talked about is AssetList where you'd maybe be able to do audits on where stuff goes etc. MarketOrders might be interesting to as you could see how quickly something is selling or coming in which might be useful. Might be a couple others as well. I can see the value but to me Yapeal is just an interface between the API and a database; I don't really want it to show data that isn't in the API. SOMER Blink Microlotteries that finish in minutes! Running for over 2 years :)
Tiberius Zol 12	Posted - 2014.06.03 11:30:00 - [486] - Quote Somerset Mahm wrote: Dragonaire wrote: True for some APIs doesn't really matter one that we talked about is AssetList where you'd maybe be able to do audits on where stuff goes etc. MarketOrders might be interesting to as you could see how quickly something is selling or coming in which might be useful. Might be a couple others as well. I can see the value but to me Yapeal is just an interface between the API and a database; I don't really want it to show data that isn't in the API. Me neither!
Dragonaire Here there be Dragons 54	Posted - 2014.06.03 18:01:00 - [487] - Quote Ok understand and after looking into it some more we came to same conclusion plus how hard it was looking programming wise. Something else we MAY do is add an event system to Yapeal so people can tie in to things like API retrieved, pre-store etc if they want to to do other stuff but not at a point willing to say it will make in at this time. Not plan that they will be able to change anything just know what's going on and maybe some read-only access to data in the pipeline to allow people to do their own thing if they want. It has advantage that if you don't need it you can ignore it and doesn't change how you use Yapeal. Anyway thanks for the feedback. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information.
Aquila Sagitta Blue-Fire 322	Posted - 2014.06.11 04:51:00 - [488] - Quote How do I get this to work with WAMP? I can't figure out how to give it no password for the database. I leave it blank it complains no matter what I do. Blue-Fire Best Fire
Jone Sad The Scope Gallente Federation 5	Posted - 2014.06.11 05:12:00 - [489] - Quote Aquila Sagitta wrote: How do I get this to work with WAMP? I can't figure out how to give it no password for the database. I leave it blank it complains no matter what I do. First you should setup your http server, after then TRY to use yapeal. ;) If you cannot setup such simple thing, maybe you should not use this library? How will you use php library if you cannot do such simple thing... Every time asking 'how' here? XD It's not 'php for dummies forum' isn't it? PS: Pay for some one, who will do it for you. But it won't solve ALL your problems.
Aquila Sagitta Blue-Fire 322	Posted - 2014.06.11 06:57:00 - [490] - Quote It is set up. I've got my website running fine with all my backend in place I'm just trying to get Yapeal to work. Yes I'm a novice and using command line is foreign to me for setting things up so I'm having problems passing blank parameters even though its blank in the config file and should work but it doesn't. So I mean if you could be helpful instead of pretentious that'd be great... Blue-Fire Best Fire

Louis Vitton Viziam Amarr Empire 79	Posted - 2014.06.11 07:36:00 - [491] - Quote Hey mate, If you are having issues please advise the errors your getting as well as also posting any configuration file information to here http://pastebin.com/ for us to look at. Please remove all password and usernames first. Post the commands you are using on the command line also please. Cheers, Louis
Aquila Sagitta Blue-Fire 322	Posted - 2014.06.11 16:27:00 - [492] - Quote The only problem I'm having is it won't accept no password. Is there any way I can leave the password blank? I mean currently its blank but it complains there's no password and won't run... Blue-Fire Best Fire
Dragonaire Here there be Dragons 54	Posted - 2014.06.11 17:15:00 - [493] - Quote Aquila Sagitta - Louis Vitton does have some good points that it helps to know what errors you are getting it also helps to know if you are having problem running yapeal.php itself or one of the install scripts and which version as well but I'll try to help anyway because the basic problem of how to do a empty parameter is the same on the command line. I'll use the install/createMySQLTables script in this example. Windows: php -f install/createMySQLTables.php -u"YapealUser" -p "" Notice the two double quotes for the password option. It's really the same idea as in the INI file. Helpfully that get's you past the problem you were having. Jone Sad - I'll assume you really were trying to be helpful with a sense of humor about you suggestions but it didn't come across that way to anyone. If that was NOT your intent then please don't make those types of post here. I understand you may NOT like post about what you find easy and not related to Yapeal directly but my view on it is helping out someone trying to use Yapeal is always worth doing and when I think they could be better served getting addition help elsewhere I usually direct them to it. In other news I'll be making an announcement about plans for Yapeal but I'll do it in a different post once I finish up something on my end later today. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information.
Aquila Sagitta Blue-Fire 322	Posted - 2014.06.11 18:22:00 - [494] - Quote What you suggested. Error I'm getting Reqs and error after testing privs Blue-Fire Best Fire
Dragonaire Here there be Dragons 54	Posted - 2014.06.11 22:45:00 - [495] - Quote Okay so windows being extra pain here try php -f install/createMySQLTables.php -- -u"YapealUser" -p "" Note added double dash after script name. Also per the errors it's returning looks like you deleted or changed something you shouldn't have in the INI file for it to say problem with [Database]. Might try making a copy from the yapeal-example.ini file again and just edit it as needed. Main thing to watch for is no missing quotes and make sure to use double quotes NOT single quotes. Also since using Windows make sure you're not using MS Office etc for edits as it'll replace them with curly quotes which don't work. If you have to try using notepad or any of the many programmer friendly editors out there for free or paid. I current use PhpStorm for my IDE and Notepad++ for extra outside of project edits. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information.
Dragonaire Here there be Dragons 54	Posted - 2014.06.12 00:35:00 - [496] - Quote Okay as I said have Announcement to make about Yapeal development etc. Some of you might have notice I pushed out a new Tagged version today 1.0.5 and for those of you that read the commit message I expect this to be the last version in the 1.0.x series. All future development is going to be in what is currently know as the 1.1.x series but naming subject to change depending on if I think that semantic version rules require something different. Everyone should start now on getting ready for using the new version as I expect to have fairly complete versions out Soon (tm). Backward compatibility breaks in 1.1.x: Uses PHP Namespaces so minimum version is PHP 5.3 but expected minimum is version 5.3.10 do to some PHP bugs. Yapeal uses mysqli instead of mysql for install scripts and PDO for main library. May be moving to PDO only in near future. INI config file going away to be replaced by Yaml instead. Other options may become available in the future but INI will NOT be one of them. Database changes. Most of these are cleanup on existing tables but several of the util* ones are being change/merge/deleted. Many 'That would be cool and someone might use them' minor features are being killed. Others I just can't think of right now. Benefits/ improvements expected with 1.1.x: Direct one-shot API calling instead of just automated randomized scan mode. This can be used for thing like web site account sign-up and key verifying. Yapeal goes fully OOP. You'll still be able to run it from crontab etc and it is still expected to mostly be used this way but you'll now have option to call the main Yapeal class directly and the per API classes also with little work. Uses Composer and Packagist. If you also use Composer in your project this should make using it a one line addition to your composer.json. Console tools. Many of the existing scripts used during install and new ones being added will use symfony2/console which should make them much more user-friendly. Faster. May or may NOT be noticeable do to network and database operations but should be. Testable. Some of the new code already has PHPUnit tests and most should have some before final release. Others I just can't think of right now. By no means are the lists complete but they should give you some idea what to expect. I will also add that changes to both lists are likely but only additions are expected to the first on the second it's more in flux as development is still ongoing. If you have ideas or code you think should be added to Yapeal please contact me as I'm open to suggestions on how to make it better and easier to use for everyone. If you would like to help please contact me or try out the 1.1.x branch from GitHub. Areas I really need help in is testing as I only have access to a couple keys myself with mostly inactive chars. Bug reports from your testing with more data would be very helpful. If you like to living on the edge try out the 1.1.x-WIP branch but be warned it's often broken and very incomplete as that's where I and another developer do our development work on the new stuff and often commit Work-In-Progress as the name implies. Alright I'll end this here and sorry for the long post but had a lot of stuff I wanted to get out. As always thanks for using Yapeal. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information.
Aquila Sagitta Blue-Fire 322	Posted - 2014.06.12 00:38:00 - [497] - Quote Same problem Redid yapeal.ini and only changed user/password stuff. Are you sure it can take no password? Blue-Fire Best Fire
Dragonaire Here there be Dragons 54	Posted - 2014.06.12 02:18:00 - [498] - Quote Okay actually looked at the code in testForMySQLDatabasePrivs.php and because of the way it test for the required settings it would NOT allow a empty password. All the other script I sure also would NOT allow it either so sorry I didn't check that part sooner but as my above post shows been busy with other Yapeal related stuff. Guess the reason it's never really come up before is even on a local only install like with WAMP it doesn't normally let you create a user with a blank password as far as I know. PhpMyAdmin I know doesn't allow them. Easiest fix is just to give the user you want to use a password. Something like 'abc123' is fine if it's only being used for some local testing and behind a good firewall. I actual use the default user and password from the example file during testing here locally all the time since I don't have anything in it but the public key and sometimes a couple others and nothing but Yapeal using the database. I also been known to dropping all the tables or whole databases several times a day during testing. Anyway sorry for NOT checking the code sooner but I rarely look at the old code except once in a while to check how I did something before so I make sure to do it differently this time because I like new bugs Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information.
Tiberius Zol 18	Posted - 2014.06.16 09:00:00 - [499] - Quote After the update to 1.0.5 i get this warnings: 2014-06-16 08:40:08.852 WARN: Caching invalid API XML for char/ContactList File: /eve/yapeal/class/YapealApiCache.php(177) 2014-06-16 08:40:08.876 WARN: Row was missing required fields (inWatchlist) that are needed for yapeal_charContactList File: /eve/yapeal/class/YapealQueryBuilder.php(211)
Dragonaire Here there be Dragons 54	Posted - 2014.06.16 18:55:00 - [500] - Quote Tiberius Zol - Did a push to master branch give it a try and see if it fixes your issue. I added issue #14 on GitHub as well for it. I'll have some comment there about it. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information.

Tiberius Zol 19	Posted - 2014.06.17 12:54:00 - [501] - Quote yeah i see. i will test it later.
Tiberius Zol 19	Posted - 2014.06.19 19:05:00 - [502] - Quote 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?
Dragonaire Here there be Dragons 54	Posted - 2014.06.19 23:13:00 - [503] - Quote 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 Eve API. Check out the Yapeal PHP Library thread for more information.
Tiberius Zol 19	Posted - 2014.06.20 08:15:00 - [504] - Quote Didn't found anything. But, as a sidenote I have changed all the keyID and vCode for my chars manually (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?
Dragonaire Here there be Dragons 54	Posted - 2014.06.21 05:32:00 - [505] - Quote 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 Eve API. Check out the Yapeal PHP Library thread for more information.
Tiberius Zol 19	Posted - 2014.06.21 08:11:00 - [506] - Quote 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)
Dragonaire Here there be Dragons 54	Posted - 2014.06.21 15:19:00 - [507] - Quote 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 Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information.
Tiberius Zol 19	Posted - 2014.06.21 17:29:00 - [508] - Quote i send some files to your yahoo mail. :-)
Dragonaire Here there be Dragons 54	Posted - 2014.06.26 17:57:00 - [509] - Quote 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. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information.
Dragonaire Here there be Dragons 54	Posted - 2014.06.27 17:33:00 - [510] - Quote 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 Eve API. Check out the Yapeal PHP Library thread for more information.



Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 [17] 18 .. 18 :: one page
First page \| Previous page \| Next page \| Last page

COPYRIGHT NOTICE
EVE Online, the EVE logo, EVE and all associated logos and designs are the intellectual property of CCP hf. All artwork, screenshots, characters, vehicles, storylines, world facts or other recognizable features of the intellectual property relating to these trademarks are likewise the intellectual property of CCP hf. EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide. All other trademarks are the property of their respective owners. CCP hf. has granted permission to EVE-Search.com to use EVE Online and all associated logos and designs for promotional and information purposes on its website but does not endorse, and is not in any way affiliated with, EVE-Search.com. CCP is in no way responsible for the content on or functioning of this website, nor can it be liable for any damage arising from the use of this website.