On Fri 25-Feb-2011 at 08:33 -0800, kfj wrote:
Yet again, I ask: developers, liaise. Please don't expect of me to do it all. I'm not a GUI person, really, and I've spent a great deal of effort getting the backend right. Maybe someone else could look at the goodies I've stacked up and think of a clever way of enabling people to use them?
Sorry, I haven't had time to look into this. I think initially the python interface would be useful even if it presents as a menu of functions that don't take any parameters. i.e. it can be merged more-or-less in the state it is in.
Then there is an issue I'd like to have considered by the group: the hsi python module could be considered a library, since it can do hugin- ish stuff outside hugin, probably linking in a few shared libraries, but if it was linked statically, not even that. A lot of hugin's code is GPLed. Is there a problem with that?
Please use 'GPL version 2 or later', this makes it easier to ship with Hugin. Are you concerned about how this effects the license of potential 3rd party plugins?
And one more thing: I'd like to see a discussion about a perspective for merging the python_scripting branch back into the mainstream. Thomas and I have made a good effort to parametrize everything in cmake and make the scripting capability a compile-time option. The intersections with other code are minimal and well #ifdeffed.
I would like to see the current Hugin 'trunk' move to a 2011.0.0 release branch as soon as possible. So the python interface should then be merged so that it goes into the next release after that.
-- Bruno -- 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
