Plugins and other features

Hi!
You need look examples with krpano package(download from krpano website) and see code in any example with plugin!
I recommend to you use text editor Notepad++ or analog with syntax highlight!
It is not difficult unless of course simple and standard features in other cases need to learn and read the forum or write to it

In short, the use cases and pasting the code a lot. You can put everything in one file, and you can insert a link to an external file, as in the example skin in krpano example and etc.:
<include url="vtouskin.xml" /> - all interface settings are stored in a separate file, that is convenient for editing and use in future projects!
To be separate action functions and plugins(layers, hotspots) are inserted inside scenes use keep=false, also used other methods(events newpano, actions if... and more)
...a lot of examples and features, but start with simple examples from krpano package by Klaus!

good luck!

Imagine a tree ...
If you insert an action (plugin) in its trunk, it will affect all the branches of the tree. If you use only the branches, it will only apply to them)
All attached files in the main file, the result will be read as a single file, it is the main factor

Example:
We load tour.xml in web html page of virtual tour:

<krpano version="1.16" title="" onstart="">


     <include url="skin/vtourskin.xml" />
     <include url="skin/compass.xml" /> 
	<plugin ....                       />
	<action ....                      />


	<scene name="scene_01" .....>
		<plugin ....                       />
		<action ....                      />
                <hotspot name="spot1"  />
		<hotspot ....                  />
	</scene>


	<scene name="scene_02" .....>
		<plugin ....                       />
                <hotspot name="spot1"  />
		<hotspot ....                  />
	</scene>
</krpano>

OR we load core.xml with other external xml's in web html page of virtual tour:

<krpano version="1.16" title="" onstart="">
     <include url="skin/vtourskin.xml" />
     <include url="settings.xml" />
     <include url="tour.xml" />  
</krpano>

Adhere to rules - code as in html will run and read from top to bottom. In general, all action(plugins, layers and etc) in included xml's run a globally for tour! Plugns, layers and hotspots put inside <scene></scene> will work inside the scene , but can call external actions...
But again, you can control the all actions that they work under certain conditions, excluding them, using the conditions(if, ifnot) and events! It is a more advanced method.
Write and distribute the code you need so that was handy edit it and read, as well as to use (include) it in other and future projects!
Maybe the programmer would have explained to differently, but I am also far from this - without experience in programming, and told in simple words, as a regular user)
I hope more skilled will correct me if I'm wrong!