I've had a quick trawl through the archives and know this has come up at least once in the past but not answered, so forgive the repeat.
Is there a particular reason why the script is in one big file? and are there any plans to give the option to split the files?
It would make much more sense from a developer and performance point of view to have multiple file so that it can be changed to add new features much more quickly and cleanly.
From a performance point of view, serving images (for example) from a static image file is much faster than the decoded base64 images embedded in the script. Further language translations do not have to be cached by the webserver unless thay are needed again yielding performance increases.
My interest is to use kplaylist as a frontend to the MediaMVP from hauppauge. I've had a reasonably successful project but felt very annoyed by the size of the script when making changes.
This can be an extension to the customized download option available already.