I guess the closest we are getting towards this dream is with the Code Snippet Gadget. Search for a wave with the tags 'code', 'snippet' and you shall find it. The wave ID is googlewave.com+252By2RZbMagM
Yours, Luciano. On 18 nov, 23:57, Olreich <[email protected]> wrote: > Or, have the live update only happen when the HTML is valid (the > entire web could be improved by forcing validation xD). Though that > might cause some SERIOUS overhead for the robot. > > On Nov 18, 9:52 pm, cmdskp <[email protected]> wrote: > > > > > And have some nice DOCUMENT_CHANGED tag and attribute auto-completing > > done by the robot. =) > > > The main problem is nested content and how when one user is maybe > > working on one section of the IFrame it suddenly jumps around because > > another person has inserted an incomplete tag above - could be > > disturbing if more than two people join in...but still well worth > > doing! > > > Perhaps offer a disable live-update tick-box to freeze the gadget for > > that participant's view of it. That would let one person finish off > > adding content without getting rapid changes appearing because someone > > else is modifying the layout. They can then untick it and see how > > their content appears... > > > On Nov 19, 1:00 am, Olreich <[email protected]> wrote: > > > > Great idea. I think the best method of editing would be to have a HTML/ > > > JS/CSS syntax highlighter (Robot). A gadget (essentially just an > > > iframe pointing at a temp-website with the data in it) showing a > > > rendered version of the web-page based upon the current code. This > > > will enable the web-page code to be highly accessible for content > > > editing and collaboration, but still remain visible in the wave. A > > > content manager of sorts so as to develop an entire website. > > > > Another possibility would be to render the webpage in a second blip, > > > but how one would reference outside files I cannot see immediately. > > > > One could also have a gadget be the editing window, but that's just no > > > fun, and doesn't use nearly enough AppEngine resources to be fun, and > > > doesn't allow for super-easy live-editing. > > > > On Nov 18, 5:42 pm, Jason Livesay <[email protected]> wrote: > > > > > I have also thought about web page editing as a wave gadget/robot > > > > combination. I think you might want not only a robot but also a gadget > > > > to > > > > add more wysiwyg functionality to the editing, like controls for editing > > > > tables etc. > > > > > I think you have a good idea. Basically, any activity that involves > > > > multiple individuals collaborating could benefit from a shared > > > > environment > > > > like the one presented in a wave and I think we should not assume that > > > > waves > > > > can only handle very simple gadgets/robots or small datasets. I think > > > > we > > > > should try to stretch it as far as it will go. > > > > > On Wed, Nov 18, 2009 at 6:28 AM, Johnny Nilsson > > > > <[email protected]>wrote: > > > > > > Hi > > > > > > Im not quite sure if I am at the right spot to share an idea I got > > > > > from watching the presentation of Google wave presentation on youtube. > > > > > > What about building a Google Wave website editor? - a Webbie! :p > > > > > > The thought I had behind this was that you should be able to use the > > > > > wave interface as an ftp-server aswell. > > > > > > Let's say you are a team of 3 persons working on a webpage. > > > > > The first person logs in to the ftp-account through the Wave > > > > > interface, and opens a file that automatically is opened as a wave. > > > > > The wave is split so you can work both graphically and by code. > > > > > > Person no. 1 starts to do some work and during this time person no. 2 > > > > > logs in to the ftp to do some more work. > > > > > > When person no 2 logs on to the ftp-server, s/he is added to the group > > > > > of active users that can work on the wave. > > > > > (perhaps in a Wave/subwave system) > > > > > Person no. 2 decides to do some work on the same html-page as person > > > > > no.1 is working on. You can view the work the other person is doing. > > > > > Help with it, roll back with the playback-function. > > > > > > Once you decide that you have done enough work, you press the publish- > > > > > button. (perhaps even automatic live update on the webpage is to > > > > > prefer in some case - let this be optional) > > > > > > I'm thinking in terms of a robot, just as Bloggie, but without the > > > > > feature that ANYONE can comment on the public webpage, as they did on > > > > > the blog in the demo. > > > > > > Like that idea? How can it be modified? Who and how is it built? > > > > > > Best regards, > > > > > Johnny > > > > > > -- > > > > > > 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]<google-wave-api%2Bunsubscribe@ > > > > > 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 [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=.
