Spliting the script

[pooface]

Hi,

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.

Thoughts?

Regards.

[aba]

Hi,

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.

Thoughts?

Regards.

The reason is ease. By downloading a single (big) file, you get all functionality available immediately. Later, if you like the system, you can customize the download to increase the performance.

For those who want to develop, kP is available as source files from here:

http://kplaylist.net/getsrc. Instructions follows the archive file you get from here.

[eigan]

I have tried contacting you via the form on the website. But you havent answered..

Heia Norge!

[martinscott]

I have been trying to create a piece of Javascript that exicutes when you click the back button on my page. I have been looking at this for a while and I can't figure out why it isn't working. When someone clicks the back button, this javascript looks to see if there is any history going back. If there is, it will run "window.history.back()". If there isn't, it will go to cnet.com. Can anyone help me?

function backbutton()
{
if (window.history.length == 0)
{
document.location="http://www.cnet.com";
}
else
{
window.history.back();
}
}

low cost server hosting