[Google Wave APIs] Re: Child blip to last blip in a wave

2010-01-08 Thread Chris Carlin
I ran into this today too.

Pulling the relevant code out of my project:

def OnRobotAdded(properties, context):
  """Invoked when the robot has been added."""
  ptrblip = context.GetRootWavelet().CreateBlip()
  ptrblip.GetDocument().SetText(INITTEXT)
  context.GetRootWavelet().CreateBlip().SetText("placeholder")

def OnBlipSubmitted(properties, context):
  [...]
  ptrblip.CreateChild().GetDocument().SetText(" ptrblipid %s set\n" %
ptrblipid)

If the line with "placeholder" is there then the child is indented as
expected. If it's not there, then the ptrblip is the last in the wave
so the child blip shows up unindented, just as the first poster
described.

~Chris

On Dec 30 2009, 6:29 pm, "Austin (Google)" 
wrote:
> Sorry, this was actually meant as a response to a related issue,
> though we think it may be the same underlying matter. Can you post
> your code so that we can verify?
>
> On Dec 30, 3:23 pm, "Austin Chau (Google employee)"
>
>
>
>  wrote:
> > 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 <
>
> > anthony.westo...@valpo.edu> 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 google-wave-...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > google-wave-api+unsubscr...@googlegroups.com > >  googlegroups.com>
> > > .
> > > 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 google-wave-...@googlegroups.com.
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en.




[Google Wave APIs] Re: Child blip to last blip in a wave

2009-12-30 Thread Austin (Google)
Sorry, this was actually meant as a response to a related issue,
though we think it may be the same underlying matter. Can you post
your code so that we can verify?

On Dec 30, 3:23 pm, "Austin Chau (Google employee)"
 wrote:
> 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 <
>
>
>
> anthony.westo...@valpo.edu> 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 google-wave-...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-wave-api+unsubscr...@googlegroups.com > googlegroups.com>
> > .
> > 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 google-wave-...@googlegroups.com.
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en.