> really a pain to try to support binary incompatible dlls, and imagine
> trying to use several applications together, each requiring a different
> version of pano13.
I agree...I'm planning on compiling PTOptimizer/PTMender statically linked to
the pano tools code...no more DLL distribution from me (with the exception of
the "original" pano12.dll which is still needed for the rest of the Panorama
Tools suite: ptstitcher, ptmorpher, ptinterpolate, etc.)
Even without binary incompatible versions of the pano??.dll, my experience is
that the average user is already confused about DLLs and versions. They
frequently have multiple copies of the DLL on their machines, in various
directories, with various revisions. Many don't know how those copies got
there, what they are for, how to determine its version number, or even what a
DLL does. Moreover the DLL is potentially used for a number of other
applications besides the GUI stitching programs (e.g. Photoshop plugins), so
one has to be extremely careful when suggesting a user remove/update/replace
the DLL file when trying to help them solve some problem.
The thought of having different versions of something like PTOptimizer floating
around on a user's machine that may or may not work with different versions of
pano12.dll pano13.dll (version 2.8.4), pano13.dll (version 2.8.something.else)
seems like a headache that can be avoided by eliminating the DLL entirely.