Re: [hugin-ptx] Hugin-2011.0_beta1 released
Hullo Yuval, On Mon, 28 Feb 2011 11:54:14 +1100, Yuval Levy wrote: Hi Terry, On February 27, 2011 07:30:04 pm Terry Duell wrote: I have tried to build a Fedora package from the beta1 archive please use the beta2. It builds OK in Fedora 14, now that it isn't looking for the 'keypoints' binary. I have done a quick check and most functions that I would normally use work OK. Selecting 'help about' causes a crash. Not seen that before. Cheers, -- Regards, Terry Duell -- 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] Hugin-2011.0_beta1 released
Hullo Yuval, On Mon, 28 Feb 2011 11:54:14 +1100, Yuval Levy wrote: Hi Terry, On February 27, 2011 07:30:04 pm Terry Duell wrote: I have tried to build a Fedora package from the beta1 archive please use the beta2. I have tried that, see below. hence using a .spec file that has been suitable for all 2010.5.0 snapshots Is a .spec file something specific to Fedora? I don't know what a .spec file. Is it in our repo? A .spec file is a Fedora specification to build a binary package from a source archive. No, the .spec file isn't in our repo. , but it fails with this source. The executable 'keypoints' is not being built. The src/hugin_cpfind/localfeatures/CmakeLists.txt has the following... OPTION (BUILD_KEYPOINTS "Build keypoints program" OFF) which wasn't included in the previous versions. Is it really intended that keypoints is not built by default? yes, it is included. The keypoints executable is useful for debugging and development purposes but has little use to the general public, hence it is better not to build it by default and not to distribute it as a binary. OK, if that is the case, then I should modify my Fedora .spec file to not try to package the keypoints binary. Thanks for your help. Cheers, -- Regards, Terry Duell -- 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] Hugin-2011.0_beta1 released
Hi Terry, On February 27, 2011 07:30:04 pm Terry Duell wrote: > I have tried to build a Fedora package from the beta1 archive please use the beta2. > using a .spec file that has been suitable for all 2010.5.0 snapshots Is a .spec file something specific to Fedora? I don't know what a .spec file. Is it in our repo? > , but it fails with this source. > The executable 'keypoints' is not being built. > The src/hugin_cpfind/localfeatures/CmakeLists.txt has the following... > > OPTION (BUILD_KEYPOINTS "Build keypoints program" OFF) > > which wasn't included in the previous versions. > > Is it really intended that keypoints is not built by default? yes, it is included. The keypoints executable is useful for debugging and development purposes but has little use to the general public, hence it is better not to build it by default and not to distribute it as a binary. HTH Yuv signature.asc Description: This is a digitally signed message part.
[hugin-ptx] Hugin-2011.0_beta2 released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hugin-2011.0.0_beta2 RELEASE NOTES Hugin is a panorama stitcher and more. A new version is available. A small error passed through the beta1. Please use this tarball instead. SCHEDULE https://launchpad.net/hugin/2011.0 The purpose of the schedule is to make the process as predictable as possible so that contributors can plan for their own contributions (e.g. translations and bug fixes) and distributors can plan for the binary builds. The schedule is just an indication. The release will happen when it is ready. DOWNLOAD The 2010.4beta2 source tarball can be downloaded * from sourceforge at http://sourceforge.net/projects/hugin/files/hugin/hugin-2011.0_beta/hugin-2011.0.0_beta2.tar.bz2/download * from launchpad at http://launchpad.net/hugin/2011.0/2011.0beta2/+download/hugin-2011.0.0_beta2.tar.bz2 This is a source code release. For executables see below. This tarball is equivalent to rev/changeset 5047:f7ea2426b8de in our Mercurial repository, where it is also tagged 2011.0beta2 Verify its SHA1SUM d625af818cec0e9f9dbe4d1bfed8453c56dd2d85 hugin-2011.0.0_beta2.tar.bz2 EXECUTABLES Users communities produce executables for their respective platforms. A number of users have built recent snapshots and executables are likely to be announced within a few days of this tarball release. Watch http://groups.google.com/group/hugin-ptx for the announcements of binary releases. If you don't see a binary for your platform it has most likely not been produced yet. Consider stepping up to the task. Instructions at http://wiki.panotools.org/Development_of_Open_Source_tools#Supported_Platforms Announce your build on http://groups.google.com/group/hugin-ptx TRANSLATIONS New strings have been added. Now is a good time to help update your language. Instructions at http://wiki.panotools.org/Hugin_translation_guide VISUAL APPEARANCE To promote artists using Hugin the project will adopt a user-contributed artwork to enrich the splash screen of this release. Selection of the artwork is by popular vote. Vote at http://www.photopla.net/hugin/2011.0.artwork.html Details at http://groups.google.com/group/hugin-ptx/t/44f1834f0d18c2d8 http://groups.google.com/group/hugin-ptx/t/2c24c7938309a241 Entries are still accepted and voting goes on until a few days before the first release candidate. If you miss this cycle you will get an opportunity to enter your artwork for the next release cycle. DEDICATION This release of Hugin is dedicated to Claudius Ptolemaeus and Marinus of Tyre. Details in the About menu. CHANGES SINCE 2010.4.0 Only two months have passed since our last release and yet there have been major changes. Hugin's own control point generator cpfind has been significantly improved; the last project from the 2010 Google Summer of Code has been integrated; many general improvements have been made. _Improved Built-in Control Points Generator_ Cpfind's detection ability has been significantly improved, especially for wide angle (> FOV 65°) images, fisheye images, and rotated images. Annecdotal evidence shows it to be more accurate than any other CP detector ever used with Hugin. A thorough, scientifical comparision against other CP detectors is welcome. If you have well formed comparison results, please publish a link on the Hugin mailing list at http://groups.google.com/group/hugin-ptx/ _Improved Fast Preview_ An Overview pane has been added to the Fast Preview window. Users can now interact with the panosphere like in a virtual reality viewer in real time and visualize all areas of the panorama with little distortion, including the zenith and nadir that are typically excessively distorted in the flat preview. It is now possible to drag individual images or arbitrary groups of images on the panosphere in the fast preview. A new gray point picker has been added for visual white balance correction. _Registration of Stereo Images_ align_image_stack is commonly used for the alignment of slightly misaligned images, e.g. for creating a High Dynamic Range image from multiple exposures when the camera was hand held. It has been extended with additional functionality for the registration of stereo images. _Other Improvements_ * Man pages are now compressed and the generation is integrated in the CMake process (Linux). * New Thoby projection modeling 10.5mm Nikkor fisheye lens * Improved support for some keyboard shortcuts * New Preferences: output file format (LDR only) * This release has the usual bugfixes and adds minor features. _Libraries and Build_ * Support has been added for gcc-4.6 compiler. * Libpano13 needs to be at least 2.9.18 _Control point generators_ Since 2010.4 Hugin ships with its own 'Patent Free' control point generator. Third-party generators are still supported through the plug-in architecture. CPFind is the recommended control point generator and the only one that has the endorsement of the Hugin pro
Re: [hugin-ptx] Hugin-2011.0_beta1 released
Hullo Yuval, On Mon, 28 Feb 2011 04:14:52 +1100, Yuval Levy wrote: [snip] DOWNLOAD The 2010.4beta1 source tarball can be downloaded * from sourceforge at http://sourceforge.net/projects/hugin/files/hugin/hugin-2011.0_beta/hugin-2011.0.0_beta1.tar.bz2/download * from launchpad at http://launchpad.net/hugin/2011.0/2011.0beta1/+download/hugin-2011.0.0_beta1.tar.bz2 This is a source code release. I have tried to build a Fedora package from the beta1 archive, using a .spec file that has been suitable for all 2010.5.0 snapshots, but it fails with this source. The executable 'keypoints' is not being built. The src/hugin_cpfind/localfeatures/CmakeLists.txt has the following... OPTION (BUILD_KEYPOINTS "Build keypoints program" OFF) which wasn't included in the previous versions. Is it really intended that keypoints is not built by default? Cheers, -- Regards, Terry Duell -- 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] 2011.0 Release Plan
On February 26, 2011 06:05:08 pm Bruno Postle wrote: > If necessary libpano13-2.9.18_beta1 could be relabeled as 'final' if > we need it for a Hugin release (since it seems to be ok). Thanks, that would be very much appreciated. > As far as Hugin is concerned, the current cpfind is so much better > than anything we had before that I'd almost recommend people use a > snapshot rather than 2010.4.0. Yes, the beta tarball is out, and Thomas and Darko are hard at work fixing the rough edges of the new overview. Nothing prevents us from getting ahead of schedule if there is the motivation to do it. I updated the documentation of the release process [0] and I cleaned up the tags in Mercurial (all tags from 2009.2 onward are now consistently named). We close development branches and I was wondering if we should also close unsupported release branches? In my documentation I suggest that: - only the latest release and the active development branches are in active development - only the previous two releases are supported - older releases are obsolete Specific to the situation now: - default and 2011.0 are in active development - 2010.4 and 2010.2 are supported (i.e. we would issue a patched version if the need arises) - anything older than that is unsupported. Any opinions about this support policy? Yuv [0] http://wiki.panotools.org/Development_of_Open_Source_tools#Release signature.asc Description: This is a digitally signed message part.
Re: [hugin-ptx] Re: hugin plugin interface - developers please liaise
On Sun 27-Feb-2011 at 00:25 -0800, kfj wrote: You are missing out. I had hoped that you'd be more interested in my project, being of the scripting kind yourself. I think it going to be very useful and want to play with it (and even learn some python), but am very limited with time at the moment. Let me point out that SWIG, which I use to generate the Python interface, can generate interfaces for other languages as well (something like two dozen), among them perl. I had suspected you'd start playing with the SWIG code to let it make a perl interface. Actually I think python is the right language to be using here, since Hugin needs to work on all platforms I expect that the Windows installer will include a pythin interpreter. Please use 'GPL version 2 or later', this makes it easier to ship with Hugin. Are you concerned about how this effects the license of potential 3rd party plugins? What I mean is this: hsi, the python module that is generated by SWIG and contains the hugin functionality, can be imported by any python script that cares to do so. It's like loading a shared library from an executable program, in fact, technically, this is just what happens. But the code that finds it way into the script via this route is GPLed. Therefore, if I understand things rightly, the module would have to make itself known as GPL software, prohibit closed-source users to import it and point a way to it's sources, plus whatever other requirements the GPL imposes. We would want people to write their own scripts and not care about this stuff so long as they didn't distribute them. Hugin is GPL, and changing this (other than to version 3) isn't ever going to be practical given the number of contributors. I don't think having the plugin interface code as LGPL would make any difference to anyone writing plugins. Sadly, the Python scripting project is slightly stalled currently. This is due to the Mac side of things - Harry couldn't get it to run, went away on a holiday and noone else took over. The Linux and Windows side seems fine and ready to be merged. Harry said to go ahead, though, never mind the Mac problems. So I hope that maybe we'll soon have hpi in 'bleeding edge' mainstream and that it can maybe be part of the next release. Now that 2011.0.0 has branched, this can happen. -- 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
[hugin-ptx] Re: Undeletable artifacts
Bart,
thanks for the reply.
I have tried rebooting on one occasion - with no effect.
I still get the error message "Cannot delete file: Cannot read from
the source file or disk"
I have also tried using cmd.exe to delete, with no effect.
I will try unlocker.
my machine doesn't recognise the xcacls command.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
Z:\Artefacts\Imagery\Photo\Calendric\2011\02\Delete>xcacls pool
panorama0001.tif
'xcacls' is not recognized as an internal or external command,
operable program or batch file.
Z:\Artefacts\Imagery\Photo\Calendric\2011\02\Delete>cd ..
Z:\Artefacts\Imagery\Photo\Calendric\2011\02>cd.\24
Z:\Artefacts\Imagery\Photo\Calendric\2011\02\24>dir
Volume in drive Z is PUBLIC
Volume Serial Number is -
Directory of Z:\Artefacts\Imagery\Photo\Calendric\2011\02\24
02/01/2011 00:38 .
02/01/2011 00:38 ..
25/02/2011 12:59 4,528,960 2011-02-240001.tif
...
25/02/2011 13:01 5,542,109 2011-02-24.jpg
25/02/2011 12:19 616,889 2011-02-24B.jpg
25/02/2011 12:19 616,889 2011-02-24C.jpg
25/02/2011 13:05 5,461,989 2011-02-24B.jpg
25/02/2011 13:13 2,644 Errorlog25022011A.log
25/02/2011 12:19 3,594,283 2011-02-24A.jpg
37 File(s) 53,766,779 bytes
4 Dir(s) 143,524,888,576 bytes free
Z:\Artefacts\Imagery\Photo\Calendric\2011\02\24>xcacls
2011-02-240001.tif
'xcacls' is not recognized as an internal or external command,
operable program or batch file.
David
--
On Feb 26, 2:46 pm, Bart van Andel wrote:
> Are the files still undeletable after a reboot? If not, there might be an
> issue with the files never being closed by the application. I can't imagine
> why this would happen, but it is a possibility. A workaround might be to use
> unlocker [0], in this case.
>
> If this is not the case, another possibility may be that somehow the files
> are saved such that you don't have rights to delete the file. Could you open
> a command prompt (cmd.exe), browse to the directory mentioned where the
> intermediate files are stored ("cd /d
> Z:\Artefacts\Imagery\Photo\Calendric\2011\02\24"
> if that's where the files are stored), and run xcacls on the temporary file
> (e.g. "xcacls 2011-02-24.tif")? This shows the access control list (ACL)
> associated with the file. Could you post the results here?
>
> By the way, I'm not sure but this last log line strikes me as abnormal?
> Maybe someone else can comment on this?
> enblend: input image "2011-02-240002.tif" does not have an alpha channel
>
> --
> Bart
>
> [0]http://unlocker.emptyloop.com/
--
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 plugin interface - developers please liaise
On 27 Feb., 09:25, kfj <_...@yahoo.com> wrote: > Just today I thought about how I could modify it > so that all dependencies to the hsi python module are removed from > hugin itself. This would mean a totally neutral python interface, and > the conversion of C++ pointers into python objects would be done by > code outside hugin. This change of design would mean that... hmmm... I'll eat my words here and state that having looked into the matter, the current implementation is the best way. So I won't change the hpi implementation - and, after all, it does what it's supposed to do. I did something else today: in a clean, fresh clone I merged the python_scripting branch back into the trunk. There were minor conflicts in three files which were trivial to sort out, and a bit of code had to be changed in the interface because some headers had moved or disappeared. No big deal at all. Afterwards I was rewarded with a Python enabled version of bleedig edge. This is nice, it runs much more smoothly than whatever was the base for the python_scripting branch. One thing that puzzled me, though, was that I could only compile with either BUILD_HSI=ON or =OFF and not compile the other version later by changing the flag; it would just maintain everything was built already and not reflect the change of the flag. To be sure the compile switch worked I checked each setting on a separate clone, and both versions performed as expected. I hope the python_scripting branch can be merged back soon before the divergence becomes greater. The compile switch off allows creation of non-hsi hugin as before, and with it on, the resulting compile is on the same patch level as trunk. Sounds like a win-win situation to me ;-) 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
Re: [hugin-ptx] Re: can't download libpano
Hi, please type: hg branch and if you are not in libpano then: hg update -C libpano and try again I suspect you are in a branch. --dmg On Sun, Feb 27, 2011 at 10:08 AM, Teodora Chitiboi wrote: > Hi again, > > I succesfuly downloaded libpano but now I can't seem to compile it. > Looks like I'm missing some header (:-?) > I am following the instructions on the wiki page. I am running under > Ubuntu 10.04 and my gcc compiler version is 4.1.3 > Here is my output. > > [ 6%] Building C object CMakeFiles/pano13.dir/file.c.o > /home/teodora/src/libpano/libpano/file.c: In function > ‘panoPSDResourcesBlockWrite’: > /home/teodora/src/libpano/libpano/file.c:235: warning: implicit > declaration of function ‘min’ > /home/teodora/src/libpano/libpano/file.c:265: error: ‘_MAX_PATH’ > undeclared (first use in this function) > /home/teodora/src/libpano/libpano/file.c:265: error: (Each undeclared > identifier is reported only once > /home/teodora/src/libpano/libpano/file.c:265: error: for each function > it appears in.) > /home/teodora/src/libpano/libpano/file.c:268: warning: implicit > declaration of function ‘GetModuleFileName’ > /home/teodora/src/libpano/libpano/file.c:265: warning: unused variable > ‘AppNamePath’ > /home/teodora/src/libpano/libpano/file.c:296: error: ‘SYSTEMTIME’ > undeclared (first use in this function) > /home/teodora/src/libpano/libpano/file.c:296: error: expected ‘;’ > before ‘SysTime’ > /home/teodora/src/libpano/libpano/file.c:297: error: > ‘TIME_ZONE_INFORMATION’ undeclared (first use in this function) > /home/teodora/src/libpano/libpano/file.c:297: error: expected ‘;’ > before ‘TimeZoneInformation’ > /home/teodora/src/libpano/libpano/file.c:299: warning: implicit > declaration of function ‘GetLocalTime’ > /home/teodora/src/libpano/libpano/file.c:299: error: ‘SysTime’ > undeclared (first use in this function) > /home/teodora/src/libpano/libpano/file.c:300: warning: implicit > declaration of function ‘GetTimeZoneInformation’ > /home/teodora/src/libpano/libpano/file.c:300: error: > ‘TimeZoneInformation’ undeclared (first use in this function) > /home/teodora/src/libpano/libpano/file.c: In function ‘addLayer’: > /home/teodora/src/libpano/libpano/file.c:1804: warning: '0' flag > ignored with precision and ‘%d’ printf format > /home/teodora/src/libpano/libpano/file.c:1829: warning: comparison is > always false due to limited range of data type > /home/teodora/src/libpano/libpano/file.c: In function > ‘readPSDMultiLayerImage’: > /home/teodora/src/libpano/libpano/file.c:2279: warning: pointer > targets in passing argument 2 of ‘panoReadINT32’ differ in signedness > /home/teodora/src/libpano/libpano/file.c:2280: warning: pointer > targets in passing argument 2 of ‘panoReadINT32’ differ in signedness > /home/teodora/src/libpano/libpano/file.c:2281: warning: pointer > targets in passing argument 2 of ‘panoReadINT32’ differ in signedness > /home/teodora/src/libpano/libpano/file.c:2282: warning: pointer > targets in passing argument 2 of ‘panoReadINT32’ differ in signedness > make[2]: *** [CMakeFiles/pano13.dir/file.c.o] Error 1 > make[1]: *** [CMakeFiles/pano13.dir/all] Error 2 > make: *** [all] Error 2 > > > Thanks again for your help. > > Best, > Teodora > > > On Feb 27, 4:38 pm, Jim Watters wrote: >> On 2011-02-27 10:17 AM, teodora chitiboi wrote:> Hi, >> >> > I'm new to Hugin and I'm trying to download Libpano13 : >> > hg >> > clonehttp://panotools.hg.sourceforge.net:8000/hgroot/panotools/panotools/l... >> >> The path has changed slightly, try this. >> >> hg clonehttp://panotools.hg.sourceforge.net:8000/hgroot/panotools/libpano >> >> -- >> Jim Wattershttp://photocreations.ca > > -- > 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 > > -- --dmg --- Daniel M. German http://turingmachine.org -- 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: can't download libpano
Hi again, I succesfuly downloaded libpano but now I can't seem to compile it. Looks like I'm missing some header (:-?) I am following the instructions on the wiki page. I am running under Ubuntu 10.04 and my gcc compiler version is 4.1.3 Here is my output. [ 6%] Building C object CMakeFiles/pano13.dir/file.c.o /home/teodora/src/libpano/libpano/file.c: In function ‘panoPSDResourcesBlockWrite’: /home/teodora/src/libpano/libpano/file.c:235: warning: implicit declaration of function ‘min’ /home/teodora/src/libpano/libpano/file.c:265: error: ‘_MAX_PATH’ undeclared (first use in this function) /home/teodora/src/libpano/libpano/file.c:265: error: (Each undeclared identifier is reported only once /home/teodora/src/libpano/libpano/file.c:265: error: for each function it appears in.) /home/teodora/src/libpano/libpano/file.c:268: warning: implicit declaration of function ‘GetModuleFileName’ /home/teodora/src/libpano/libpano/file.c:265: warning: unused variable ‘AppNamePath’ /home/teodora/src/libpano/libpano/file.c:296: error: ‘SYSTEMTIME’ undeclared (first use in this function) /home/teodora/src/libpano/libpano/file.c:296: error: expected ‘;’ before ‘SysTime’ /home/teodora/src/libpano/libpano/file.c:297: error: ‘TIME_ZONE_INFORMATION’ undeclared (first use in this function) /home/teodora/src/libpano/libpano/file.c:297: error: expected ‘;’ before ‘TimeZoneInformation’ /home/teodora/src/libpano/libpano/file.c:299: warning: implicit declaration of function ‘GetLocalTime’ /home/teodora/src/libpano/libpano/file.c:299: error: ‘SysTime’ undeclared (first use in this function) /home/teodora/src/libpano/libpano/file.c:300: warning: implicit declaration of function ‘GetTimeZoneInformation’ /home/teodora/src/libpano/libpano/file.c:300: error: ‘TimeZoneInformation’ undeclared (first use in this function) /home/teodora/src/libpano/libpano/file.c: In function ‘addLayer’: /home/teodora/src/libpano/libpano/file.c:1804: warning: '0' flag ignored with precision and ‘%d’ printf format /home/teodora/src/libpano/libpano/file.c:1829: warning: comparison is always false due to limited range of data type /home/teodora/src/libpano/libpano/file.c: In function ‘readPSDMultiLayerImage’: /home/teodora/src/libpano/libpano/file.c:2279: warning: pointer targets in passing argument 2 of ‘panoReadINT32’ differ in signedness /home/teodora/src/libpano/libpano/file.c:2280: warning: pointer targets in passing argument 2 of ‘panoReadINT32’ differ in signedness /home/teodora/src/libpano/libpano/file.c:2281: warning: pointer targets in passing argument 2 of ‘panoReadINT32’ differ in signedness /home/teodora/src/libpano/libpano/file.c:2282: warning: pointer targets in passing argument 2 of ‘panoReadINT32’ differ in signedness make[2]: *** [CMakeFiles/pano13.dir/file.c.o] Error 1 make[1]: *** [CMakeFiles/pano13.dir/all] Error 2 make: *** [all] Error 2 Thanks again for your help. Best, Teodora On Feb 27, 4:38 pm, Jim Watters wrote: > On 2011-02-27 10:17 AM, teodora chitiboi wrote:> Hi, > > > I'm new to Hugin and I'm trying to download Libpano13 : > > hg > > clonehttp://panotools.hg.sourceforge.net:8000/hgroot/panotools/panotools/l... > > The path has changed slightly, try this. > > hg clonehttp://panotools.hg.sourceforge.net:8000/hgroot/panotools/libpano > > -- > Jim Wattershttp://photocreations.ca -- 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] can't download libpano
Thank you :) On Sun, Feb 27, 2011 at 4:38 PM, Jim Watters wrote: > On 2011-02-27 10:17 AM, teodora chitiboi wrote: > >> Hi, >> >> I'm new to Hugin and I'm trying to download Libpano13 : >> hg clone >> http://panotools.hg.sourceforge.net:8000/hgroot/panotools/panotools/libpano.hg >> > The path has changed slightly, try this. > > hg clone http://panotools.hg.sourceforge.net:8000/hgroot/panotools/libpano > > > -- > Jim Watters > http://photocreations.ca > > -- > 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 > -- Teodora . -- 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] can't download libpano
On 2011-02-27 10:17 AM, teodora chitiboi wrote: Hi, I'm new to Hugin and I'm trying to download Libpano13 : hg clone http://panotools.hg.sourceforge.net:8000/hgroot/panotools/panotools/libpano.hg The path has changed slightly, try this. hg clone http://panotools.hg.sourceforge.net:8000/hgroot/panotools/libpano -- Jim Watters http://photocreations.ca -- 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] 2011.0 Artwork: voting starts now
Hoi Habi, On February 27, 2011 10:02:34 am David Haberthür wrote: > Thanks for setting this up. I was just wondering if - for voting - we don't > need any names associated with the entries, so people vote freely. Good point for the next iteration. But then entries should not be made in public in the first place [0]. There are a few other T&C issues (e.g. multiple entries per person) that need to be refined/addressed, but I rather let this iteration complete as-is for now (we're doing well), then do a post-mortem analysis and make changes for the next iteration. > "David Haberthuer" instead of "David Habertuehr" :) Sorry for the typo! Fixed (while waiting for a test build on the way to the 2011.0beta1 release). It is actually a file name that was mis-spelled by myself and propagated. All I had to do was to rename the file and run the script again. The file name has no influence on the voting. Keep on voting! Yuv [0] http://groups.google.com/group/hugin-ptx/t/2c24c7938309a241 signature.asc Description: This is a digitally signed message part.
[hugin-ptx] can't download libpano
Hi,
I'm new to Hugin and I'm trying to download Libpano13 :
hg clone
http://panotools.hg.sourceforge.net:8000/hgroot/panotools/panotools/libpano.hg
but I get :
** unknown exception encountered, details follow
** report bug details to http://mercurial.selenic.com/bts/
** or mercur...@selenic.com
** Mercurial Distributed SCM (version 1.4.3)
** Extensions loaded:
Traceback (most recent call last):
File "/usr/bin/hg", line 27, in
mercurial.dispatch.run()
File "/usr/lib/pymodules/python2.6/mercurial/dispatch.py", line 16,
in run
sys.exit(dispatch(sys.argv[1:]))
File "/usr/lib/pymodules/python2.6/mercurial/dispatch.py", line 30,
in dispatch
return _runcatch(u, args)
File "/usr/lib/pymodules/python2.6/mercurial/dispatch.py", line 46,
in _runcatch
return _dispatch(ui, args)
File "/usr/lib/pymodules/python2.6/mercurial/dispatch.py", line 454,
in _dispatch
return runcommand(lui, repo, cmd, fullargs, ui, options, d)
File "/usr/lib/pymodules/python2.6/mercurial/dispatch.py", line 324,
in runcommand
ret = _runcommand(ui, options, cmd, d)
File "/usr/lib/pymodules/python2.6/mercurial/dispatch.py", line 505,
in _runcommand
return checkargs()
File "/usr/lib/pymodules/python2.6/mercurial/dispatch.py", line 459,
in checkargs
return cmdfunc()
File "/usr/lib/pymodules/python2.6/mercurial/dispatch.py", line 453,
in
d = lambda: util.checksignature(func)(ui, *args, **cmdoptions)
File "/usr/lib/pymodules/python2.6/mercurial/util.py", line 386, in
check
return func(*args, **kwargs)
File "/usr/lib/pymodules/python2.6/mercurial/commands.py", line 649,
in clone
update=opts.get('updaterev') or not opts.get('noupdate'))
File "/usr/lib/pymodules/python2.6/mercurial/hg.py", line 187, in
clone
src_repo = repository(ui, source)
File "/usr/lib/pymodules/python2.6/mercurial/hg.py", line 63, in
repository
repo = _lookup(path).instance(ui, path, create)
File "/usr/lib/pymodules/python2.6/mercurial/httprepo.py", line 263,
in instance
inst.between([(nullid, nullid)])
File "/usr/lib/pymodules/python2.6/mercurial/httprepo.py", line 184,
in between
d = self.do_read("between", pairs=n)
File "/usr/lib/pymodules/python2.6/mercurial/httprepo.py", line 128,
in do_read
fp = self.do_cmd(cmd, **args)
File "/usr/lib/pymodules/python2.6/mercurial/httprepo.py", line 102,
in do_cmd
proto = resp.headers['content-type']
File "/usr/lib/python2.6/rfc822.py", line 388, in __getitem__
return self.dict[name.lower()]
KeyError: 'content-type'
Could I get any help with this please? Thanks.
Best,
Teodora.
--
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] 2011.0 Artwork: voting starts now
Hey Yuv. On 26.02.2011, at 19:25, Yuval Levy wrote: > Hi all, > > You will find at [0] images of the candidates for the splash screen / about > menu of the upcoming Hugin 2011.0, as well as a link to vote for your > favorite. > > Rules and the detailed description of the entries are at [1]. > > Voting is open now and will stay open during the beta phase of the release > cycle. Voting will close a couple of days before the end of the beta phase > and the splash screen will be integrated into the first release candidate. Thanks for setting this up. I was just wondering if - for voting - we don't need any names associated with the entries, so people vote freely. And if we need the names, I'd like you to change my name do "David Haberthuer" instead of "David Habertuehr" :) Habi -- 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] Big list of suggestions
On Sat, Feb 26, 2011 at 07:35:50PM -0500, Yuval Levy wrote: > > - I would like to be able to move/resize the overall view under > > the "Preview" and "Layout" tabs with the mouse (ie. not > > with the sliders). > > Why, if I may ask? And how would you like the mouse to behave? When examining a preview, you would like to have a quick overview look. Then you notice a detail, zoom in on the detail, zoom back out. repeat. You want to be able to leave you hand on the mouse while you look here, there. All this would be preferred if it can be done with "big gestures" instead of having to exactly click on scrollbars etc. That's the "why". Now the how. :-) Most programs have a "click-to-drag" and a "scroll-to-zoom" configuration. That'd be nice. One program I often use has middle click to drag and another uses leftclick to drag. Annoying. But both these are easy to find if you leave your hand on your mouse, and can be operated with the eyes "on the image" instead of "on the mousepointer"... > > - I don't know how to adjust the scale of the images in the overview > > window (they seem too big in my project). > There should not be a need to scale the images in the overview > window. That's their size, shape, position in relation to the > panosphere. If they seem to big, the project is not properly > aligned / optimized. I think he's looking for the pano-fov parameters. Try "fit" or adjust the fov parameters on the "stitch" tab. Roger. -- ** r.e.wo...@bitwizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 ** **Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233** *-- BitWizard writes Linux device drivers for any device you may have! --* Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. Does it sit on the couch all day? Is it unemployed? Please be specific! Define 'it' and what it isn't doing. - Adapted from lxrbot FAQ -- 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 plugin interface - developers please liaise
On 27 Feb., 00:05, Bruno Postle wrote: > Sorry, I haven't had time to look into this. You are missing out. I had hoped that you'd be more interested in my project, being of the scripting kind yourself. Let me point out that SWIG, which I use to generate the Python interface, can generate interfaces for other languages as well (something like two dozen), among them perl. I had suspected you'd start playing with the SWIG code to let it make a perl interface - I made a feeble attempt to do so, but knowing nothing of perl I gave up at the first hurdle... > I think initially the > python interface would be useful even if it presents as a menu of > functions that don't take any parameters apart from the currently active panorama, that is. But it's a severe limitation. For example now I'm working on a plugin that works on image pairs. I either have to hardcode the image numbers into the script, write GUI code myself to let a window pop up to ask for them, or require the user to make the desired images 'active' and 'deactivate' the others. This is not nice. The clean way would be for the user to highlight the images in question in the image tab and then call the plugin from the contect menu. > i.e. it can be merged > more-or-less in the state it is in. I think so as well. Just today I thought about how I could modify it so that all dependencies to the hsi python module are removed from hugin itself. This would mean a totally neutral python interface, and the conversion of C++ pointers into python objects would be done by code outside hugin. This change of design would mean that - other people would be free to write their own python modules rather than having to rely on hsi - hugin would merely be extended by a dependency on python (maybe not even a run-time dependency, the way I think it can be done is only require python if the plugin interface is actually used) and not be dependent on hsi I feel that this might make the introduction into the mainstream even less of a concern. I'll look into the matter and report back, with a bit of luck the changes should be small (couple of days) > >Then there is an issue I'd like to have considered by the group: the > >hsi python module could be considered a library, since it can do hugin- > >ish stuff outside hugin, probably linking in a few shared libraries, > >but if it was linked statically, not even that. A lot of hugin's code > >is GPLed. Is there a problem with that? > > Please use 'GPL version 2 or later', this makes it easier to ship > with Hugin. Are you concerned about how this effects the license of > potential 3rd party plugins? What I mean is this: hsi, the python module that is generated by SWIG and contains the hugin functionality, can be imported by any python script that cares to do so. It's like loading a shared library from an executable program, in fact, technically, this is just what happens. But the code that finds it way into the script via this route is GPLed. Therefore, if I understand things rightly, the module would have to make itself known as GPL software, prohibit closed-source users to import it and point a way to it's sources, plus whatever other requirements the GPL imposes. This is why libraries are often put under LGPL or a similar less restrictive license, so that anyone can use them with their code, even if they're commercial. I don't want to infringe upon the rights of any of the hugin contributors by opening up a route of access to their code that goes against their licensing of it. This is why I want the issue discussed. I think the ideal solution would be if the developers who have contributed code that is exposed via hsi might modify their licensing to allow use of their code via hsi under a less restrictive license, but if this is not feasible I want to be certain that all requirements are met to satisfy the contributors' current licensing under GPL. > >And one more thing: I'd like to see a discussion about a perspective > >for merging the python_scripting branch back into the mainstream. > >Thomas and I have made a good effort to parametrize everything in > >cmake and make the scripting capability a compile-time option. The > >intersections with other code are minimal and well #ifdeffed. > > I would like to see the current Hugin 'trunk' move to a 2011.0.0 > release branch as soon as possible. So the python interface should > then be merged so that it goes into the next release after that. Sadly, the Python scripting project is slightly stalled currently. This is due to the Mac side of things - Harry couldn't get it to run, went away on a holiday and noone else took over. The Linux and Windows side seems fine and ready to be merged. Harry said to go ahead, though, never mind the Mac problems. So I hope that maybe we'll soon have hpi in 'bleeding edge' mainstream and that it can maybe be part of the next release. Kay -- You received this message because you are subscribed to the Google Groups "Hugin and other free p
