On Fri 12-Nov-2010 at 01:07 -0800, kfj wrote:
On 11 Nov., 19:28, "bruno.postle" <[email protected]> wrote:

The #-hugin lines are used by the hugin GUI to store non-critical
metadata as key=value pairs.  Your parser should at least  preserve
them, though we don't have a spec.

So what non-critical metadata are there, apart from the crop factor?

No idea, they are non-critical so all you need to do is preserve them.

Can I rely on these data preceding the line they belong to?

I've only ever seen them like this, however it is quite possible that the parser simply reads them in order.

Maybe it's time for a new format? Like, XML-based? After all we're
only talking metadata, so processing time shouldn't be that critical,
and there are very good tools to parse XML efficiently (at least in
Python...).

I agree the .pto format is ugly and that we wouldn't design it like this today, but unless you can identify real functionality that can't be achieved with the existing format, switching would only be pain (and a lot of it).

The last time we needed to extend the format was when k-lines were added and this was quite straightforward.

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