[ptx] Things to do before the next hugin release

[Pablo d'Angelo]

On Thu, 04 Nov 2004, Douglas Wilkins wrote:

> > - complete translations (probably need to find more translators)
> > - language selector (for the windows people, who can't do LANG=xx)
> 
> A unicode build would solve this problem. Currently, by setting the
> system locale, hugin will run in translated fashion on windows, but the
> process to set the locale is not obvious. see 
> wxWidgets is a non-unicode program, so I
> needed to set the system locale for that. See:
> 
> http://www.microsoft.com/globaldev/handson/user/xpintlsupp.mspx
> under
> Changing Language for non-Unicode Programs
> 
> for info for XP and
>  
> http://www.microsoft.com/globaldev/handson/user/2kintlsupp.mspx
> under
> Changing System Locale
> 
> for windows 2000 specific information. 

Looks like a hassle.. however, most people probably want to use windows in
the default language, so changing is not really a thing done everyday or?

What about the Win9X systems, I've recompiled wxWindows on win for unicode,
and it complained that libunicows was not found, and that unicode apps will
only work on WinNT based systems.

And the libunicows homepage says (it depends on MSLU from microsoft):
MSLU comes with licensing terms that are highly unfriendly to Open Source
applications: although you can freely distribute unicows.dll with your
application, your licensing terms must meet certain conditions that no Open
Source license can. Namely, you must forbid further redistribution and the
license must be an EULA accepted by the user either in writing or using
click-through or shrink-wrap mechanism.

I really like microsoft.

> > - maybe we should add one of these annoying "Tip of the day"
> >   windows with tips and tricks, people won't discover easily.
> 
> With an option to turn it off :-)

sure!

> > - maybe fix the layout issues on small screens, although I have no idea how
> >   this can be done with the current XRC.
> 
> Either:
> 1. Reduce the border etc. widths (leading to a "squashed" look)
> 2. Use a "tabbed" style inside of each current tab to reduce the
> required screen size.
> 3. Hide some of the functionality behind an "advanced" button
> 4. ?? No Idea :-)

Hmm, I tried the cheap solution of adding scrollbars to the widgets to big
for the screen, but that didn't work as advertised in the wxWindows
documentations.

ciao
  Pablo