On 6 Aug., 22:34, Yuval Levy <[email protected]> wrote: > On July 28, 2011 04:26:14 pm Tom Sharpless wrote:
> > If I were going to seriously re-jigger Hugin, I would focus on libpano > > and its horribly inadequate PT scripts. As a practical matter we are > > no longer supporting interoperability with the classic PanoTools, so > > we don't need PT scripts. I suggest documenting Hugin's persistent > > information base, defining a new, extensible project file format to > > hold it. (preferably .ini format, not XML) and writing a new libpano > > to handle it (changing as few APIs as possible, and dropping as many > > unused old ones as possible). That would do far more, in my opinion, > > to foster future improvement than any amount of re-factoring of GUI > > code. > > You are welcome to define such a new project format; make a proposition; > write specifications; even write all the necessary code if you have the time > and skill. It's the Open Source Way. Nobody guarantees adoption, though. > since you, Tom, mention .ini format, I'd like to mention that python has a module (configparser) which readily scans .ini files with very little work on the user's part. I've used it in my woa plugin - since parameter passing/user interaction with python plugin's isn't yet satisfactorily solved, I put all parameters into an .ini file and read them thusly. It was a snap. Since we might have python available on all platforms in the not-too-distant future and anticipate shifting workload to it, I recommend considering doing parsing in python. It lends itself beautifully to it (it also has ready-made modules to parse XML, for example) - and the coding is certainly much more transparent than what we have now. You'd be up and running with a prototype in half a day. .ini format initially seems like a good idea - it's already established, and the sections could be used for the different entities like CPs and images. But the syntax is a bit spartan for my taste and I fear that it might be too meagre to encompass all we need - plus some room to manoevre to extend in the future. In a way, the data handling backend of hugin (the panodata section) is a plain old database application. I'm quite convinced that with a bit of research we might stumble upon a ready-made set of modules (or libraries, if we want to do it in C/C++) which offers - a syntax for structured data description (meta-language) - derived from that, data structures for internal use (the relevent python ore C++ object definitions) - and persistent storage for them (like, tables in a database) - plus an import/export facility to make human-readable output and possibly even import pto - a graphical tool to look at the data - finally, transactional integrity and rollback ability sort of like an on-rails approach. think of how nice it would be to have all that in a neat packet instead of having to code it all ourselves (or, maintain the code which is already there)! And be able to just change or add bits in the data description and have all facets altered without manual intervention. In my experience I've often found that time spent searching for the right tool is better spent than time coding. Any ideas? Kay -- 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
