I agree with Daniel. Here's what I replied to Jeremy in our email conversation: I think right-clicking to manually check it will actually save them some load. If I want to know the up-to-date number right now, then I'll go to http://wave.google.com and load everything just to check it. By enabling the right-click on-demand, it'll relieve demand from the server because I won't be loading everything that wave requires (which is a lot) every time I'm curious about my account.
If they don't see eye-to-eye on that reasoning, I think your proposed mid-point (refresh only if it's past 5 minutes) would be okay as long as the UI shows the "loading" icon briefly so the user doesn't think it didn't catch the oncontext event. On Oct 15, 9:50 pm, Daniel Wagner-Hall <[email protected]> wrote: > While this makes sense for doing frequent calls in the background, > right-clicking the extension really is just a shortcut to actually > going to the Wave site - if anything, you're actually *saving* them > the bandwidth of dealing with serving up images and things... > > > > On Thu, Oct 15, 2009 at 3:46 PM, Jeremy Selier <[email protected]> wrote: > > > Thanks again Nathan, I will look into that! > > > I will copy paste here what I answered you about the right click > > refresh: > > > The thing is, the Wave team contacted me to not over-request their > > servers. So I set the time to 30 minutes. We get agreed that the best > > would be to set by default to 30 minutes and to offer in settings a > > frequency of 5 minutes at the minimum. As I don't have time to add > > settings in my extension, I just set to 30 minutes. Your right click > > option is cool but this is not what I have agreed with the Wave team. > > So I will maybe change the behavior. > > > What do you think of : right click = refresh if it's been 5 minutes > > since the last refresh, if not indication to wait for XX minutes > > before asking for refresh. > > > On Oct 15, 4:40 pm, "Nathan J. Brauer" <[email protected]> wrote: > >> Excellent work. I was just thinking about my want for this kind of > >> extension today actually. > > >> I've just made my own modifications to this... > > >> Changes: > >> - Now features more informative icons. They tell you when the > >> extension is checking for new waves, and if there is an error (ex not > >> logged in) retrieving the json. > >> - Right-clicking the button will manually check your wave inbox > >> (before the 30 minute interval) > >> - Added credits to the original Gmail extension, Jeremy, and myself in > >> the manifest description > >> - Changed the version to 1.3.2 > > >> If you'd like to try my version, you can go > >> here:http://thebrauergroup.com/labs/ > > >> Jeremy, you're more than welcome to make these changes in yours and > >> push them through with your update URL. I didn't change the update URL > >> in the manifest so anything after version 1.3.2 will clear out the > >> changes I made. > > >> Let me know what you think :) > > >> On Oct 14, 10:20 pm, Jeremy Selier <[email protected]> wrote: > > >> > Hi folks, > > >> > I just released a simple extension to check for Google Wave unread > >> > Waves. It's based on Gmail checker so there's nothing amazing in > >> > there. Just thought it could be interesting for some people here. It > >> > currently checks only for wave.google.com and not the google apps > >> > wave. > > >> > You can get it here > >> > :http://www.jeremyselier.com/fr/entry/chrome-extension-google-wave-che... > > >> > Let me know if you have any problems with it. > > >> > -- > >> > Jeremy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" 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/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
