PanoPanel <-> OptimizeFrame

[Pablo d'Angelo]

Hi!

Currently we have two places where the optimizer can be called,
PanoPanel and OptimizerFrame.

Kai-Uwe seems to prefer to include the optimize step into the PanoPanel,
while I think it will become overloaded, and should be a separate
optimize window.

What do the other users think about it?

I just looked a bit into PanoPanel and it seems that the "detach"
feature is hardwired into PanoPanel, leading to much code that is
concerned with keeping them in sync.
Maybe there should be a detachable panel (as a separate class), that
can be teared of an notebook. the sync could probably go through the
model (at least partly).

I would also like to base all output image sizes on the hvof/vvof of the
panorama, so that I don not have to try many times to get the right
ratio for the panorama.

so the user can select the hfov/vfov of the panorama, or let it
calculate from current panorama. This means that we would have
(h/v)fov settings and a width setting, while the height is computed
from them. I'll add methods to get the h/vfov to Panorama.

ciao
  Pablo
--
http://wurm.wohnheim.uni-ulm.de/~redman/
Please use PGP