Open GoogleCodeExporter opened 8 years ago
How many visits per day do your wave-based pages get? Will you be running your
own walkaround instance with your own money? Do you need live updates of these
pages on your blog, or a static view? Are the waves publicly editable?
Original comment by oh...@google.com
on 12 Mar 2012 at 7:39
I just checked the stats and my main wave-based page only gets around 30 views
per month. So maybe creating my own Walkaround instance for running it wouldn't
cost me much money.
This same main wave-based page has public set to read-only, but is open to
collaboration for members of our Google Groups (55 members). However I must
admit that it hasn't been edited for months, and obviously it could be replaced
by a simple static HTML page - But I loved that this "Why should you count on
the Wave Technology?" post was actually inside a wave...
The second most viewed wave-based webpage only gets around 20 views per month,
but this one makes embedding a wave more useful since it's a full-access
publicly editable helpdesk.
Original comment by jeremy.ngl
on 12 Mar 2012 at 10:13
Original comment by oh...@google.com
on 27 Mar 2012 at 7:30
Is there implementation in the wave-protocol project for control public/private
sharing of waves, or will this need to be a new feature that can't reuse code
from the Apache project?
Original comment by internetparty@wetheinter.net
on 2 Apr 2012 at 5:26
The controls for public sharing are probably better discussed in issue 4. I
don't think there is much code for sharing controls in Apache Wave; as far as I
know, the only part that's implemented there is making participant ids like
@example.com (no local part) give anyone in that domain access to the wave.
The trickier parts are indexing (which is very different between walkaround and
Apache Wave) and an intuitive UI for adding such participants (which should be
shared but isn't implemented yet).
I know very little about embedding, what code is needed for it, and whether
Apache Wave has any of that.
Original comment by oh...@google.com
on 2 Apr 2012 at 8:44
Is it possible to access only the right panel of Walkaround (the opened wave)
with a specific URL? Such an URL would allow to simply embed a wave using an
iframe. What I have in mind is an embed solution as simple as
http://www.google.com/webelements/#!/youtube-news
Original comment by jeremy.ngl
on 26 Apr 2012 at 12:51
Oh, actually I've just find out that a right click on a wave title in the
Walkaround inbox allows to copy such an URL
(https://wavereactor.appspot.com/wave?id=538C4V9dlu7rujYV for example). So
using an iframe it should be easy to embed Walkaround waves this way.
Original comment by jeremy.ngl
on 26 Apr 2012 at 1:04
Mmm... The problem is that despite having "public@a.gwave.com" as a
participant, such a Walkaround wave can't be displayed to google account users
that are not already participant in it... Back to step one :-/
Original comment by jeremy.ngl
on 26 Apr 2012 at 1:09
I've just found that this wave-api javascript for embedding wave is still
online:
http://wave-api.appspot.com/public/embed.js
Maybe it can be used as an inspiration source...
Original comment by jeremy.ngl
on 10 Jun 2012 at 10:15
Original issue reported on code.google.com by
jeremy.ngl
on 12 Mar 2012 at 11:11