edfink
03-02-2008, 07:25 PM
Hi all. My family is starting to get sick of looking at test versions of my FPP tours. (“Hurry! Come look at it again! The controls are 10% more transparent than they were twenty minutes ago, plus the onOver glow is blurrier now, and I moved the small buttons 5 pixels lower!”) :)
So I figured it’s time to post the links here.
University of Minnesota (4 aerial panos, but only one ground level pano)
http://BigEyeInTheSky.com/View.asp?CID=U_of_M
Las Vegas Larger tour than above (17 aerial and 35 ground-level panos), but with older lens and not as sharp as the U of M tour.
http://BigEyeInTheSky.com/View.asp?CID=Las_Vegas
Each aerial with all its linked ground-level panoramas and still photos are a single XML file, and each link to another aerial opens a new tour/xml file. Believe me, it would have GREATLY simplified things if I’d have kept each panorama as a separate page/xml, but I really love the Flash Fullscreen option, and opening a URL knocks it out of Fullscreen mode. This way, at least you can explore one aerial and whatever ground-level panos it links to while staying Fullscreen, and only fall out of Fullscreen mode when jumping to another aerial.
I did try loading all the Las Vegas panoramas as a single XML file, and it worked fine for me, but a couple of my beta testers had problems – maybe because the XML file alone was almost 1MB.
The biggest part of all this was the VBS scripting and DB work to generate the XML.
To me, it’s a lot faster and easier to position the hotspots in the equirectangular image in Photoshop. Plus, that’s the closest to my original workflow, which relied heavily on Photoshop layers. With some modifications I was able to reuse a fair amount of my old code, things like my “PositionaAllHelicopters” script that pulls GPS coordinates from the DB for all the linked aerials and calculates distance and bearing to each other, then positions all the helicopter icons in Photoshop.
I still have all my hotspots as uniquely numbered layers in Photoshop, where I can quickly drag them into position, but now they’re just placeholders. Instead of leaving them visible in the image, I run a script that gets the x/y for each hotspot layer, stores the position in an Access DB, and turns off the Photoshop layer before creating the QTVR. Then I run another script to read the DB and generate the XML to create (recreate?) each placeholder hotspot layer as an FPP hotspot.
I don’t know if I’m the only one with this kind of weird workflow - I just kind of “thunk it up” because I’m lazy and I’m looking for an easy way to deal with a lot of hotspots.
For now these aren’t visible from my home page, but as soon as I can get all my infrastructure in place I intend to switch my whole site over entirely to FPP.
Ed Fink
Ed@BigEyeInTheSky.com
http://BigEyeInTheSky.com
So I figured it’s time to post the links here.
University of Minnesota (4 aerial panos, but only one ground level pano)
http://BigEyeInTheSky.com/View.asp?CID=U_of_M
Las Vegas Larger tour than above (17 aerial and 35 ground-level panos), but with older lens and not as sharp as the U of M tour.
http://BigEyeInTheSky.com/View.asp?CID=Las_Vegas
Each aerial with all its linked ground-level panoramas and still photos are a single XML file, and each link to another aerial opens a new tour/xml file. Believe me, it would have GREATLY simplified things if I’d have kept each panorama as a separate page/xml, but I really love the Flash Fullscreen option, and opening a URL knocks it out of Fullscreen mode. This way, at least you can explore one aerial and whatever ground-level panos it links to while staying Fullscreen, and only fall out of Fullscreen mode when jumping to another aerial.
I did try loading all the Las Vegas panoramas as a single XML file, and it worked fine for me, but a couple of my beta testers had problems – maybe because the XML file alone was almost 1MB.
The biggest part of all this was the VBS scripting and DB work to generate the XML.
To me, it’s a lot faster and easier to position the hotspots in the equirectangular image in Photoshop. Plus, that’s the closest to my original workflow, which relied heavily on Photoshop layers. With some modifications I was able to reuse a fair amount of my old code, things like my “PositionaAllHelicopters” script that pulls GPS coordinates from the DB for all the linked aerials and calculates distance and bearing to each other, then positions all the helicopter icons in Photoshop.
I still have all my hotspots as uniquely numbered layers in Photoshop, where I can quickly drag them into position, but now they’re just placeholders. Instead of leaving them visible in the image, I run a script that gets the x/y for each hotspot layer, stores the position in an Access DB, and turns off the Photoshop layer before creating the QTVR. Then I run another script to read the DB and generate the XML to create (recreate?) each placeholder hotspot layer as an FPP hotspot.
I don’t know if I’m the only one with this kind of weird workflow - I just kind of “thunk it up” because I’m lazy and I’m looking for an easy way to deal with a lot of hotspots.
For now these aren’t visible from my home page, but as soon as I can get all my infrastructure in place I intend to switch my whole site over entirely to FPP.
Ed Fink
Ed@BigEyeInTheSky.com
http://BigEyeInTheSky.com