Yes, it made me really happy to see someone else on this forum :)

—Zachary “Gamer_Z.” Yaro
On Jan 17, 2013 2:48 AM, "Serj" <[email protected]> wrote:

> I glad that I was able to explain and that someone is still trying to make
> interesting opensocial gadgets
>
> On Wednesday, January 16, 2013 11:09:45 PM UTC+7, Zachary Yaro wrote:
>>
>> Ah, I suppose that does make sense.  Thank you for clarifying that.
>>
>> —Zachary “Gamer_Z.” Yaro
>> On Jan 16, 2013 5:37 AM, "Serj" <[email protected]> wrote:
>>
>>> callback to gadgets.util.**registerOnLoadHandler is event that notify that 
>>> gadget infrastructure and it's container is ready. thus you can set 
>>> handlers to perform communication with parent window: set gadget's height, 
>>> get stored state
>>>
>>> gadget wave api is also using that handler to do it's internal init:
>>>
>>>
>>> /**
>>>  * Internal initialization.
>>>  */
>>> wave.internalInit_ = function() {
>>>   wave.checkWaveContainer_();
>>>   if (wave.isInWaveContainer()) {
>>>     gadgets.rpc.register('wave_**participants', 
>>> wave.receiveWaveParticipants_)**;
>>>     gadgets.rpc.register('wave_**gadget_state', wave.receiveState_);
>>>     gadgets.rpc.register('wave_**state_delta', wave.receiveStateDelta_);
>>>     gadgets.rpc.register(
>>>         'wave_private_gadget_state', wave.receivePrivateState_);
>>>     gadgets.rpc.register(
>>>         'wave_private_state_delta', wave.receivePrivateStateDelta_**);
>>>     gadgets.rpc.register('wave_**gadget_mode', wave.receiveMode_);
>>>     gadgets.rpc.call(null, 'wave_enable', null, '1.0');
>>>   }
>>> };
>>>
>>> /**
>>>  * Sets up the wave gadget variables and callbacks.
>>>  */
>>> (wave.init_ = function() {
>>>   if (window['gadgets']) {
>>>     gadgets.util.**registerOnLoadHandler(**function() {
>>>       wave.internalInit_();
>>>     });
>>>   }
>>> })();
>>>
>>>
>>> at that time wave api initialize state object but it's null and then it 
>>> registers to opensocial rpc listeners which will transfer state deltas, 
>>> participants, etc. and only after that it will be able to receive any data
>>>
>>>
>>> In my practice and according to wave api's asynchronous model you shouldn't 
>>> perform state actions until setStateCallback is fired for state and 
>>> setParticipantCallback for participants
>>>
>>>
>>> On Wednesday, January 16, 2013 4:59:36 PM UTC+7, Zachary Yaro wrote:
>>>>
>>>> Why then would it happen in the gadgets.util.**registerOnLoadHan**dler
>>>> callback?  The impression I got is that should not fire until the gadget
>>>> has been fully loaded.
>>>>
>>>> —Zachary “Gamer_Z.” Yaro
>>>>
>>>>
>>>> On 16 January 2013 02:42, Serj <[email protected]> wrote:
>>>>
>>>>> I don't think that this behavior is bug. This just means that at that
>>>>> moment gadget haven't receive it's state yet.
>>>>>
>>>>>
>>>>> On Wednesday, January 16, 2013 1:43:10 PM UTC+7, Zachary Yaro wrote:
>>>>>>
>>>>>> Funny enough, years later, I am now seeing this bug for the first
>>>>>> time (in Chrome, in both Rizzoma and Wave-In-A-Box).  I know it was a 
>>>>>> while
>>>>>> ago, but did you ever find a solution?
>>>>>>
>>>>>> —Zachary “Gamer_Z.” Yaro
>>>>>>
>>>>>  --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Google Wave API" group.
>>>>> To view this discussion on the web visit https://groups.google.com/d/*
>>>>> *ms**g/google-wave-api/-/**sYVnqUVNzO**sJ<https://groups.google.com/d/msg/google-wave-api/-/sYVnqUVNzOsJ>
>>>>> .
>>>>>
>>>>> To post to this group, send email to google-...@googlegroups.**com.
>>>>> To unsubscribe from this group, send email to google-wave-a...@**
>>>>> googlegroups.**com.
>>>>> For more options, visit this group at http://groups.google.com/**group
>>>>> **/google-wave-api?hl=en<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 view this discussion on the web visit https://groups.google.com/d/**
>>> msg/google-wave-api/-/**XRSPoc0WZCsJ<https://groups.google.com/d/msg/google-wave-api/-/XRSPoc0WZCsJ>
>>> .
>>> To post to this group, send email to google-...@googlegroups.**com.
>>> To unsubscribe from this group, send email to google-wave-a...@**
>>> googlegroups.com.
>>> For more options, visit this group at http://groups.google.com/**
>>> group/google-wave-api?hl=en<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 view this discussion on the web visit
> https://groups.google.com/d/msg/google-wave-api/-/RLatXuwAcmsJ.
> 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.

Reply via email to