Pheal 0.1.0 released

Ok, after pheal dev version hat customizeable keys in for a while,
but people kept bugging me, i’ve created a new release.

Pheal-0.1.0 has
- custom keys enabled by default
- ssl enabled by default

update if you want to use custom keys (you should want that)
dont update if you only have legacy keys and dont want to switch.

listed at 3rdpartyeve.net

I havent been blogging much lately, neither about Pheal nor about anything else. There has been alot happening arround Pheal since my last post, several other developers have added work to it, and nowadays i believe its the best solution for PHP driven 3rd part eve apps.

I recently started a new project, 3rdpartyeve.net which is basically a site listing 3rdparty work arround EVE Online – and ofcourse Pheal is one of the first porjects that i added there

King23 Pheal CLI

A few people have been asking me for more examples on the usage of pheal lately,
so i hacked together a short example utilizing King23 Tasks to create a simple CLI to the EVE API, atm it doesnt really cover much functionality, but it should be a nice live demonstration on how to use Pheal.

More Information on this are available at its Github page

Edit: it also contains usage of Doctrine, as earlier shown on this Blog :)

Pheal: PHP EVE API Library

Introduction

Pheal, (yet )a(nother) PHP Library for reading the API is available now,
it is basically a port of EAAL (which is for Ruby), and does not come with many extras (a file cache handler is included, but can be replaced by other handlers quite simple).

Why?

In the last few days i have been looking for PHP Libraries that allow me to work with the EVE Online API. It should also be used integrated in my King23 Framework

I found two libraries that are worth mentioning:

Both can do the job just fine, but both have their problems too.

Ale besides the EVE Api also has some functionality to access
the EVE Central API, but tends to return SimpleXMLElements (or in most cases a own Class derived from those). While that allows a few nice xml tricks, it can get quite annoying when you forget to cast something you expect to be a string.

Yapeal allready got me running away when the documentation in its ini file said that it *requires* a database to be set. I don’t want to have a rdbms running, just for some library
fetching xml documents.

both require configuration through ini files, which i find rather odd, since when deploying an application i dont want the user to go through all sorts of ini files from the libraries used, i want him to use one central application configuration.

So how to use Pheal?

please check the Github Page for a bit of info on how to use it, further tutorials might come up during the next few weeks on this blog.

regards,
PP