Obviously, there is more than one valid and useful approach to this idea of website editing in a Wave. I just wanted to mention again that I personally would put more effort into the gadget and WYSIWYG side of things than to the robot and markup side of things. I feel that web development has really been led astray with the over-reliance upon manual XHTML and CSS editing -- we sort of forgot how successful GUI development on desktop systems has been taking advantage of widgets,components, WYSIWYG form editors, etc. Anyway, I realize that is not a popular perspective today among other web developers and I admit that practically speaking editing the code allows for quite a lot of flexibility and might be easier to implement. Also, I have to admit the reality is that I spend most of my time at work in VIM manually editing PHP, XHTML and CSS. I just think that with the right tools, things don't have to be like that, although again, easier said than done.
Whatever the approach taken I suggest that those interested in pursuing a website editor using Waves immediately take the action of forming and joining a Google or other project group and move the discussion and progress into that group. Generally speaking I don't know if there is a better forum for discussion of Google Wave projects, although it does seem this might be slightly off topic since the name of the group includes the word API. I think those that are looking into API details are the ones starting new projects with the technical skills to move forward on them and this group probably is the best place to hook up with others like that. But I think taking the next step to actually align goals and start collaborating is easier said than done, so we should realize that and take care to take the action of forming and joining groups. Also it would probably be better for the Wave API traffic if people that identify common projects start taking the discussion into forums for those groups. Not to be too presumptuous or get too far ahead, but I went ahead and created a Google Code project in case anyone wants to work on/discuss this in there. I added each email address in this thread as a project owner. http://code.google.com/p/wavewebsites/ On Wed, Nov 18, 2009 at 5:00 PM, Olreich <olre...@gmail.com> 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 <ithk...@gmail.com> 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 <nadrend...@gmail.com > >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 google-wave-...@googlegroups.com. > > > To unsubscribe from this group, send email to > > > google-wave-api+unsubscr...@googlegroups.com<google-wave-api%2bunsubscr...@googlegroups.com> > <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 google-wave-...@googlegroups.com. > To unsubscribe from this group, send email to > google-wave-api+unsubscr...@googlegroups.com<google-wave-api%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-wave-api?hl=. > > > -- 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=.
