kfj wrote:
On 4 Feb., 00:37, Bruno Postle <[email protected]> wrote:
We haven't had any bugs related to the file-format for years,
switching Hugin to a different format at this stage would be
self-indulgent and would bring lots of disadvantages.
How about introducing a new format as an option? Nobody wants to
instantly get rid of pto format, and it will remain with us for a
while to deal with legacy data. Just when it comes to adding support
for new features, pto is approaching it's limits. It was a clear, well-
thought-out, simple-to-parse language when it was conceived of: single-
letter line headers and field headers, no comments with hidden
meaning. The single-letter field headers broke first, and they were
the least-well-thought-out part where forseeable lack of capability
was sacrificed to parsing simplicity. Why was argument passing changed
from -o style to --output style? Precisely the same issue.
XML would be much easier to parse
--
Gnome Nomad
[email protected]
wandering the landscape of god
http://www.cafepress.com/otherend/
--
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
