fieldOfView | SPi-V devfolder based slideshows
Hi everybody,
scenario:
I have about 100 panos to display placed in a folder. I have the thumbnails of each pano with same file names but in another folder.
The interface have two modes, one with just next previous buttons, and thumbnail view.
a couple of questions:
1. I want to make a slide show of panos in a folder. Do i have to add each pano as a scene in the xml file? I mean consider there are 100 panos in a folder. We make a simple interface with next previous buttons. when i press next it display the next image in the folder.
2. Do i have make uielement node for each thumbnail and link it to specific pano/scene? is it not possible to load another pano in existing scene. Like the scenes panoelement changes to the filename of thumb but from a different folder.
I hope I am not too confusing :)
Mahboob
Re: folder based slideshows
I would do this not with pure SPi-V, but with a SPi-V extension using Director.
If you were to make one big XML file for all those panoramas, the resulting XML file would be very large and would take some time to process, Director has the 'power' to discover the exact number of panoramas in your folder, load the thumbnails etc.
Re: folder based slideshows
Different question - when I specify some scenes (for example 20) is there a way to choose next (or previous) one, so I could watch whole tour with two buttons?
Re: folder based slideshows
Yes there is (since 1.4.x), but it is not documented. I will create a scriptlet for it.
Re: folder based slideshows
I'd be interested in this as well.
Re: folder based slideshows
Here are two behaviors for next and previous buttons:
...<behavior id="next_scene_behavior">
<action event="release" type="setProperty" target="_scenes_id" property="index" value="_next" />
<action event="release" type="setView" scene="$_scenes_id" />
</behavior>
...
<behavior id="previous_scene_behavior">
<action event="release" type="setProperty" target="_scenes_id" property="index" value="_previous" />
<action event="release" type="setView" scene="$_scenes_id" />
</behavior>
...
Behind the scenes, there's a list of all scene ids named '_scenes_id'. Apart from '_next' and '_previous', you can also jump to the '_first', '_last' and a '_random' scene using this technique.
Re: folder based slideshows
Works perfect! Thanks
Re: folder based slideshows
Actually not so perfect ;)
I've found, that:
So i think, that those two actions doesn't update _scene_id value.
Re: folder based slideshows
I'll look in to that.Will be fixed in SPi-V 1.4.8
"list" example
I'm just getting back to trying to figure this out...
I think I get the behavior stuff... but I don't get the list stuff.
Can you post or point me to a sample of how the list node should look with a couple of scenes?
Thanks in advance - Graydon
EDIT:
Ignore the above - I'd delete it... but then the below wouldn't make sense.
OK - I know I ask dumb questions... forgive me in advance because I'm sure there are more to come.
I was thinking that with some sort of list - /list structure would be all of the scenes identified / listed in whatever order you wanted... kinda like a table of contents.
after looking at the scene switcher example... realized that wasn't the case...
I can't explain it... but I got it to work so that I can index back and forth through flats and panos all day long.
eventually I'll figure this stuff out
: )
Re: folder based slideshows
what would be a reasonable number of panoramas to deal with in a single xml file.
I would imagine there are a lot of variables... but any real world experience / guidance would be appreciated.
Re: folder based slideshows
It is basically not the number of panoramas that 'does it', but the amount of XML that needs to be parsed. You have to start worrying when your XML, along with any scriptlets, starts exceeding half a megabyte.
Whenever possible, if you're using scriptlets, make sure that you include them at the global node level, and not in each and every scene. If you include them in each scene, they will need to be parsed for each scene.