Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 1 post(s) |
Joanne Breau
Capsuleers for Sisters of EVE
0
|
Posted - 2014.11.14 03:02:24 -
[1] - Quote
I'm a webdev and am used to dealing with PHP and MySQL, had an idea for an web app for EVE and thought "Can't be too hard, can it?" But I can't even start. I don't know where to go to get the necessary information. The tutorial stickied here seems to be terribly outdated, the developers.eveonline.com site has minimal information, and the libraries are overwhelming (as well as not very documented).
I don't know if I'm taking the wrong approach here. My webapp only needs to be able to fetch public character data and public killmails (from a link pasted by the user. I'm not trying to make another killboard site, I promise). These requests are supposed to happen only when an user inputs information, so the overly complicated stuff such as cronjobs don't seem really useful to me, but every resource I find seems to focus on this kind of stuff.
I might need a way to have users authenticate their characters, but I want to learn the basics before I tackle that problem. |
Darius Pythe
Academy of Evil
0
|
Posted - 2014.11.14 04:05:08 -
[2] - Quote
@Joanne Breau - are you reading some of the topics in this section? I have posted one called
Working on a Project? - [Evil At Work Network]
In where i mention if anyone needs help, assistance or similar to ask.
The Evil At Work Network has a team of people that do development and design if you are looking to learn. |
Kali Izia
GoomWaffe Goonswarm Federation
24
|
Posted - 2014.11.14 04:29:22 -
[3] - Quote
The best resource right now for the XML API is https://neweden-dev.com/API
If you want public character data, you're probably looking at using something like CharacterInfo from the XML API.
For kilmails, you can get the user to copy the CREST URL from the client and parse that directly, it outputs JSON. If you want to use existing killboard links instead, Zkillboard has a good API for getting their kills and has info on their site.
For character auth, use SSO. Information for that is on the developer site. |
Joanne Breau
Capsuleers for Sisters of EVE
0
|
Posted - 2014.11.14 04:52:17 -
[4] - Quote
Thanks Darius. I skimmed through your thread, but thought it was more intended for the people who want to make something but don't know how to program. Rereading now I see you are also offering general help :)
Right now I've managed to get through my first hurdle, getting a Character ID from a Character Name (and then Character Info from that ID). If I get stuck again I'll post there.
Kali, thanks for the info. I'll look into the SSO, and get started on parsing the JSON for my purposes. |
Darius Pythe
Academy of Evil
0
|
Posted - 2014.11.14 04:58:35 -
[5] - Quote
I'm Going to send you a mail, and invite you to one of our Voice servers to assist with what ever you need. Thanks for reading my post again.
The Evil At Work Network is focused on helping with projects including how-to's. We are a community here. |
|
CCP FoxFour
C C P C C P Alliance
3682
|
Posted - 2014.11.14 08:54:24 -
[6] - Quote
I would also highly recommend looking into one of the available libraries for the XML API: https://wiki.eveonline.com/en/wiki/XML_API_Libraries
It can save you a lot of time and effort.
@CCP_FoxFour // Technical Designer // Team Size Matters
Third-party developer? Check out the official developers site for dev blogs, resources, and more.
|
|
Louis Vitton
Viziam Amarr Empire
81
|
Posted - 2014.11.15 21:17:54 -
[7] - Quote
Hey mate,.
I use Phealng (https://github.com/3rdpartyeve/phealng) it is very simple to use. Peter has done a grate job with it and he also updates it when required from my experience. It doesnt put the content directly into my database, i do that and it allows me to place the content in multiple tables if required with no edit to source.
If you dont want to create the tables however you can use yapeal (https://github.com/Dragonrun1/yapeal) this will put the content directly into your database for you and than you just need to build some stuff around it and off you go. Little harder to extend and if the api changes such as something is added (new field) in one of the api's it will required Dragonrun to update before you can get it in the database unless you do that yourself. |
Maestro Del'Tirith
Caldari Provisions Caldari State
0
|
Posted - 2014.11.15 21:44:27 -
[8] - Quote
Where is there good information on CREST API? I thought the XML API was the "old stuff" and we should use CREST but then there is no data on what the CREST API URLs even are, as far as I can tell. |
Dragonaire
Here there be Dragons
66
|
Posted - 2014.11.16 05:43:58 -
[9] - Quote
CREST is suppose to be self documenting if you use OPTIONS instead of GET, or POST at the HTTP level but many endpoints aren't public yet so it's a bit hit or miss if you get everything you might want/need from what I've seen so far.
On the XML API being the 'old stuff' with all the changes and updates that have been happening there it actually been becoming even better and more useful over the last few months thanks to CCP FoxFour's work on it.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Kali Izia
GoomWaffe Goonswarm Federation
24
|
Posted - 2014.11.16 06:52:14 -
[10] - Quote
CCP FoxFour is also adding a documentation endpoint SoonGäó so you can just make a single call instead of having to walk through all of CREST doing a bunch of OPTIONS calls.
As far as resources, I don't know if there are any really great ones that have everything in one place. New Eden Dev has a few things listed for it, but it's missing newer endpoints. Reading through dev blogs where things were announced is probably your best bet right now.
Or if you're feeling really adventurous and want to go through the OPTIONS calls, all you really need to know is that the public CREST root is https://public-crest.eveonline.com/ and the "real" CREST root (that should eventually replace public CREST) is https://crest-tq.eveonline.com/. You have to use crest-tq for OPTIONS, they won't work on public-crest. But all of your other requests need to go to public-crest for now. |
|
Maestro Del'Tirith
Caldari Provisions Caldari State
0
|
Posted - 2014.11.16 15:37:07 -
[11] - Quote
Ok - so I want to pull information like skills, assets, transactions etc - I don't see endpoints for these in CREST - so is the XML API the only way to work with this kind of information at this point?
I was imagining that the SSO would work in concert with CREST - is the SSO nothing at all but authentication at this point, with no controlled access to character data? |
Dragonaire
Here there be Dragons
66
|
Posted - 2014.11.16 19:51:27 -
[12] - Quote
SSO will be used to access the character and corporation detail data in CREST once they are made public but for now they aren't. All the things you asked about are already available through the XML API and have been for a while now so it's you best bet at this time. There is no plan for the XML APIs to go away even after stuff starts being made available in CREST. At some point when CREST is 'complete' there probably will be a slow transition from XML to it and the older XML APIs being phased out but it is expected to take several years for that to happen according to CCP.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Steve Ronuken
Fuzzwork Enterprises Vote Steve Ronuken for CSM
4192
|
Posted - 2014.11.16 23:19:13 -
[13] - Quote
https://www.fuzzwork.co.uk/crestDocumentation.php has some documentation on crest, based on a beta that Foxfour released.
Doesn't work in firefox, due to some oddness with CORS. works in chrome.
If you run into any particular problems, feel free to yell in my direction.
During uk working hours I can normally be found (as Fuzzysteve) on #eve-dev on irc.coldfront.net
Woo! CSM 9!
Fuzzwork Enterprises
Twitter: @fuzzysteve on Twitter
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |