Hey, we love you too Cheer, even more maybe when we see TW7 :)
Quote
I see, the deep link feature is implemented in this (TW7) release. Actually, in almost the same way i did it before - using TW API.
During the loading of the tour a small javascript code checks if the main tour application (twviewer.swf) is loaded and API is available. If yes, the code grabs a variable named firstscene from URL and switches the scene.
If you want, you may try it out yourself:
http:\\path_to_your_tour\your_tour_name.html?firstscene=preferredscene
My Tourweaver components: http://www.optitecha.lt/categories/3
During the loading of the tour a small javascript code checks if the main tour application (twviewer.swf) is loaded and API is available. If yes, the code grabs a variable named firstscene from URL and switches the scene.
If you want, you may try it out yourself:
http:\\path_to_your_tour\your_tour_name.html?firstscene=preferredscene
My Tourweaver components: http://www.optitecha.lt/categories/3
P.S. I've got it working. TextAreas still doesn't work, but i don't need them yet.
Basicly, the solution is:
* to create (save as) different project for every customer who needs a deep link and set starting movie track to specific scene (which wants a customer).
* put into web (ftp) (only) one published project;
* copy config_xxx.bin and images_xxx.zip files from all projects into tour folder on web;
* provide links for customers to specific html files.
This gives one tour and different entry points. Downside is that you have to maintain the same tour copies on your disk, but if your customers pay good money - why not.
Best wishes,
Madmux
My Tourweaver components: http://www.optitecha.lt/categories/3
Basicly, the solution is:
* to create (save as) different project for every customer who needs a deep link and set starting movie track to specific scene (which wants a customer).
* put into web (ftp) (only) one published project;
* copy config_xxx.bin and images_xxx.zip files from all projects into tour folder on web;
* provide links for customers to specific html files.
This gives one tour and different entry points. Downside is that you have to maintain the same tour copies on your disk, but if your customers pay good money - why not.
Best wishes,
Madmux
My Tourweaver components: http://www.optitecha.lt/categories/3
Sort of. I've enabled directory browsing, so you can look at the given example file structure. Browse it here:
http://www.virtualivizija.lt/demo/amcdl/
I used the shared player therefore html files (index1 and index2 in this example) must be placed in the directory root while other configuration files must be placed in the tour directory (amc in this case).
Into this directory such the different configuration files should be placed:
* config_xxx.bin,
* filesizex.tzt
* images_xxx.zip,
* resources_xxx.zip
It is not easy to explain it ni a short post, maybe i'll make video tutorial on how to do this.
My Tourweaver components: http://www.optitecha.lt/categories/3
http://www.virtualivizija.lt/demo/amcdl/
I used the shared player therefore html files (index1 and index2 in this example) must be placed in the directory root while other configuration files must be placed in the tour directory (amc in this case).
Into this directory such the different configuration files should be placed:
* config_xxx.bin,
* filesizex.tzt
* images_xxx.zip,
* resources_xxx.zip
It is not easy to explain it ni a short post, maybe i'll make video tutorial on how to do this.
My Tourweaver components: http://www.optitecha.lt/categories/3