Just started working for me in all instances. Cool!

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


On Thu, Apr 8, 2010 at 12:44 AM, Joel Dietz <jdi...@gmail.com> wrote:

> Can someone verify that fetchWavelet is working for them w/ the JAVA API?
>
> I'd like to be able to add / edit / delete blips in the fetched wavelet.
>
> I also wouldn't mind doing this with blindWavelet if anyone has that
> working.
>
>
> d3developer.com | twitter.com/fractastical | twitter.com/jdietz
>
>
> On Wed, Apr 7, 2010 at 9:43 PM, Joel Dietz <jdi...@gmail.com> wrote:
>
>> now I just get "java.io.IOException: internalError: Internal error"
>> whenever I try to fetch a wavelet.
>>
>>
>>
>>
>> d3developer.com | twitter.com/fractastical | twitter.com/jdietz
>>
>>
>> On Wed, Apr 7, 2010 at 4:21 AM, Kapil Neurgaonkar <caps...@gmail.com>wrote:
>>
>>> Hi Jd,
>>>
>>> Try using fetchWavalet instead of blindWavalet.
>>>
>>> Regards,
>>> Kapil Neurgaonkar
>>>
>>>
>>> On Wed, Apr 7, 2010 at 12:52 AM, Joel Dietz <jdi...@gmail.com> wrote:
>>>
>>>> Suppose I wanted to create a new wavelet on a button click and then
>>>> append a link to the new wavelet from the blip which had the button.
>>>>
>>>> Since we can't assign the Id until after the Wavelet is created, I am
>>>> using the onWaveletCreated event handler.
>>>>
>>>> I can sucessfully initialize the old wavelet like so:
>>>>
>>>>         Wavelet originatingWavelet =
>>>> this.blindWavelet(oldWaveId,oldWaveletId);
>>>>
>>>> Then try to load the blips:
>>>>
>>>>         Map<String,Blip> blipsFromOriginatingWavelet =
>>>> originatingWavelet.getBlips();
>>>>         LOG.log(Level.WARNING, "This many blips:" +
>>>> blipsFromOriginatingWavelet.size());
>>>>
>>>> Unfortunately I always get a size of 0.
>>>>
>>>> This also does not work:
>>>>
>>>>      Blip originatingBlip =
>>>> originatingWavelet.getBlip(originatingBlipID)
>>>>
>>>> originatingBlip is always null.
>>>>
>>>> Is there a workaround?
>>>>
>>>> Jd
>>>>
>>>> d3developer.com | twitter.com/fractastical | twitter.com/jdietz
>>>>
>>>>
>>>> On Tue, Apr 6, 2010 at 3:12 PM, Joel Dietz <jdi...@gmail.com> wrote:
>>>>
>>>>> Well, you can also just delete the rootBlip and replace it.
>>>>>
>>>>> Jd
>>>>>
>>>>> d3developer.com | twitter.com/fractastical | twitter.com/jdietz
>>>>>
>>>>>
>>>>> On Mon, Apr 5, 2010 at 8:47 PM, Joel Dietz <jdi...@gmail.com> wrote:
>>>>>
>>>>>> I notice that when you start a wave, the first blip is in edit mode
>>>>>> (i.e.  you have to click on the "done" button  ). Even if you add a robot
>>>>>> which adds things to the rootblip, this blip remains in edit mode. One
>>>>>> problem with this is that if a robot adds a form element (e.g. a button) 
>>>>>> to
>>>>>> the rootblip (which would seem the obvious place), the participant can't 
>>>>>> use
>>>>>> the form until they click the "done" button.
>>>>>>
>>>>>> Here's an example. This code:
>>>>>>
>>>>>>   public void onWaveletSelfAdded(WaveletSelfAddedEvent event) {
>>>>>>
>>>>>>       Wavelet wavelet = event.getWavelet();
>>>>>>       wavelet.setTitle("Test Robot 2");
>>>>>>       Blip rootblip = wavelet.getRootBlip();
>>>>>>       rootblip.append(new FormElement(ElementType.RADIO_BUTTON_GROUP,
>>>>>> "rb_group"));
>>>>>>       rootblip.append(new FormElement(ElementType.LABEL, "Item1",
>>>>>> "Item 1"));
>>>>>>       rootblip.append(new FormElement(ElementType.RADIO_BUTTON,
>>>>>> "Item1", "rb_group"));
>>>>>>       rootblip.append(new FormElement(ElementType.LABEL, "Item2",
>>>>>> "Item 2"));
>>>>>>       rootblip.append(new FormElement(ElementType.RADIO_BUTTON,
>>>>>> "Item2", "rb_group"));
>>>>>>       rootblip.append(new FormElement(ElementType.BUTTON,
>>>>>> "select_button", "Boy would I like to be able to click this button right
>>>>>> now"));
>>>>>>
>>>>>> }
>>>>>>
>>>>>> Produces the attachment.
>>>>>>
>>>>>> Is there a way for a robot to toggle edit mode for a blip?
>>>>>>
>>>>>> The only possible work around I can think of is to remove the
>>>>>> participant from the wave and then add them in again (although I haven't
>>>>>> tested this).
>>>>>>
>>>>>>
>>>>>> Jd
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>  --
>>>> 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<google-wave-api%2bunsubscr...@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<google-wave-api%2bunsubscr...@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.

Reply via email to