On August 28, 2010 05:52:17 am thePanz wrote:
> Hi, I've created a small installer for Hugin 2010.1
Cool. What installer framework did you use?
> I'd like to know where (in the rewindows registry) Hugin stores its
> settings: I'd like to provide a full-clean uninstall and to update
> settings with the installed ContrlPoint generators before public my
> installer :)
>
> Any help?
look for the [Registry] section. Line 193 and following at the time of
writing.
the settings for the CP generators are around line 214 and can probably need
an update for the new multi-row mode.
Yuv
IIRC those are only presets. It does not really matter if the CP generators
are delivered with the Hugin installer or not, the presets are written into
the registry so that the user can select one of them. Of course, if the
associated CP detector is not present, it won't work.
Packages of Hugin have been circulating with or without included CP
generators. Most CP generators available are encumbered by patents in some
jurisdictions, making a distribution of an installer like yours (from your
description I infer that it includes panomatic) touchy. Make sure it's OK in
your jurisdiction - panomatic is protected by the SURF patent.
> Waiting for your feedback and suggestions.. :)
Thank you for your work. Do you want to commit your script to the project's
repository?
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 hugi...@googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
On August 31, 2010 10:18:16 am Aron H wrote:
> I'm a bit surprised you chose to implement a new installer, instead of
> working on the one already committed to Hugin, based on InnoSetup.
> Was it lacking some features, or did you not know it was there?
I can't speak for him but there can be many reasons to implement a new
installer. I implemented the current InnoSetup installer [0] back in the 0.7
days when there was already an MSI-based Installer [1].
My motivation for changing to InnoSetup was simple: I had previous experience
with InnoSetup and it took me less time than trying to understand the
convoluted Microsfot stuff.
An installer is pretty much a self-contained endeavor and a change of
technology does not have many consequences on the rest of the project. So any
technology is game as long as it does its job.
Yuv
[0]
http://hugin.hg.sourceforge.net/hgweb/hugin/hugin/file/93786aecb6fb/platforms/windows/installer
[1]
http://hugin.hg.sourceforge.net/hgweb/hugin/hugin/file/93786aecb6fb/platforms/windows/msi
I forgot this very important detail. Sorry. This is what makes your
installer superior to anything else we had previously.
Adding a "License" for each CP-generator during install is not necessary.
What I would advise to do is to put a generic disclaimer - the same one for
all CP-generators - with a statement like:
"you have elected to download and install one or many additional software
packages for control point generation. Be aware that these packages are
separate from Hugin. These packages may or may not be encumbered by patents
in your residence's jurisdiction and they are subject to their own licenses.
It is your responsibility to make sure that you are not infringing on any
rights when installing and running these packages in your jurisdiction".
Have the user accept it prior to initiating the download/install of the third
party packages.
Note that my feedback is given blind (I have no Windows box to test your
Installer), so maybe the process is not as I imagine it. Feel free to adapt
my feedback to your needs or push back at me my wrong assumptions.
> Great! Maybe if I could commit my edits and corrections to Hugin
> repository may be better, what you think? I'm non new to SVN, CVS or
> HG version control systems... let me know..
do you have a SourceForge user name? please publish it here so that you can
be granted write privilege on the Hg repository. Hugin no longer uses SVN or
CVS. Don't worry about being new, there is very little that can go wrong when
using Hg.
Welcome on board!
Yuv
nobody followed up on this and I was away and am still submerged by a pile of
"todos".
I've granted you access, you can now push your edits to the official repo on
SF (a good place would be a new folder in platforms/windows); and you can add
files to SourceForge download section.
Sorry I don't have more time to support you at the moment, others can tell you
how to push your edits.
This is also a good time to clean up and update the authors.txt [0] file - add
people who have contributed to the new installer; as well as people who have
contributed new things to Hugin since that file was last updated. I put in a
few things I know out of my head, but I have not been following Hugin closely
enough. Best thing is if the individual contributors would add themselves.
[0]
http://hugin.hg.sourceforge.net/hgweb/hugin/hugin/file/d21377b2c560/authors.txt
I've just downloaded and installed. Worked perfectly so far, but the
command line utilities give TIFFReadDirectory warnings (f.e. regarding
invalid XML packets which is quite common for files written by photoshop
or DPP) as modal dialogs again instead of console output. This was
already solved many versions ago.
This is probably not related to your installer but to the hugin and
utilities version it installs. In this case align_image_stack.exe
Pre-Release 2010.1.0.5161 built by zoran zorkic might be the culprit.
--
Erik Krause
http://www.erik-krause.de
Sorry John. I don't know why either - my post are plain text written with
KMail. Anybody else experiencing this issue?
An issue I have is with one or two users posting HTML mails to the mailing
list - but given the "evolution" of email clients I am afraid we'll have to
live with that.
Yuv
> Sorry John. I don't know why either - my post are plain text written with
> KMail. Anybody else experiencing this issue?
Nope, they all arrive fine here on the other end of the world. Maybe John added you to his Killfile [1]
Habi
This is a very long standing problem with Microsoft products
refusing to view pgp-mime signed mail.
--
Bruno
> I assume, that the builder has compiled libtiff without this change.
> Please check your libtiff.
In this case: thePanz, could you use a different source for the binaries
in the installer?
Am 12.09.2010 17:18, schrieb T. Modes:In this case: thePanz, could you use a different source for the binaries in the installer?
I assume, that the builder has compiled libtiff without this change.
Please check your libtiff.
On September 3, 2010 03:12:01 pm thePanz wrote:
> http://thepanz.netsons.org/post/windows-instaler-for-hugin-2010
I've imported your NSIS installer [0] to sourceforge. As stated previously,
you have write access to the repo and it should not be much different than Hg
on BitBucket. Or do you see an advantage in using BitBucket over SourceForge?
saluti
Yuv
[0]
http://hugin.hg.sourceforge.net/hgweb/hugin/hugin/file/tip/platforms/windows/huginsetup
On September 15, 2010 09:38:55 am thePanz wrote:
> Thank you for importing my NSIS package into SourceForge. I've been
> quite busy in latest days, I'll continue posting my updates to SF as
> soon as possible.
> I'd like to know (I read about this feature on Mercurial website) if
> SF can handle sub-repositories: I'd like to maintain (and get in sync)
> only with the HuginSetup part of the "Hugin" project because I don't
> have any expertise (and knowledge) on Hugin and wxWidgets
> programming..
where in the Mercurial website do you read about this feature? You know more
than I. When I researched this feature it was not available. Usually what is
default in Mercurial trickles down to SF, maybe with some delay, but they do
update / keep up.
what we can do if it is more convenient for you is start an extra repository -
qw currently have seven [0] of them and SF sets no limits.
let me know if you can add to the Hugin main repo (preferred, since that's
were all other packages / installers of Hugin are generated for other
platforms) or if you prefer me to open a new repo for you.
buon fine settimana.
Yuv