On Dec 4, 1:37 pm, David Nesting <[email protected]> wrote: > The annotations are annotating the text. If you replace the text, the > annotations serve no purpose, and have nowhere to point, so the only > reasonable thing to do is drop them. If you're reading the text, doing some > manipulation of the text (but keeping it mostly intact), and then replacing > the entire text of the blip with a new version, consider making your edits > more targeted and using the mutators supplied by the wave API. With the > read/mutate/replace approach, what happens when someone is making an edit to > the same block of text? Wave is normally great with concurrent edits, but > not when those edits involve replacing the entire content over and over > again with a slightly different version. > > David
My robot only responds to BLIP_SUBMITTED events so I am not so sure that is going to be too much of a problem, but I see your point. Right now I am going with the idea of looping over the submitted blip text and running a match loop and then using the TextView.replace() methodwith the range supplied form the string. Does this sound like a better approach to you? -- 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.
