On 9 Jan., 06:05, Yuval Levy <[email protected]> wrote: > On January 3, 2011 09:49:21 am Bruno Postle wrote: > > > 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. > > this is the wrong way of doing things. first write the specs, then > implemented them. as an extra bonus, well written specs are the documentation > that often lacks^H^H^H^H^Hfollows implementation. >
That's not fully correct. I agree with Bruno. First write the spec of the *function* and *not of the fileformat*. The implementation of the function determines then the modification of the pto file format. E.g. the weight, first you need to know how the optimizer can work with the weight factors: can the algorithm better work with float numbers (0.0 - 1.0 or better 0.0 - 100.0) or it is better to use integer (0 - 100 or 0 - 256 or ...). So the implementation determines the number format and the number format specify then the file spec. If you write first the file spec and the implement the function you will often need to trade off between the spec of the file format and the requirements of the existing code, which makes it more complicate. So as a first step we need the spec of the function and not of the file format. Thomas -- 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
