WaveGigs.

Google Wave Extensions

Google March 12 formally launched its extensions for Google Wave, a move to fortify the real-time collaboration platform's functionality and cultivate a large developer ecosystem.

Google Wave rolls e-mail, instant messaging and real-time document editing into one platform, which has grabbed more than 1 million users since its broader launch last September. Google launched Wave to open source because it wants developers to write programs that augment that platform in ways that go beyond Google's own application expertise.

Extensions, added as a link to the Google Wave navigation panel, are the fruit of this effort. The Wave Extensions gallery comprises a set of waves containing extension installers. This "Read me first" wave offers a tutorial on how to use extensions.

via http://www.devsource.com/c/a/Architecture/Google-Wave-Launches-Extensions-to-Crank-Up-Software-Development/

Comments (0)

Posted

Feedback from using Google Wave

Interesting problems discussed - but even more interesting suggestions for improvements.

Many of these pain points can be improved with robots.

Invitations to a wave should be by URL, sent via email or instant messaging or any other means, and if Google Wave wants to make it easier, it should tie into your existing contact list.

Google Wave shouldn't require an account for those invited to join a wave, and if someone wants to create an account, it should for now be associated with existing Google accounts, and not be entirely separate.

For those who already use Gmail, Google should think about non-intrusive ways of integrating Google Wave into Gmail to eliminate the notification problem and create a bit more of a network effect. For those not using Gmail, email notification is a must.

Though seeing people typing in real-time can be useful, the feature should be optional, to allow people to finish a thought before others reply or comment on it.

The interface for switching between editing and replying needs to be both more obvious and faster, and the constant creation of inadvertent replies should be eliminated.

Google Wave should remember if you have collapsed a blip and not show it again unless it gets new traffic, or even collapse replies after they're read, just like an email conversation in Gmail. There should also be a way of hiding all replies completely, so an edited document can be read without interruption.

If Google Wave is to be useful for document collaboration, it has to be able to publish a wave to other formats and mediums, such as email, straight text, RTF, HTML, to a blog post, or to a content management system. Copy-and-paste is not an interface.

Blips should be allowed to have user-defined metadata like completion status, task assignment, and due dates so Google Wave could become useful for task and project management.

via http://db.tidbits.com/article/11074

Comments (0)

Posted

How Google Wave can change your life

Google Wave can make your small business communication easier. Managing people, process and documents in a freeform way like email - but more trackable and extendable.

From maxklein:

What has Google Wave done for me?

My stress level is way lower
Conversations are now organised in topics, and no longer flat
Fights have become more constructive
Working across multiple time zones is no longer a problem
I can share screenshots, design documents with multiple and different people with ease
I have a single control panel to manage all my conversation with everyone I am working with
Before Google Wave, I felt like I was working very much and getting very little done. After google wave, I feel I am doing little work, but I am making more and more money every month
I feel in control of my business - with my iPhone I can access the heart of my business anytime and anywhere

What's missing from Google Wave?

You cannot manage your contacts or create contact groups. It's easy to add people to waves that you don't want in there.

But in general, if you are collaborating with people and you have not tried Google Wave, then you are perhaps missing the greatest thing to happen to small web based businesses since Dropbox.

via http://maxklein.posterous.com/on-how-google-wave-surprisingly-changed-my-li

Comments (0)

Posted

Google Wave email gateway

Overview
Emaily is a robot running on Google AppEngine, which works as a gateway between Google Wave and Email. With this, you can send and receive emails inside Google Wave.

Planned Features
New Email button
Creating an extension from Emaily allows us to add a "New Email" button next to the "New Wave" button, and create an even more easy way to add an email.
Threading support
Emaily will recognize email-threads and it will ad a new incoming message to the proper thread instead of creating a new wave for it.
Additional planned features
Viewing HTML email.
Sending and receiving attachments.
Automatic management of wave/email users.
via http://emaily.dlux.hu/#TOC-How-to-use-it

Comments (0)

Posted

Python Google Wave Robot Tutorial

According to the tutorial from Google:

The easiest way to understand how extensions work in Wave is to build a Wave robot. Robots are applications that interact with a Wave through the Wave protocol (HTTP interface). Currently, we only support robots hosted with Google App Engine. In the future, we will support any client architecture that implements the Wave protocol.

So make sure you are familiar with Google App Engine before proceeding. From there it is simply implementing a standard App Engine application that handles Wave API events.

In this tutorial, we'll use the Python client library to develop a sample robot. (The concepts apply here equally well to users of the Java™ client library, though implementation details will be different.) In this brief tutorial, you will create a simple robot, upload it to App Engine, and see it working with Wave.

via http://code.google.com/intl/ja/apis/wave/extensions/robots/python-tutorial.html

Comments (0)

Posted

Another round of Google Wave invites

WaveGigs invites you to email invite@wavegigs.com to receive an invitation.

First 10 people to respond will receive an invite.

-WaveGigs Team

Comment (1)

Posted

Google Wave iPhone app

Mobile seems to be the perfect platform for pushing Google Wave adoption.

There was a iPhone Google Wave app in the store - but it was pulled. I think you should expect to see this as a built in app somewhere in the next few months. Wave already works great when you point your browser to wave.google.com on your mobile device.

via http://www.washingtonpost.com/wp-dyn/content/article/2009/11/21/AR2009112101026.html

Comments (0)

Posted

Wave complete guide - recently updated

Wave Terminology:

Google wave brings a whole new set of terms to communication. This list is quite helpful in understanding the basic components of wave.

- Wave: A wave, specifically, refers to a specific threaded conversation. It can include just one person, or it can include a group of users or even robots (explained below). The best comparison I can make is that it’s like your entire instant messaging (IM) history with someone. Anything you’ve ever discussed in a single chat or conversation is a wave.

- Wavelet: A wavelet is also a threaded conversation, but only a subset of a larger conversation (or a wave). It’s like a single IM conversation – a small part of a larger conversation and a larger history. Wavelets, though, can be created and managed separately from a wave.

- Blip

: Even smaller than a Wavelet, a Blip is a single, individual message. It’s like a single line of an IM conversation. Blips can have other blips attached to them, called children. In addition, blips can either be published or unpublished (once again, it’s sort of like typing out an IM message but not yet sending it).

- Document: A document actually refers to the content within a blip. This seems to refer to the actual characters, words, and files associated with a blip.

- Extension: An extension is a mini-application that works within a wave. So these are the apps you can play with while using Wave. There are two main types of extenisons: Gadgets and Robots

- Gadgets: A gadget is an application users can participate with, many of which are built on Google’s OpenSocial platform. A good comparison would be iGoogle gadgets or Facebook applications.

- Robots: Robots are an automated participant within a wave. They can talk with users and interact with waves. They can provide information from outside sources (i.e. Twitter

) or they can check content within a wave and perform actions based on them (i.e. provide you a stock quote if a stock name is mentioned).

- Embeded Wave: An embeded wave is a way to take a Google Wave and the conversation within it and place it on your website. Users could use this as a chatroom, as a way to contact you, or for something more.

via http://mashable.com/2009/05/28/google-wave-guide/

Comments (0)

Posted