The client never parses
all he needs to know is the tophy id...
the daemon itself does all the parsing :)
On Fri, Aug 20, 2010 at 11:50 AM, bartbes <email address hidden> wrote:
> I'd like to say you still need to parse a trophy *object* it for
> GetTrophies.
>
> Anyway, back on-topic:
> So, you deprecate one of the 4 documented functions.. well, okay, I can
> manage, but what is the file format? The 'dummy' file was filled with
> 'random' strings..
>
> --
> Bring back RegisterTrophy
> https://bugs.launchpad.net/bugs/620762
> You received this bug notification because you are a member of OMG!,
> which is subscribed to omg.
>
> Status in OMG!: New
>
> Bug description:
> Of course I understand you're still working on the API, but I must say that
> parsing a trophy object is hard enough, let alone making one, that's why I
> prefer RegisterTrophy over InsertTrophy.
> Well that, and the fact that it is one of the few documented functions.
>
>
>
The client never parses
all he needs to know is the tophy id...
the daemon itself does all the parsing :)
On Fri, Aug 20, 2010 at 11:50 AM, bartbes <email address hidden> wrote:
> I'd like to say you still need to parse a trophy *object* it for /bugs.launchpad .net/bugs/ 620762
> GetTrophies.
>
> Anyway, back on-topic:
> So, you deprecate one of the 4 documented functions.. well, okay, I can
> manage, but what is the file format? The 'dummy' file was filled with
> 'random' strings..
>
> --
> Bring back RegisterTrophy
> https:/
> You received this bug notification because you are a member of OMG!,
> which is subscribed to omg.
>
> Status in OMG!: New
>
> Bug description:
> Of course I understand you're still working on the API, but I must say that
> parsing a trophy object is hard enough, let alone making one, that's why I
> prefer RegisterTrophy over InsertTrophy.
> Well that, and the fact that it is one of the few documented functions.
>
>
>
-- seilo.geekyogre .com
This is me doing some advertisement for my blog http://