On http://www.waveprotocol.org/code/wave-in-a-box-task-list: "The Google Wave team is putting finishing touches on a new, improved wave panel, which will be released as open source in early October 2010."
On Oct 11, 10:31 pm, James Purser <[email protected]> wrote: > By "new wave panel" do you mean the Rich Text Editor or the client overall? > > > > On Tue, Oct 12, 2010 at 1:30 PM, Gamer_Z. <[email protected]> wrote: > > This reminds me: I read that a new wave panel was supposed to be > > released in “early October”. Has this happened yet? > > > On Oct 11, 10:23 pm, James Purser <[email protected]> wrote: > > > No, your build processes sound like they worked fine. > > > > Wave In A Box is still very much a work in progress. It isn't anywhere > > near > > > the level of the Google Wave service at the moment, but it is growing > > > rapidly. > > > > James > > > > On Tue, Oct 12, 2010 at 1:12 PM, MissChatter <[email protected]> > > wrote: > > > > I got it running on my MacBook Pro (to test) and a Solaris server > > > > (where I ultimately want to run it), but it in no way resembles the > > > > Google Wave my discussion group is accustomed to. There are no > > > > usernames/timestamps in blips and I don't see a way to save a blip > > > > other than click out of it. Also, can't seem to do nested replies. > > > > > I've looked at all the documentation and roadmap stuff and I guess I'm > > > > not sure what to expect at this stage. We use Google Wave heavily and > > > > I'm trying to replicate it for when the site shuts down. > > > > > Firefox shows "NEVER_CONNECTED" so it only seems to work in Chrome and > > > > Safari (on a Mac). Firefox on the Solaris host doesn't even allow you > > > > to click the "Login" button. > > > > > But even logging in as an added user, active waves don't show up in > > > > the left pane. But if I refresh on the user who started the wave and > > > > re-login, it shows up. > > > > > So I'm guessing this has a long way to go? Or did something go wrong > > > > in both of my build processes? > > > > > -- > > > > You received this message because you are subscribed to the Google > > Groups > > > > "Wave Protocol" group. > > > > To post to this group, send email to [email protected]. > > > > To unsubscribe from this group, send email to > > > > [email protected]<wave-protocol%2bunsubscr...@goog > > > > legroups.com> > > <wave-protocol%2bunsubscr...@goog legroups.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 [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<wave-protocol%2bunsubscr...@goog > > legroups.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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
