Hi Kay,
Am 16.01.2011 18:32, schrieb kfj:
> Once I've test-run the code from hugin I'll publish through the usual
> channel. So far there has been so little echo to my work that I am
> getting the feeling that hardly anyone actually reads my posts or is
> at all interested. This is regrettable, since I am certain that my
> path to Python integration is opening up very interesting new
> possibilities. Let me name but a few:
>
> - plugins can provide glue to closely cooperate with other
> applications
> - other code can be glued in without having to link it
> - code contribution from users is made much easier
> - optional functionality can be accessed on on demand
> - Python code can be used to do advanced maths (see numpy, SciPy)
I'm spending all my hugin time on the cpfind improvement now, so I
didn't have much time to try your python work. However, I do a lot of
python programming at work, and I really like it, and I think it would
be a great addition to hugin.
The full benefits might not be obvious to everybody, so don't let the
lack of feedback disapoint you.
I think once some examples of how to use the interface are available,
even people that could not do any hugin coding can start to contribute.
Btw. in order to make it easier for us track your work (and add
improvements etc.), it would be great if you could offer a hg branch of
it (maybe not on sourceforge, if you have issues with that, but maybe at
some other site (for example: bitbucket or so).
Sorry for not answering the tech questions, I'll do this later if nobody
jumps in.
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
