This example shows how to use image-strips / sprite-sheets
as animated hotspot images.
The images will be animated by dynamically changing the crop setting
(which 'cuts-out' a certain region of the image) by xml action codes.
The do_crop_animation <action>
in this example has no dependencies and can be easily reused in own examples.
It supports vertical, horizontal and tiled image-strips and loops the images from left-top to right-bottom.
As parameters the pixel-size of one frame and the favored frame-rate need to be set.
In this example the soundinterface plugin will be used
to extend krpano with support for sounds. That plugin needs to get loaded once and then there are actions
available for playing sound.
To automatically start and stop the background sound only for the current pano (e.g. when using several scenes)
the playback will be controlled by pano-local events.
Additionally a small button is included to pause and resume the sound.
This is an example to demonstrate the possibilities of the new WebGL-based blending modes in version 1.19.
The different blending-modes are custom settings for the blend
parameter of the loadpano() / loadscene() actions.
Beside of this the examples shows how to use custom xml structures (the <blendmodes> element is a custom one)
and how to drag layers and to use the scrollarea plugin.
Several example usages of the new combobox.xml plugin.
The examples show how to define the combobox elements statically and dynamically and how to customize the design.
This example rotates images accordingly to the current viewing direction.
The compass elements are build-out of several layers and images - and one of these images
will be rotated when the viewing changes.
Define a custom right-click / long-press-touch context-menu.
This exampels shows to define a custom context-menu items - in this case here with options to
change the control mode and to change the viewing projection.
The example also shows how to include html content (like an image) inside the context menu item
(but this works only in the HTML5 viewer).
This tour was first build using the MAKE VTOUR droplet and then modified manually.
For navigating between the rooms hidden polygonal hotspots are used.
All panos were aligned the same way during stitching and with that and by using the
KEEPVIEW flag it's possible
to keep the same looking direction when moving through the panos.
This is a tour made fully automatically with the MAKE VTOUR (MULTIRES) droplet (but to save download space
in the package, the multires images were removed and replaced by the smaller single-res images).
The input images in this example were geo-tagged - and with that the map and the map-spots were automatically enabled and added.
This is a mainly custom made tour. The images itself were build by using the MAKE VTOUR droplet, but
the skin and the hotspots are custom made xml code.
This is a fully manually built tour (where the images itself were generated using the droplets of course)
without a given skin.
As navigation a small map with spots, where the active one shows a radar cone, and animated
hotspots in the panos are used.
This example shows a possibility for how to drag the hotspot position.
Additional the position of the hotspot will be formatted as xml code and shown via the
textfield plugin.
This example shows how to drag <layer> elements and the difference between
maskchildren=true
(clip children elements) and maskchildren=false (no clipping).
Example for the direct usage of fisheye images (without stitching or dewarping).
The fisheye image parameters could be determined using PTGUI.
See here for more.
This could be used with video files or mjpeg live streams (e.g. for dome webcams) as well.
This is an example about the hotspot flying setting.
By tweening it from 0.0 to 1.0 a hotspot can move from it's
normal position inside the pano to a fixed position on the screen.
The example manages the state of several hotspots. When one hotspot is flying out, the others will
automatically fly back in.
Field-of-view type comparison and fixed screen-size aspects.
The view.fovtype setting defines
how the view.fov field-of-view setting
relates to the window-size.
Here a comparison of the different settings and how they work on different screen-size aspects.
This is a simple example for how to include the
googlemaps plugin and set a spot on it.
In Flash there is no Google Maps API available anymore - there the
bingmaps plugin will be used instead.
Note - the Bing Maps API requires an API key for using.
This example shows two videoplayer xml scripts - one plays a normal videofile - and the other plays a Youtube video.
During the video playback a darken background layer will cover the pano and the other user interface elements.
In this example a distorted hotspot image that shows a different pano content will be used.
That hotspot will be faded-in when hovering an invisible polygonal hotspot, which acts as 'hit-area' for the
image hotspot.
This example shows three possibility to visualize the pano image loading progress -
as image-based loop animation (an image-strip with a crop animation),
as loading bar (by changing the size of a layer element)
and as percent text.
It would be possible just to include one of the example xml files to add that kind of loading progress animation
to an own pano or tour.
Show two panos for comparison. Either side-by-side or split into half-half.
For this example the stereo-support of the krpano viewer is used.
For loading stereo images see here:
image.stereo
and for rendering stereo images here:
display.stereo
An example 'tooltip' implementation - by assigning the 'tooltip' style and a 'tooltip' attribute
to an layer or a hotspot, it will automatically show the given tooltip text when the element will be hovered.
Videopano - a fully featured panoramic-video player skin.
This is an example for a panoramic video player.
It provides a simple xml interface for adding several video-quality files.
For using / adding own videos they would be only added once in the videopano.xml file.
The user interfaces provides: play/pause controls, a seeking bar, volume/mute control,
options for changing the quality, the playback rate and the viewing projection
(including a special 'flat' view), fullscreen buttons, gyroscope control and VR support.
The layout and design can be easily adjusted with a few settings in the videointerface.xml.