A few that may or may not have already been considered.

[GoogleCodeExporter]

Wave edit toolbar:
Perhaps condense the gadgets into a select box and possibly do the same 
with text formatting options.

Wave list pane:
When new edits are made to a wave, move the icon of the editor all of the 
way to the left and highlight/outline icon to make it obvious who has most 
recently edited (same with the icons at the top of the wave pane.

Bots as application features:
Configurable audio event notifications. I know a robot can do this, but I 
can imagine so many useful robots that would better serve Wave adoption 
than waiting for bots, that could in many cases, outnumber wave 
participants. How about an attendance/receptionist feature? Basically any 
bots that have at least an 80% overall value rating should be considered 
for feature integration. 

Keep up the great work!! I'm pushing hard in my organization for Wave. It 
will be quite some time before I run out of ideas for how Wave can be 
applied! :)

Original issue reported on code.google.com by mrjeffh...@gmail.com on 19 Oct 2009 at 1:21

[GoogleCodeExporter]

Re 1) that is coming in a few days (a dropdown with additional edit icons).

Re 2) That's interesting idea, can you discuss in the user forum?
http://www.google.com/support/forum/p/Wave?
hl=en&utm_source=HC&utm_medium=leftnav&utm_campaign=wave

Re 3) So, some robots would become always-on robots? I have suggested being 
able to 
specify robots that are on every Wave, but I guess you're suggesting that we 
decide 
which ones those are? The main issue here would be security -- we don't have a 
way to 
guarantee that a robot's code is secure, if it comes from a non-Googler, so we 
would 
not want to impose it on all of a developer's waves. It could be malicious.

Original comment by pamela.fox on 19 Oct 2009 at 2:52

• Changed state: NeedsMoreInfo