<<
used root_blip.CreateChild() and this works programmatically but (this
is where the thread title comes from) the first child is placed at the
same indentation level as the root_blip and subsequent blips are
indented one level between it and the root_blip (the second potential
bug I've found).>>

I'm having this same problem.  Is there any way to control indentation from
the JAVA robot API (i.e. create an indented blip reply instead of just a
blip reply) ?

thx in advance!

Jd

d3developer.com | twitter.com/fractastical | twitter.com/jdietz


On Wed, Nov 4, 2009 at 4:02 AM, Patrick <[email protected]> wrote:

>
> Howdy, folks!
>
> tl;dr - Are there any best practices for managing concurrently related
> blips via the robot that created them?
>
> I'm trying to wrap my head around this scenario and I can't tell if
> I'm finding bugs in the API or merely misunderstanding it. Before I
> get to those I'll setup a little background on the robot.
>
> I'm making a Wave interface for my character profile/sketch app. The
> robot takes the wavelet's title and uses it as the profile's name. It
> then breaks each element (age, appearance, etc.) into a separate blip
> and records the section in the first line of the blip (similar to the
> wavelet title annotation). Edits made are saved into the database.
>
> Displaying and editing works fine but deleting blips (specifically so
> the user can refresh the wave to pull changes made on the main site
> without being forced to create a new wave) has been the death of me.
>
> At first I would create blips via wavelet.CreateBlip() and then delete
> the blips when the wavelet title changed (i.e. the user wanted to load
> a new profile) and that would work so long as I didn't create any new
> blips (this is one of the bugs I think I found) if I did then nothing
> would happen.
>
> My second attempt is to use buttons so the user has to manually clear
> the blips, but the context that gets passed doesn't include the blips
> created through the wavelet (at least not that I can find) so then I
> used root_blip.CreateChild() and this works programmatically but (this
> is where the thread title comes from) the first child is placed at the
> same indentation level as the root_blip and subsequent blips are
> indented one level between it and the root_blip (the second potential
> bug I've found).
>
> Additionally, I tried inline blips and that works too but each blip
> gets it's own speech bubble and deleting them leaves a large empty
> space. I just thought to try an inline blip with children but it's
> late and Wave isn't cooperating. If deleting the parent blip deletes
> the children this may be a viable option. But I'd still like some
> feedback =D
>
> Optimally I'd like to store a list of the blipID's in a data document
> and never have to delete and recreate blips, but the blip IDs the
> Python API creates are just placeholder IDs ("TBD_googlewave...").
>
> Thanks for any help you can offer!
> ~ Patrick
>
> --~--~---------~--~----~------------~-------~--~----~
> 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.

Reply via email to