Windows Build of GUI Overhaul Branch

[Matthew Petroff]

These are 32-bit Windows builds of the GUI Overhaul branch including
lensfun and Python support as well as a build of the Enblend and
Enfuse development repository tip.

Installer:
https://www.box.com/s/498e09d35722d868a169

7z Archive:
https://www.box.com/s/9490c58eef67bb099174


-Matthew

[kfj]

On 27 Mai, 04:18, Matthew Petroff <matt...@mpetroff.net> wrote:
> These are 32-bit Windows builds of the GUI Overhaul branch including
> lensfun and Python support as well as a build of the Enblend and
> Enfuse development repository tip.

Matthew, your build does not work for me:

- On W7, it installs, but crashes instantly when I try to run it
- On XP, it installs and runs, but crashes when I try to run plugins.

I noticed that the _hsi module is absent from your installer. This is
the shared library containing the python interface, it's made from the
C code which swig produces. So importing hsi from a python prompt
doesn't work either - hsi tries loading _hsi first thing, and it can't
find it (because it's not there). I suppose this failure to load _hsi
may produce the crash when trying to run plugins from hugin, but it's
only a guess. Did the plugin interface run on your system? Any hints
what might be wrong?

Kay

[Matthew Petroff]

While I included enough of Python for Hugin to run, I did not include
enough for the Python based features to work. I also mistook
"_hsi.pyd" for a ".pyc" file and accidentally deleted it before
packaging the build. Here is a new build that includes a stripped down
Python install similar to what is included with Blender or the GIMP
(the old build only included Python32.dll). I was not able to
reproduce your instant crash on Windows XP, 7, or 8 developer preview.

Installer:
https://www.box.com/s/85d189101c86e16609c8

7z Archive:
https://www.box.com/s/36b8b4d0a092da63c535

-Matthew

[Emad ud din Bhatt]

Hi,

I have just installed latest build. It installed perfectly on windows. 

But where can I see, add/delete already existing images in project?

How to set different Y,P,R values for images?

How to find exposure settings for images?

Where can I set Output size like 6000x3000 or whatever I want?

Cant see output options like Fused n blended, blended fused.

Is it still under process ?

Regards,

Emaad

--
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

--


Emaad
www.flickr.com/emaad

[Harry van der Wolf]

Hi Emaad,

2012/5/29 Emad ud din Bhatt <xyz...@gmail.com>

Hi,

I have just installed latest build. It installed perfectly on windows. 

But where can I see, add/delete already existing images in project?

How to set different Y,P,R values for images?

How to find exposure settings for images?

Where can I set Output size like 6000x3000 or whatever I want?

Cant see output options like Fused n blended, blended fused.

Is it still under process ?

I assume it's identical on all platforms, so from the "graphical assistant" you enable the "old" mode via "Edit -> Edit panorama". This enables the advanced/expert screens.

Harry

[Steeve]

Matthew

Thanks for posting these. I tried running your version, but I still
get the same exception after loading images as I get from my own build
of Hugin (posted previousily), which is re-assuring in some ways but
does not help me get a working Hugin.

I'll try another Windows machine.. tonight.

Regards
Steve

[Frederic Da Vitoria]

The new Gui works perfectly on my Vista. I did have a crash during stitching, but since this is not what GUI Overhaul is about, I concentrate on the UI.

2012/5/30 Steeve <smb...@googlemail.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 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

--
Frederic Da Vitoria
(davitof)

Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org

[kfj]

On 28 Mai, 21:48, Matthew Petroff <matt...@mpetroff.net> wrote:

> While I included enough of Python for Hugin to run, I did not include
> enough for the Python based features to work.

What is the point? Why don't you just do it like Brian in his Windows
build which he published a couple of days before you? It's a python-
enabled build, so to run it, python has to be installed. Not a
crippled isolated version (which is specifically missing the modules
which would be needed to run the few included plugins), but an
ordinary python install which everyone can get with a few clicks from
python.org. Your minimal python takes up lots of space and has heaps
of totally unnecessary stuff, and if any needed python modules can be
installed into it, it would take some wizardry which is certainly way
beyond the usual mechanism of just picking them up from the 'cheese
shop' (the python package index PyPI).

> I also mistook
> "_hsi.pyd" for a ".pyc" file and accidentally deleted it before
> packaging the build.

Ooops... you happened to forget the core component ;-)

If your intention was to provide a demo of the new GUI, you had better
built it without python. Packaging a crippled python interface will
make everyone think it's crap.

> Here is a new build that includes a stripped down
> Python install similar to what is included with Blender or the GIMP
> (the old build only included Python32.dll).

I think this isn't a good idea. I say again: If the user installs a
python-enabled build, he/she needs a proper python installation. You
don't want all the confused users to come complaining on hugin-ptx not
understanding how they can install modules etc.

