EVE Technology Lab

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.

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.

Me neither!

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.

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...

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...

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.

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

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.