Thank you Jon for the kind reply and I agree 100% with Morten and the lovely success in how you've managed to load your tour so seamlessly.
So the only sequencing that you overtly and are directly controlling in the Røros church tour are the initial graphic elements mentioned through the
- Code: Select all
load_sequence_1 - > done - > load_sequence_2
functions?
Or more simply put, are all loading directions handled via functions?
I confess that I do not fully understand much about how the so-called "preloader" works (and the many other aspects of FPP and FFC). The user may interact with the preloader through the FFC GUI and which appears to have been first introduced in December 2008 (as mentioned in
this thread) and which preceded the development of the so called "Tourificator" very shortly thereafter.
Can / do you use the preloader feature in loading functions ?
Can / do you use the preloader feature in loading files other than pano files ?
At
its debut, preloader is described thus:
Preloader:
Enable/Disable preloader
Simultaneous loads (decide how many files are loaded at the same time)
Once the Tourificator's problems have been solved, all panos in the tour would appear in the list, where you can decide which images/mov's/mp3's/videos/xml's/png's/jpg's/swf's etc. would load first and in which order.
Using this in combination with Poorificator is absolutely possible, and you can provide the URL to the images/files you want to preload.
This enables next pano to load in the background, while the user is viewing the first pano, cutting short the time people have to wait before the next pano is ready.
Can there be more than one instance of preloader; e.g.,
- Code: Select all
<preloader1>
<links maxConnections="1">
<link url="files/plugins/ffc_mediaplayer.swf"/>
<link url="files/media/sound/Doug%20Bellis%20-%20Track%202.mp3"/>
</links>
</preloader1>
forces earliest loading of only player and music track separately before:
- Code: Select all
<preloader2>
<links maxConnections="1">
<link url="files/visualFiles/7849_u.jpg"/>
<link url="files/visualFiles/7849_d.jpg"/>
<link url="files/visualFiles/7849_l.jpg"/>
<link url="files/visualFiles/7849_r.jpg"/>
<link url="files/visualFiles/7849_f.jpg"/>
<link url="files/visualFiles/7849_b.jpg"/>
</links>
</preloader2>
And then the follow up question is:
Can preloader2, preloader3, etc., be called through a function ?; for example, at the beginning of loading pano1 call for the loading of files a, b and c; then through an event / function overtly call for next batch of files to be loaded ?
Another thing related to this issue is the
DEFAULT creation of grayscale panos used during transitions and that are introduced during the "Tourificator" process and specifically the creation of the loadPano functions. I'm uncertain if their use enhances the loading experience for the website visitor or if employing the grayscale panos actually compounds the problem by gobbling up bandwidth which may be better served elsewhere. They do give the visitor something to see, though I wonder about any alternatives.
And what of the order in which things are listed in the .xml file ? Surely those things must be looked at by the browser in knowing what to get and in what order beginning with the
parameters and its own itemized list of files:
- Code: Select all
<parameters>
panoName = files/visualFiles/8855
panoType = cube
segments = 30
zoomMax = 2
pan = 18.89
frameRate = 60
loaderTextColor = 0
loaderBackColor = 0
layer_1 = files/plugins/hotspots.swf
layer_101 = files/plugins/ffc_contextmenu.swf
layer_3 = files/plugins/ffc_tooltips.swf
layer_100 = files/plugins/logoMeter.swf
layer_98 = files/plugins/ffc_mediaplayer.swf
layer_58 = files/plugins/ffc_preloader.swf
</parameters>
The newly restored church and more over your tour Jon serves as an excellent example of how things can be elegantly loaded and I very much appreciate your explanations into its inner workings.
Kindest regards,
Kelly