[Google Wave APIs] Re: gadget state unavailable in onload handler

2009-11-18 Thread \x00
I just did a test of jQuery(document).ready(function($){...}) vs. gadgets.util.registerOnLoadHandler(function(){...}) jquery loads *after* which is what you want. There is nothing sophisticated about gadgets.util.registerOnLoadHandler But anyway don't take my word for it. -- You received this

[Google Wave APIs] Re: gadget state unavailable in onload handler

2009-11-18 Thread cmdskp
I use state.submitDelta(...) or state.submitValue(...) to update the state to the server. For clearing values, I've set them to null (as recommended in the guides) with those functions. Haven't tried state.reset() I'd expect updateState to trigger more than once as more state is sent. It's

[Google Wave APIs] Re: gadget state unavailable in onload handler

2009-11-17 Thread qMax
This is exactly what i do in current code of http://qmax.academ.org/wave/test.xml But the state is still null before first stateCallback call. On 17 ноя, 00:19, Adam Ness adam.n...@gmail.com wrote: I believe that the document.onload and the standard jQuery $(function(){}) methods don't work

[Google Wave APIs] Re: gadget state unavailable in onload handler

2009-11-17 Thread qMax
Can someone give a live gadget code that gets state in onload handler ? -- 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 APIs] Re: gadget state unavailable in onload handler

2009-11-17 Thread \x00
Sandbox is working. I don't know about the non developer preview. What you describe is very much as if the state is not persistent. Are you getting a persistent state if you were to reload the frame? If not the gadget is not hooked to the wave. It is in developer preview. -- You received this

[Google Wave APIs] Re: gadget state unavailable in onload handler

2009-11-17 Thread \x00
I just set the state. foo should be 'thestate' -- 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 APIs] Re: gadget state unavailable in onload handler

2009-11-17 Thread qMax
of course i see thestate there, but only after state updated, not after gadget loaded do you see it right after opening the wave? On Nov 17, 11:50 pm, \\x00 dt01pqt...@yahoo.com wrote: I just set the state. foo should be 'thestate' -- You received this message because you are subscribed to

[Google Wave APIs] Re: gadget state unavailable in onload handler

2009-11-17 Thread Justin
Anyone else finding their gadgets not working right now? -- 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

Re: [Google Wave APIs] Re: gadget state unavailable in onload handler

2009-11-17 Thread pamela (Google Employee)
The wave-preview library (served from wave-api.appspot.com) was down for approximately 30 minutes this morning, and OpenSocial templates were broken for about 3 hours. These were separate but somewhat related issues. We're looking into tests that will prevent these from happening in the future. -

[Google Wave APIs] Re: gadget state unavailable in onload handler

2009-11-17 Thread Daniel Faust
I'm not exactly sure if I understand your problem correctly. Basically you need two callbacks. One you set up with gadgets.util.registerOnLoadHandler(waveInit); at this point you probably can't even use any of the wave functionality, you don't even have any of your HTML code rendered. Google

[Google Wave APIs] Re: gadget state unavailable in onload handler

2009-11-17 Thread qMax
wave-preview does not work in chrome at all and in firefox it trigger state update twice after loading state.reset() does not trigger state update callback neither with nor without wave-preview On 18 ноя, 07:38, pamela (Google Employee) pamela...@gmail.com wrote: The wave-preview library

[Google Wave APIs] Re: gadget state unavailable in onload handler

2009-11-16 Thread \x00
http://groups.google.com/group/google-wave-api/browse_thread/thread/f5e2cd06e804f8c2 I don't use Just put if (typeof wave != 'undefined' wave.isInWaveContainer()){ wave.setStateCallback(stateUpdated); wave.getState() gadgets.window.adjustHeight(); } at the end of

[Google Wave APIs] Re: gadget state unavailable in onload handler

2009-11-16 Thread qMax
Ok. I believe in magic. But this time i cannot figure out what exact magic is necessary. Here is minimal gadget, containing only debug log and printing state/ mode/viewer/host at various stages: http://qmax.academ.org/wave/test.xml At start of onloadHandler there is: if (wave === undefined ||

[Google Wave APIs] Re: gadget state unavailable in onload handler

2009-11-16 Thread \x00
It is in a wave by specification. The gaget load event basically amounts to sticking scriptgadgets.util.runOnLoadHandlers();/script on the end of your gadget. But there is still some code appended after that. Don't bother specifying head and body tags. Just shove in the scripting and the rest

[Google Wave APIs] Re: gadget state unavailable in onload handler

2009-11-16 Thread \x00
html, head, body tags should be stripped. -- 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