Renewing OSX Distribution (was Re: [ptx] Hugin 0.6 on OS X Crashing)

[David Haberthür]

On 09.08.2006, at 00:37, Ippei UKAI wrote:

> Can I try summarising a bit about the installation issues on OSX?
[snip]
>
> Autopano-sift
> More people feel autopano-sift optional compared to enblend, and I  
> think it can be rather dealt as a plugin rather than an integral  
> component. It also has stability issues with shell scripts. So it  
> should be dealt on a different thread.

I heavily rely on autopano-sift for creation of my panoramas (and  
thus cannot wait for hugin 0.6.1 :-) ). for me it produces good  
results which i can then refine really fast by hand.
i think because it requires mono there is no easy solution to the DnD- 
problem here.
or is there a possibility to warn/alert the enduser that "hugin"  
requires mono to fully work (with all the plugins) out of the box?

>
> Suggested change to hugin itself
>
> In the preference, the paths to enblend and autopano should be the  
> choice between "Search Default Locations" and "Specify custom  
> path". On Linux, "default search locatins" would be the bin search  
> paths, and on Mac, would be "Application Support" folders of user  
> and system levels, and inside the .app application bundle.

sounds good to me!

>
> Suggested Installation (HuginOSX and enblend)
>
> - Current
> HuginOSX: DnD
> enblend:  Either using AppleScript (that puts enblend into  
> HuginOSX.app), or manual placement with specifying path in preference
> - 1x DnD (The best if ok to put enblend inside HuginOSX)
> HuginOSX: DnD
> enblend: Inside HuginOSX.app (If the user wants to use enblend from  
> commandline, download the tools package)
> - 2x DnD (still better than current)
> HuginOSX: DnD
> enblend: DnD to Application Support folder by user
> - 1x Installer Pkg
> HuginOSX: Installer Pkg
> enblend: Installer Pkg

if there's a vote, i'd raise my hand for the 1x DND-version.
since i have absolutely no experience in licenses and programming i  
don't know if this is feasible..
if software comes with an installer package i always get a bit wary,  
because i don't know what it does in the end... the DnD assures me  
that the software doesn't write stuff to where i don't want it to...

> Suggested Distribution of command line tools
>
> - Current: as a directory, in the same download as HuginOSX+enblend
> - separate .tgz to download
> - .tgz in the same download as HuginOSX+enblend
> - Installer Pkg in the same download as HuginOSX+enblend

for the command line tools (which i don't use) i think the way it is  
as current is quite suitable. maybe a bit more explanation to it? but  
again, this is from a non programmer-side...

oh, and thank you guys for that wonderful piece of software. and  
thanks to ippei for the major work in "porting" it to OS X.
if i could program i'd help! but at the moment i can only share my  
views as an experienced end-user

habi




david haberthuer | rodtmattstr. 73 | ch-3014 bern | +41 76 330 17 96  
| +41 31 332 56 07 | habi.gna.ch