Hi Passiday- It should be entirely possible to do what you want to do, based on that description, and I think it's a great idea. I wrote a blog post about Joomla + Google Wave a few months back (http://otherfancystuff.blogspot.com/2009/10/joomla-google-wave-possibilities.html), and I mentioned this sort of Wave usage.
I would recommend taking a look at Exporty-bot: http://wave-samples-gallery.appspot.com/about_app?app_id=75018 It exports the root blip of Waves as HTML into a datastore, and remembers who the participants are, so that it can authenticate people who can view the wave. A modified version of Exporty-bot is used to power our Wave APIs FAQ: http://wave-api-faq.appspot.com The modified version takes care of table of contents and special documentation formatting, but is quite similar code. You can use a modified version of exporty to export the waves to serve statically, and use the embed API on your site to let admins edit waves. To extract more structured information, you could have the robot look for particular syntax, or you could put a gadget in the waves for that info and have the robot extract the state keys. - pamela On Fri, Jan 8, 2010 at 10:05 AM, Passiday <passi...@gmail.com> wrote: > Hello, > > I'd like to use the Wave to replace our existing clunky self-made CMS > system for the internet shop, at least for the large text descriptions > for starts. > > I guess that would be something like this: > 1. Create a separate wave for each product, get it's id, save in the > database. Perhaps one user should be added to it, so that someone > could edit it later. It's a bit unclear how to keep the wave from > dying, it feels that wave needs at least one user to follow it, kind > of fragile for mission-critical product database. > 2. Whenever user with editing rights opens the website in edit mode, > she can edit the product description on-site (wave editing embedded > using API). > > The question is, how to extract pure html of the main from the wave > (stripped from all non-first level blips) at the server-side, to > present the site to normal users who'd be just browsing the site, not > with intention to edit it. > > I am just making my first steps in the Wave world, so my > contemplations and questions might be silly. But I'd guess that using > the Wave as CMS is kind of the very first thing that comes in one's > mind. What could be better than having an intelligent rich-text > editing tool that allows collaborative development both on-site and in > Wave home? > > The next thing would be to add also other field editing to the wave, > ie, altering the product name in seperate edit box and then being able > to extract it from wave somehow. Seeing how I can edit different > fields in my user profile within a wave, I guess that's totally > possible, by developing a smart extension. But what's not clear to me > right now is, how the data from wave can be extracted by some bot, so > that it can be saved in a database for static retrieval later. > > Passiday > > -- > 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. > > > >
-- 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.
