Hygiene and reusability.

Say, you have a very deep tree structure on your webserver, with krpano xml files all over the place. You could place the *.swf and *.js files in each of the folders. But it is much smarter to have only one copy of these files, so if you ever want to upgrade krpano to a newer version you only have to update one set of files. So if you wanted to use a plugin in those xml files, you *could* use a path with lots of ../../../'s, but let me assure you that you will quickly loose count. %swfpath% makes it more "neat". Plus it will not break if you ever decide to move those xml files to different level in the folder tree.

Another scenario is if you have generic xml files that you use in multiple projects using <include>. By using placeholders you can make these xml files truly generic and independent of their location on our webserver.

Krprotect has it's own placeholders in the gui to resolve paths.

I have to say that I have exhanged them all to standard paths. I discovered already at my first tests that they did not work on iPad with the structure I have.

I assemble all the data in 1 folder and place the start index.html outside this folder.
The place holder work with the the standard structure that the vtour produces but if you move the html outside the folder the paths only work in flash.

Hans