Hi All As a sideline spectator, I've been half-reading this thread, but I still have a few ideas that may be rubbish, or perhaps ground some of you, while you can have a snort about my ignorance ;-)
As I understand hugin, quite a few scripting interfaces have already been created around the pano libraries and the fusing/blending engine. I was actually under the impression that what I see of hugin is mostly user interface code and glue, while the real work is done in the commandline code and libs. (I deduce this from having the make file system to do the stitching.) So the gui gathers the images, feeds them to cpfind, provides some interaction for the user to fix the robotic output and then to set some parameters for the final stitch. Some of the interface is plain and some is really fancy with the GL preview. In the end, all is put into a makefile and/or PTO file (I think) and the gui is done, onto batch-a-stitch (or whatever). So, writing a different gui in a different language is probably quite a bit of work, but by no means a rewrite of hugin. I like the idea of using a scripting language for the gui, because of the reasons Yuval gave (no need to re-iterate). Python seems quite a good choice, and there are even alternative (perhaps faster) interpreters in e.g. pypy Tnx for reading (if you got this far) Cheers Simon -- 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
