On Thu 03-Feb-2011 at 20:54 +0900, Daniel M. German wrote:
I think the real problem is lack of central parser development,
lack of code that people can reuse to do the parsing. Everybody
has to create their own, and everybody is afraid of breaking the
parser of the others.
I don't think anyone is afraid of that ;-)
Again I feel that I have to point out that we all know the .pto
format is ugly (you can go back to the early PTX discussions which
were all about the file format), nobody has identified some vital
functionality that we need that requires a change to something else.
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.
Slightly related: ptgui now has mask editing using bitmaps rather
than vectors, does anyone know how these bitmaps fit into the ptgui
.pts file format?
--
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
