On 16 Jan., 19:39, Pablo d'Angelo <pablo.dang...@web.de> wrote:
> 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. that is the aim of the plugin interface. And things are looking great so far; everything seems to have worked out as I hoped it would. > 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). I need some time then to learn how to do that. I work on my bleeding edge repo extract on this system, I haven't branched out, since the changes are minimal. But I'll make an effort to figure out what I need to do to offer a branch for testing purposes. I have a repo on Launchpad where I usually publish my code, could I make a hugin branch there? Please excuse my ignorance of these matters, I really haven't taken any time to learn mercurial. > Sorry for not answering the tech questions, I'll do this later if nobody > jumps in. As far as the plugin interface for hugin goes, I've boiled it down now to a header declaring a single variadic function to call a Python plugin; every component of hugin should be able to simply include the header and be plugin-enabled, while all code to access the py side of things is in a separate object file. The only requirement on the build side is that the Python libs have to be added to the common libraries. I have modifies CMakeList.txt files that do the trick. I just couldn't think of a good place to put a call to a plugin for testing purposes. But I've tested it from somewhere likely, and it seems to work. thank you for your feedback; I appreciate you are busy with cpfind (thumbs up)! And, after all, there's no rush, but I was wondering if anybody out there took any notice of what I do, since there was so little echo. Kay -- 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
