Welcome ShopTalkShow listeners!

Hi there if you’re visiting from ShopTalkShow, it’s great that Dave and Chris are going to review PerformerJS.

I’m Chris and PerformerJS was born out of some JavaScript I wrote about … 6 years ago I think. It struck me that for simple JavaScript interactions and design patterns there was no need to write any JavaScript code, and even simple code like you get with jQuery plugins was putting some front-end people off using these modern techniques. You know what it’s like; you copy and paste something you saw somewhere but it doesn’t work. If you don’t understand how that code worked you’ve got no chance of fixing it.

PerformerJS means you don’t have to understand what $(function(){ $("hideme").hide(); }) means, you just need to add (mostly) sensibly-named CSS classes to elements for them to do stuff.

Click this to read more…

So that’s the history, what about the future? Well, at my day job we’re starting to use PerformerJS more and more so there’s a lot of motivation for me to keep the code up to date, add new features, and fix bugs. Plus attention from other developers is worth a lot, too.

Rather than make Performer do everything and the kitchen sink, I’d rather focus on providing the most used design patterns and functionality and leave the really clever stuff up to plugins that will do it better anyway, or developers who know JavaScript much better than me.

But that doesn’t mean PerformerJS is standing still, oh no. Coming very soon in "imagepopper", which allows you to pop open an image from a URL (like a larger version of a product thumbnail, for example) in a modal dialog, with the option to style it like a polaroid picture.

I’m also planning on completely rewriting the code from scratch. This is for two reasons:

  1. Some of the code – OK< most of it - is really old and not best-practices. I've learned a lot about JavaScript over the last couple of years, and it's time to put that knowledge to use.
  2. At the moment PerformerJS has a load of methods that translate an internal call into something that one of the supported libraries understands. With jQuery taking over the world I think it would be better to natively support jQuery, then provide versions of PerformerJS that includes translation code to work with MooTools and Prototype. And, potentially, other libraries as well (YUI, extJS etc). Any help with that would be gratefully received.

So, thanks for visiting. I hope you find PerformerJS cool and useful. If you find any bugs please let me know, and if you want to help out please get in touch. PerformerJS is now on GitHub, so fork me!.

Comments are closed.