search

vega113 / walkaround

Automatically exported from code.google.com/p/walkaround
Apache License 2.0
0 stars 0 forks source link

Resurrect chrome wave activity notifier #87

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Maybe i'm just overlooking something, but I don't see notification of 
Walkaround wave activity as an available feature or as something on the 
roadmap.  Resurrecting the Chrome wave activity notifier is all I have in mind.

Drew

What steps will reproduce the problem?
1.
2.
3.

What is the expected output?  What do you see instead?

What browser and browser version are you using?  On what operating system?
Chromium 17.0.963.83 (Developer Build 127885 Linux) Ubuntu 11.04

What URL does your browser show when the problem occurs?  Did you compile
walkaround on your machine, or are you using a public instance?
Public instance.   wavereactor.appspot.com

Original issue reported on code.google.com by r.drew.d...@gmail.com on 26 Mar 2012 at 7:36

GoogleCodeExporter commented 9 years ago

Original comment by oh...@google.com on 27 Mar 2012 at 7:22

GoogleCodeExporter commented 9 years ago

Original comment by oh...@google.com on 27 Mar 2012 at 7:29

GoogleCodeExporter commented 9 years ago 
Yuri made a version of the notifier that is compatible with Apache Wave: 
http://mail-archives.apache.org/mod_mbox/incubator-wave-dev/201204.mbox/%3CCAH7_
oNLTzbBH33ErbA83k2yxnf_y3TAEzCJc-3sXH7yzke_TrA@mail.gmail.com%3E

It should be relatively easy to modify the walkaround server side to support 
the endpoints it requires.

Original comment by oh...@google.com on 28 Apr 2012 at 6:03

GoogleCodeExporter commented 9 years ago 
I do not think that would be the best course of action.  As I said in the 
Apache Wave mail thread, the extension only works if the user is signed in all 
the time, and a better plan for the long-term might be to make walkaround work 
with data API-based notifiers like the one Google built.

Feel free to correct me if that would not be a better idea.

Original comment by zmy...@gmail.com on 29 Apr 2012 at 8:22

GoogleCodeExporter commented 9 years ago 
In this case, the advantage of building on the existing code, even if it's not 
perfect, is that it's less work than building something new.

Why is it a problem if the extension only works if the user is signed in?  
Walkaround should leave you signed in by default -- do you sign out manually 
every time you're done?

Original comment by oh...@google.com on 29 Apr 2012 at 8:18

GoogleCodeExporter commented 9 years ago 
While I like to stay signed in all the time, I know people who do prefer 
signing out when they are done.

That said, you have a good point—using existing code would be easier and 
faster than building something new.

Original comment by zmy...@gmail.com on 29 Apr 2012 at 11:37