On June 19, 2011 05:04:54 AM kfj wrote: > Hi all! > > I've modified hpi.py, the plugin dispatcher, to provide better > information about exceptions occuring in the python plugins.
Thank you, this is a useful big step in the right direction.
> printed to the console (sorry, I haven't found a better way yet)
Don't be sorry, it's an improvement, and the feedback is much more useful now:
$ hugin
MainFrame::RestoreLayoutOnNextResize()
run python script: /usr/local/share/hugin/data/plugins/crop_cp.py
hpi: accessing plugin file /usr/local/share/hugin/data/plugins/crop_cp.py
hpi: plugin crop_cp.py failed with ImportError: "No module named wx"
hpi: stack traceback:
File "/usr/lib/python2.7/dist-packages/hpi.py", line 44, in hpi_dispatch
success = plugin [ 'entry' ] ( *args )
File "/usr/local/share/hugin/data/plugins/crop_cp.py", line 184, in entry
import wx
hpi: terminating with exit code -11
Python interface returned -11
(please don't see this as a request for help to fix this - it is just to show
the feedback. something along sudo apt-get install python-wxgtk should help.
have not tried yet).
> I've slightly modified hpi.py's facility to run plugins without hugin
> being active.
OK, so how will it behave when hugin internals (as opposed to panorama model
internals) will be exposed? E.g. if a plugin will try to access the two
images currently selected in the CP tab?)
> I've added two skeleton plugins which do nothing
skeleton or ghosts? I did not find any trace of them in the patch.
http://bazaar.launchpad.net/~kfj/+junk/script/files/head:/main/?sort=date did
not help me identifying them either.
> Thanks to whoever picks it up!
Thank you for moving this forward!
Yuv
signature.asc
Description: This is a digitally signed message part.
