On Thu 10-Mar-2011 at 07:58 -0800, kfj wrote:
The groundworks for a plugin interface for hugin is laid. The interface at the software level is deliberately unstructured - meaning that any number of hugin objects of arbitrary types can be passed to a plugin. But the GUI currently doesn't make use of this power; it merely allows to 'call a Python script' and passes just a single parameter - the currently active panorama. While this can already be useful, it is obviously very limited.
Just as the CPGs and the other collateral software can be parametrized and can feed back this needs to be possible for plugins as well.
I think the solution is obvious: plugins that don't require input or provide output can work as they do currently. Any other plugins need to use wxPython to provide a GUI.
-- 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 [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
