[hugin-ptx] Hugin Docs

[Stephan Hegel]

Hi,

Recently there was a proposal to use Doxygen for documentation
purposes. I'd support this 'cause Doxygen is available for Win,
Mac and Linux. It is fairly stable and we've used it in several
projects for years.

It seems there are already preparations made in the source code
to use it: see src/dox/mainpage.dox.

To get it started and to encourage everybody to have a look I've
setup a Doxygen configuration file for Hugin. The following is
straight forward:

1st. install the "Doxygen" package (I've just used 1.5.3 which
 comes with openSUSE 10.3)
2nd. drop the attached "Doxyfile" into the hugin source root
3rd. cd to the hugin source root
4th. run: doxygen
5th. point your browser to ./Doxygen/html/index.html

Well, beside the class hierarchy Doxygen can only find what's
already documented in the source code. There is certainly a lot
of space for improvements.

In case you want to fiddle around with the configuration file, load
it in your favorite editor and explore the possible definitions
or run "doxywizard Doxyfile". If you want to start from scratch,
"doxygen -g" creates a new, annotated configuration file.

Rgds,
  Stephan.

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---



Doxyfile.gz
Description: GNU Zip compressed data

[hugin-ptx] Re: pvQt -- a new portable OpenGL panorama viewer

[Tim Nugent]

Any tips on building in Ubuntu?

Installed qtopengl-dev e

I got:

