On Sun 02-Jan-2011 at 21:47 -0500, Yuval Levy wrote:
If there are no objections I will updated the specs both in Hugin and in Libpano to make developers aware of things to come.
There is no need to update the docs until the feature exists, the implementation often determines the details anyway. e.g. weights are unlikely to be integers as already noted.
Note that an existing hack to simulate weighting is to simply duplicate control points, it works ok.
I don't know how many parsers there are out there that do parse pto files. I hope for them that they are designed as robustly as your Python parser or Hugin's own parser. A good parser should be able to ignore noise such as extra parameters that it does not need; or have a 'strict' syntax option to throw warnings with a switch to disable those warnings. Feature request for Panotools. https://bugs.launchpad.net/panotools/+bug/696673 I don't know if Bruno's Perl tools are affected?
Panotools::Script is ok, it will just ignore any unknown parameters so long as they are implemented using the existing syntax.
I don't think there is a problem here, if extra data needs to be added to the Hugin .pto format then it can be added, the other tools can catch up. See the addition of photometric parameters and masks to see how it can be done painlessly.
-- Bruno -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