The python interface is deliberately designed to empower the user.
Anyone can pick one of the template plugins and come up with a
modified version ready to run in a few minutes. This is partly
intended and designed, and partly due to the fact that hugin's
developer community has, so far, not bothered about integrating the
plugins into hugin, so to make them behave differently, there is no
menu or mask or such, you can only 'run' them without parameters. I
hope eventually they will use wxpython to do some GUI, but so far I
feel it's best to leave them open to easy user modification.

GIMP and blender plugins are much more involved, so they are sort of a
closed shop, there is an installation mechanism from inside the
program, and writing them is for a few wizards and may take days. The
whole philosphy behind the hugin plugin interface is to make it as
accessible as possible. This is why there is a menu point 'run python
program' - it simply launches any old plugin from anywhere on the
systen which a user may have written. It's really quite simple. The
more formalized installation of select plugins which, then, appear in
the actions menu, is for well-tested plugins which are considered
worthy of being distributed with hugin.

> I was not able to
> reproduce your instant crash on Windows XP, 7, or 8 developer preview.

This may well be due to the W7 installation I used, which is in a
virtual machine. On XP, which is on a physical machine, I experienced
no crashes.

I do have a few complaints, though. While the new GUI is a matter of
taste, and it seemed to do it's job, The python interface in your
build is mediocre at best:

hsi can only be imported from the place where you have put it.
Normally, python modules go to a place in the python installation
where they live with all the other modules, and any python session on
the system can just import them by the simple statement 'import xyz'.
No joy here.

Running a python session from the command line in c:\Programme\hugin
\bin, I could import hsi, but help(hsi) threw an exception. The plugin
interface is only half of the show; the hsi python module enables any
python script which imports it to use most of hugin's backend
functionality - hugin isn't needed at all. This is another point that
sets it apart from, say, Gimp - I don't think you can import the gimp
into your python programs; there. it's only a plugin interface. Hsi is
both, this is why I often refer to it as hsi/hpi: hugin scripting
interface/hugin plugin interface. And python is the glue to make all
kinds of different modules cooperate. Several of my plugins run from
the command line as well, but all of thgis only really works if python
is installed properly.

Running the simple plugins from hugin did work. But as soon as I tried
to run one of those which require additional modules (which aren't in
your minimal install), the python interface returned -1 and became
stuck in that state, meaning that subsequently trying to run any of
the plugins which did run initially would now fail with the same
return code.

Much as I appreciate that you have finally put some effort into
including the python interface in a windows build, I think the current
state is doing it a disservice. Please consider making it mandatory to
have python installed for a python-enabled hugin to run. I think going
that way, you'll soon have it running nicely, and we can finally see
windows user using (and, hopefully, writing) plugins as well.

Kay

[Matthew Petroff]

I guess the best method would be to distribute two versions, one
without Python and one with Python. I'll look into extending the
installer to check for Python and allow the user to download and
install it if it is not already installed.

Now that you mentioned that you were using a virtual machine, I know
what caused the crash. Your virtual machine does not support the
OpenGL preview. Therefore, unless the interface is set to expert,
Hugin crashes since the new GUI uses the OpenGL preview in the main
interface.

-Matthew

[kfj]

On 4 Jun., 03:02, Matthew Petroff <matt...@mpetroff.net> wrote:

> I guess the best method would be to distribute two versions, one
> without Python and one with Python. I'll look into extending the
> installer to check for Python and allow the user to download and
> install it if it is not already installed.

I think this is the best solution. A regular Python install makes sure
that all python-related features will run smoothly and as expected by
python users. And since the python interface is admittedly taking up
quite a bit of space (particularly the _hsi module), this will limit
bandwith consumption - many users may be perfectly happy without the
plugins (while there are so few) and there's no point transmitting
megabytes of stuff to them they never use.

When installing hugin on a system with python, the python modules
should be placed in the appropriate place inside the python
installation, so they can be loaded from any python program running on
that system. For example with a Python 2.7 install on my Windows XP
system the path would be C:\Python27\Lib\site-packages. As far as I
know this is specified in cmake's install rules, so you may be able to
pick the correct destination from there. I'm not sure if the
construction of your installer is cmake-driven, so if it isn't you may
have to set these installation target locations manually.

Thomas made sure that the python-enabled version would run on windows,
so if you run into difficulties, he should be able to help you put it
all into place. He knows much better than I what to do on Windows, I'm
a Linux user. I only test on Windows because I've written the
interface and would like to see it used on other platforms as well.

> Now that you mentioned that you were using a virtual machine, I know
> what caused the crash. Your virtual machine does not support the
> OpenGL preview. Therefore, unless the interface is set to expert,
> Hugin crashes since the new GUI uses the OpenGL preview in the main
> interface.

So that's another mystery solved! I thought openGL was such an old
technology that my oracle virtual box machines with all guest
extensions would sure support it...

Mind you - initially there is a warning that the openGL preview cannot
be used. There, hugin could be gracefully terminated (or switch to
'panorama editing' mode) instead of crashing. But this is not your
responsibility.

With the old GUI I was able to still use hugin, I just couldn't use
the openGL preview, while the 'old' preview still worked correctly.

Kay