[EMAIL PROTECTED]:~/src/pvqt$ make
g++ -Wl,--no-undefined -o bin/pvQt build/main.o build/pvQtPic.o
build/pvQtView.o build/MainWindow.o build/GLwindow.o build/pvQt_QTVR.o
build/picTypeDialog.o build/pictureTypes.o build/moc_pvQtPic.o
build/moc_pvQtView.o build/moc_MainWindow.o build/moc_GLwindow.o
build/moc_picTypeDialog.o build/moc_pictureTypes.o-L/usr/lib
-L/usr/X11R6/lib -lQtOpenGL -lQtGui -lQtCore -lGLU -lGL -lpthread
build/GLwindow.o: In function `GLwindow::equi_file(QStringList)':
/home/tnugent/src/pvqt/src/GLwindow.cpp:114: undefined reference to
`pvQtView::showPic(pvQtPic*)'
build/GLwindow.o: In function `GLwindow::cube_files(QStringList)':
/home/tnugent/src/pvqt/src/GLwindow.cpp:137: undefined reference to
`pvQtView::showPic(pvQtPic*)'
build/GLwindow.o: In function `GLwindow::QTVR_file(QString)':
/home/tnugent/src/pvqt/src/GLwindow.cpp:90: undefined reference to
`pvQtView::showPic(pvQtPic*)'
build/GLwindow.o: In function `GLwindow':
/home/tnugent/src/pvqt/src/GLwindow.cpp:13: undefined reference to
`pvQtView::pvQtView(QWidget*)'
/home/tnugent/src/pvqt/src/GLwindow.cpp:13: undefined reference to
`pvQtView::pvQtView(QWidget*)'
build/moc_pvQtView.o: In function `pvQtView::qt_metacall(QMetaObject::Call,
int, void**)':
/home/tnugent/src/pvqt/build/moc_pvQtView.cpp:92: undefined reference to
`pvQtView::setPan(int)'
/home/tnugent/src/pvqt/build/moc_pvQtView.cpp:93: undefined reference to
`pvQtView::setTilt(int)'
/home/tnugent/src/pvqt/build/moc_pvQtView.cpp:94: undefined reference to
`pvQtView::setSpin(int)'
/home/tnugent/src/pvqt/build/moc_pvQtView.cpp:95: undefined reference to
`pvQtView::setZoom(int)'
/home/tnugent/src/pvqt/build/moc_pvQtView.cpp:96: undefined reference to
`pvQtView::setDist(int)'
/home/tnugent/src/pvqt/build/moc_pvQtView.cpp:97: undefined reference to
`pvQtView::step_pan(int)'
/home/tnugent/src/pvqt/build/moc_pvQtView.cpp:98: undefined reference to
`pvQtView::step_tilt(int)'
/home/tnugent/src/pvqt/build/moc_pvQtView.cpp:99: undefined reference to
`pvQtView::step_zoom(int)'
/home/tnugent/src/pvqt/build/moc_pvQtView.cpp:100: undefined reference to
`pvQtView::step_roll(int)'
/home/tnugent/src/pvqt/build/moc_pvQtView.cpp:101: undefined reference to
`pvQtView::step_dist(int)'
/home/tnugent/src/pvqt/build/moc_pvQtView.cpp:102: undefined reference to
`pvQtView::reset_view()'
/home/tnugent/src/pvqt/build/moc_pvQtView.cpp:103: undefined reference to
`pvQtView::home_view()'
/home/tnugent/src/pvqt/build/moc_pvQtView.cpp:104: undefined reference to
`pvQtView::full_frame()'
/home/tnugent/src/pvqt/build/moc_pvQtView.cpp:105: undefined reference to
`pvQtView::super_fish()'
/home/tnugent/src/pvqt/build/moc_pvQtView.cpp:106: undefined reference to
`pvQtView::showPic(pvQtPic*)'
/home/tnugent/src/pvqt/build/moc_pvQtView.cpp:107: undefined reference to
`pvQtView::picChanged()'
build/moc_pvQtView.o:(.rodata._ZTV8pvQtView[vtable for pvQtView]+0x14):
undefined reference to `pvQtView::~pvQtView()'
build/moc_pvQtView.o:(.rodata._ZTV8pvQtView[vtable for pvQtView]+0x18):
undefined reference to `pvQtView::~pvQtView()'
build/moc_pvQtView.o:(.rodata._ZTV8pvQtView[vtable for pvQtView]+0x40):
undefined reference to `pvQtView::sizeHint() const'
build/moc_pvQtView.o:(.rodata._ZTV8pvQtView[vtable for pvQtView]+0x44):
undefined reference to `pvQtView::minimumSizeHint() const'
build/moc_pvQtView.o:(.rodata._ZTV8pvQtView[vtable for pvQtView]+0x50):
undefined reference to `pvQtView::mousePressEvent(QMouseEvent*)'
build/moc_pvQtView.o:(.rodata._ZTV8pvQtView[vtable for pvQtView]+0x5c):
undefined reference to `pvQtView::mouseMoveEvent(QMouseEvent*)'
build/moc_pvQtView.o:(.rodata._ZTV8pvQtView[vtable for pvQtView]+0xe8):
undefined reference to `pvQtView::initializeGL()'
build/moc_pvQtView.o:(.rodata._ZTV8pvQtView[vtable for pvQtView]+0xec):
undefined reference to `pvQtView::resizeGL(int, int)'
build/moc_pvQtView.o:(.rodata._ZTV8pvQtView[vtable for pvQtView]+0xf0):
undefined reference to `pvQtView::paintGL()'
build/moc_pvQtView.o:(.rodata._ZTV8pvQtView[vtable for pvQtView]+0x110):
undefined reference to `non-virtual thunk to pvQtView::~pvQtView()'
build/moc_pvQtView.o:(.rodata._ZTV8pvQtView[vtable for pvQtView]+0x114):
undefined reference to `non-virtual thunk to pvQtView::~pvQtView()'
collect2: ld returned 1 exit status
make: *** [bin/pvQt] Error 1

2008/10/10 mike watson <[EMAIL PROTECTED]>

>
> Tom Sharpless wrote:
>
> > Building pvQt requires the Qt development framework, which is huge but
> > reliable and easy to use, and zlib, which is tiny and ubiquitous.
> > There  is a prebuilt win32 (MinGW) executable on SF, along with the
> > needed MinGW and Qt DLLs.  It is in a self extractor that only runs on
> > Windows, but soon there will be a source tar too.  And you can check
> > out the source tree with "svn co
> https://pvqt.svn.sourceforge.net/svnroot/pvqt
> > pvqt ".
> Built on ubuntu intrepid (well once I realised my default ws qt3). Seems
> to work f

[hugin-ptx] Re: pvQt -- a new portable OpenGL panorama viewer

[mike watson]

Tom Sharpless wrote:

> Building pvQt requires the Qt development framework, which is huge but
> reliable and easy to use, and zlib, which is tiny and ubiquitous.
> There  is a prebuilt win32 (MinGW) executable on SF, along with the
> needed MinGW and Qt DLLs.  It is in a self extractor that only runs on
> Windows, but soon there will be a source tar too.  And you can check
> out the source tree with "svn co https://pvqt.svn.sourceforge.net/svnroot/pvqt
> pvqt ".
Built on ubuntu intrepid (well once I realised my default ws qt3). Seems 
to work fine and proved to be an amusing distraction this evening.


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: pvQt -- a new portable OpenGL panorama viewer

[Erik Krause]

Am Friday, October 10, 2008 um 13:15 schrieb Tom Sharpless:

> It has a few glitches, the worst of which is that it can't tell
> whether it is running on an OpenGL implementation that actually
> supports it -- if not, it just shows all white images.

I can see a grid after it started, I can move this grid, but if I 
load images they are all white. Does this mean my OpneGL version is 
too low?

best regards
--
Erik Krause
Offenburger Str. 33
79108 Freiburg


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] pvQt -- a new portable OpenGL panorama viewer

[Tom Sharpless]

Another panorama viewer?  Well, yes, I think some of you might be
interested in this one.  It began as an exercise  for learning Qt and
OpenGL, which I hoped might produce a useful viewer for Linux.  But it
works so well (on the right hardware) that I've decided to release it
to the world (https://sourceforge.net/projects/pvqt/).

pvQt uses the advanced texture mapping capabilities of  OpenGL version
2.0 or better, to generate true 3D views: the panorama is projected on
a cylinder or sphere, whose interior is seen in perspective from a
movable point of view.  That makes it possible to rotate the view in
all 3 dimensions (yaw, pitch, and roll) and to change the perspective
continuously from rectilinear (when the eye is at the center) through
increasingly "fisheye-like" views, out to a "super fisheye" that can
show almost 288 degrees of the panosphere.

At present pvQt only knows how to display spherical panoramas, in
equirectangular or cubic formats (including cubic QTVRs).  But it is
designed to handle all the common pano formats and show "flat" photos
too.  It has a few glitches, the worst of which is that it can't tell
whether it is running on an OpenGL implementation that actually
supports it -- if not, it just shows all white images.

Building pvQt requires the Qt development framework, which is huge but
reliable and easy to use, and zlib, which is tiny and ubiquitous.
There  is a prebuilt win32 (MinGW) executable on SF, along with the
needed MinGW and Qt DLLs.  It is in a self extractor that only runs on
Windows, but soon there will be a source tar too.  And you can check
out the source tree with "svn co https://pvqt.svn.sourceforge.net/svnroot/pvqt
pvqt ".

Cheers, Tom
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Bad behaviour with 2 images cropped from the same image

[Seb Perez-D]

On Fri, Oct 10, 2008 at 15:16, paolobenve <[EMAIL PROTECTED]> wrote:
> Reproduce it this way:
> - crop an image in two different ways; I cropped one so that it
> remained vertical (h > l), the other horizontal ( h - load the 2 images and hit the align button in the assistant tab
> - the preview window shows a very bad result.

My guess is that the images are given the same lens - but this is
clearly not the case since they are cropped in different ways.

The solution: give the two images different lenses, and optimize in
addition on the fov of one of them.

Cheers,

Seb

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Request For Comments: hugin 0.8.0 release cycle

[luca vascon]

Please, let me understand... is there a new hugin avaliable for windows I
can download and try?!?
I don't know if I'm getting older so fast or if it is definitively time for
me to move from computers to wine and olive oil production..
:-)

2008/10/9 Yuval Levy <[EMAIL PROTECTED]>

>
> Gerry Patterson wrote:
> > Do you mean you will be creating windows installers for the
> > trunk?   I don't think there will be any more activity in the gsoc2008
> > branch anymore...
>
> Yes.
>
>
> > It looks to me as initial support for doxygen was put into the code base
> > a while back.  If you are unfamiliar with doxygen I would take a quick
> > look at it. :
> >
> > 
> > http://www.stack.nl/~dimitri/doxygen/
> > 
> >
> > I think it would be quite useful, as it is fairly automatic to get an
> > overall picture of the class hierarchy used in hugin.  What I really
> > like is comments in the code are used to generate portions of the
> > documentation.  So you get overall picture which one can browse and also
> > on hand documention when editing the code.
>
> thanks - that's sure a positive contribution. I have no clue of doxygen.
> something new to learn.
>
> Yuv
>
> >
>

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Bad behaviour with 2 images cropped from the same image

[J. Schneider]

paolobenve schrieb:
> It's strange, but hugin (3409) can't deal well with images cropped
> from the same image.
> 
> Reproduce it this way:
> - crop an image in two different ways; I cropped one so that it
> remained vertical (h > l), the other horizontal ( hhttp://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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Bad behaviour with 2 images cropped from the same image

[paolobenve]

It's strange, but hugin (3409) can't deal well with images cropped
from the same image.

Reproduce it this way:
- crop an image in two different ways; I cropped one so that it
remained vertical (h > l), the other horizontal ( hhttp://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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: nona -r hdr creates INF pixels

[David Brodsky]

On Thu, 9 Oct 2008, tennevin.yves wrote:
> 
> This looks related to  this bug:
> 
> https://sourceforge.net/tracker/index.php?func=detail&aid=1850361&group_id=77506&atid=550441

Ok, I see the problem, but I dont see a solution. Can someone please
give me a hint? I'm willing to work on it.

As d'Angelo wrote in the thread clipping alone is not a right direction.
Another option is to store each channel in 32 bit float (OpenEXR allows
that), but I'm not sure if it could be read by other programs that
expect half. And finally there may be a way how to not exceed max half
and thus not create INF.

Regards

David Brodsky

> David Brodsky wrote:
> > Hi,
> >
> > [ Andrew, I'm Ccing you because I don't know if you're on the list ]
> >
> > first of all, thanks for the great tool (hugin). But I've run into a
> > problem I can't solve. When I try to create hdr panorama with hugin,
> > some areas looks like [1]. The red areas actually represents pixels with
> > infinite values in red channel.
> >
> > At first I thought it was an error in enblend, but now I've discovered
> > that nona creates one pixel with infinite value in red channel. I've put
> > all necessary files at [2]. If I do
> >
> > nona -r hdr -m EXR_m -o small1-small9_hdr_ -i 4 small1-small9.pto
> >
> > then the output contains bad pixel. Its coords are x: 227 y: 247,
> > counting from zero. I can imagine that this makes enblend create bad
> > areas, because infinity propagates all the way through the pyramids.
> > (This is only my guess).
> >
> > So I think that it is an error that nona creates a pixel with infinite
> > value and therefor looses any precision.
> >
> > One final thing: As you can see on the image [1] there is something what
> > looks like black dashed horizontal lines. This is caused by
> > hugin_hdrmerge which creates images like [3]. See dots on the left and
> > line on the bottom. Again I thing this can make enblend create pictures
> > with errors.
> >
> > Please let me know if there is anything I can do to correct these errors
> > or help invastigating.
> >
> > Regards
> >
> > David Brodsky
> >
> > P.S. Andrew, as you can see you can discard my previous email to you
> > because it may not be an error in enfuse. Thanks.
> >
> > [1]: http://trekie.sinister.cz/enblend.jpg
> > [2]: http://trekie.sinister.cz/nona-inf.zip
> > [3]: http://trekie.sinister.cz/nona.jpg

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---