Re: [Google Wave APIs] Re: Google Wave is Dead
To any googlers reading this. Whatever the hell happened to releasing a full wave server and client like promised at IO? Fedone isnt what you promised. Maybe if you stuck to your word adoption would have been better. Predictable yes, poorly managed even more so. The least you can do now google if your not going to develop it is make good on your word and open up the source youve been holding back and let the community do what you couldnt. 2010/8/5 Daniel França > I agree > I gave up some projects for wave cause missing API and features. > and no company will adopt that without the federation protocol working. > and how about the speed? why long time after wave is still really slow? is > this the XML protocol (it is XML, right?), the client? I don't know, but > when I showed google wave to someone, the first thing they noticed is "How > slow is that". > > On Wed, Aug 4, 2010 at 9:11 PM, AkiRoss wrote: > >> On Aug 5, 1:31 am, Brett Morgan wrote: >> > Pretty simple really. >> > >> > Wave had 60+ engineers assigned. If you assume each engineer costs >> somewhere >> > between 100k and 250k total spend (salary, office space, airfares, >> accom, >> > shares, ...), then you are looking at somewhere between $6M and $20M a >> year >> > in project cost. Plus servers, bandwidth, etc, etc. >> > >> > To justify that number takes a serious uptake of usage. As the press >> release >> > says, Wave wasn't seeing the uptake expected. So it got killed, and the >> > engineers will be moved on to other projects that are justifying their >> cap >> > ex spend. >> >> Interesting. If I may say something - as a wave fan and user really >> disappointed by this (predictable?) decision - is only that wave has >> been handled pretty bad. >> I'm sure the work done is something big, and that the 60+ engineers >> worked hard, but the way in which Google handled the whole thing... I >> felt pretty soon that wasn't done right. >> Surely, having hype helps when diffusing a product, but I think that >> introducing a platform is something pretty big, which requires long >> time, strong positions and most of all something that users may >> immediately appreciate. Wave has been launched with the formula "we >> want you to help us", but to assure the project a long way, you can't >> start with still have the standards to be defined. I think that Google >> should have first developed a complete and formal system, which - even >> if incomplete - could provide evident advantages (as Wave was when it >> was released), and immediately make the user base larger by providing >> usable API. Wave wasn't like that: the simple client-server protocol >> wasn't well defined and it was initially marked as low-priority, but >> most users don't care about server-side protocol. Google provides the >> Wave service, it's a good start, it's not important if you want it to >> become a widespread standard, first of all you must make users in the >> position of using that protocol. >> I started to look at wave with deep interest. Me as many others, >> thought that such platform could lead to new kind of communication >> tools, new kind of real-time interaction over the net, but when Wave >> has been released, we found only a playground to see if we had ideas >> on how to use the GUI you created. I'm not aware about any Python/Java/ >> C++ API that was enabling users to interact quickly with wave, so >> client-side projects and ideas - that are the only things that can >> lead to a widely used technology - were precluded. It took a whole >> year to see the client Open Source, and still was "too personal to be >> quickly used". >> Don't get me wrong: this strategy may work. If you open your >> technology and state your interests (e.g. replacing mails), some users >> may be interested in helping the "low level development", but most of >> users don't care about it and the real potential of the project well >> be evident only in the long term, because common developers will have >> to wait for defined protocols, working APIs, a working set of base >> features. This kind of project handling can lead to a pretty quick >> diffusion: even if partially wrong and incomplete, users could start >> to invent new things using the good platform it is. >> Instead, Google mostly said "hey, look how good is this technology. >> It's wonderful, but could be better. So, before making it usable, we >> expect you to help us in making it even better". This could work, but >> you can't expect to make money fast. >> Before having a good web client, I think it would have been better to >> give APIs that allowed users to develop their new applications, their >> new clients, around the platform capabilities. >> I always felt that something was wrong with Wave... And that >> "something" - I think - were the priorities. The project had the >> highest priority to make itself better, before make itself flexible >> and usable. >> Maybe I missed something, but this is how I see it (and how I >> ex
[Google Wave APIs] Re: Python cron call
On Tue, Nov 3, 2009 at 12:16 AM, Jeroen van Wissen
wrote:
>
> Did you manage to have it working ?
> I'd like to know how you got your script working that the cron job is
> called... coz I can't find any working example.
> My cron's won't get called :S
I'm working with Java (in the Preview) and I've setup robot cron
configuration as below. No matter what path I define it simply just
isn't called.
Can a Googler confirm this is a known issue and if we might expect a resolution?
http://wave.google.com/extensions/robots/1.0";>
8
>
>
> On Oct 5, 9:26 pm, André wrote:
>> I've since configured the cron job and my code is called, but I can't
>> parse the context in order to return some action. The code I have is
>> this:
>>
>> json_body = sys.stdin.read()
>> context, events = robot_abstract.ParseJSONBody(json_body)
>>
>> This is what comes in the wire:
>>
>> Incoming: {"blips":{"map":
>> {},"javaClass":"java.util.HashMap"},"robotAddress":"ajustestransparen...@appspot.com","events":
>> {"javaClass":"java.util.ArrayList","list":[]},"wavelet":null}
>>
>> This is the error I get:
>>
>> : 'NoneType' object has no attribute
>> 'get'
>> Traceback (most recent call last):
>> File "/base/data/home/apps/ajustestransparentes/1.336796539236639238/
>> wakeup.py", line 23, in
>> context, events = robot_abstract.ParseJSONBody(json_body)
>> File "/base/data/home/apps/ajustestransparentes/1.336796539236639238/
>> waveapi/robot_abstract.py", line 37, in ParseJSONBody
>> context = ops.CreateContext(data)
>> File "/base/data/home/apps/ajustestransparentes/1.336796539236639238/
>> waveapi/ops.py", line 598, in CreateContext
>> context.AddWavelet(data['wavelet'])
>> File "/base/data/home/apps/ajustestransparentes/1.336796539236639238/
>> waveapi/ops.py", line 539, in AddWavelet
>> wavelet = OpBasedWavelet(wavelet_data, self)
>> File "/base/data/home/apps/ajustestransparentes/1.336796539236639238/
>> waveapi/ops.py", line 127, in __init__
>> super(OpBasedWavelet, self).__init__(json)
>> File "/base/data/home/apps/ajustestransparentes/1.336796539236639238/
>> waveapi/model.py", line 92, in __init__
>> self.creator = json.get('creator')
>>
>> I've seen this error mentioned before
>> herehttp://code.google.com/p/wave-robot-python-client/issues/detail?id=11
>> but I'm not sure if this is a server problem or a problem in the
>> python API, or both.
>>
>> André
>>
>> On Oct 4, 1:22 am, André wrote:
>>
>>
>>
>> > Hello.
>>
>> > I'm looking for an example of a python robot which uses the cron
>> > facility to periodically update a wave. Is there one?
>>
>> > Is this already supported? I noticed theRegisterCronJob() call but
>> > this takes a path as a parameter... Do we have to implement a handler
>> > at another URL? What are we passed so that we can update a wavelet?
>>
>> > Best regards,
>> > André Cruz
>
> >
>
--
Damian Murphy
dam...@murf.org
--~--~-~--~~~---~--~~
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-api@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=en
-~--~~~~--~~--~--~---
[Google Wave APIs] Re: Debug option dissapeared from wavesandbox?
Thanks Pamela, Any update on this? Doesn't seem to be enabled in the new sandbox release. On Oct 14, 1:56 pm, "pamela (Google Employee)" wrote: > Hi Damian- > From my tests, we seem to have disabled (removed) it. I'll look into > re-enabling it. > > - pamela > > On Wed, Oct 14, 2009 at 11:51 PM, Damian wrote: > > > > > > > I am trying to debug a gadget that I have created. According to post > > below, > > >http://groups.google.com/group/google-wave-api/browse_thread/thread/9... > > > if I add ?ll=debug before the "#" in the URL of the Wave then I should > > see a "Show debug log" menu option at the top of the "Debug" menu. > > > I am not seeing this. have tried on Chrome 4.0.x and FF 3.0.x > > > This is the format of my url: > > >https://wave.google.com/a/wavesandbox.com/?ll=debug#restored:wave:wav... > > > Anybody else having this issue or am I doing something obviously > > wrong? Thanks for any help. > > > Damian --~--~-~--~~~---~--~~ 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-api@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=en -~--~~~~--~~--~--~---
[Google Wave APIs] Debug option dissapeared from wavesandbox?
I am trying to debug a gadget that I have created. According to post below, http://groups.google.com/group/google-wave-api/browse_thread/thread/9fca5fde5b56e37e/65acaf0b659214e5 if I add ?ll=debug before the "#" in the URL of the Wave then I should see a "Show debug log" menu option at the top of the "Debug" menu. I am not seeing this. have tried on Chrome 4.0.x and FF 3.0.x This is the format of my url: https://wave.google.com/a/wavesandbox.com/?ll=debug#restored:wave:wavesandbox.com!w%252Bxhk6VOEgA Anybody else having this issue or am I doing something obviously wrong? Thanks for any help. Damian --~--~-~--~~~---~--~~ 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-api@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=en -~--~~~~--~~--~--~---
[Google Wave APIs] Re: Is it possible to import GWT gadget into wave
Hi Johannes, would you add me to your wave as I am also developing a gwt/wave gadget with rpc? oxford .at. wavesandbox.com or d.w.flannery .at. googlewave.com Cheers, Damian On Oct 9, 1:58 pm, Johannes Feulner wrote: > Hi maxsap, > > gadgets written in GWT also run in Google Wave. I've written a gadget and > found one rough edge: BWT RPC doesn't work from within gadgets due to some > specific technical problems. I replaced the GWT RPC with JSON RPC and now it > works. > > Tell me your Wave or Sandbox username and I will send you a wave containing > my implementation and maybe we can discuss it in more detail. > > jofeux > > 2009/10/1 maxsap > > > > > > > Hello all, I am developing a gadget for the wave and while I was > > looking for a way to play audio from within the wave without using > > flash I got this idea.This article > > >http://groups.google.com/group/Google-Web-Toolkit/browse_thread/threa... > > says that it is possible to build a google gadget with GWT but could I > > use the same gadget as a wave gadget? > > thanks in advanced maxsap --~--~-~--~~~---~--~~ 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-api@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=en -~--~~~~--~~--~--~---
[Google Wave APIs] Re: Developer's Wave acct
its open again On Thu, Oct 1, 2009 at 4:24 AM, Wildcat wrote: > > It`s not available anymore...when Google will open subscribes > again? > > On Sep 29, 5:44 pm, Andrey Fedorov wrote: > > The sign-up is here: > > > > https://services.google.com/fb/forms/wavesignupfordev/ > > > > Cheers, > > Andrey > > > > On Tue, Sep 29, 2009 at 4:30 PM, A G wrote: > > > > > I'd like to develop for Google wave and would appreciate an account. > > > Thanks, AG > > > > --~--~-~--~~~---~--~~ 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-api@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=en -~--~~~~--~~--~--~---
[Google Wave APIs] Re: Google Has No Clothes!
Ahh yes, but the whole point of the beta as it currently stands was / is to allow dev's to get into wave, have a look around and get straight into making gadgets / robots etc to extend the functionality of wave before the general availability / public beta. The current beta has only limited seats according to google, and that is why there is a waiting list of devs to get in. While they are waiting to get in there are end users already inside sandbox doing no dev work at all and just complaining that wave is slow / buggy / hard to use. And thats what sparked my original comment - its sad to see some of the limited amount of seats in the sandbox being taken up by this sort of "dead weight" while there are productive and willing developers waiting to get their hands dirty. -Damian On Thu, Sep 10, 2009 at 8:23 PM, robin wrote: > > This is not about dev vs. non-dev. There are as many non-devs waiting > to get onto the sandbox as devs. There are also many non-devs who > enthusiastically support waves as not, as there are devs who will > oppose it. I also disagree with gg, but such partisan comments don't > really help. > > > On Sep 10, 1:57 am, Damian Guppy wrote: > > It saddens me that people like you who clearly are not devs have access > to > > the sandbox while some real developers are still waiting for access. > > > > On Tue, Sep 8, 2009 at 5:18 AM, gg wrote: > > > > > Does anyone here really think wave is going to take off > > > > > It is so slow, so buggy! You can't even delete waves you do not want > > > in your inbox! It is unbelievable to me how much money Google wastes > > > on stuff like this that just does not work! > > > Anyone remember this: > > > > >http://www.lively.com/goodbye.html > > > > > And even more unbelievable is how many developers follow them blindly > > > down the path > > > > --~--~-~--~~~---~--~~ 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-api@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=en -~--~~~~--~~--~--~---
[Google Wave APIs] Re: Google Has No Clothes!
It saddens me that people like you who clearly are not devs have access to the sandbox while some real developers are still waiting for access. On Tue, Sep 8, 2009 at 5:18 AM, gg wrote: > > Does anyone here really think wave is going to take off > > It is so slow, so buggy! You can't even delete waves you do not want > in your inbox! It is unbelievable to me how much money Google wastes > on stuff like this that just does not work! > Anyone remember this: > > http://www.lively.com/goodbye.html > > And even more unbelievable is how many developers follow them blindly > down the path > > > > --~--~-~--~~~---~--~~ 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-api@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=en -~--~~~~--~~--~--~---
