On 9 Jan., 10:23, "T. Modes" <[email protected]> wrote:
> That's not fully correct. I agree with Bruno.
> First write the spec of the *function* and *not of the fileformat*.
This is a hen-and-egg problem. How did nature solve it? By evolution.
How do you evolve in software? You write a prototype, then privately
iterate { test, document, modify, }. Then you introduce it as an
option and have it peer-reviewed, and once you get feedback (or
consent by silence) , you might even do another couple of iterations
before introducing it to the public.
You can't reasonably expect to get either the docu or the
implementation right straight away, no matter how good your idea or
your coding skills are.
Kay
--
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
