On Sat 26-Nov-2011 at 13:24 -0800, kfj wrote:

The situation is worsened by the fact that the core library hugin
relies on, libpano, isn't really documented either. Just for the
laugh: today I posted to their (libpano's) developer mailing list and
I saw that the last post was three months ago by a guy asking 'where
is the documentation'. He didn't even get an answer. I must be mad
throwing my lot with such a bunch... but some of the software is
excellent ;-)

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 isn't much pressure to change it, though there are lots of people who can commit code. I've done the recent releases whenever there was some reason to get improvements out to the users.

Basically: if you are working on adding vectorisation then you _are_ the libpano13 developers ;-)

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.

--
Bruno

--
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

Reply via email to