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 correctly in wave due to the odd
> loading ordrer. Instead, use
>
> function init() {
> if( typeof wave!='undefined' && wave.isInWaveContainer() ) {
> // do your wave-specific initialization here
> }}
>
> gadgets.util.registerOnLoadHandler(init);
>
>
>
> On Mon, Nov 16, 2009 at 8:07 AM, qMax <qwigly...@gmail.com> wrote:
> > 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 || ! wave.isInWaveContainer()) {
> > alert('I wanna be in a wave!');
> > return;
> > }
>
> > Here is instance of it:
> >https://wave.google.com/a/wavesandbox.com/#restored:wave:wavesandbox....
>
> > After gadget loaded it shows that state/viewer/host/mode are null (but
> > not undefined).
--
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=.
