lmao=Robin-Hood= wrote:
Perhaps Jeff will give them some lessons in programming...
Last edited by Hurricane (2007-02-19 06:53:48)
I was waiting for that. Me too. :ashamed:Hurricane wrote:
I have no idea how to use that stuff as I am a website and in general coding noob, but good job!
No no, no apologies are necessary. I'm just not a developer at all, so I guess most of the features of this update go right over my head.chuyskywalker wrote:
Like I had said when I hinted at it's release: this is a feature for developers. Some very cool things may come of it from motivated people, but not instantly. Sorry!Havok wrote:
Hmm... I'm impressed with the new features, but I was hoping the new features would be more flashy... Good work nonetheless.
Like I said to Chuy, I'm not a developer or clan leader/member, so most of the features aren't useful to me. By flashy, I mean something like bringing the sigs back (with a guide for dummies like me).kilgoretrout wrote:
More flashy? This shit is awesome. It's really, really flashy from a coder's standpoint. This is going to open up a ton of possibilities for clan pages and such. Thanks a lot, Chuy. It's extremely cool of you to develop this API and let people piggy back off of your hard work.Havok wrote:
Hmm... I'm impressed with the new features, but I was hoping the new features would be more flashy... Good work nonetheless.
Actually, parsing XML from Javascript is a pain in the butt. You have to use the built in and ackward DOM traversal methods. With JSON, it's just done. That's it. It's data. The JS interpreter, literally, looks like this:falafel wrote:
i looks cool
it would be even better if I could get the stats as XML though (easy access from both javascript and PHP with XML DOM)
var json_object = eval("("+json_code+")");
alert(json_object.pid + " -- " + json_object.nick);$json_object = json_decode($json_code); echo $json_object->pid . " -- " . $json_object->nick;
QFE!chuyskywalker wrote:
I think JSON is actually a better format than XML for data sets like this.
Agree with Ty.=Robin-Hood= wrote:
Well that will probably be the day that we are obliged to pay for a number of patches that will fuck up BF2s!Ty wrote:
Fucking Hell dude, when are EA going to pay you for all this?
Nah lets just hint at the pay pal button
hint hint
top right corner
Hint hint
R
Does Chuy have an unwanted van at the end of his garden?Towelly wrote:
Does no-one else find it funny that the support e-mail address can be read as "a pikey @ bf2s.com"?
No? Just me then, either way, good stuff.
what ads??? There are no ads here! And I'm very happy about it!Scorpion0x17 wrote:
Agree with Ty.=Robin-Hood= wrote:
Well that will probably be the day that we are obliged to pay for a number of patches that will fuck up BF2s!Ty wrote:
Fucking Hell dude, when are EA going to pay you for all this?
Nah lets just hint at the pay pal button
hint hint
top right corner
Hint hint
R
But also, mustn't mention those google ads and how clicking on them generates income for chuy...
Oh, sorry, did I just mention google ads and how clicking on them generates income for chuy?
So sorry, won't do it again...
I guess in this case, 99.9% of people using it are going to put it on their prepackaged PHP sites; and its leaner with bandwidth. I'm with you falafel in having something a bit more context agnostic. Either way its a pretty easy parse.chuyskywalker wrote:
Actually, parsing XML from Javascript is a pain in the butt. You have to use the built in and ackward DOM traversal methods. With JSON, it's just done.falafel wrote:
i looks cool
it would be even better if I could get the stats as XML though (easy access from both javascript and PHP with XML DOM)
I think JSON is actually a better format than XML for data sets like this.
Last edited by jsnipy (2007-02-20 03:30:35)
Nobody is stopping anybody in generating some prefixed scripts that handle the basics. If they are posted, they might end up in the wiki, as example. (For the interested and knowledgeable few: hint hint!)jsnipy wrote:
I guess in this case, 99.9% of people using it are going to put it on their prepackaged PHP sites; and its leaner with bandwidth. I'm with you falafel in having something a bit more context agnostic. Either way its a pretty easy parse.