[Google Wave APIs] Re: Embed API tutorial example broken on latest Chrome?
ading: "https://wave.google.com/a/ wavesandbox.com/wfe/channel?gsessionid=osHIr4JU_fAC- NO8hFxd_g&VER=6&SID=DCF8C823EF9A6083&RID=28711&AID=0&zx=y0rm71- ozbcx7&t=1". 24Unsafe JavaScript attempt to access frame with URL file:///Users/bjnortier/Desktop/embed.html from frame with URL https://wave.google.com/a/wavesandbox.com/?client.type=embedded&parent=file%3A///Users/bjnortier/Desktop/embed.html&wave_id=wavesandbox.com!w%2BDTGTb4IaA. Domains, protocols and ports must match. wave.google.com/a/wavesandbox.com/?client.type=embedded&parent=file %3A///Users/bjnortier/Desktop/embed.html&wave_id=wavesandbox.com!w %2BDTGTb4IaA:57XHR finished loading: "https://wave.google.com/a/ wavesandbox.com/wfe/channel?gsessionid=osHIr4JU_fAC- NO8hFxd_g&VER=6&SID=DCF8C823EF9A6083&RID=28712&AID=9&zx=3ybdnq-4gj2sy&t=1". 10Unsafe JavaScript attempt to access frame with URL file:///Users/bjnortier/Desktop/embed.html from frame with URL https://wave.google.com/a/wavesandbox.com/?client.type=embedded&parent=file%3A///Users/bjnortier/Desktop/embed.html&wave_id=wavesandbox.com!w%2BDTGTb4IaA. Domains, protocols and ports must match. wave.google.com/a/wavesandbox.com/?client.type=embedded&parent=file %3A///Users/bjnortier/Desktop/embed.html&wave_id=wavesandbox.com!w %2BDTGTb4IaA:57XHR finished loading: "https://wave.google.com/a/ wavesandbox.com/wfe/channel?gsessionid=osHIr4JU_fAC- NO8hFxd_g&VER=6&RID=rpc&SID=DCF8C823EF9A6083&CI=0&AID=0&TYPE=xmlhttp&zx=cik0pf- xl8rz7&t=1". On Feb 8, 10:58 pm, "pamela (Google Employee)" wrote: > It is working for my Chrome, 4.0.249.43 on Linux. > > Which example are you looking at? > > We had an issue, but as far as I'm aware, it was resolved. > > - pamela > > > > On Mon, Feb 8, 2010 at 9:50 PM, bjnort...@gmail.com > wrote: > > I'm getting this cross-domain error today in both Safari and Chrome > > (Chrome version 4.0.249.49 (35163) beta, Safari version 4.0.4 > > (6531.21.10)) > > > Has this been unsolved since Dec 14/15? > > > On Dec 15 2009, 8:46 pm, FrankBehrens wrote: > >> I'm in the club, with Chrome 4.0.249.30 on OSX Snow Leopard, Frank > > > -- > > 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 > > athttp://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 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=en.
[Google Wave APIs] Wave Embed API and Contact management
Hi Is there an example of how the profile and contact management works in the embed API? I'm referring to specifically to methods: provideProfiles(profiles:Object) setContactProvider(providerFunc:Function) setContacts(contacts:Array.) I've tried different approaches, but either nothing happens or errors are generated. Thanks! Benjamin -- 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=en.
[Google Wave APIs] Re: Embed API tutorial example broken on latest Chrome?
I'm getting this cross-domain error today in both Safari and Chrome (Chrome version 4.0.249.49 (35163) beta, Safari version 4.0.4 (6531.21.10)) Has this been unsolved since Dec 14/15? On Dec 15 2009, 8:46 pm, FrankBehrens wrote: > I'm in the club, with Chrome 4.0.249.30 on OSX Snow Leopard, Frank -- 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=en.
[Google Wave APIs] Re: Google Wave Gadget persistence layer
Pamela is right, it's easy to serialise/deserialize JSON strings, the
browsers that support Wave have native JSON support.
Simply use JSON.parse(jsonString) and JSON.stringify(object)
As Davis says, it's probably a good idea to store the nodes and
structure of the tree separately to avoid conflicts. Since a tree is a
simplified form of a graph, you can store it like a lot of graph
implementations do, as a set of vertices and a set of edges. The one
user can edit the structure and another the fields of a node and avoid
*some* conflicts
Cheers
Benjamin
On Dec 9, 5:20 pm, "Jiang, Guoqian, Ph.D."
wrote:
> Thank you very much for your suggestion and this is very helpful,
>
> I think DataBlip is a great idea. Let us assume that each node of a tree
> structure is represented as a wave blip and the entire tree will be a
> wavelet. We just need a UI rendering layer (say a Gadget) that can
> access the data blip. The curation of the tree will just mimic the blip
> creating, editing or deleting. In this way, we do not need worry about
> the conflicts among collaborators as we can leverage built-in wave
> feature.
>
> I think the Google Wave API can transform a tree structure into a
> wavelet and its blips but I am not sure if there is a way that a UI
> layer in a Gadget can access and communicate with the blips,
>
> Any idea?
>
> Thanks,
>
> -Guoqian
>
>
>
> From: google-wave-api@googlegroups.com
> [mailto:google-wave-...@googlegroups.com] On Behalf Of David Nesting
> Sent: Wednesday, December 09, 2009 10:31 AM
> To: google-wave-api@googlegroups.com
> Subject: Re: [Google Wave APIs] Google Wave Gadget persistence layer
>
> On Tue, Dec 8, 2009 at 10:36 AM, Jiang, Guoqian, Ph.D.
>
> wrote:
>
> My use case is that I want to reprensent a tree structure in a
> google wave gadget and a group will work collaboratively on curating the
> tree structure e.g. editing a node, adding a sub node or deleting a
> node.
>
> Assuming the tree structure is based on a json object, my
> question is whether there is a persistence layer API to store and
> restore a json object,
>
> You can serialize the JSON to a text string, and store that text string,
> as Pamela says, but I would not recommend serializing the entire tree in
> this way. If two people are editing different parts of the tree at the
> same time, one person's edits could revert the edits done by the other
> person, if they are made close together. If you can come up with a
> scheme to represent your tree in as granular a manner as possible, that
> would work best, possibly by doing something like:
>
> ...submitDelta({'tree.0.1.0'}, value) # Sets the first child of the
> second child of the first child of the tree
>
> By doing this, you're reinventing some of what Wave automatically does
> for blip content. It's a shame there isn't a way to better leverage
> that (e.g. a DataBlip that you control the mutations to and presentation
> of).
>
> David
>
> --
>
> 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
> athttp://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 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=en.
[Google Wave APIs] Re: Dynamic height gadget not always resizing
For anyone else reading this, I've managed to fix it, it was my mistake. I started from the button counter example, so the main content div had an explicit height specified: The different behaviour in FF and Webkit confused me a bit. I.e. if you're having height problems, make sure there is no "height" style specified Cheers Benajmin On Nov 28, 9:46 am, "bjnort...@gmail.com" wrote: > Hi > > I have a gadget in development that uses and gadgets.window.adjustHeight(); > > The dynamic resizing works in Chrome (Win) and Safari (Mac), but not > in Firefox (3.5.5 on Mac and Win) > > You can find it here:http://www.dayfindr.com/dayfindr_wave_test.xml > > Any ideas? > > Thanks! > Benjamin > > On Nov 15, 3:40 pm, "\\x00" wrote: > > > The problem is no more, at least in firefox 3.5.5 -- 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=en.
[Google Wave APIs] Re: Dynamic height gadget not always resizing
Hi I have a gadget in development that uses and gadgets.window.adjustHeight(); The dynamic resizing works in Chrome (Win) and Safari (Mac), but not in Firefox (3.5.5 on Mac and Win) You can find it here: http://www.dayfindr.com/dayfindr_wave_test.xml Any ideas? Thanks! Benjamin On Nov 15, 3:40 pm, "\\x00" wrote: > The problem is no more, at least in firefox 3.5.5 -- 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=en.
