Steve Schacht wrote:
>>>> a marginally better approach is to pursue browser/app "sniffing" to
>>>> see what a user has installed, and then deliver the pano to them in a
>>>> specific format.
>>>
>> not marginally. Definitely superior.
>
> In addition to the extra work involved, doesn't that also mean extra
> storage? (which of course isn't free) I'm trying to decide on a
> single Web deployment format. I'm leaning toward QT but might look
> more closely at ptviewer.
ZERO extra work. Photographers using the platform provided by my company
just need to upload an equirect. The system takes care of the rest:
conversion/storage/detection/display.
Extra storage is required indeed, but at today's cost this is really
marginal. Assuming your average QTVR is 1MB, adding all other formats go
to about 5MB. At current HDD prices below 0.50 US$/GB storage is peanuts.
>> QT can't do ADR like Shockwave does. From a CMS perspective...
>
> What is ADR
Advanced Dynamic Range. An example tells the story better than a
thousand words (requires Shoclwave):
<http://dativ.at/fotos/panoramas/adr/adr.html> (Bernhard Vogl is one of
the best HDR/ADR authors out there).
> and CMS?
Content Management System. The principle of generating the tour
automatically rather than hand crafting it. So you tell the CMS once
which node is related to which other and where to place the hotspot and
the CMS generates the output for the different plugins, as opposed to
manually authoring for each and every plugin.
>
>> I can easily add hotspot
>> shapes, positioning, URLs and all sort of overlays to Java/ptviewer and
>> Shockwave/SPi-V).
>
> I didn't know hotspots could be added to ptviewer panos. Have any
> URLs handy which discuss how to do that?
I have a live example on my company's platform:
<http://www.voxcasa.com/visite.php?sia=x42500> defaults to Java if
detected. You can manually override the plugin selection by clicking on
the button that looks like an equalizer, next to the full screen button.
This is still V1 and soon to be updated.
> Yes, it can be quite challenging at times, and I'm not even trying to
> cater to every browser out there. Basically, I test on IE 6+,
> Firefox, and Netscape on Windows, and on Safari, Opera, Firefox, and
> OmniWeb on Mac. If other browsers happen to be [reasonably]
> standards-compliant and work, great; but I don't have to time to
> support (let alone test) every browser out there.
I have no Mac (waiting for Apple to finally release OSX for non-Apple
hardware) and test on IE 6+ Windows, FF Windows/Linux, Opera
Windows/Linux, Konqueror/Linux (which I understand is the closest
relative to Safari in the non-Apple world).
> I don't like it when pano sites force the browser window to full
> screen and commandeer my display.
Same here.
> Nor do I care for all the context switching that results from the
> entire Web page reloading to display a new pano.
still transitioning from there, but I can relate to what you mean.
> I really wanted the ability to "replace" an existing pano with a new
> one inside the page. I gave up trying to manipulate the QT plugin via
> JS in favor of using AJAX to load a new pano in only a portion of the
> page. It works quite well on the browsers tested.
<http://br.xenaura.com/test.php> uses Ajax. I've had reports of
quirkiness under Safari, but overall it works better than expected. The
capabilities detection is asynchronous too. I am terribly slow in
developing it because it is JavaScript and I have tried to avoid
JavaScript for the last ten years, so my code is not exactly clean, and
debugging JavaScript is tedious for me.
Yuv
_______________________________________________
Do not post admin requests to the list. They will be ignored.
QuickTime-VR mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quicktime-vr/email@hidden
This email sent to email@hidden
