I ended up getting one of those nifty Cr-48 laptops that Google has been giving out. I haven’t written anything about it because, well, it’s like using Chrome. If you’ve used the browser (and especially if you’re a power user) you won’t find much new. There’s very little that I do outside of the context of a browser, and if I consider the Chrome OS laptop my portable machine (to be used in conjunction with a desktop), there’s really nothing that can’t be done online.
The one thing I do miss from the desktop world is desktop notification systems (like Growl, or the native Windows/Linux ones) that I could use with my native Campfire clients. Luckily Chrome (and by extension Chrome OS) supports desktop notifications natively as well, so I created an extension that will take care of this in the browser-only world of Chrome.
Chrome Campfire Notifications is very bare bones at the moment, but I plan to release updates to allow for some amount of configuration. It does work as advertised, though, giving you notifications when Campfire messages come through.
Thanks for the great campfire extension! Any word on updates? I’d like to be able to change notification settings (i.e. display time, permanency, etc.)
Is there are quick way to make notifications remain permanently on desktop until closed?
you can email me direct at gt[at]attorneysync.com
I’ve updated it with an icon in the address bar that allows you to disable/enable notifications, but was waiting for someone to actually say that they needed the persistence options before I implemented them. Guess it’s time to get to work.
Are you looking to open source the code for this or interested in contributors? I might be willing to help out with some of the requested features and have a few features I’d like to see myself.
I am looking into some way to do this. I’m no longer using Campfire, and don’t think it would be a good idea to pay for a campfire subscription solely to develop this extension. Even if I put the code up on Github, I wouldn’t be able to test contributions before publishing them to the Chrome extension gallery. I’ll likely put the source up and then change the name of the extension so someone else can take over development.
Being an extension, its source is inherently “open” (that is you can poke around at it), if you want to mess with it in the mean time.