Office Hours: Nov 11/18 (NOW CLOSED) Welcome to API office hours! *Please top post your question or comment about the robot, gadget, or embed API to make sure we see it. You can do so by replying to this blip.* *A transcript of this wave will be made publicly available. If you don't want to appear in the transcript, delete your blip after getting a response. Be careful not to remove neighboring blips.* *And don't add robots to this wave!* 11:06 am
[email protected]: in gadget, after onload handler triggered, the stateupdated automatically triggers. can we rely it will be triggered after onload completed? and similary, if i call submitDelta inside state callback - will they come in order in another gadget? 11:08 am [email protected]: not necessary right after onload completed. more accurately it should be when wave gadget library is done loading and after your state callback handler is set. That's the point when the initial state callback will be invoked. Yes if you invoke submitDelta, it will generate state callback in other instance of that gadget within the same wave. 11:08 am [email protected]: the order is preserved? if i hadle event triggered by delta A and inside callback submit delta B. 11:09 am [email protected]: yes the order is preserved in respect to the order they are received by the wave server. 11:10 am [email protected]: when subitting state value that is the same as already present, stateupdate is not triggered. is it intended behaviour, can we rely on it? 11:11 am [email protected]: yes. to be safe you can always put logic in your handler to do sanity check berfore performing any action on the update value. But yes, state callback will be triggered when the state value has been changed. 11:12 am [email protected]: thus, it's impossible to do 'dumb' state update just to shake all gadget instances? probably solution is to put shaked=timestamp then 11:13 am [email protected]: yes generating timestamp state would be one way to do this. 11:14 am [email protected]: in wave-api group it was asked, but asker seems missing here. will robots be able to access blips/wavelets out of scope of current event? 11:15 am [email protected]: robot has access to the context of the triggering blip, its immediate parent and child context. Anything other than it has no access to. 11:16 am [email protected]: what if i build an operation manually, using waveid/waveletid/blipid out of context? 11:17 am [email protected]: you can perform action to that blip such as appending, etc. But you still have no context to its actual content, like if you want to parse out any FormElement within the blip. A new mechanism we are working is the active gateway API which will allow a robot to make active request to wave to retrieve full context of any blip. 11:17 am [email protected]: json rpc calls, mentioned in robot wire proto draft? 11:18 am [email protected]: that's just the underlying protocol for all robots-to-wave server communciation. 11:18 am Edited by [email protected]: you mean you are working on making it an api methods? 11:19 am [email protected]: yes the active gateway is a new inovacation mechanism that will be part the new client library. 11:19 am [email protected]: that's cool. thanks : 11:20 am [email protected]: yet another question on robots. "wave conversation model" mentioned operations to manipulate conversation manifest. how they will be implemented? 11:21 am [email protected]: that's something we are still working on. 11:22 am Edited by [email protected]: my quriousity here is in fact that if such operations will be like "move this blip there" they probably should be operational transformable. 11:23 am [email protected]: I was going to say taht it is something that is still under going design and discussion internally. The exact way how conversation model will play out is not confirmed yet. 11:24 am [email protected]: seems there is alot of work on Wave yet :) 11:24 am [email protected]: i wonder why there're no developers here. i missed some of recent OH. is it always so quiet? 11:25 am [email protected]: maybe sleeping :) I just woke up...well an hour ago. Perhaps closer to brunch or lunch time. 11:26 am [email protected]: its about 7pm UTC. is whole google team hosted in Sydney? 11:26 am [email protected]: mostly, Marcel, David and I are in US and a few others. 11:46 am [email protected]: what is time difference between you and downunder team? 11:46 am [email protected]: Sydney is GMT+11 at the moment 11:47 am [email protected]: yea when I was there last week it was 17 hours into the future (relative to US pacific) 11:48 am [email protected]: pacific is UTC-8 ? and australia have summer time? 11:49 am [email protected]: yea i believe CA is GMT-7 or -8 depends on daylight saving. 11:29 am Edited by [email protected]: (continueing offtopic :) what happend to sandbox yesturday? it was not responding several hours. 11:30 am [email protected]: yea some hiccups we were experiencing. That affected my work as well :) Sandbox is a big playground to our development 11:30 am [email protected]: it started to work sonn after Stephanie returned to Sydney. no correlation ? :) 11:31 am [email protected]: haha no, the prod team took care of that issue as quickly as they could. 11:52 am Edited by [email protected]: ok. thanks for chat, Austin :) 11:52 am [email protected]: likewise, good talking with you today :) 11:33 am Edited by [email protected]: oh. one more. what does feature "wave-preview" give, (besides not working in Chrome and triggering more events in firefox) ? anything other then gadget mode? 11:33 am [email protected]: are you asking what's the difference between wave preview vs sandbox? 11:34 am [email protected]: nope. that gadget xml <Require feature="wave-preview"/> 11:36 am [email protected]: oh i see. That basically does automatically import of the wave gadget library so you don't have to script include it in your javascript part. 11:37 am [email protected]: i guess <Require feature="wave"/> does the same. i'm about what difference b/ween these features. 11:38 am [email protected]: Vadim is not around, he is the gadget man. But from what I know wave vs wave-preview in require feature is that wave-preview is the latest push of hte wave gadget library while "wave" is the stable push. Using "wave-preview" would be more responsive to latest features. 11:39 am Edited by [email protected]: nobody knows what are those new features? 11:40 am [email protected]: right now they are essentially the same. But we create the differentiation for future tolerance of the gadget developers. 11:03 am -- 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=.
