Hey, any of you guys still interested in this kind of usage for Wave?
I don't have sandbox access yet but I've read through most of the
stuff out there and this is what I understand could work:
For the sake of example let's say I want to build a blogging service
(I don't really). I create a small App Engine application that will
take care of the publishing side of it. This app will...
1. take the request of the visitor and make it into a wave ID
2. use the Embed API to render the wave for that ID
3. render a nice theme with the post embeded in it
provided
pub...@a.gwave.com and read-only are implemented at some
point as promised, this should work well, right?
For all this to happen though, the app needs to get some data
beforehand that allows it to match the slug in the request with the
wave ID and determine that wave belongs to certain blog which in turn
belongs to certain user.
So we build a robot that a user will add to every wave he wants to
make into a blog post. This robot will communicate all this necessary
data to the app: Creator ID, participants IDs, Wave ID, title,
creation time, updates, status (published or not), etc.
Does this seems like a sound approach to you? There are tons of
questions obviously...
¿Can you handle blog creation/configuration from within wave with wave
forms displayed by the robot...? (I have never seen wave except in
videos, so this may be a dumb question... but I'm thinking somewhat
like Twave)
¿How would you create views that render multiple post titles to make
something like a home page? ¿How many embeds are acceptable before it
starts to slow down the page?
¿Is it possible to have the robot app and the publishing app access
the same data in App Engine?
¿How much formatting can you apply to embedded waves?
Anyway, I won't go on or nobody will reply :-) I'd love to hear any
comments...