Why was Tab Slideshow created?
Several years back, I was working in a NOC where we had several monitoring and dashboard web sites we wanted to have visible on our bigscreen. Rather than build a complicated webapp with portlets and web services and fade transitions, Tab Slideshow was born as a simple solution to keep an eye on multiple webpages. (Six months later it had been replaced with a "one dashboard to rule them all" webapp, but despite that I've kept maintaining Tab Slideshow over the years.)
What's next for Tab Slideshow
Tab Slideshow is supposed to be a simple solution, not a "everything but the kitchen sink" tab powerhouse. (If you want one, there are several good power-user, lots-of-features tab add-ons on AMO).
I've added a few features that stay true to the problem the extension is trying to solve. These are pretty much driven by requests from end users, like the ability to turn it on and off (pretty obvious feature, but I didn't need it to solve my initial problem) and customizable tab refreshing instead of all or none.
Future planned features:
- Customizable tab cycle delaying
- Replace current ad hoc tab customizing by URL matching logic
About the Developer
|User since||March 5, 2007|
|Number of add-ons developed||2 add-ons|
|Average rating of developer's add-ons||Rated 4 out of 5 stars|