headers
Bruno Postle | 1 May 2009 01:00
X-Face

Re: libpano13-2.9.14_beta2 released


On Fri 01-May-2009 at 00:25 +0200, Guido Kohlmeyer wrote:
>
> there is currently no negative feedback regarding my Albers 
> projection fix, thus please commit the attached file to the trunk.

Thanks, committed as svn963.

--

-- 
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 <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 0 comments |
headers
Andreas Metzler | 1 May 2009 09:28
X-Face

Re: libpano13-2.9.14_beta2 released


In gmane.comp.misc.ptx Bruno Postle <bruno <at> postle.net> wrote:
> A question:  libpano13-2.9.14_beta2 was released seven weeks ago and 
> there have been no bug reports, can I assume that this version is ok 
> for a 'stable' release?
[...]

Hello,

I think library versioning is broken due to ABI breakage (compared to
2.9.12) and therefore a soname bump is necessary:

filter.h: struct adjust_Prefs has new member int faststep
panorama.h struct TrformStr has new member int fastStep

The struct is part of the ABI and adding members changes its size,
afaik this breaks binary compatibilty.

cu and- this is a showstopper -reas
--

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

--~--~---------~--~----~------------~-------~--~----~
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 <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx-unsubscribe <at> googlegroups.com
(Continue reading)

Permalink | Reply | 0 comments |
headers
Andreas Metzler | 1 May 2009 10:22
X-Face

Re: libpano13-2.9.14_beta2 released


In gmane.comp.misc.ptx Andreas Metzler <ametzler <at> downhill.at.eu.org> wrote:
> In gmane.comp.misc.ptx Bruno Postle <bruno <at> postle.net> wrote:
>> A question:  libpano13-2.9.14_beta2 was released seven weeks ago and 
>> there have been no bug reports, can I assume that this version is ok 
>> for a 'stable' release?
[...]

> I think library versioning is broken due to ABI breakage (compared to
> 2.9.12) and therefore a soname bump is necessary:

> filter.h: struct adjust_Prefs has new member int faststep
> panorama.h struct TrformStr has new member int fastStep

> The struct is part of the ABI and adding members changes its size,
> afaik this breaks binary compatibilty.

> cu and- this is a showstopper -reas

Verified.

A hugin 0.7.0 binary built against libpano13 2.9.12 crashes
reproducibly just when using the [Optimze Now] button if it is running
against libpano13 2.9.14_beta2. (And a quick successful test
with a hugin 0.7.0 binary built against libpano13 2.9.14 shows that
just the ABI is broken, not the API.)

thanks, cu andreas

--~--~---------~--~----~------------~-------~--~----~
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bruno Postle | 1 May 2009 11:29
X-Face

Re: libpano13-2.9.14_beta2 released


On Fri 01-May-2009 at 09:28 +0200, Andreas Metzler wrote:
>
>I think library versioning is broken due to ABI breakage (compared to
>2.9.12) and therefore a soname bump is necessary:
>
>filter.h: struct adjust_Prefs has new member int faststep
>panorama.h struct TrformStr has new member int fastStep

Ok, it's been 0:0:0 since forever, are you saying it needs to be 1:0:0?

--

-- 
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 <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 0 comments |
headers
Andreas Metzler | 1 May 2009 12:22
X-Face

Re: libpano13-2.9.14_beta2 released


In gmane.comp.misc.ptx Bruno Postle <bruno <at> postle.net> wrote:
> On Fri 01-May-2009 at 09:28 +0200, Andreas Metzler wrote:

>>I think library versioning is broken due to ABI breakage (compared to
>>2.9.12) and therefore a soname bump is necessary:

>>filter.h: struct adjust_Prefs has new member int faststep
>>panorama.h struct TrformStr has new member int fastStep

> Ok, it's been 0:0:0 since forever, are you saying it needs to be 1:0:0?

Hello,

that would be in line with normal libtool versioning and should do
the trick on the platforms where you make use of it (Linux and Darwin
afaict.) The soname would change from libpano13.so.0 to libpano13.so.1.

I do not understand what (is supposed to) happens on other systems
(especially *BSD or Windows), or even why the -version-info option is
only used selectively, surely libtool should be smart enough to do the
right thing. ;-)

thanks, cu andreas
--

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

--~--~---------~--~----~------------~-------~--~----~
(Continue reading)

Permalink | Reply | 0 comments |
headers
J. Schneider | 1 May 2009 13:26
Picon
Picon

German translation: a few questions about original strings


Hi,
I can take care of this. Although some of Guido's translations were a 
lot better; I think he did a very good job at "harmonizing" the 
expressions.
As I am currently having time (or procrastinating on other things by 
translating ...) I think I'll do what I can and if somebody else is 
going to review what I am not content with (I'll leave those strings 
marked as fuzzy) this will improve things.

Some remarks and questions:

1.
In the English original there should be corrected:
- "Specify output prefix" should have ": " appended for not having the
   output path following without a whitespace character.
