>> 
 >> No. :) we need to document them. At this point my goal has been to
 >> create a mapping from PTO to txt formats (txt is the libpano format).

 kfj> It's been pointed out that those 'cousins' of hugin which also use pto
 kfj> dialects seem to give a damn about compatibility (I think some are
 kfj> commercial and may become incompatible deliberately) - and the best
 kfj> idea everyone had was putting their data into what is, by orthodox
 kfj> standards, a comment. I would advocate putting an end to this mess and
 kfj> starting with a new format. Something clean and well-thought out
 kfj> rather than an ugly old-timer with patches and quirks. 

I like the simple text file format that libpano started with (with some
minor problems, such as dependence between lines, making it impossible
to cut-and-paste lines).

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. So here is my pledge: 

 to deliver a parser that can be used with any product that parsers the
 PTO format (and its variants) and can be embedded under any license
 (commercial and proprietary). 

The current code is a big step in this direction, but its license will
have to change for this to happen (I am ok with that).

This library could be useful for the current state, or the future (if a
new format and parser is developed). New variables can be added to it
(or if somebody can just maintain a light-fork from it if they don't
want to send the new spec to us.



-- 
--
Daniel M. German                  
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .

-- 
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

Reply via email to