Hi,

Image tags can't be set with global actions, they need to be defined in the xml before load, but on the other hand, you wont have to change them often. A trick I could recommend is using styles alot. This way a hotspot only needs an atv and atv and a location.



Depending on your skillelvel with PHP. On projects where the xml changes a lot, I tend to write a parser. I start off dropping my panos on the droplet and upload it. Next I run my parser that runs through the tour.xml and reads out all the scene tags, view tags, hotspots etc Once thats done I can output it in any form I want, even JSON. Other benefits is, you could easily minify your tour or generate zip files for easy download. PHP has my preference, but it takes a bit time to setup for the first time.

Hi,

Zitat von »MarcW.«

But what´s for example with the <image>-node.
Some years ago it was like:
<image>
<left/>
<front/>
<right/>
...
</image>

nowadays the shorter way is:
<image>
<cube>
<mobile/>
</image/>

Just as note - both image syntax are still working of course and basically it doesn't matter which syntax is used - the <cube> one is only a nicer/shorter one.
And the <image> related settings are typically not changing... (unless you change the image itself)

Best regards,
Klaus

If you try to save space. You could use my minify tool (see my signature). Alsoo there's a use who made a npm and textmate script to minify. Could easily save 50% of the xml file.