On 26 Nov., 18:51, Jaroslav <[email protected]> wrote: > I don't mind joining in or debugging the problems I encounter, but is > there any documentation of the code? That's usually the biggest issue > with open source, no documentation :(
Sadly this is true. The only documentation on how to use the software is in the panotools wiki, but noone seems to have bothered to document the code much or present a technical outline of what is where and why. The situation is worsened by the fact that the core library hugin relies on, libpano, isn't really documented either. Just for the laugh: today I posted to their (libpano's) developer mailing list and I saw that the last post was three months ago by a guy asking 'where is the documentation'. He didn't even get an answer. I must be mad throwing my lot with such a bunch... but some of the software is excellent ;-) > I already got one idea, putting the images into stacks automatically, > it's "real fun" clicking a hundred of images into stacks... > Or should I just ignore stacks with HDR and don't use > align_image_stack.exe? I doubt that. I wrote a python plugin which does precisely that (putting the images into stacks), but so far the python interface is only readily available for some Linux users. The python interface code works under Windows as well, but AFAIK none of the packagers has created an installer which contains it, so if you want the code you have to compile yourself, which is a tall order under Windows. This is the status quo after the code has been made to run under Windows sometime this spring. So I can't help you here, either - I'm quite frustrated myself that my code (I wrote the python interface) is withheld from the wider public because of some statically-linked-versus-dynamically- linked argument, if that really is what it is... I asked here for help with some finer points in the stacking code so that I could make a really nice plugin, but I didn't get a reply to that post, either. So it's sitting here half ready and works for me, but I've given up any hope for help with the code. It's read the code or wait for others to provide what you need. If you're capable of doing stuff on the command line - pto files are plain text files and you can just use text processing tools to adapt the stack numbers in the pto. 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
