| Pages: 1 [2] :: one page |
|
|
| Author |
Thread Statistics | Show CCP posts - 5 post(s) |
Mark Hamill
Amarr
Galactic Waste Management
EVE Trade Consortium
   |
Posted - 2011.05.07 17:54:00 -
[31]
Edited by: Mark Hamill on 07/05/2011 17:54:46
 Originally by: Mark Hamill
Originally by: hankey
I think issue with extra line break after DESC field is still presents.
CCP Stillman, do you guys have plans to sort it out?
Could we please get an answer to this????
CSV exports look like this now
2011-04-24 12:45:00,4246641101,Planetary Construction,Mark Hamill,CONCORD,Planet IV,-250000.00,4424711487.48,"Construction on EveLocation ID: 40344524, ""Planet IV"":
1 x Gas Storage Facility
",,
with lots of extra line breaks.
Is CCP gonna fix this or do I once again start writing anti-ccp-borked code to straighten out your messes???
Oh the hell with it. Tired of waiting on responses to this and bugreports. Go play with your CQ. New features with bugs are ALWYAS more important than fixing what's broken. I'll do the same thing I did when you guys decided to change the way marketlog exports were named (i.e. Tash-Murkon-Small YF-12a Smartbomb-08302010.txt. What idiot uses the same token for field separators that are found in field names? NO. DON'FIX IT NOW. I've already made a workaround for this too). I'll yet again rewrite EVETycoon to unscrew your inability to stick to one format.
EVETycoon Marketing, trading and reprocessing tool. |
Etil DeLaFuente
|
Posted - 2011.05.18 09:07:00 -
[32]
Would it be possible to get an xsd for each of the API ?
also,
What is the purpose of having CharacterSheet and CharacterInfo ? If i want to have all the details about a character, i need to query both and aggregate the results. Resource and time consuming, not good.
CharacterSheet has some info missing in CharacterInfo (ancestry, DoB, gender, cloneName, cloneSkillpoints), and CharacterInfo has some info missing in CharacterSheet (skillpoints, security status, ship type, ship name). Both using the same api key level (full in this case).
CharacterInfo should be the header of CharacterSheet. Therefore, if i want all details, skills, certificates etc.. i'd only need to query CharacterSheet. If i don't care about skills and such, i'd only need to query CharacterInfo.
|
Dragonaire
Caldari
Corax.
Everto Rex Regis
|
Posted - 2011.05.18 14:54:00 -
[33]
I've made XSDs for many of the APIs which you can find in Yapeal. They are hiding in the cache/ directory for lack of a better place to put them for now  I planned on extracting them into a separate download but having gotten around to that yet.
--
Finds camping stations from the inside much easier.
Designer of Yapeal for Eve API.
|
Etil DeLaFuente
|
Posted - 2011.05.18 22:06:00 -
[34]
Originally by: Dragonaire
I've made XSDs for many of the APIs which you can find in Yapeal. They are hiding in the cache/ directory for lack of a better place to put them for now I planned on extracting them into a separate download but having gotten around to that yet.
Thanks, i'll have a look, but a better place would be on ccp's server and an xsd schema uri included in each XML content returned by the APIs. It's not like it's a brand new thing around...
|
Dragonaire
Caldari
Corax.
Everto Rex Regis
|
Posted - 2011.05.19 04:27:00 -
[35]
I'd like to see CCP use them during testing when they are making changes to the APIs so they'd catch some of the more glaring mistakes they always seem to have like misplaced <cachedUntil/> elements that keep breaking everyone's libraries/apps etc.
Be glad to have them use mine for that matter if it would help as I know it takes some time and testing to make the XSDs and insure they are validating things correctly  Nice thing with XSDs are they should be all be one time work and only need a little TLC when changes are plan on one of the APIs. I even did a genetic one for all APIs that is used until I get around to making one for an API. You know with it that at least the basic structure is correct even if the core data part isn't. It insures everything is inside <eveapi/> that starts with a <currentTime/> and either a <error/> or <result/> element followed by <cachedUntil/> which isn't inside <result/> or missing and that the date/times are in the correct format. If they had been using something like that all along nearly 50% of the API errors I've seen would have been caught before it was released. 
--
Finds camping stations from the inside much easier.
Designer of Yapeal for Eve API.
|
|
|
| |
|
| Pages: 1 [2] :: one page |
| First page | Previous page | Next page | Last page |