The visual really helped, I wasn't thinking properly so I apologize for that and thanks for your clarification on the subject. So from what I understand now, how about this: if we can export the whole conversation, to a file or something, then the robot can stri[p off everything besides the root blip and then sync it back may be
-- Regards, Vikram Dhillon On Sunday 22 November 2009 08:15:13 pm Olreich wrote: > GetChildren on the root blip will get the first blip. Unfortunately, > because the root blip has to be the blip submitted to have that > function work, it's limited. In fact, it's even more limited because > of the fact that the root blips child's child is null in the current > version of the API. (an annoying quirk) > > Visual: > > r--->Blip 1 > ^--->Blip 2 > ^--->Blip A > ^--->Blip B > ^--->Blip C > ^--->Blip 3 > ^--->Blip 4 > r = root > ^ = child of last indentation (Blips A and 3 are both children of Blip > 2) > > So in that context, let's say the Event happened on Blip 1. Well, it's > the root blip, so it has no parents, but it does have a child (Blip > 2). getChildren will return a list with Blip 2 in it. But, if one > get's Blip 2 (in any fashion) because it is not the Blip that was > acted upon, you will get null for both it's parent (Blip 1) and it's > children (Blips A and 3). > > The reason for this is that a bot works in the same way that a human > participant does, in that every update has just the information about > the one blip, instead of all the blips, to reduce bandwidth. > > Something that just came to me would be, upon the bot being added, it > should have to be able to see ALL the blips (like when you get a new > wave and having the entire conversation load, but only having small > parts change after that). Thus, it should be able to make a full list > of the blips. Then, when a blip event happens, and the blip is not on > the list you made, then the Bot adds it to the list. I'm not sure if > this is the functionality, but it should be. And if it's not when I > test it, I'll be adding a bug, because the Robot is not a full > participant unless it is able to read the entire conversation right > off the bat. > > -- > > 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=. > -- 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=.
