We thought it might be useful to point at some starter documentation for the new web client, as well as pointing to some of the more interesting parts of the code for those of you interested in working with it.
The web client is implemented using GWT [http://code.google.com/webtoolkit]. It is a testbed/sample for the newly open sourced editor, model and concurrency control code, which is also in GWT. The code for the web client can be found in the directory gwt_src/org/waveprotocol/wave/examples/fedone/ [http://code.google.com/p/wave-protocol/source/browse?repo=io2010#hg/g...] in the io2010 repository. The code uses the (new in GWT 2.0) UiBinder approach to defining its user interface.
Currently the client allows you to view and create waves, as well as add replies and edit existing blips. It also allows you to add participants to an existing wave - both local and remote (via federation).
You can use it by running "ant all" (or "ant dist-server compile_gwt"), setting up the server in the same way as before [http://code.google.com/p/wave-protocol/wiki/Installation], then visiting http://localhost:9898 in a browser. Login with a full user@yourdomain. At the moment, only Chrome, Safari 5 and Webkit nightly are supported, as they're the only browsers that have the required Websocket support.
Here's a brief look at some of the files to look at if you're interested in adding features or functionality to the current client, or to implement your own client using the code be open sourced.
gwt_src/org/waveprotocol/wave/examples/fedone/simplewebclient - this directory contains the bulk of the user interface for the client. In that directory, you'll find the following files of interest:
* client/CcStackManager.java
This file shows how to hook up the client side concurrency control stack. The concurrency control stack takes care of sending messages out to the network, and applying real time changes to the current state of the editor.
* client/EditorWidget.java
This file hooks up the newly open-sourced editor widget to the view of a wave.
* client/WaveView.java
This is the right hand panel of the main view of the client, showing the display of blips in the wave. As noted in the initial email announcing this code, right now this only displays top level blips in the conversation.
In the gwt_src/org/wave/waveprotocol/examples/fedone/waveclient/common directory are GWT-specific versions of the client-server protocol implementation for the client. As we previously mentioned, we're aware of the deficiencies of the current client-server protocol, and will be looking to update it soon to be closer to the client-server protocol we use for the wave.google.com service.
It's worth emphasising that the io2010 branch of the repository is a temporary thing - once the code is cleaned up and the tests are all working again, we'll be landing the code into the default trunk repository. Instructions for checking out a copy of the io2010 code can be found at http://code.google.com/p/wave-protocol/source/checkout?repo=io2010
Thanks,
Anthony (on behalf of JD, Alex, Dan, Soren, Bob and Christian)
On Thu, 2010-06-24 at 17:46 +1000, Anthony Baxter wrote: > Hi folks,
> We thought it might be useful to point at some starter documentation > for the new web client, as well as pointing to some of the more > interesting parts of the code for those of you interested in working > with it.
> The web client is implemented using GWT > [http://code.google.com/webtoolkit]. It is a testbed/sample for the > newly open sourced editor, model and concurrency control code, which > is also in GWT. The code for the web client can be found in the > directory gwt_src/org/waveprotocol/wave/examples/fedone/ > [http://code.google.com/p/wave-protocol/source/browse?repo=io2010#hg/g...] > in the io2010 repository. The code uses the (new in GWT 2.0) UiBinder > approach to defining its user interface.
> Currently the client allows you to view and create waves, as well as > add replies and edit existing blips. It also allows you to add > participants to an existing wave - both local and remote (via > federation).
> You can use it by running "ant all" (or "ant dist-server > compile_gwt"), setting up the server in the same way as before > [http://code.google.com/p/wave-protocol/wiki/Installation], then > visiting http://localhost:9898 in a browser. Login with a full > user@yourdomain. At the moment, only Chrome, Safari 5 and Webkit > nightly are supported, as they're the only browsers that have the > required Websocket support.
> Here's a brief look at some of the files to look at if you're > interested in adding features or functionality to the current client, > or to implement your own client using the code be open sourced.
> gwt_src/org/waveprotocol/wave/examples/fedone/simplewebclient - this > directory contains the bulk of the user interface for the client. In > that directory, you'll find the following files of interest:
> * client/CcStackManager.java
> This file shows how to hook up the client side concurrency control > stack. The concurrency control stack takes care of sending messages > out to the network, and applying real time changes to the current > state of the editor.
> * client/EditorWidget.java
> This file hooks up the newly open-sourced editor widget to the view of a wave.
> * client/WaveView.java
> This is the right hand panel of the main view of the client, showing > the display of blips in the wave. As noted in the initial email > announcing this code, right now this only displays top level blips in > the conversation.
> In the gwt_src/org/wave/waveprotocol/examples/fedone/waveclient/common > directory are GWT-specific versions of the client-server protocol > implementation for the client. As we previously mentioned, we're aware > of the deficiencies of the current client-server protocol, and will be > looking to update it soon to be closer to the client-server protocol > we use for the wave.google.com service.
> It's worth emphasising that the io2010 branch of the repository is a > temporary thing - once the code is cleaned up and the tests are all > working again, we'll be landing the code into the default trunk > repository. Instructions for checking out a copy of the io2010 code > can be found at > http://code.google.com/p/wave-protocol/source/checkout?repo=io2010
> Thanks,
> Anthony (on behalf of JD, Alex, Dan, Soren, Bob and Christian)
Thank you for sharing!
When I compiled the GWT source code with ANT, there are some errors
and warnings.
It reports like this:
[java] [ERROR] Errors in 'D:\Workspace\google-wave\wave-protocol-
io2010\src\org\waveprotocol\wave\client\editor\testing
\MockTypingSink.java'
[java] [ERROE] line 71 No source code is available for type
junit.framework.TestCase; did you forget to inherited a required
module?
..................................
At last,it report:
[java] Compiling 15 permutations
...........................
[java] Compile of permutations succeeded.
Did I Compiled it successfully?
On 6月24日, 下午3时46分, Anthony Baxter <anthonybax...@gmail.com> wrote:
> We thought it might be useful to point at some starter documentation
> for the new web client, as well as pointing to some of the more
> interesting parts of the code for those of you interested in working
> with it.
> The web client is implemented using GWT
> [http://code.google.com/webtoolkit]. It is a testbed/sample for the
> newly open sourced editor, model and concurrency control code, which
> is also in GWT. The code for the web client can be found in the
> directory gwt_src/org/waveprotocol/wave/examples/fedone/
> [http://code.google.com/p/wave-protocol/source/browse?repo=io2010#hg/g...]
> in the io2010 repository. The code uses the (new in GWT 2.0) UiBinder
> approach to defining its user interface.
> Currently the client allows you to view and create waves, as well as
> add replies and edit existing blips. It also allows you to add
> participants to an existing wave - both local and remote (via
> federation).
> You can use it by running "ant all" (or "ant dist-server
> compile_gwt"), setting up the server in the same way as before
> [http://code.google.com/p/wave-protocol/wiki/Installation], then
> visitinghttp://localhost:9898in a browser. Login with a full
> user@yourdomain. At the moment, only Chrome, Safari 5 and Webkit
> nightly are supported, as they're the only browsers that have the
> required Websocket support.
> Here's a brief look at some of the files to look at if you're
> interested in adding features or functionality to the current client,
> or to implement your own client using the code be open sourced.
> gwt_src/org/waveprotocol/wave/examples/fedone/simplewebclient - this
> directory contains the bulk of the user interface for the client. In
> that directory, you'll find the following files of interest:
> * client/CcStackManager.java
> This file shows how to hook up the client side concurrency control
> stack. The concurrency control stack takes care of sending messages
> out to the network, and applying real time changes to the current
> state of the editor.
> * client/EditorWidget.java
> This file hooks up the newly open-sourced editor widget to the view of a wave.
> * client/WaveView.java
> This is the right hand panel of the main view of the client, showing
> the display of blips in the wave. As noted in the initial email
> announcing this code, right now this only displays top level blips in
> the conversation.
> In the gwt_src/org/wave/waveprotocol/examples/fedone/waveclient/common
> directory are GWT-specific versions of the client-server protocol
> implementation for the client. As we previously mentioned, we're aware
> of the deficiencies of the current client-server protocol, and will be
> looking to update it soon to be closer to the client-server protocol
> we use for the wave.google.com service.
> It's worth emphasising that the io2010 branch of the repository is a
> temporary thing - once the code is cleaned up and the tests are all
> working again, we'll be landing the code into the default trunk
> repository. Instructions for checking out a copy of the io2010 code
> can be found athttp://code.google.com/p/wave-protocol/source/checkout?repo=io2010
> Thanks,
> Anthony (on behalf of JD, Alex, Dan, Soren, Bob and Christian)
Yes, that's an error in the test building, it won't affect the real client build. I'll look at fixing that in the next day or two so that the errors go away.
> Thank you for sharing! > When I compiled the GWT source code with ANT, there are some errors > and warnings. > It reports like this:
> [java] [ERROR] Errors in 'D:\Workspace\google-wave\wave-protocol- > io2010\src\org\waveprotocol\wave\client\editor\testing > \MockTypingSink.java' > [java] [ERROE] line 71 No source code is available for type > junit.framework.TestCase; did you forget to inherited a required > module? > ..................................
> At last,it report: > [java] Compiling 15 permutations > ........................... > [java] Compile of permutations succeeded.
> Did I Compiled it successfully?
> On 6月24日, 下午3时46分, Anthony Baxter <anthonybax...@gmail.com> wrote: >> Hi folks,
>> We thought it might be useful to point at some starter documentation >> for the new web client, as well as pointing to some of the more >> interesting parts of the code for those of you interested in working >> with it.
>> The web client is implemented using GWT >> [http://code.google.com/webtoolkit]. It is a testbed/sample for the >> newly open sourced editor, model and concurrency control code, which >> is also in GWT. The code for the web client can be found in the >> directory gwt_src/org/waveprotocol/wave/examples/fedone/ >> [http://code.google.com/p/wave-protocol/source/browse?repo=io2010#hg/g...] >> in the io2010 repository. The code uses the (new in GWT 2.0) UiBinder >> approach to defining its user interface.
>> Currently the client allows you to view and create waves, as well as >> add replies and edit existing blips. It also allows you to add >> participants to an existing wave - both local and remote (via >> federation).
>> You can use it by running "ant all" (or "ant dist-server >> compile_gwt"), setting up the server in the same way as before >> [http://code.google.com/p/wave-protocol/wiki/Installation], then >> visitinghttp://localhost:9898in a browser. Login with a full >> user@yourdomain. At the moment, only Chrome, Safari 5 and Webkit >> nightly are supported, as they're the only browsers that have the >> required Websocket support.
>> Here's a brief look at some of the files to look at if you're >> interested in adding features or functionality to the current client, >> or to implement your own client using the code be open sourced.
>> gwt_src/org/waveprotocol/wave/examples/fedone/simplewebclient - this >> directory contains the bulk of the user interface for the client. In >> that directory, you'll find the following files of interest:
>> * client/CcStackManager.java
>> This file shows how to hook up the client side concurrency control >> stack. The concurrency control stack takes care of sending messages >> out to the network, and applying real time changes to the current >> state of the editor.
>> * client/EditorWidget.java
>> This file hooks up the newly open-sourced editor widget to the view of a wave.
>> * client/WaveView.java
>> This is the right hand panel of the main view of the client, showing >> the display of blips in the wave. As noted in the initial email >> announcing this code, right now this only displays top level blips in >> the conversation.
>> In the gwt_src/org/wave/waveprotocol/examples/fedone/waveclient/common >> directory are GWT-specific versions of the client-server protocol >> implementation for the client. As we previously mentioned, we're aware >> of the deficiencies of the current client-server protocol, and will be >> looking to update it soon to be closer to the client-server protocol >> we use for the wave.google.com service.
>> It's worth emphasising that the io2010 branch of the repository is a >> temporary thing - once the code is cleaned up and the tests are all >> working again, we'll be landing the code into the default trunk >> repository. Instructions for checking out a copy of the io2010 code >> can be found athttp://code.google.com/p/wave-protocol/source/checkout?repo=io2010
>> Thanks,
>> Anthony (on behalf of JD, Alex, Dan, Soren, Bob and Christian)
> -- > You received this message because you are subscribed to the Google Groups "Wave Protocol" group. > To post to this group, send email to wave-protocol@googlegroups.com. > To unsubscribe from this group, send email to wave-protocol+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
When I run the web client - I am not able to log in. I can enter a
login address, but the login button is still grayed out. There is a
message in the upper right corner "Never_Connected
In the bottom window I have this output:
Tue Jun 29 09:14:58 GMT-700 2010[INFO] Attemping to reconnect
Tue Jun 29 09:14:58 GMT-700 2010[INFO] SimpleWebClient.onModuleLoad()
done
> We thought it might be useful to point at some starter documentation
> for the newwebclient, as well as pointing to some of the more
> interesting parts of the code for those of you interested in working
> with it.
> Thewebclientis implemented using GWT
> [http://code.google.com/webtoolkit]. It is a testbed/sample for the
> newly open sourced editor, model and concurrency control code, which
> is also in GWT. The code for thewebclientcan be found in the
> directory gwt_src/org/waveprotocol/wave/examples/fedone/
> [http://code.google.com/p/wave-protocol/source/browse?repo=io2010#hg/g...]
> in the io2010 repository. The code uses the (new in GWT 2.0) UiBinder
> approach to defining its user interface.
> Currently theclientallows you to view and create waves, as well as
> add replies and edit existing blips. It also allows you to add
> participants to an existing wave - both local and remote (via
> federation).
> You can use it by running "ant all" (or "ant dist-server
> compile_gwt"), setting up the server in the same way as before
> [http://code.google.com/p/wave-protocol/wiki/Installation], then
> visitinghttp://localhost:9898in a browser. Login with a full
> user@yourdomain. At the moment, only Chrome, Safari 5 and Webkit
> nightly are supported, as they're the only browsers that have the
> required Websocket support.
> Here's a brief look at some of the files to look at if you're
> interested in adding features or functionality to the currentclient,
> or to implement your ownclientusing the code be open sourced.
> gwt_src/org/waveprotocol/wave/examples/fedone/simplewebclient - this
> directory contains the bulk of the user interface for theclient. In
> that directory, you'll find the following files of interest:
> *client/CcStackManager.java
> This file shows how to hook up theclientside concurrency control
> stack. The concurrency control stack takes care of sending messages
> out to the network, and applying real time changes to the current
> state of the editor.
> *client/EditorWidget.java
> This file hooks up the newly open-sourced editor widget to the view of a wave.
> *client/WaveView.java
> This is the right hand panel of the main view of theclient, showing
> the display of blips in the wave. As noted in the initial email
> announcing this code, right now this only displays top level blips in
> the conversation.
> In the gwt_src/org/wave/waveprotocol/examples/fedone/waveclient/common
> directory are GWT-specific versions of theclient-server protocol
> implementation for theclient. As we previously mentioned, we're aware
> of the deficiencies of the currentclient-server protocol, and will be
> looking to update it soon to be closer to theclient-server protocol
> we use for the wave.google.com service.
> It's worth emphasising that the io2010 branch of the repository is a
> temporary thing - once the code is cleaned up and the tests are all
> working again, we'll be landing the code into the default trunk
> repository. Instructions for checking out a copy of the io2010 code
> can be found athttp://code.google.com/p/wave-protocol/source/checkout?repo=io2010
On Wed, Jun 30, 2010 at 02:31, cyclingastrobrewer <pca...@gmail.com> wrote: > When I run the web client - I am not able to log in. I can enter a > login address, but the login button is still grayed out. There is a > message in the upper right corner "Never_Connected
> In the bottom window I have this output: > Tue Jun 29 09:14:58 GMT-700 2010[INFO] Attemping to reconnect > Tue Jun 29 09:14:58 GMT-700 2010[INFO] SimpleWebClient.onModuleLoad() > done
> On Jun 24, 12:46 am, Anthony Baxter <anthonybax...@gmail.com> wrote: >> Hi folks,
>> We thought it might be useful to point at some starter documentation >> for the newwebclient, as well as pointing to some of the more >> interesting parts of the code for those of you interested in working >> with it.
>> Thewebclientis implemented using GWT >> [http://code.google.com/webtoolkit]. It is a testbed/sample for the >> newly open sourced editor, model and concurrency control code, which >> is also in GWT. The code for thewebclientcan be found in the >> directory gwt_src/org/waveprotocol/wave/examples/fedone/ >> [http://code.google.com/p/wave-protocol/source/browse?repo=io2010#hg/g...] >> in the io2010 repository. The code uses the (new in GWT 2.0) UiBinder >> approach to defining its user interface.
>> Currently theclientallows you to view and create waves, as well as >> add replies and edit existing blips. It also allows you to add >> participants to an existing wave - both local and remote (via >> federation).
>> You can use it by running "ant all" (or "ant dist-server >> compile_gwt"), setting up the server in the same way as before >> [http://code.google.com/p/wave-protocol/wiki/Installation], then >> visitinghttp://localhost:9898in a browser. Login with a full >> user@yourdomain. At the moment, only Chrome, Safari 5 and Webkit >> nightly are supported, as they're the only browsers that have the >> required Websocket support.
>> Here's a brief look at some of the files to look at if you're >> interested in adding features or functionality to the currentclient, >> or to implement your ownclientusing the code be open sourced.
>> gwt_src/org/waveprotocol/wave/examples/fedone/simplewebclient - this >> directory contains the bulk of the user interface for theclient. In >> that directory, you'll find the following files of interest:
>> *client/CcStackManager.java
>> This file shows how to hook up theclientside concurrency control >> stack. The concurrency control stack takes care of sending messages >> out to the network, and applying real time changes to the current >> state of the editor.
>> *client/EditorWidget.java
>> This file hooks up the newly open-sourced editor widget to the view of a wave.
>> *client/WaveView.java
>> This is the right hand panel of the main view of theclient, showing >> the display of blips in the wave. As noted in the initial email >> announcing this code, right now this only displays top level blips in >> the conversation.
>> In the gwt_src/org/wave/waveprotocol/examples/fedone/waveclient/common >> directory are GWT-specific versions of theclient-server protocol >> implementation for theclient. As we previously mentioned, we're aware >> of the deficiencies of the currentclient-server protocol, and will be >> looking to update it soon to be closer to theclient-server protocol >> we use for the wave.google.com service.
> which browser? you need one that supports websockets.
> On Wed, Jun 30, 2010 at 02:31, cyclingastrobrewer <pca...@gmail.com> > wrote: > > When I run the web client - I am not able to log in. I can enter a > > login address, but the login button is still grayed out. There is a > > message in the upper right corner "Never_Connected
> > In the bottom window I have this output: > > Tue Jun 29 09:14:58 GMT-700 2010[INFO] Attemping to reconnect > > Tue Jun 29 09:14:58 GMT-700 2010[INFO] SimpleWebClient.onModuleLoad() > > done
> > On Jun 24, 12:46 am, Anthony Baxter <anthonybax...@gmail.com> wrote: > >> Hi folks,
> >> We thought it might be useful to point at some starter documentation > >> for the newwebclient, as well as pointing to some of the more > >> interesting parts of the code for those of you interested in working > >> with it.
> >> Thewebclientis implemented using GWT > >> [http://code.google.com/webtoolkit]. It is a testbed/sample for the > >> newly open sourced editor, model and concurrency control code, which > >> is also in GWT. The code for thewebclientcan be found in the > >> directory gwt_src/org/waveprotocol/wave/examples/fedone/ > >> [ > http://code.google.com/p/wave-protocol/source/browse?repo=io2010#hg/g...] > >> in the io2010 repository. The code uses the (new in GWT 2.0) UiBinder > >> approach to defining its user interface.
> >> Currently theclientallows you to view and create waves, as well as > >> add replies and edit existing blips. It also allows you to add > >> participants to an existing wave - both local and remote (via > >> federation).
> >> You can use it by running "ant all" (or "ant dist-server > >> compile_gwt"), setting up the server in the same way as before > >> [http://code.google.com/p/wave-protocol/wiki/Installation], then > >> visitinghttp://localhost:9898in a browser. Login with a full > >> user@yourdomain. At the moment, only Chrome, Safari 5 and Webkit > >> nightly are supported, as they're the only browsers that have the > >> required Websocket support.
> >> Here's a brief look at some of the files to look at if you're > >> interested in adding features or functionality to the currentclient, > >> or to implement your ownclientusing the code be open sourced.
> >> gwt_src/org/waveprotocol/wave/examples/fedone/simplewebclient - this > >> directory contains the bulk of the user interface for theclient. In > >> that directory, you'll find the following files of interest:
> >> *client/CcStackManager.java
> >> This file shows how to hook up theclientside concurrency control > >> stack. The concurrency control stack takes care of sending messages > >> out to the network, and applying real time changes to the current > >> state of the editor.
> >> *client/EditorWidget.java
> >> This file hooks up the newly open-sourced editor widget to the view of > a wave.
> >> *client/WaveView.java
> >> This is the right hand panel of the main view of theclient, showing > >> the display of blips in the wave. As noted in the initial email > >> announcing this code, right now this only displays top level blips in > >> the conversation.
> >> In the gwt_src/org/wave/waveprotocol/examples/fedone/waveclient/common > >> directory are GWT-specific versions of theclient-server protocol > >> implementation for theclient. As we previously mentioned, we're aware > >> of the deficiencies of the currentclient-server protocol, and will be
On Wed, Jun 30, 2010 at 10:13, Paul Carff <pca...@gmail.com> wrote: > Google Chrome > 5.0.375.86
> On Tue, Jun 29, 2010 at 4:18 PM, Anthony Baxter <anthonybax...@gmail.com> > wrote:
>> which browser? you need one that supports websockets.
>> On Wed, Jun 30, 2010 at 02:31, cyclingastrobrewer <pca...@gmail.com> >> wrote: >> > When I run the web client - I am not able to log in. I can enter a >> > login address, but the login button is still grayed out. There is a >> > message in the upper right corner "Never_Connected
>> > In the bottom window I have this output: >> > Tue Jun 29 09:14:58 GMT-700 2010[INFO] Attemping to reconnect >> > Tue Jun 29 09:14:58 GMT-700 2010[INFO] SimpleWebClient.onModuleLoad() >> > done
>> > On Jun 24, 12:46 am, Anthony Baxter <anthonybax...@gmail.com> wrote: >> >> Hi folks,
>> >> We thought it might be useful to point at some starter documentation >> >> for the newwebclient, as well as pointing to some of the more >> >> interesting parts of the code for those of you interested in working >> >> with it.
>> >> Thewebclientis implemented using GWT >> >> [http://code.google.com/webtoolkit]. It is a testbed/sample for the >> >> newly open sourced editor, model and concurrency control code, which >> >> is also in GWT. The code for thewebclientcan be found in the >> >> directory gwt_src/org/waveprotocol/wave/examples/fedone/
>> >> Currently theclientallows you to view and create waves, as well as >> >> add replies and edit existing blips. It also allows you to add >> >> participants to an existing wave - both local and remote (via >> >> federation).
>> >> You can use it by running "ant all" (or "ant dist-server >> >> compile_gwt"), setting up the server in the same way as before >> >> [http://code.google.com/p/wave-protocol/wiki/Installation], then >> >> visitinghttp://localhost:9898in a browser. Login with a full >> >> user@yourdomain. At the moment, only Chrome, Safari 5 and Webkit >> >> nightly are supported, as they're the only browsers that have the >> >> required Websocket support.
>> >> Here's a brief look at some of the files to look at if you're >> >> interested in adding features or functionality to the currentclient, >> >> or to implement your ownclientusing the code be open sourced.
>> >> gwt_src/org/waveprotocol/wave/examples/fedone/simplewebclient - this >> >> directory contains the bulk of the user interface for theclient. In >> >> that directory, you'll find the following files of interest:
>> >> *client/CcStackManager.java
>> >> This file shows how to hook up theclientside concurrency control >> >> stack. The concurrency control stack takes care of sending messages >> >> out to the network, and applying real time changes to the current >> >> state of the editor.
>> >> *client/EditorWidget.java
>> >> This file hooks up the newly open-sourced editor widget to the view >> >> of a wave.
>> >> *client/WaveView.java
>> >> This is the right hand panel of the main view of theclient, showing >> >> the display of blips in the wave. As noted in the initial email
Hello,
I've been playing with your web client and noticed that it lacks the
"multiple carets" feature.
What I mean by multiple carets is that when 2 or more users edit the
same wave, each one's caret has a different color and its name above
(like in real GoogleWave).
With the current open source code, how difficult would it be to
implement such a feature ?
Or do you plan to open source that part of the editor too and when
would it be that?
Thank you!
On Jun 24, 9:46 am, Anthony Baxter <anthonybax...@gmail.com> wrote:
> We thought it might be useful to point at some starter documentation
> for the new web client, as well as pointing to some of the more
> interesting parts of the code for those of you interested in working
> with it.
> The web client is implemented using GWT
> [http://code.google.com/webtoolkit]. It is a testbed/sample for the
> newly open sourced editor, model and concurrency control code, which
> is also in GWT. The code for the web client can be found in the
> directory gwt_src/org/waveprotocol/wave/examples/fedone/
> [http://code.google.com/p/wave-protocol/source/browse?repo=io2010#hg/g...]
> in the io2010 repository. The code uses the (new in GWT 2.0) UiBinder
> approach to defining its user interface.
> Currently the client allows you to view and create waves, as well as
> add replies and edit existing blips. It also allows you to add
> participants to an existing wave - both local and remote (via
> federation).
> You can use it by running "ant all" (or "ant dist-server
> compile_gwt"), setting up the server in the same way as before
> [http://code.google.com/p/wave-protocol/wiki/Installation], then
> visitinghttp://localhost:9898in a browser. Login with a full
> user@yourdomain. At the moment, only Chrome, Safari 5 and Webkit
> nightly are supported, as they're the only browsers that have the
> required Websocket support.
> Here's a brief look at some of the files to look at if you're
> interested in adding features or functionality to the current client,
> or to implement your own client using the code be open sourced.
> gwt_src/org/waveprotocol/wave/examples/fedone/simplewebclient - this
> directory contains the bulk of the user interface for the client. In
> that directory, you'll find the following files of interest:
> * client/CcStackManager.java
> This file shows how to hook up the client side concurrency control
> stack. The concurrency control stack takes care of sending messages
> out to the network, and applying real time changes to the current
> state of the editor.
> * client/EditorWidget.java
> This file hooks up the newly open-sourced editor widget to the view of a wave.
> * client/WaveView.java
> This is the right hand panel of the main view of the client, showing
> the display of blips in the wave. As noted in the initial email
> announcing this code, right now this only displays top level blips in
> the conversation.
> In the gwt_src/org/wave/waveprotocol/examples/fedone/waveclient/common
> directory are GWT-specific versions of the client-server protocol
> implementation for the client. As we previously mentioned, we're aware
> of the deficiencies of the current client-server protocol, and will be
> looking to update it soon to be closer to the client-server protocol
> we use for the wave.google.com service.
> It's worth emphasising that the io2010 branch of the repository is a
> temporary thing - once the code is cleaned up and the tests are all
> working again, we'll be landing the code into the default trunk
> repository. Instructions for checking out a copy of the io2010 code
> can be found athttp://code.google.com/p/wave-protocol/source/checkout?repo=io2010
> Thanks,
> Anthony (on behalf of JD, Alex, Dan, Soren, Bob and Christian)
Hello,
I've been playing with your web client and noticed that it lacks the
"multiple carets" feature.
What I mean by multiple carets is that when 2 or more users edit the
same wave, each one's caret has a different color and its name above
(like in real GoogleWave).
With the current open source code, how difficult would it be to
implement such a feature ?
Or do you plan to open source that part of the editor too and when
would it be that?
Thank you!
On Jun 24, 9:46 am, Anthony Baxter <anthonybax...@gmail.com> wrote:
> We thought it might be useful to point at some starter documentation
> for the new web client, as well as pointing to some of the more
> interesting parts of the code for those of you interested in working
> with it.
> The web client is implemented using GWT
> [http://code.google.com/webtoolkit]. It is a testbed/sample for the
> newly open sourced editor, model and concurrency control code, which
> is also in GWT. The code for the web client can be found in the
> directory gwt_src/org/waveprotocol/wave/examples/fedone/
> [http://code.google.com/p/wave-protocol/source/browse?repo=io2010#hg/g...]
> in the io2010 repository. The code uses the (new in GWT 2.0) UiBinder
> approach to defining its user interface.
> Currently the client allows you to view and create waves, as well as
> add replies and edit existing blips. It also allows you to add
> participants to an existing wave - both local and remote (via
> federation).
> You can use it by running "ant all" (or "ant dist-server
> compile_gwt"), setting up the server in the same way as before
> [http://code.google.com/p/wave-protocol/wiki/Installation], then
> visitinghttp://localhost:9898in a browser. Login with a full
> user@yourdomain. At the moment, only Chrome, Safari 5 and Webkit
> nightly are supported, as they're the only browsers that have the
> required Websocket support.
> Here's a brief look at some of the files to look at if you're
> interested in adding features or functionality to the current client,
> or to implement your own client using the code be open sourced.
> gwt_src/org/waveprotocol/wave/examples/fedone/simplewebclient - this
> directory contains the bulk of the user interface for the client. In
> that directory, you'll find the following files of interest:
> * client/CcStackManager.java
> This file shows how to hook up the client side concurrency control
> stack. The concurrency control stack takes care of sending messages
> out to the network, and applying real time changes to the current
> state of the editor.
> * client/EditorWidget.java
> This file hooks up the newly open-sourced editor widget to the view of a wave.
> * client/WaveView.java
> This is the right hand panel of the main view of the client, showing
> the display of blips in the wave. As noted in the initial email
> announcing this code, right now this only displays top level blips in
> the conversation.
> In the gwt_src/org/wave/waveprotocol/examples/fedone/waveclient/common
> directory are GWT-specific versions of the client-server protocol
> implementation for the client. As we previously mentioned, we're aware
> of the deficiencies of the current client-server protocol, and will be
> looking to update it soon to be closer to the client-server protocol
> we use for the wave.google.com service.
> It's worth emphasising that the io2010 branch of the repository is a
> temporary thing - once the code is cleaned up and the tests are all
> working again, we'll be landing the code into the default trunk
> repository. Instructions for checking out a copy of the io2010 code
> can be found athttp://code.google.com/p/wave-protocol/source/checkout?repo=io2010
> Thanks,
> Anthony (on behalf of JD, Alex, Dan, Soren, Bob and Christian)
Hello,
I've been playing with your web client and noticed that it lacks the
"multiple carets" feature.
What I mean by multiple carets is that when 2 or more users edit the
same wave, each one's caret has a different color and its name above
(like in real GoogleWave).
With the current open source code, how difficult would it be to
implement such a feature ?
Or do you plan to open source that part of the editor too and when
would it be that?
Thank you!
On Jun 24, 9:46 am, Anthony Baxter <anthonybax...@gmail.com> wrote:
> We thought it might be useful to point at some starter documentation
> for the new web client, as well as pointing to some of the more
> interesting parts of the code for those of you interested in working
> with it.
> The web client is implemented using GWT
> [http://code.google.com/webtoolkit]. It is a testbed/sample for the
> newly open sourced editor, model and concurrency control code, which
> is also in GWT. The code for the web client can be found in the
> directory gwt_src/org/waveprotocol/wave/examples/fedone/
> [http://code.google.com/p/wave-protocol/source/browse?repo=io2010#hg/g...]
> in the io2010 repository. The code uses the (new in GWT 2.0) UiBinder
> approach to defining its user interface.
> Currently the client allows you to view and create waves, as well as
> add replies and edit existing blips. It also allows you to add
> participants to an existing wave - both local and remote (via
> federation).
> You can use it by running "ant all" (or "ant dist-server
> compile_gwt"), setting up the server in the same way as before
> [http://code.google.com/p/wave-protocol/wiki/Installation], then
> visitinghttp://localhost:9898in a browser. Login with a full
> user@yourdomain. At the moment, only Chrome, Safari 5 and Webkit
> nightly are supported, as they're the only browsers that have the
> required Websocket support.
> Here's a brief look at some of the files to look at if you're
> interested in adding features or functionality to the current client,
> or to implement your own client using the code be open sourced.
> gwt_src/org/waveprotocol/wave/examples/fedone/simplewebclient - this
> directory contains the bulk of the user interface for the client. In
> that directory, you'll find the following files of interest:
> * client/CcStackManager.java
> This file shows how to hook up the client side concurrency control
> stack. The concurrency control stack takes care of sending messages
> out to the network, and applying real time changes to the current
> state of the editor.
> * client/EditorWidget.java
> This file hooks up the newly open-sourced editor widget to the view of a wave.
> * client/WaveView.java
> This is the right hand panel of the main view of the client, showing
> the display of blips in the wave. As noted in the initial email
> announcing this code, right now this only displays top level blips in
> the conversation.
> In the gwt_src/org/wave/waveprotocol/examples/fedone/waveclient/common
> directory are GWT-specific versions of the client-server protocol
> implementation for the client. As we previously mentioned, we're aware
> of the deficiencies of the current client-server protocol, and will be
> looking to update it soon to be closer to the client-server protocol
> we use for the wave.google.com service.
> It's worth emphasising that the io2010 branch of the repository is a
> temporary thing - once the code is cleaned up and the tests are all
> working again, we'll be landing the code into the default trunk
> repository. Instructions for checking out a copy of the io2010 code
> can be found athttp://code.google.com/p/wave-protocol/source/checkout?repo=io2010
> Thanks,
> Anthony (on behalf of JD, Alex, Dan, Soren, Bob and Christian)
I got the same problem on Chrome 5 stable with Linux. Since the io2010 branch contains the 7.1.4 jetty, the patch won't help I suppose.
So I "upgraded" to Chrome 6 dev. Now it is continuously switching between Connected and Disconnected and I still can't log in. The server log looks like en endless repetition of:
> On Wed, Jun 30, 2010 at 10:13, Paul Carff <pca...@gmail.com> wrote: > > Google Chrome > > 5.0.375.86
> > On Tue, Jun 29, 2010 at 4:18 PM, Anthony Baxter <anthonybax...@gmail.com
> > wrote:
> >> which browser? you need one that supports websockets.
> >> On Wed, Jun 30, 2010 at 02:31, cyclingastrobrewer <pca...@gmail.com> > >> wrote: > >> > When I run the web client - I am not able to log in. I can enter a > >> > login address, but the login button is still grayed out. There is a > >> > message in the upper right corner "Never_Connected
> >> > In the bottom window I have this output: > >> > Tue Jun 29 09:14:58 GMT-700 2010[INFO] Attemping to reconnect > >> > Tue Jun 29 09:14:58 GMT-700 2010[INFO] SimpleWebClient.onModuleLoad() > >> > done
> >> > On Jun 24, 12:46 am, Anthony Baxter <anthonybax...@gmail.com> wrote: > >> >> Hi folks,
> >> >> We thought it might be useful to point at some starter documentation > >> >> for the newwebclient, as well as pointing to some of the more > >> >> interesting parts of the code for those of you interested in working > >> >> with it.
> >> >> Thewebclientis implemented using GWT > >> >> [http://code.google.com/webtoolkit]. It is a testbed/sample for the > >> >> newly open sourced editor, model and concurrency control code, which > >> >> is also in GWT. The code for thewebclientcan be found in the > >> >> directory gwt_src/org/waveprotocol/wave/examples/fedone/
to test the source of the problem I wrote a small web page that
connects to FedOne via websockets and sends an initial request
I receive two messages in return from the server:
{"version":1,"sequenceNumber":
0,"messageType":"ProtocolWaveletUpdate","messageJson":"{\"1\":\"wave://
indexwave/indexwave/dummy+root\",\"2\":[],\"6\":false,\"7\":
\"ch16\"}"}
{"version":1,"sequenceNumber":
0,"messageType":"ProtocolWaveletUpdate","messageJson":"{\"1\":\"wave://
indexwave/indexwave/dummy+root\",\"2\":[],\"6\":true}"}.
Then the websocket is closed. This means the error is either with
Chrome or with the Server. At least it is not the client code I
suppose.
> I got the same problem on Chrome 5 stable with Linux. Since the io2010
> branch contains the 7.1.4 jetty, the patch won't help I suppose.
> So I "upgraded" to Chrome 6 dev. Now it is continuously switching between
> Connected and Disconnected and I still can't log in. The server log looks
> like en endless repetition of:
> > On Wed, Jun 30, 2010 at 10:13, Paul Carff <pca...@gmail.com> wrote:
> > > Google Chrome
> > > 5.0.375.86
> > > On Tue, Jun 29, 2010 at 4:18 PM, Anthony Baxter <anthonybax...@gmail.com
> > > wrote:
> > >> which browser? you need one that supports websockets.
> > >> On Wed, Jun 30, 2010 at 02:31, cyclingastrobrewer <pca...@gmail.com>
> > >> wrote:
> > >> > When I run the web client - I am not able to log in. I can enter a
> > >> > login address, but the login button is still grayed out. There is a
> > >> > message in the upper right corner "Never_Connected
> > >> > In the bottom window I have this output:
> > >> > Tue Jun 29 09:14:58 GMT-700 2010[INFO] Attemping to reconnect
> > >> > Tue Jun 29 09:14:58 GMT-700 2010[INFO] SimpleWebClient.onModuleLoad()
> > >> > done
>> I got the same problem on Chrome 5 stable with Linux. Since the io2010 >> branch contains the 7.1.4 jetty, the patch won't help I suppose.
>> So I "upgraded" to Chrome 6 dev. Now it is continuously switching between >> Connected and Disconnected and I still can't log in. The server log looks >> like en endless repetition of:
>> > >> which browser? you need one that supports websockets.
>> > >> On Wed, Jun 30, 2010 at 02:31, cyclingastrobrewer <pca...@gmail.com> >> > >> wrote: >> > >> > When I run the web client - I am not able to log in. I can enter a >> > >> > login address, but the login button is still grayed out. There is a >> > >> > message in the upper right corner "Never_Connected
>> > >> > In the bottom window I have this output: >> > >> > Tue Jun 29 09:14:58 GMT-700 2010[INFO] Attemping to reconnect >> > >> > Tue Jun 29 09:14:58 GMT-700 2010[INFO]
> >> I got the same problem on Chrome 5 stable with Linux. Since the io2010 > >> branch contains the 7.1.4 jetty, the patch won't help I suppose.
> >> So I "upgraded" to Chrome 6 dev. Now it is continuously switching > between > >> Connected and Disconnected and I still can't log in. The server log > looks > >> like en endless repetition of:
> >> > On Wed, Jun 30, 2010 at 10:13, Paul Carff <pca...@gmail.com> wrote: > >> > > Google Chrome > >> > > 5.0.375.86
> >> > > On Tue, Jun 29, 2010 at 4:18 PM, Anthony Baxter < > anthonybax...@gmail.com
> >> > > wrote:
> >> > >> which browser? you need one that supports websockets.
> >> > >> On Wed, Jun 30, 2010 at 02:31, cyclingastrobrewer < > pca...@gmail.com> > >> > >> wrote: > >> > >> > When I run the web client - I am not able to log in. I can enter > a > >> > >> > login address, but the login button is still grayed out. There > is a > >> > >> > message in the upper right corner "Never_Connected
> >> > >> > In the bottom window I have this output: > >> > >> > Tue Jun 29 09:14:58 GMT-700 2010[INFO] Attemping to reconnect > >> > >> > Tue Jun 29 09:14:58 GMT-700 2010[INFO] > SimpleWebClient.onModuleLoad() > >> > >> > done
> When I run the web client - I am not able to log in. I can enter a
> login address, but the login button is still grayed out. There is a
> message in the upper right corner "Never_Connected
> In the bottom window I have this output:
> Tue Jun 29 09:14:58 GMT-700 2010[INFO] Attemping to reconnect
> Tue Jun 29 09:14:58 GMT-700 2010[INFO] SimpleWebClient.onModuleLoad()
> done
> On Jun 24, 12:46 am, Anthony Baxter <anthonybax...@gmail.com> wrote:
> > Hi folks,
> > We thought it might be useful to point at some starter documentation
> > for the newwebclient, as well as pointing to some of the more
> > interesting parts of the code for those of you interested in working
> > with it.
> > Thewebclientis implemented using GWT
> > [http://code.google.com/webtoolkit]. It is a testbed/sample for the
> > newly open sourced editor, model and concurrency control code, which
> > is also in GWT. The code for thewebclientcan be found in the
> > directory gwt_src/org/waveprotocol/wave/examples/fedone/
> > [http://code.google.com/p/wave-protocol/source/browse?repo=io2010#hg/g...]
> > in the io2010 repository. The code uses the (new in GWT 2.0) UiBinder
> > approach to defining its user interface.
> > Currently theclientallows you to view and create waves, as well as
> > add replies and edit existing blips. It also allows you to add
> > participants to an existing wave - both local and remote (via
> > federation).
> > You can use it by running "ant all" (or "ant dist-server
> > compile_gwt"), setting up the server in the same way as before
> > [http://code.google.com/p/wave-protocol/wiki/Installation], then
> > visitinghttp://localhost:9898ina browser. Login with a full
> > user@yourdomain. At the moment, only Chrome, Safari 5 and Webkit
> > nightly are supported, as they're the only browsers that have the
> > required Websocket support.
> > Here's a brief look at some of the files to look at if you're
> > interested in adding features or functionality to the currentclient,
> > or to implement your ownclientusing the code be open sourced.
> > gwt_src/org/waveprotocol/wave/examples/fedone/simplewebclient - this
> > directory contains the bulk of the user interface for theclient. In
> > that directory, you'll find the following files of interest:
> > *client/CcStackManager.java
> > This file shows how to hook up theclientside concurrency control
> > stack. The concurrency control stack takes care of sending messages
> > out to the network, and applying real time changes to the current
> > state of the editor.
> > *client/EditorWidget.java
> > This file hooks up the newly open-sourced editor widget to the view of a wave.
> > *client/WaveView.java
> > This is the right hand panel of the main view of theclient, showing
> > the display of blips in the wave. As noted in the initial email
> > announcing this code, right now this only displays top level blips in
> > the conversation.
> > In the gwt_src/org/wave/waveprotocol/examples/fedone/waveclient/common
> > directory are GWT-specific versions of theclient-server protocol
> > implementation for theclient. As we previously mentioned, we're aware
> > of the deficiencies of the currentclient-server protocol, and will be
> > looking to update it soon to be closer to theclient-server protocol
> > we use for the wave.google.com service.
> > Additionally, Alex North has posted a wiki page with a walk through of
> > the new model code
> to test the source of the problem I wrote a small web page that
> connects to FedOne via websockets and sends an initial request
> I receive two messages in return from the server:
> {"version":1,"sequenceNumber":
> 0,"messageType":"ProtocolWaveletUpdate","messageJson":"{\"1\":\"wave://
> indexwave/indexwave/dummy+root\",\"2\":[],\"6\":false,\"7\":
> \"ch16\"}"}
> {"version":1,"sequenceNumber":
> 0,"messageType":"ProtocolWaveletUpdate","messageJson":"{\"1\":\"wave://
> indexwave/indexwave/dummy+root\",\"2\":[],\"6\":true}"}.
> Then the websocket is closed. This means the error is either with
> Chrome or with the Server. At least it is not the client code I
> suppose.
On Fri, Jul 2, 2010 at 07:35, Torben <torben.w...@gmail.com> wrote: > Hi,
> to test the source of the problem I wrote a small web page that > connects to FedOne via websockets and sends an initial request
> I receive two messages in return from the server: > {"version":1,"sequenceNumber": > 0,"messageType":"ProtocolWaveletUpdate","messageJson":"{\"1\":\"wave:// > indexwave/indexwave/dummy+root\",\"2\":[],\"6\":false,\"7\": > \"ch16\"}"} > {"version":1,"sequenceNumber": > 0,"messageType":"ProtocolWaveletUpdate","messageJson":"{\"1\":\"wave:// > indexwave/indexwave/dummy+root\",\"2\":[],\"6\":true}"}.
> Then the websocket is closed. This means the error is either with > Chrome or with the Server. At least it is not the client code I > suppose.
> -- > You received this message because you are subscribed to the Google Groups "Wave Protocol" group. > To post to this group, send email to wave-protocol@googlegroups.com. > To unsubscribe from this group, send email to wave-protocol+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
> > --
> > You received this message because you are subscribed to the Google Groups "Wave Protocol" group.
> > To post to this group, send email to wave-protocol@googlegroups.com.
> > To unsubscribe from this group, send email to wave-protocol+unsubscribe@googlegroups.com.
> > For more options, visit this group athttp://groups.google.com/group/wave-protocol?hl=en.
> > --
> > You received this message because you are subscribed to the Google Groups "Wave Protocol" group.
> > To post to this group, send email to wave-protocol@googlegroups.com.
> > To unsubscribe from this group, send email to wave-protocol+unsubscribe@googlegroups.com.
> > For more options, visit this group athttp://groups.google.com/group/wave-protocol?hl=en.
On Jun 30, 6:46 pm, Flueras Bogdan <flueras.bog...@gmail.com> wrote:
> Hello,
> I've been playing with your web client and noticed that it lacks the
> "multiplecarets" feature.
> What I mean bymultiplecarets is that when 2 or more users edit the
> same wave, each one'scarethas a different color and its name above
> (like in real GoogleWave).
> With the current open source code, how difficult would it be to
> implement such a feature ?
> Or do you plan to open source that part of the editor too and when
> would it be that?
Hi Flueras,
Unfortunately, that code has not yet been open sourced because it
depends on a bunch of google specific profile stuff. I am actually
looking at it now though and it should be pretty easy to disentangle
so I'll probably just do that.
In the meantime, it is relatively straight forward to implement
yourself. Just register an AnnotationMutationHandler; with a
PaintFunction for colouring the selection range and a BoundaryFunction
for rendering the user's name at the boundary of the selection
annotation.
