On 27 Nov., 23:36, Bruno Postle <[email protected]> wrote: > The situation with libpano13 is that people come and go and work on > it when they have a feature or a bug to fix. It is mature so there > ... > Basically: if you are working on adding vectorisation then you _are_ > the libpano13 developers ;-)
Point taken. But how about extending the notion of 'mature'? To me, maturity in software doesn't only mean running without crashing and doing what is intended, but it also includes a cleanly defined interface and documentation. I have dug into libpano's code every now and then and whenever I made the effort to figure out what it's doing, I found it does it quite well indeed. But it was always a big effort. Library code without documentation isn't worth half what it would be worth with it. I only have that much time to spare for working on it, and if I have to spend 90% of my time figuring out what it does, I can only spend 10% on improving it. Not documenting code puts a spanner in a project's work and actively discourages others from participating: most people who consider participating will look at it, say 'oh my god' and turn elsewhere. > Don't be surprised if you don't get much feedback. If you want the > patch committed, you need to say it is ready, or ask for commit > access. If there are changes that are important for Hugin then we > can coordinate releases. Fair enough. I am yet far from committing a patch, as I haven't really made up my mind on how to deal with strided data and what other code there might be which would lend itself easily to vectorization. One of the problems I have in assessing the situation is the lack of a proper interface to the library - in my experience usually library libXYZ has something like XYZ.h which defines what functions and types are available, and in libpano it's all in various header files - it looks like the library was only a second thought and initially all the panotools were just statically linked. Wouldn't it be a noble aim for the libpano developers (and here I mean those who already know the code) to share their knowledge? I know that Mr. Dersch seems to be out of the picture - I suppose he has started the tradition of just coding the stuff never mind anyone else - but maybe some of those who take care of libpano now have gained sufficient insight to improve on his 'documentation'? 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 [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
