This is not possible with the API's current representation of parent and children blips. In order for you to iterate over the blips in the "conversation" order, the API needs to expose the conversation model. You can read more about the model in the Wave Protocol specification:
http://www.waveprotocol.org/draft-protocol-specs/wave-conversation-model (particularly "Conversation Manifest Document") We do plan to expose the conversation model in the API at a later date, so please stay tuned to the blog and forum for updates. Austin On Wed, Dec 16, 2009 at 10:11 AM, Anthony Westover < [email protected]> wrote: > I have noticed that when creating a child of the bottommost blip in a > wave, the child is not indented, but any subsequent children are(since > the parent blip is no longer the last blip, the first child is) Just a > small thing, but it seems really out of place, there is no way to tell > if the last blip is a reply directly to a previous blip, or a brand > new blip appended to the end of the wave. > Right now it is: > > Parent Blip > Second Child > Third Child > nth Child > First Child > New Blip > > instead of > > Parent > First Child > Second Child > nth Child > New Blip > > -- > > You received this message because you are subscribed to the Google Groups > "Google Wave API" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-wave-api%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-wave-api?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
