test version of official installers for Hugin 0.8 on Windows
allard
I built two versions of installer files for Hugin 0.8 on Windows. One
version includes patented control point generators (
http://hugin.panotools.org/testing/hugin/Hugin08_W32_complete_setup.exe
) and one that does not include them (
http://hugin.panotools.org/testing/hugin/Hugin08_W32_ncpg_setup.exe ).
Please test them so they can be uploaded to the sourceforge
repository. The only thing that needs to be tested is the installer
itself, the program is the SVN4008 version that was decided to be the
official 0.8 release and should not require testing.
What I need to know is
-are the texts of the installer licence and release notes acceptable?
-is the program installed correctly with all the options as selected?
-any other issues regarding the installation?
Any suggestions on the installer licence texts are welcome, that's not
really my specialty. I haven't really had time to do a lot of testing
of things like installing parallel versions, but that seems to work in
the limited tests I did. If everyone agrees this is ok, someone with
access can upload these to sourceforge, I don't have access there.
allard
Yuval Levy
> The only thing that needs to be tested is the installer
> itself, the program is the SVN4008 version that was decided to be the
> official 0.8 release and should not require testing.
I'd test the programm too, to make sure that there is no bug introduced
by the build chain, as we've experienced recently with Ad's snapshots.
Yuv
RueiKe
for some quick testing before I call it a day so I just loaded a
recent project (93 8bit tiffs with 10,707 control points). It loaded
fine, optimize with no problems, quick preview has no issues, stitched
a small pano out of it with no issues. I also started it up in
Chinese Traditional and went through the menus with no issues. I
could run through a complete project tomorrow night, but out of time
now.
Regards,
Rick
On Jul 27, 12:20 pm, allard <ka...@physics.leidenuniv.nl> wrote:
> Hi all,
>
> I built two versions of installer files for Hugin 0.8 on Windows. One
RueiKe
above, with the Traditional Chinese interface. I verified the "Align"
function from the assitant tab, fine tune all points, optimize
everything, and optimized exposure with no problems. The only
concerns, which are not new for this release, are I always get a TIFF
library error when I open an existing project. Also, many strings
that should be translated, are still in English, some of which I am
pretty sure were in the po file, but still don't seem to be used. I
don't consider either a big issue.
Regards,
Rick
>
> - Show quoted text -
allard
general thing? Apart from that, no complaints yet it seems. How long
should we wait to release this?
Allard
RueiKe
The language problems are with some strings of some dialog boxes.
Looks like from comments in the source code repository that some of
these might have been fixed recently. When I have time, I will
download the latest build and document all cases of untranslated
strings in a new discussion thread. Also, to make it easier for
future translators, it may be a good idea to clean up the .po file. I
had to translate many strings that I have never seen while running the
application. The language problems are minor and since they display
in English when not translated, I don't think it is a significant
issue.
I don't see any issues from my tests, but sometimes I get the feeling
that my work flow may be non-typical, and maybe a bit extreme. I
don't see any issues with the release, but seeing results from another
tester would be good confirmation.
Regards,
Rick
Yuval Levy
RueiKe wrote:
> The language problems are with some strings of some dialog boxes.
there is a report from Thomas Modes of a bug that Hugin in Windows
changes the locale unexpectedly:
I could not reproduce in Ubuntu.
> download the latest build and document all cases of untranslated
> strings in a new discussion thread. Also, to make it easier for
> future translators, it may be a good idea to clean up the .po file.
thanks for offering to clean up. There is a script in the translation
folders
<http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/trunk/src/translations/extract-messages.sh?revision=3587>
For the little I understand of bash scripts, this one merges new strings
into the .po file. It would be good if a volunteer skilled enough at
bash would spare you the manual work of cleaning up. You translators
deserve better than the current status.
> I don't think it is a significant issue.
agree, it should not block the release of the installer like it has not
blocked the release of the source tarball.
> results from another tester would be good confirmation.
my windows box is unaccessible at the moment :( and when it will be
accesible there is enough bread on my table. Christoph Spiel's
enblend-enfuse staging branch does not build on Windows and he is
helping me to fix that. And then there is a bug (because of Windows)
with celeste_standalone not finding the model file.
> On Jul 29, 12:32 pm, allard <ka...@physics.leidenuniv.nl> wrote:
>> no complaints yet it seems. How long
>> should we wait to release this?
Hi Allard,
I have not gone over it yet. You mentioned the licensing and release
texts. Looks like I'll have to spend more time in Windows than I would
like. Sigh...
Yuv
allard
Just to help you stay away from the dark side, here's what I made of
the text fileinstaller_licence.txt:
_____________
Copyright (C) 2006-2009 Pablo d'Angelo.
Additional Authors see AUTHORS.txt files in the documentation.
Built and packaged for binary redistribution 2009/07/26 by Allard.
UPGRADES
This version of Hugin is backwards compatible, and there should not be
good reasons to keep using the previous stable version. If you wish to
do so however, it is possible to install them side-by-side. If not,
please uninstall the previous version before running this installer.
SHELF-LIFE
Hugin is under constant development, and the code evolves rapidly.
Nevertheless, stable releases like this are not very frequent. If you
are looking for newer features or the latest cutting edge development
snapshots, and are willing to accept all the risks involved, look for
them at Yuval Levy's page: <http://panospace.wordpress.com/downloads/
>. New stable releases will be announced on the hugin home page:
<http://hugin.sf.net/>
DISCLAIMER
The programs in this installer are tested to some extent, but they may
not
work as expected. Use them at your own risk.
This installer is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
LICENSE
The control point generators shipped with this installer
* autopano-sift-C
* panomatic
* Autopano
are based on the SIFT algorithm. This algorithm is patented in the USA
by the University of British Columbia. Commercial applications of
these control point generators in the USA may require a licence from
the University of British Columbia.
For all other parts of this installer, you are free to use, copy,
distribute, modify them. Unless you distribute you should not be
worried by
the following licensing terms.
All files in this archive are subject to the included licenses.
Details in
enblend/LICENSE_GPL.txt
enblend/LICENSE_VIGRA.txt
hugin/LICENSE_GPL.txt
hugin/LICENSE_JHEAD.txt
hugin/LICENSE_VIGRA.txt
panotools/LICENSE_GPL.txt
DISTRIBUTION
Distribution in compliance with GPL permitted and encouraged.
If you distribute, you MUST include a copy of the applicable
licenses and give access to the source code of executable binaries.
The source code for the binaries can be acessed at
enblend <http://sourceforge.net/cvs/?group_id=123407>
hugin <http://sourceforge.net/svn/?group_id=77506>
panotools <http://sourceforge.net/svn/?group_id=96188>
DOCUMENTATION
Basic information:
- start hugin from the start / all programs menu. Use the help menu.
- start binaries from the command line with no arguments.
Further usage information may be found at
<http://wiki.panotools.org/Hugin>
<http://wiki.panotools.org/Enblend>
<http://wiki.panotools.org/Enfuse>
<http://wiki.panotools.org/Panotools>
<http://wiki.panotools.org/Panorama_Tools_Plugins>
It is likely that some or all information at the above page does not
apply
to the software installed. If the installed software does not perform
as expected, it is because it is experimental and some functions may
be
incomplete, broken, obsolete, new or otherwise missing in action.
Before reporting problems with the documentation or asking for
support,
please download the lastest version of this installer from
<http://panospace.wordpress.com/downloads/>
and see if it solves the problems you'd like to report.
_____________
The release notes I just copy-pasted from Bruno's post on this forum.
I'm not very well informed about the exact legal implications of the
patent situation, so it would be great if someone can confirm this
won't get the hugin project into trouble. Except for patent lawyers I
haven't met any Windows user (including myself) who actually reads
licence agreements, so I guess that part is the only thing that
matters.
Allard
Henk Tijdink
For me there is some confusion about the control point pickers.
You mention that all control point pickers are based on the SIFT
algorithm. (Autopano-sift-C, Panomatic and Autopano)
But when selecting autopano(A. Jenny) in the preference screen it
can't find autopano.exe in the binaries.
Checking the binaries I find an autopano.exe, but that is the
autopano.exe from Autopano-sift of S. Nowozin(generatekey.exe and
autopano.exe)
The autopano from A. Jenny is not in the installer, but only the
autopano-SIFT of S. Nowozin or derivate of it.
When you download and install Autopano of A. Jenny then you can use it
when giving the path in the preference screen.
Kind regards,
Henk Tijdink
Yuval Levy
allard wrote:
> Just to help you stay away from the dark side, here's what I made of
> the text fileinstaller_licence.txt:
it's not so much the dark side, as it is the hot side. no airco in the
office, my boss is cheap (did I tell you I'm my own boss?) so I work on
the Ubuntu notebook in the airconditioned zone.
thanks for providing the text, my feedback between the lines.
> UPGRADES
> This version of Hugin is backwards compatible, and there should not be
> good reasons to keep using the previous stable version. If you wish to
> do so however, it is possible to install them side-by-side. If not,
> please uninstall the previous version before running this installer.
not really. 0.7 and 0.8 will conflict in the registry. IIRC using the
more recent autopano expandos in 0.8 will result in hugin 0.7 passing a
wrong input to autopano in 0.7.
> SHELF-LIFE
>
> Hugin is under constant development, and the code evolves rapidly.
> Nevertheless, stable releases like this are not very frequent. If you
> are looking for newer features or the latest cutting edge development
> snapshots, and are willing to accept all the risks involved, look for
> them at Yuval Levy's page: <http://panospace.wordpress.com/downloads/
>> . New stable releases will be announced on the hugin home page:
> <http://hugin.sf.net/>
I'd remove completely this paragraph. it is appropriate with snapshots.
for a release people can expect it to last longer.
Add: <http://wiki.panotools.org/Hugin_FAQ>
and cut away what is below. Again: this is a release, not a snapshot.
> It is likely that some or all information at the above page does not
> apply
> to the software installed. If the installed software does not perform
> as expected, it is because it is experimental and some functions may
> be
> incomplete, broken, obsolete, new or otherwise missing in action.
>
> Before reporting problems with the documentation or asking for
> support,
> please download the lastest version of this installer from
> <http://panospace.wordpress.com/downloads/>
> and see if it solves the problems you'd like to report.
>
> _____________
last but not least, change the url.txt before compiling the installer.
point it to http://hugin.sourceforge.net/installed/0.8.0.shtml if you
have not done so yet (sorry I could not check, I'm now away for the
weekend and have no access to my windows workstation)
> I'm not very well informed about the exact legal implications of the
> patent situation, so it would be great if someone can confirm this
> won't get the hugin project into trouble. Except for patent lawyers I
> haven't met any Windows user (including myself) who actually reads
> licence agreements, so I guess that part is the only thing that
> matters.
There are two InnoSetup files in the repository: one with and one
without CP generators. If you don't want to get in troubles, the
conservative approach is to use the one without the CP generators.
Not reading the license agreements does not protect anybody from the
law. Each individual is expected to know and comply with their
jurisdiction's laws.
The "hugin project" is not a legal entity. As such it can't get into
troubles. We, individuals, can.
To be honest: my personal situation and my own risk assessment are such
that I have to pass on uploading your file for distribution. YMMV. If
you tell me your SF handle, I'll give you upload access, but I won't
upload your file myself, nor will I download and run it.
Yuv
Bruno Postle
>
>The language problems are with some strings of some dialog boxes.
I'm sure this is a build problem, some dialog boxes are entirely
generated by wxwidgets and would appear in English if the hugin
translation resources were present but not the wxwidgets.
--
Bruno
Yuval Levy
the wxWidgets in the SDK should be complete. Is it possible that this is
rather a consequence of the libpano locale bug that was recently fixed
by Thomas Modes?
Yuv
Bruno Postle
>>
>> I'm sure this is a build problem, some dialog boxes are entirely
>> generated by wxwidgets and would appear in English if the hugin
>> translation resources were present but not the wxwidgets.
>
>the wxWidgets in the SDK should be complete. Is it possible that this is
>rather a consequence of the libpano locale bug that was recently fixed
>by Thomas Modes?
Maybe, but these dialog boxes are very Chinese on Linux when I
change my locale to zh_TW.UTF-8
--
Bruno
Yuval Levy
Henk Tijdink wrote:
> For me there is some confusion about the control point pickers.
sorry for the confusion. Thomas Modes has improved this in SVN, so you
can expect an improvement in the next release.
> But when selecting autopano(A. Jenny) in the preference screen it
> can't find autopano.exe in the binaries.
IIRC this is because we can't distribute Alexandre Jenny's binaries.
Also it is most likely that in the future we'll move toward a "plugin"
system like on the Mac, rather than delivering all the CP generators in
the package. As a user you will have the choice to intall the one or the
other CP generator.
Yuv
allard
other thread) immediateley.
allard