It is true that the API does not convey the true conversation model of the document, and this leads to some confusion and inconsistencies
We are looking into the sudden change in the API that was reported, however, to see what changed on our side. On Tue, Jan 12, 2010 at 9:31 PM, chiang <[email protected]> wrote: > Looking at Google Wave Conversation Model spec, it seems that the > blips are organised around a conversation, rather than blip itself > (e.g. root blip). So it may be intentional that blips are structured > to have only 2 levels. But why 2 levels and not 1 level, could be to > do with easier manipulation of blips, say to copy from one wave to > another, yet keep the separations? > > On Jan 11, 7:04 pm, boaz sapir <[email protected]> wrote: >> I have exactly the same problem. >> For blips which are more than one level bellow the root, the getter >> methods return wrong (empty) results. For example getDocument().getText >> () returns an empty string, getChildren() returns an empty list (so it >> is not possible to traverse the tree beyond the first level). >> >> On Jan 9, 2:46 pm, Thomas Jungblut <[email protected]> >> wrote: >> >> > Okay I got a closer look and it seems, that the getter methods do not >> > return the content they should. No problem with getChildren(). >> >> > I opened up issue 615 and restored the old working version. > > -- > 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. > > > >
-- 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.
