Hi everybody, I undusted the code I started few years ago and finally completed a working prototype:
https://bitbucket.org/dmgerman/panoparser (it is here temporarily until sourceforge gives us shell access again). If you download it and compile it, you will find that it creates a program called "testparser". It uses one command line option, the name of a PTO file. It will convert this PTO file to an equivalent .TXT panotools script. THe idea of this parser is old: if we have a single parser (as a library) we can then have multiple tools reading (and perhaps generating) these files. One of the goals is to replace (or at least create an alternative execution path) the parser in libpano, so we can more easily upgrade it when we need new options/variables. This will probably help in the creation of more portable lens parameters. --dmg -- -- 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 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
