[hugin-ptx] bug in libpano/PTmender
FYI, Adding Tr parameters to the script will restrict the output of the any remapped image be at most 180 degrees, even if it can spawn longer (such as most of the cylindrical panoramas). I am not sure why this happens yet. --dmg -- -- Daniel M. German http://turingmachine.org/ http://silvernegative.com/ dmg (at) uvic (dot) ca replace (at) with @ and (dot) with . -- 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
[hugin-ptx] Re: German translation questions (and a little poedit problem)
Hallo Joachim, J. Schneider schrieb am 26.12.09 20:20: Hi all, while I wish I had the time to try to get my hugin to compile I can at least do a little on the translation. So here are a few questions: Could somebody point me out what exactly is meant by excess in Calculate crop borders such that the final images has the largest area without excess? Is it white space? 'final images' looks like a typo to me. It's only one final image, otherwise the following 'has' needs to be 'have'. The phrase itself is a tooltip, right? James Legg added: The excess is any area in the output not covered by an input image (where the stitch result will be transparent). More accurately, the whole phrase could be Set the crop to the largest rectangle containing only points which input images map to, but that is probably too long and too mathematical. ok, so how about Berechne die Beschnittkanten (oder vielleicht -grenzen?) für eine maximale Bildfläche, die keine Bereiche ohne Bildinformationen enthält Does anybody have an idea how to translate (de)ghosting into German (or with what other terms have other translators come up? I have looked into French and Suppression d'éléments fantômes would be Unterdrückung von Phantomelementen. Not so bad, but I'm not content. Probably a French translation tries harder to find a solution without English elements in it. I also try to find a German expression but sometimes a literal translation makes no sense and the English term is already common in German discussions. 'deghosting' is not that bad but how about one of these: 'Überlappung/Erscheinung/Unterdrückung von Halbbildern'? Has anybody had an idea how to translate stitcher. The direct tranlation doesn't make much sense in German. A nice short term like stitcher would be needed, but I can think of long clumsy expressions only. Stitcher is already in use (also as a verb stitchen), so I think we can just use it as is. I translated the last two release notes http://hugin.sourceforge.net/releases/2009.4.0/de.shtml http://hugin.sourceforge.net/releases/2009.2.0/de.shtml The original version is always the en.shtml file. If you find errors or better expressions just tell me. Where is upstream used? Sorry, no idea. What about translating advanced options with ausführliche Optionen? I haven't seen other occurences of advanced (in this meaning) in hugin. Erweiterte Einstellungen mehr Optionen... (shorter; if it's a button) mehr... (if space is really restricted) The translation of Calculate optimal image size, such that the resolution in the image center stays similar has been marked fuzzy. Has the English original changed? I find Optimale Bildgröße berechnen, so dass die Auflösung der Bildmitte etwa der Originalauflösung entspricht still quite good. Output modes again: Has the term merge been discussed before? (I can only remember discussing blending and fusing.) Verschmelzen is the direct translation, I tend to use it. I think that's about merging layers, right? 'verbinden' would be a solution but there's also a Auf die Hintergrundebene reduzieren in Photoshop which IMHO could be used in a similar way like 'auf eine Ebene reduzieren' if that's not too long. Carl -- 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
[hugin-ptx] Re: [PanoTools-devel] bug in libpano/PTmender
D M German wrote: FYI, Adding Tr parameters to the script will restrict the output of the any remapped image be at most 180 degrees, even if it can spawn longer (such as most of the cylindrical panoramas). I am not sure why this happens yet. Only images that have nonzero TrXYZ should be affected by this, as they are fist projected onto a plane and thus cannot have more than 180 degrees in the final panorama. The behaviour of images with Tr(XYZ)0 should not change. 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 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
[hugin-ptx] Problems compiling hugin 2009.4.0
Hi, I went through the wiki here (http://wiki.panotools.org/ Hugin_Compiling_ubuntu) to compile hugin on ubuntu 8.04. Everything went pretty smooth but when I try to run hugin I get: 2...@2lss-laptop:~/hugin-build$ hugin hugin: error while loading shared libraries: libhuginbase.so.0.0: cannot open shared object file: No such file or directory 2...@2lss-laptop:~/hugin-build$ ldd /usr/local/bin/nona linux-gate.so.1 = (0xb7f12000) libhuginbase.so.0.0 = not found libboost_thread-gcc42-mt-1_34_1.so.1.34.1 = /usr/lib/libboost_thread- gcc42-mt-1_34_1.so.1.34.1 (0xb7eef000) libpano13.so.2 = /usr/local/lib/libpano13.so.2 (0xb7e7f000) liblapack.so.3gf = /usr/lib/atlas/liblapack.so.3gf (0xb775d000) libblas.so.3gf = /usr/lib/atlas/libblas.so.3gf (0xb7412000) libhuginvigraimpex.so.0.0 = not found libImath.so.2 = /usr/lib/libImath.so.2 (0xb740d000) libIlmImf.so.2 = /usr/lib/libIlmImf.so.2 (0xb7394000) libIex.so.2 = /usr/lib/libIex.so.2 (0xb737e000) libHalf.so.2 = /usr/lib/libHalf.so.2 (0xb733b000) libjpeg.so.62 = /usr/lib/libjpeg.so.62 (0xb731b000) libtiff.so.4 = /usr/lib/libtiff.so.4 (0xb72c8000) libpng12.so.0 = /usr/lib/libpng12.so.0 (0xb72a5000) libz.so.1 = /usr/lib/libz.so.1 (0xb728f000) libexiv2.so.2 = /usr/lib/libexiv2.so.2 (0xb7113000) libstdc++.so.6 = /usr/lib/libstdc++.so.6 (0xb702) libm.so.6 = /lib/tls/i686/cmov/libm.so.6 (0xb6ffb000) libgcc_s.so.1 = /lib/libgcc_s.so.1 (0xb6ff) libc.so.6 = /lib/tls/i686/cmov/libc.so.6 (0xb6ea1000) libpthread.so.0 = /lib/tls/i686/cmov/libpthread.so.0 (0xb6e88000) librt.so.1 = /lib/tls/i686/cmov/librt.so.1 (0xb6e7f000) libexpat.so.1 = /usr/lib/libexpat.so.1 (0xb6e5e000) /lib/ld-linux.so.2 (0xb7f13000) I have all dependencies with the exception of libglew-dev, package manager installed libglew1.5-dev instead 2...@2lss-laptop:~/hugin-build$ aptitude search libglew v libglew-dev - c libglew1.4 - The OpenGL Extension Wrangler - runtime environment i A libglew1.5 - The OpenGL Extension Wrangler - runtime environment i libglew1.5-dev - The OpenGL Extension Wrangler - development environment Can anyone point me in the right direction? Thanks for reading. -- 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
[hugin-ptx] make: pto2mk: No such file or directory
OS X version 10.6.2 When I run panostart on directory full of tifs it appears to run properly including the creation of the .pto file. However panostart errors out at the very end with the below: pto2mk -o 0001_observatory-0015_observatory.pto.mk -p 0001_observatory-0015_observatory 0001_observatory-0015_observatory.pto make: pto2mk: No such file or directory make: *** [0001_observatory-0015_observatory.pto.mk] Error 1 I have this version of Hugin installed: Version 2009.4.0 built by Skip Gaede but I do not find pto2mk? -- 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
[hugin-ptx] Re: [PanoTools-devel] bug in libpano/PTmender
Hi Pablo, Pablo D M German wrote: FYI, Adding Tr parameters to the script will restrict the output of the any remapped image be at most 180 degrees, even if it can spawn longer (such as most of the cylindrical panoramas). I am not sure why this happens yet. Pablo Only images that have nonzero TrXYZ should be affected by this, as they Pablo are fist projected onto a plane and thus cannot have more than 180 Pablo degrees in the final panorama. Pablo The behaviour of images with Tr(XYZ)0 should not change. I agree. The problem is the execution path of libpano. When a parameter is found, its corresponding function is executed as part of the stack, even if the parameters do not alter the image (such as Tr(XYZ)0). I suspect that the translation function becomes undefined (return nans) when the point if beyond 90 degrees on either of the four directions. The result of this is that the output image has the right size, but has no data outside the 90 degrees boundary. I suspect the best approach is to test for the values of the Tr* parameters in the parser, and if they are zero, do not set the im-cp.trans to TRUE. This can be done for several other parameters too, and will remove unnecessary processing. Pablo ciao Pablo -- -- Daniel M. German http://turingmachine.org/ http://silvernegative.com/ dmg (at) uvic (dot) ca replace (at) with @ and (dot) with . -- 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
[hugin-ptx] Re: Layout branch merged
James. Using the Hugin Windows SDK I've been able to build recent versions of Hugin from 0.8 to 2009.2. It has taken me most the day, but I have been able to build your merged layout model changes from the trunk (svn 4827) for Windows 32bit using MSVC C++ 9.0 Express Edition. Comments, don't think these all relate to your changes. (1) Boost seems to have been increased to version 1.41.0, but the old version seems to work 1.39.0? I can't find a pre-compiled version of boost 1.41.0 for Windows, tried (http://www.boostpro.com/download) (2) Now I've got it, don't really know what to do with it, I can see the new layout button on the preview screen and new stack buttons on the images tab.Are there any instructions/documentation for the layout model? (3) The buttons are on the GPU preview screen are too wide, the show control points button is lost from the window. (4) Error when calling Autopano.exe Could not execute command hugin\files\bin\autopano.exe /allinone / path:C:\DOCUME~1\Stephen\LOCALS~1|temp /keys:10 /project:oto / name:ap_CC.tmp /size:1024 /f path/img1.jpg path/img2.jpg If it helps anyone else I've included my notes from todays effort below. Regards Stephen Download hugin source and just try exisiting pre-merge MSVC project: Error in huginbase: 4..\..\..\hugin\src\hugin_base\panotools\PanoToolsInterface.cpp (497) : error C2039: 'trans_x' : is not a member of 'correct_Prefs' Think this means I need latest version of panotools13, downloaded panotools libpano13-2.9.15_beta3. Could not get cmake to run for this: CMake Error at C:/Program Files/CMake 2.7/share/cmake-2.7/Modules/ FindPackageHandleStandardArgs.cmake:57 (MESSAGE): Could NOT find wxWidgets (missing: wxWidgets_FOUND) Call Stack (most recent call first): C:/Program Files/CMake 2.7/share/cmake-2.7/Modules/ FindwxWidgets.cmake:782 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) CMakeLists.txt:50 (FIND_PACKAGE) Four components of WxWidgets shown as not found.. E.g. wx_dbgrid. Try using old vc project file in libpano download regardless, remember to set enviroment variables for wxwidgets and Java SDK, from panotools wiki: http://wiki.panotools.org/Build_pano12_from_sourcecode_MSVC Get panotool's windows specific files not in source tarball from sourceforge. tools/compat_win32/getopt.h|c Bogged down in missing external symbols.. then realised that the actual build configuration I needed was RELEASE CMD LIB and these missing symbols are related to GUI DLL builds. Have created a static libpano.lib .. needs renaming to pano13.lib?. Go back and build hugin, I got an error message CMake is re-running because generate.stamp.list is missing. Looks like I did not understand how cmake works, and trashed my hugin build. Could not get Boost options to configure in CMAKE, go back to Boost 1.39.0, now cmake will complete. Open hugin solution, and build, finally copy various files to get package to build. Have a working build of Hugin from the trunk, which includes layout model, and enblend 4.0 On Dec 23, 8:40 pm, James Legg lankyle...@gmail.com wrote: I have merged the gsoc2009_layout branch with trunk. ... -- 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
Re: [hugin-ptx] make: pto2mk: No such file or directory
Hi Joe, 2009/12/27 PortlandPano j...@marquesdigital.com OS X version 10.6.2 When I run panostart on directory full of tifs it appears to run properly including the creation of the .pto file. However panostart errors out at the very end with the below: pto2mk -o 0001_observatory-0015_observatory.pto.mk -p 0001_observatory-0015_observatory 0001_observatory-0015_observatory.pto make: pto2mk: No such file or directory make: *** [0001_observatory-0015_observatory.pto.mk] Error 1 I have this version of Hugin installed: Version 2009.4.0 built by Skip Gaede but I do not find pto2mk? That's correct. The Hugin for OSX as distributed by the builders never contains the tools apart from the necessary ones for the bundle to function. pto2mk is not distributed in or with the bundle. I'll have a look at it. Harry -- 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
Re: [hugin-ptx] German translation questions (and a little poedit problem)
On Sat 26-Dec-2009 at 20:20 +0100, J. Schneider wrote: Where is upstream used? In the new About dialog window, there are some 'tabs': About Authors Sponsors Upstream License The Upstream tab contains some mention of other software used in Hugin such as Vigra, enblend etc... The translation of Calculate optimal image size, such that the resolution in the image center stays similar has been marked fuzzy. Has the English original changed? The capitalisation and trailing full stops in the tooltips have been made consistent. So the string punctuation has probably changed slightly, but gettext is still able to match it. When saving I get 19:50:36: D:\hugin-trunk\src\translations\de.po:406: number of format specifications in 'msgid' and 'msgstr' does not match 19:50:36: msgfmt: found 1 fatal error I can't remember I had changed anything anywhere. Just pulled the current version and worked on translations as always. I'll rather not upload the file in this state? The format specifications are stuff like '%s' which are interpreted at runtime. The problem section looks like this: msgid Too many arguments (images). Try using the %%s parameter in preferences.\n \n Could not execute command: %s msgstr Zu viele Argumente (Bilder). Versuchen Sie den %s-Parameter in den Einstellungen zu benutzen.\n \n Konnte das KOmmando nicht ausführen: This looks like it will go wrong, it should look something like this: msgstr Zu viele Argumente (Bilder). Versuchen Sie den %%s-Parameter in den Einstellungen zu benutzen.\n \n Konnte das KOmmando nicht ausführen: %s -- 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 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
Re: [hugin-ptx] Problems compiling hugin 2009.4.0
On Thu 24-Dec-2009 at 10:33 -0800, 2lss wrote: Everything went pretty smooth but when I try to run hugin I get: 2...@2lss-laptop:~/hugin-build$ hugin hugin: error while loading shared libraries: libhuginbase.so.0.0: cannot open shared object file: No such file or directory 2...@2lss-laptop:~/hugin-build$ ldd /usr/local/bin/nona linux-gate.so.1 = (0xb7f12000) libhuginbase.so.0.0 = not found Can anyone point me in the right direction? Thanks for reading. Two possibilities: The Hugin libraries haven't been installed, can you see them in /usr/local/lib ? The libraries are installed, but the linker doesn't see them, this could have several causes. Try running `ldconfig` as root, else check that /etc/ld.so.conf or LD_LIBRARY_PATH are set up correctly to use libraries in /usr/local/lib -- 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 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
Re: [hugin-ptx] Re: Layout branch merged
On Sun 27-Dec-2009 at 10:46 -0800, Steeve wrote: (2) Now I've got it, don't really know what to do with it, I can see the new layout button on the preview screen and new stack buttons on the images tab.Are there any instructions/documentation for the layout model? Not yet, most of the changes are in the backend: The layout mode lets you view the project as an undirected graph with links representing control points. The stack buttons are related to new functionality allowing different photos to be grouped together by sharing image parameters. Previously this was only available within the lens number system, but now it is possible to link positions (roll, pitch yaw) of photos - In the future other groupings will be possible such as sensor response curve or XYZ positions. (3) The buttons are on the GPU preview screen are too wide, the show control points button is lost from the window. This is being worked-on, see the discussion from a week or two ago. Think this means I need latest version of panotools13, downloaded Get panotool's windows specific files not in source tarball from sourceforge. tools/compat_win32/getopt.h|c This will be fixed in the next libpano13 beta (which will be soon). -- 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 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
Re: [hugin-ptx] Re: Layout branch merged
On Sun, 2009-12-27 at 10:46 -0800, Steeve wrote: (1) Boost seems to have been increased to version 1.41.0, but the old version seems to work 1.39.0? I can't find a pre-compiled version of boost 1.41.0 for Windows, tried (http://www.boostpro.com/download) I'm using boost 1.38, I don't think updating it is necessary. (4) Error when calling Autopano.exe Could not execute command hugin\files\bin\autopano.exe /allinone / path:C:\DOCUME~1\Stephen\LOCALS~1|temp /keys:10 /project:oto / name:ap_CC.tmp /size:1024 /f path/img1.jpg path/img2.jpg Have you built Autopano and copied the binary to that path? This shouldn't have changed in the merge. -James -- 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
[hugin-ptx] Re: German translation questions (and a little poedit problem)
Bruno Postle schrieb am 28.12.09 00:17: On Sat 26-Dec-2009 at 20:20 +0100, J. Schneider wrote: Where is upstream used? In the new About dialog window, there are some 'tabs': About Authors Sponsors Upstream License The Upstream tab contains some mention of other software used in Hugin such as Vigra, enblend etc... Macht 'Integriert' Sinn? msgstr Zu viele Argumente (Bilder). Versuchen Sie den %%s-Parameter in den Einstellungen zu benutzen.\n \n Konnte das KOmmando nicht ausführen: %s In 'das KOmmando' steckt ein Fehler, stattdessen eins davon: - das Kommando - den Befehl Carl -- 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
[hugin-ptx] Re: Announce: Enblend/Enfuse version 4.0 - Final Release
On Dec 19, 8:29 pm, James Legg lankyle...@gmail.com wrote: Personally, I prefer a long page with one vertical scrollbar at the edge of the window rather than a fixed border with a scrollable window in the middle. done. not perfect, but good for some testing. feedback welcome. 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 hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: 2009-04 RC3 Windows binaries available for testing
allard wrote: It is identified as Pre-release 2009.5.0.4740 That's a known problem, but it's not applicable here. I admit I built this from SVN, not from the tarball. Nevertheless, if you build from the tarball I believe it still doesn't tell you it's a release. The SVN nr should be 4742 though... Next time, please do your homework before calling things what they are not. You need to understand that building from SVN is not synonymous for building trunk. SVN is like a hard disk. It can have (and in this case has) many folders. One of them is called trunk [0], and this is where the latest development takes place. In the case 2009.4, the folder to build from is [1]. Each release cycle starts with copying trunk to a new folder, and as time passes by the difference between the two folders increases as trunk move forward on features and the release folder moves forward on clean/polish. The revision number only identifies the moment in the sequence of changes when a folder was used; not which folder was used. In the case of 2009.4/4742 vs. trunk/4742 you were lucky that the differences were not too radical. If you were to take the same shortcut now, the differences between 2010.0/HEAD and trunk/HEAD are major. You would only generate confusion. If you want to build release candidates of 2010.0 the right way, point your SVN client to [2]. There are additional things to consider. Read carefully the mailing list to keep up to date with what the developers are doing. Read the SVN logs. Know your way around. If you don't have time, don't cut short this important due diligence. Delegate it. Ask others. But don't skip it. In a controlled environment (e.g. corporate world) your mistake would be serious enough to put somebody under stricter supervision or even remove them from the job. Here I can only appeal to your sense of responsibility. Next time make sure you understand what you are doing and the consequences it has on the project, the community and last but not least on yourself (my understanding is that you are currently subject to US jurisdiction?). Yuv [0] http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/trunk/ [1] http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/releases/2009.4/ [2] http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/releases/2010.0/ -- 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
[hugin-ptx] Re: Hugin 2009.4.0 released
Bruno Postle wrote: Thanks to everyone responsible for this release! Thanks to you for picking up the pieces and bringing the process I left suspended to completion. Good job! Also congratulations to James for merging into trunk the layout branch. You guys have done an excellent job at absorbing the backlog of new features/developments and preparing Hugin for more. I'm less sanguine about what I read has happened on this mailing list / community in the past two months. Following are my observations about the past two months, the immediate future, and the far future. THE PAST TWO MONTHS Looking at the list from a distance, I see more than what I can / want to tolerate of (in no particular order) 1 - (unintentional but avoidable) mistakes 2 - trolling 3 - partial lack of direction, sense of purpose 1- I replied to the one uninformed and unintentional mistake that IMHO should not be left unaddressed [0]. There were some more, minor technical ones. The technical documentation is out there to set thing straight [1]. Most contributors have stepped in and understood the separation of development cycles from release cycles and its advantages. I deem the restructuring of the repository a milestone accomplished. The occasional uninformed and unintentional mistake should be addressed, first and foremost with some self-responsibility of the contributor. 2 - I made an effort to ignore the troll even when I see smart people fall for it; and when I see misconceptions spread. Subject matter is secondary in a troll. Community reaction is what matters. Silence is the best reaction to a troll. But not to personal attacks. I am disappointed at how this community has done things the other way around: so much subject matter discussion (that mostly went nowhere) and little reaction to personal attacks, veiled and direct. [2] [3]. 3 - The partial lack of direction and sense of purpose relates specifically to the Windows version. My plan was to bring the Windows support in line with the excellent Mac support. My wish was to achieve this for the release of the layout branch (2010.2) and from then on to keep tracking closely the tarball releases, like the OSX bundles have been doing for some time. I suspect it is an unrealistic wish. The undertaking is bigger than what most people who have rushed in support of a Windows version think. It starts with the SDK that is not even defined. It takes a process of keeping things updated and in sync. Unfortunately, while Windows users clearly express the wish for a binary installer, most of those who achieve partial (or full) results on their own machine stop short of publishing/sharing and helping others to build on top of their results. The wheel is being reinvented constantly. Windows users seem not to learn from those who have been through it before them. Search this lists' archives. I have tried to pass on the knowledge / build up people's ability to contribute the individual parts of the SDK. I have tried to structure the effort. I consider the current status of Windows support to be my biggest failure over my past three years with Hugin, but I lack the support, resources and motivation to fix this. A quick fix would be to install a clean Windows environment, SDK, and build Hugin itself. Probably a week of work. Then come quality assurance and release, which is in itself easily another few days. It would be short-lived though, and unless properly maintained over the long term it would quickly become obsolete. I still have a clear plan in mind, but with so little interest from Windows users to listen and contribute it is not worthwhile to repeat what I've already been saying on this list for more than a year. Search the archives. IMMEDIATE FUTURE Hugin moves on, and 2010.0 will come along well with or without me. The tracks are laid. My first and foremost goal, when contributing to a project is to make myself redundant. Only so can the project be viable in the long term; and only so I can progress to higher levels. Bruno has done a great job at picking up the pieces of the 2009.4 release, but I wish for somebody new to drive the 2010.0 release. If Hugin is to survive, it needs a next generation to step in. Then you need somebody to drive GSoC 2010 participation, if you want to participate again. The mentoring organization is up there. For now Pablo, Alexandre, and I have admin access. I won't be available in 2010. You'll have to start preparing in a few weeks if you want to be ready. The developers will take care of fixing the bugs introduced with the new features in trunk. I have no doubt about this. Trunk is in a better state than ever, and you developers rock. The immediate future will be without me. I will stay member of the group via the web but will not revert to receive it in my mailbox. I wish all of you well - in Hugin or in your other endeavors. I have sent a little personal something to few of you. It may still be in the tangles of the postal service, or it