- "Cannot open app in Hugin." Bruno once answered my question about the
   meaning of this string: 'It should say "Cannot open project in
   Hugin."' (Btw: When does this happen? When a file is corrupted?)

2.
On the camera and lens tab there is a "Reset..." button (which should 
read "Reset ..." I believe) and in the following dialogue there is a 
string "Lens parameters" that is translated in the PO file but still 
displayed in English.

3.
There is one string that I had a question about some time ago and I 
forgot about this loose end:
>> >"<project1 <output prefix>> <project2 <output prefix>> <project3"
(Continue reading)

Permalink | Reply | 8 comments |
headers
J. Schneider | 1 May 2009 15:26
Picon
Picon

adapting the GUI for different workflows


Hi all,

I believe I remember when 0.7 was being worked on it was supposed to be 
a features release and 0.8 was supposed to be a UI release. Therefore 
some ideas were postponed that were UI improvements.
During the discussion someone came up with an idea (that was derived 
from some other application) on how to adapt hugin's GUI to different 
workflows - unfortunately I can't find the email any more, so I don't 
know to whom the credit goes.

Every once a while someone asks for changes to the UI to fit special 
needs such as linear panoramas. Or optimizing the UI for certain kind of 
input (fisheye, stacks, ...) or output (stacks, hdr, blended, ...).

Now I have come up with a sketch of how I understood the aforementioned 
idea. It is only a rough  pencil sketch, but I think it conveys the 
basic idea:
- The workflow is represented as a flow diagram
- Any action, any command, any option is represented by a box
- Actions are assembled via drag and drop
- Bifurcations allow to produce different types of output from
   one set of input images. They would probably have to be exe-
   cuted successively, particularly if they contain user inter-
   action.
- even incomplete workflows can be saved and used as modules in other
   workflows. (button "insert saved here")

The sketch can be found here:
http://www.joachimschneider.info/hugin_workflow_assembly.gif
(Continue reading)

Permalink | Reply | 2 comments |
headers
James Legg | 1 May 2009 16:57
Picon

Re: adapting the GUI for different workflows


On Fri, 2009-05-01 at 15:26 +0200, J. Schneider wrote:
> Hi all,
> 
> I believe I remember when 0.7 was being worked on it was supposed to be 
> a features release and 0.8 was supposed to be a UI release. Therefore 
> some ideas were postponed that were UI improvements.
> During the discussion someone came up with an idea (that was derived 
> from some other application) on how to adapt hugin's GUI to different 
> workflows - unfortunately I can't find the email any more, so I don't 
> know to whom the credit goes.
> 
> Every once a while someone asks for changes to the UI to fit special 
> needs such as linear panoramas. Or optimizing the UI for certain kind of 
> input (fisheye, stacks, ...) or output (stacks, hdr, blended, ...).

The idea of my Summer of Code project is to allow the user to specify
their needs, and then get the optimal UI and settings; so this is fairly
interesting to me at the moment.

> Now I have come up with a sketch of how I understood the aforementioned 
> idea. It is only a rough  pencil sketch, but I think it conveys the 
> basic idea:
> - The workflow is represented as a flow diagram
> - Any action, any command, any option is represented by a box
> - Actions are assembled via drag and drop
> - Bifurcations allow to produce different types of output from
>    one set of input images. They would probably have to be exe-
>    cuted successively, particularly if they contain user inter-
>    action.
(Continue reading)

Permalink | Reply | 1 comment |
headers
cri | 1 May 2009 19:49
Picon

Hugin on Ubuntu Jaunty


I've just successfully finished compiling Hugin (3814) on Ubuntu
Jaunty following the guide on the wiki.
I don't know if anyone already tried this, but I wanted to post here
to confirm that the wiki guide works also on Ubuntu 9.04 although it
is not written on the page.
--~--~---------~--~----~------------~-------~--~----~
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 <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 10 comments |
headers
Guido Kohlmeyer | 1 May 2009 19:51
Picon

Re: German translation: a few questions about original strings


Dear Joachim,

J. Schneider schrieb:
> Hi,
> I can take care of this. Although some of Guido's translations were a 
> lot better; I think he did a very good job at "harmonizing" the 
> expressions.
> As I am currently having time (or procrastinating on other things by 
> translating ...) I think I'll do what I can and if somebody else is 
> going to review what I am not content with (I'll leave those strings 
> marked as fuzzy) this will improve things.

Let me know if you finished with rough translations. I would like to 
review them afterwards to avoid double work done by you and me.

> 2.
> On the camera and lens tab there is a "Reset..." button (which should 
> read "Reset ..." I believe) and in the following dialogue there is a 
> string "Lens parameters" that is translated in the PO file but still 
> displayed in English.

The tripple points are commonly used to note about a following dialog 
and no direct action. I used the notation without space so far.

> 6.
> Among the untranslated strings there are mostly projection names. For 
> these I am not quite sure about the translations. I believe we should 
> stick to keeping the English expressions in brackets behind the 
> translations because in conversations (e.g. on the net) even German
(Continue reading)

Permalink | Reply | 1 comment |

Gmane