Hi Kay, Am 10.01.2011 12:39, schrieb kfj:
I have set out creating a scripting interface for hugin.
Great, I think that hugin can benefit greatly from such an interface, both for custom utilities, as well as quick prototyping of new ideas.
So the next thing that I feel needs to be done before I proceed is this: - decide which part of the hugin functionality should be scriptable
In addition to the basic Data model (as you seem to have done already), the algorithms in hugin_base/algorithms might be useful for scripting workflows. Here, maybe only the static driver functions are required in the scripting language as the multi step approach (custruct algorithm object, call runAlgorithm() & get the results out of the object) is probably quite a hassle when writing scripts.
Btw. is your code available in some repo? Maybe a new hugin_scripting branch would be a good idea.
The next step, the 'mechanism to use scripted content from hugin', would require code linked into hugin to interface with a scripting language, enabling stuff like 'plugins'.
That would be especially helpful for customizing workflows etc. If the integration also extends to wxPython, new GUI functionality could be quite easily prototyped or even implemented in python.
ciao Pablo -- 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
