[Google Wave APIs] Re: Google Wave website editor?
What is happening with the MediaWiki Wave project? Have you guys heard of that? WYSIWYG for MediaWiki with all of wave's features could be a starting point for this idea. On Nov 19, 2:54 pm, SantaBrígida wrote: > 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 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 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 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 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 > > > > > 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 id
[Google Wave APIs] Re: Google Wave website editor?
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 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 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 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 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 > > > > 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 > > > > g
[Google Wave APIs] Re: Google Wave website editor?
Wow! What a response! Thank you :) I have read the full discussion now and Im not sure I got everything, since Im a bit too tired, but... You said that WYSIWYG-editing might be hard if you are several users working on the same page - Possible solution: A function that lets you highlight/cut out/mark or reserve an area for yourself, that you are in charge of. Kind of like creating headlines in a document and person no. 1 work on headline no.1. And the "editation-program" keeps track of what order the headlines - reserved areas - was in from the beginning. But the reserved area isnt locked in size. You can add as much as you feel necesarry etc. Everyone else can join in on discussions and start discussions about something in your private edit-area, but cannot edit themselves. Same function should go with the code. Ofcourse other users that are working with the same project should be able to highlight and copy ideas from eachother, but NOT EDIT the same private area. Perhaps a function where an "owner of an edit-area" should be able to give access to others to edit a certain part of the code or graphical design. Why do I sense that a cooperation between Google and Adobe would be fantastic, and let Dreamweaver CS # have this Google Wave function added to it. :) -- 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=.
Re: [Google Wave APIs] Re: Google Wave website editor?
Perhaps a better use of resources would be to add these "missing" layout/formatting features directly into Wave? Improve the existing WYSIWYG features of Wave, in other words, without giving up and reimplementing it elsewhere? Many users of a web publishing tool may find the editor capabilities in Wave to be perfectly adequate for their needs. Where additional styling hints may be needed, you can use an extension/robot to add annotations. These won't be visible in the editor without some system of rendering plugins, but your export process can probably do something useful with them. It's possible that the publishing goal can then be worked on independently of the editing goal. David On Thu, Nov 19, 2009 at 9:59 AM, Olreich wrote: > A gadget for display makes sense, a gadget for editing essentially > skips the entire idea of collaborative editing (WYSIWYG editing makes > it much more difficult to do things collaboratively, as that's a ton > of rendering without canvas). I disagree with WYSIWYG in general > though, as I've used Dreamweaver quite a bit, and it promotes inline > styles, and does not promote semantic code, even with CS4. A WYSIWYG > editor would be good, but doesn't exactly leverage the abilities of > wave from what I can tell. > > On Nov 19, 12:49 pm, David Nesting wrote: > > On Thu, Nov 19, 2009 at 9:04 AM, Jason Livesay > wrote: > > > 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 > > > > So, I don't mean to dissuade anyone from working on things designed like > > this. I'm really interested to see how this approach turns out. > > > > The chief complaint I have with a gadget-oriented approach is that you > start > > abandoning the services already provided by Wave. You can no longer > > leverage spelly, or linky, for instance. You have to re-implement your > own > > editor within the gadget. At that point, the only thing you're using > Wave > > for is (presumably) to store the resulting document. You might be able > to > > save yourself some work and just implement this as a stand-alone web app? > > Are there other ways we can continue to leverage Wave but approach this > in > > a gadget-oriented manner? > > > > David > > -- > > 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=. > > > -- 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=.
[Google Wave APIs] Re: Google Wave website editor?
It looks like I was the only one that was especially concerned with WYSIWYG or gadgets. I think it is wise to focus on approaches that take advantage of as many of the Wave tools as possible. So you guys have a point about the emphasis on robots. Maybe another more general suggestion might be to consider the advantages users of the tool will have over other (non-wave-based) tools. On Nov 19, 9:49 am, David Nesting wrote: > On Thu, Nov 19, 2009 at 9:04 AM, Jason Livesay wrote: > > 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 > > So, I don't mean to dissuade anyone from working on things designed like > this. I'm really interested to see how this approach turns out. > > The chief complaint I have with a gadget-oriented approach is that you start > abandoning the services already provided by Wave. You can no longer > leverage spelly, or linky, for instance. You have to re-implement your own > editor within the gadget. At that point, the only thing you're using Wave > for is (presumably) to store the resulting document. You might be able to > save yourself some work and just implement this as a stand-alone web app? > Are there other ways we can continue to leverage Wave but approach this in > a gadget-oriented manner? > > David -- 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=.
[Google Wave APIs] Re: Google Wave website editor?
A gadget for display makes sense, a gadget for editing essentially skips the entire idea of collaborative editing (WYSIWYG editing makes it much more difficult to do things collaboratively, as that's a ton of rendering without canvas). I disagree with WYSIWYG in general though, as I've used Dreamweaver quite a bit, and it promotes inline styles, and does not promote semantic code, even with CS4. A WYSIWYG editor would be good, but doesn't exactly leverage the abilities of wave from what I can tell. On Nov 19, 12:49 pm, David Nesting wrote: > On Thu, Nov 19, 2009 at 9:04 AM, Jason Livesay wrote: > > 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 > > So, I don't mean to dissuade anyone from working on things designed like > this. I'm really interested to see how this approach turns out. > > The chief complaint I have with a gadget-oriented approach is that you start > abandoning the services already provided by Wave. You can no longer > leverage spelly, or linky, for instance. You have to re-implement your own > editor within the gadget. At that point, the only thing you're using Wave > for is (presumably) to store the resulting document. You might be able to > save yourself some work and just implement this as a stand-alone web app? > Are there other ways we can continue to leverage Wave but approach this in > a gadget-oriented manner? > > David -- 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=.
[Google Wave APIs] Re: Google Wave website editor?
Seems like a good idea to me. Wave API does seem vaguely inappropriate now that we're talking about design rather than whether or not the API can handle it. On Nov 19, 12:04 pm, Jason Livesay wrote: > 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 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 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 > >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
Re: [Google Wave APIs] Re: Google Wave website editor?
On Thu, Nov 19, 2009 at 9:04 AM, Jason Livesay wrote: > 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 So, I don't mean to dissuade anyone from working on things designed like this. I'm really interested to see how this approach turns out. The chief complaint I have with a gadget-oriented approach is that you start abandoning the services already provided by Wave. You can no longer leverage spelly, or linky, for instance. You have to re-implement your own editor within the gadget. At that point, the only thing you're using Wave for is (presumably) to store the resulting document. You might be able to save yourself some work and just implement this as a stand-alone web app? Are there other ways we can continue to leverage Wave but approach this in a gadget-oriented manner? David -- 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=.
Re: [Google Wave APIs] Re: Google Wave website editor?
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 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 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 >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. > > > >
[Google Wave APIs] Re: Google Wave website editor?
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 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 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 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 > > > 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 > > > 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
[Google Wave APIs] Re: Google Wave website editor?
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 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 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 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 > > 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=.
[Google Wave APIs] Re: Google Wave website editor?
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 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 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 > 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=.
