Nekkid Ninjas

Follow up:

Because of the differences between the two versions it is necessary to create 2 versions of the same extension with slight differences in the code.

This can (and often does) cause problems, first we have to manage the 2 different sets of files, then we have to track the bugs (if any) separately as sometimes they do not have the same bugs, which means version numbers often don’t stay the same.
Then we have to maintain both the files, updating them with new functionality, checking both of them, re-uploading them. Ect ect

So as you can see, something that takes a day to develop can take a week to manage, and no amount of time spent on customer support.

So what to do in a situation like this?

Well you could just put up with it and look at it as a necessary evil
Or
You could do it half cocked and make it Joomla 1.5 legacy compatible
Or finally
You can be a ninja, put in a bit of effort and make the same thing work on both versions.

I am currently playing around with a few ideas on my new extension project, that I am confident will work.

will it be a viable solution for all our extension releases? Well I’m not sure, but it certainly is an interesting one.

So stay tuned for the second part of this post, and find out if I am right.

Woochaa!