Managing extension conflict on js files

Question

I have and (community) extension that switches the product images when you change the options of a configurable product. This works great.
I've also developed some extension that changes the select elements of the configurable options to images and labels. Again this works as expected.
Now the issue. Both of them need to remove from the head block the varien/configurable.js javascript file that handles the configurable products and add their own file. So basically both of them override the js class Product.Config. Both of them need to override the initialize function in the class so I cannot add in my extension Product.Config.prototype.initialize = function(){...}. Or can I?
As you can imagine they don't work together.
Is there any way to solve these kind of conflicts without cloning the changes that the community extension brings to the table into my js file and building on that?

Answer 1

As mentioned in my comment above, depending on the code involved you can subclass the prototype Product.Config and inherit from it. So for example something like this:

var MyProduct.Config = Class.create(Product.Config, {
    initialize: function($super, config){
        $super(config); //this calls the parent initialize
        //do your custom stuff here        
    }
});

More info on prototype's inheritance is here.

As you have guessed afterwards you would use

spConfig = MyProduct.Config(...)

instead of

spConfig = Product.Config(...)