Am 07.03.21 um 10:22 schrieb Bruno Postle:
On Sun 07-Mar-2021 at 10:05 +0100, Harry van der Wolf wrote:
Op za 6 mrt. 2021 om 20:03 schreef yuv:
From far away, it looks like there are four alternatives:
(a) do nothing;
(b) distribute pv along Hugin;
(c) integrate pv's functionalities into Hugin; or
(d) integrate Hugin's functionalities into pv.
My vote would be for (b), just like Kay himself also mentions.
I think this would be good, it makes sense to have a panorama viewer in
the Hugin bundle. Though aside from getting it working on all
architectures, there is a question of who maintains it once it is in the
Hugin codebase? There will be bugs that need fixing, weird new
compiler/library combinations, translations etc... Note that currently
there is a single person doing code maintenance, collecting
translations, _and_ doing the releases - these could easily be different
roles.
I propose that for now I remain upstream and responsible for the code. I
can fork out releases which I consider sufficiently stable. The hugin
builders can simply clone my git repo, *there are already branches for
all major platforms*. What's missing is the *platform integration* -
like where it is installed, if it is installed at all (my Windows
bundles are stickware, so people can just put them on a DVD alongside
with their images and give their users a free viewer to look at them),
what icon is displayed for it, what mime types are associated - and I
don't know enough about Windows or macOS to provide that, and when it
comes to Linux, I already have a debian package to maintain, so I'd be
happy if someone else could do that part - maybe somone who can build
AppImages or flatpaks. The hugin builders/packagers would be in a good
position to do so, because they already know how to roll out stuff to
their platform. Harry has demonstrated that for macOS this is not
terribly hard to do - but I could not have done this, I don't even have
a mac.
We don't know if pv will be well-received by the users - it may be too
complicated, not international enough, too slow for dual core laptops...
but throwing it out from a bundle is just as easy as putting it in and
helping it to a wider audience. Then people can decide whether they like
it or not. If people do like it, there will be ways to keep it afloat,
I'm sure. I'll do my best to keep offering a stand-alone version, and
when I get around to it, I'll try and set up a CI/CD pipeline to build
automatically and have binary for every push, but it would be nice to
get some help for that as well, just as Harry has done for macOS. And I
did also propose that packagers might offer a 'flavour' of the hugin
bundle offering my code as an addition. No reason to make an either/or
decision.
For now I'm quite busy getting the code up to the features I intend it
to have, and that's what I think I'm good at.
Kay
--
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/hugin-ptx/18878b08-376e-9644-3bc0-6ff4025791e5%40yahoo.com.
