Hi Pamela, Well, not yet investigated because the JSON library does not work, but I already have the solution, instead of using JSON.stringify I use gadgets.json.stringify.
a good example: http://www.processwave.org/2009/12/invity-behind-scenes.html The problem is solved for me. Thanks for your time! 2009/12/13 Matias Molinas <[email protected]>: > Hi Pamela, thanks. > > First of all apologies for not detecting more specifically the problem before. > It is easier to complain rather than work :-) > I think now that I know I can help. > In the url: > > http://www.bubaproject.com/test.xml > > you can see a test Gadget, it includes the library: > > http://www.bubaproject.com/js/json2.js > > It is originally from JSON.org and has been modified by the author of > jqgrid (Tony Tomov) for jqgrid. > > This library makes that while Wave states work properly in Firefox 3 > fail in Firefox 3.5 and Chrome. > > I will try to avoid using this library, but it would be good to know > the reason for the failure. > > Thanks again, Matias > > 2009/12/13 pamela (Google Employee) <[email protected]>: >> Hi Matias - Please link to a simplified version of the gadget code so that >> we can see what you're doing. >> -pamela >> On Fri, Dec 11, 2009 at 6:05 PM, Matias Molinas <[email protected]> >> wrote: >>> >>> Works for me, but only in firefox 3 :-( . I suspect that this is a >>> problem initializing the state, but I can not even identify. >>> Thank you very much! >>> >>> 2009/12/10 dirtside <[email protected]>: >>> > I actually figured out that using submitValue() instead of submitDelta >>> > () seems to work properly for whatever key. Not sure why, but at least >>> > my gadget works now :-) >>> > >>> > On Dec 9, 3:50 pm, dirtside <[email protected]> wrote: >>> >> I'm developing a Wave gadget. It sets a callback function for >>> >> setStateCallback() and setParticipantCallback(), which apparently gets >>> >> called immediately, three times (I'm guessing once for the >>> >> setStateCallback and once each for the two participants). >>> >> >>> >> The callback function (updateDisplay) calls another internal function >>> >> which calls wave.getState(). Well, the first time it calls >>> >> wave.getState() I get a JS error saying that wave.getState() is null, >>> >> which I guess means it hasn't been initialized yet. So my question is, >>> >> why is wave calling the callbacks before the wave object is fully >>> >> initialized, or am I doing something wrong? >>> > >>> > -- >>> > >>> > 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. >>> > >>> > >>> > >>> >>> -- >>> >>> 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. >>> >>> >> >> -- >> >> 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. >> > -- 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.
