Quoted from "AdolfoJunge"

is there any way to avoid this?

Quoted from "klaus.krpano"

Hi,

the editor plugin doesn't directly 'unencrypt' the xml, it rebuilds the xml structure dynamically by reading out all currently elements and settings.

Quoted from "AdolfoJunge"

is there any way to avoid this?

Yes, you can disable the external interfaces and embed the xml and plugin files into the swf with the krpano Protect Tool.

Best regards,
Klaus

Quoted from "klaus.krpano"

Right, sorry, I haven't re-read your first post about the HTML5 usage .
Then in this case there is only the possibility to encrypt the xml itself, but reading out variables by the interface will be possible.

If your are planing to write very special and unique code, then you could also write a Javascript plugin and protect your code there and optionally also with the krpano encryption. Then your code will be not read-able from extern in any way.

Best regards,
Klaus

Quoted from "Zephyr"

In the end it's all javascript, so it's always open. Google chrome autoformats minified code for example when viewed in source, makes it pretty readable. Only thing you can do is make it a bit harder with uglify/obfuscating. Which makes it harder to read and alter, but works fine if you just copy paste.

Or make it reliable to a server. For example, I have javascript apps that communicate through ajax with REST. Cool that you can copy paste code, but it wont do anything without the proper json responses of the server. Even this would be hackable by mimcing the server. But come on it's just a panorama tour with a graphic map etc :D :p

you could alsoo put alot of footprint in there. iow comments, author mentions, start functions with AJ (AdolfoJunge)

Rather share code on the forum ;) I bet 90% of the code you have now is from the droplet, combined with some nifty code and tricks from people on this forum.