I found this a little bit sad. Instead of merging the developing power 
everyone is working on its own code.
Yes, it is easier to work on own code. But for the longer one it would be 
better to combine the developing skills and work on a common code base.
This would also have the advantage that not all code needs to be written 
and debugging several times in several iterations.
So please consider working at a common code base or at least port the 
improvements to enblend/enfuse.

Thomas


-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/f16efb68-9ef2-4857-840f-f06372065d9an%40googlegroups.com.
  • [hugin-ptx] Im... 'kfj' via hugin and other free panoramic software
    • Re: [hugi... Harry van der Wolf
      • Re: [... 'Kay F. Jahnke' via hugin and other free panoramic software
        • R... Monkey
          • ... T. Modes
            • ... 'Kay F. Jahnke' via hugin and other free panoramic software
          • ... 'Kay F. Jahnke' via hugin and other free panoramic software
        • R... Harry van der Wolf
          • ... 'Kay F. Jahnke' via hugin and other free panoramic software
            • ... Harry van der Wolf
              • ... 'Kay F. Jahnke' via hugin and other free panoramic software
                • ... yuv
                • ... 'Kay F. Jahnke' via hugin and other free panoramic software
                • ... yuv
                • ... Monkey

Reply via email to